• Cat Herder:Jessica Lyon
• Manager:Miro Collas
• HR Manager (FSG Helpers):Dorrie Bellman
• Land Manager:Flossy Andrew
• Assistant Managers:Coral Sharpshire, Kio Feila
• RolePlay and Scifi Portal manager:Teresa Firelight

• Abinathra
• akafox
• Alexegram
• Angela Kwak (Dutch)
• ChuckPC
• Fayleen Bellios
• FrankASinatra
• ImaLuckygirl
• Jolie Serendipity
• Kitty Beery (Dutch)
• LegitBonzai (Dutch)
• Liliana Darwinian (Portuguese)
• MacMaccee (German)
• maiyasaeria
• MarcSeven Lubitsch
• meady212
• PassionateAviator
• Pim Peccable
• Sparkle Weatherwax
• Tracy Argus
• Webbi Jonson

• 0079Galadriel
• briannainchains
• Hilary Querrien
• MarcSeven Lubitsch
• nuttidoxieg4 merryman
• panterapolnocy
• Starwolff2000
• Varahi Lusch

• Education:Alexegram, Dorrie Bellman, ImaLuckygirl
• Avatar Education:Kio Feila, Tracy Argus
• Small Events Planner:Jolie Serendipity
• FS Tour Guide:Fayleen Bellios

Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example, go to the top menu, Advanced → Debug Settings (press Ctrl-Alt-D to enable Advanced, if it isn't):

• RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
• TextureLoadFullRes should never be enabled (in other words, it should be set to FALSE).

If you are advised to raise LOD above 4, please disregard that advice.

Similarly, there is a notecard going round which suggests settings to prevent graphics crashes. Sadly, those settings can often result in perfectly ordinary content refusing to render. So if you have changed debug settings per such a notecard, revert them.

For both the cases above, should you not remember what settings you changed, then proceed as follows:

1. Back up your settings as explained here.
2. Then wipe settings by following the instructions on this page.
3. Log back in and see if this fixes your problem. If it does, you can try a restore and see if the issue returns.
4. If the problem does return, wipe settings again and set them from scratch.

If you are getting the error in the title, then please refer to this page, this page or this page for those using Intel graphics for possible solutions.

With thanks to Skua Sarrasine for having found the first of these.

Symptom:“This is a bug thats only experienced with Firestorm running. Basically, at seemingly random, but very infrequent times, my dual screens will bug out, producing two displays of solid colour, randomly. Sometimes Windows will return saying it recovered from an error code 7 or 3.”

Some research turned up this for error code 7; it suggests setting physX to CPU. And that seems to have solved the issue.

Note also the (apparent) interaction with Chrome.

This is a known issue with Windows 7, 8.1, and 10 with a 64-bit operating system; it affects other programs in addition to Second Life viewers.

Please try the following - but NOT while logged in.

• Go to the Start button
• Type services.msc and then press enter.
• Wait until the services window pops up.
• You may have to expand the window a bit to see the services.
• Look for DesktopWindowManager.
  • If it is running, right click it and select Stop. Wait until it stops.
  • You will probably see your desktop transparency window borders go flat. No worries.
• Right click again and select Properties.
  • In the Startup type, select Manual. Click OK.

• Open the Task Manager, by one of the following methods…
  1. Right click the task bar and choose Task Manager.
  2. Click the Start button and type Task Manager, then click on the result.
  3. Press Ctrl+Alt+Del and choose Task Manager from the list.
  4. Press Ctrl+Shift+Esc.
• Click More Details link at the bottom if needed
• Look at the several column headers, they will show a percentage of use. Memory or Disk may show a high percentage when Firestorm is not responding.
• Click on one of the high-percentage column headers to sort the processes. The top one is likely the cause. If it's your antivirus, make sure you have whitelisted Firestorm and its cache (refer to this page for whitelisting guidance).

If you find the Firestorm seems to freeze up every so often, then try these things, one at a time, testing after each one:

• Viewer freezes while “Loading world…“– If you have Intel HD 620 or Intel HD 630, and Windows 10 – This is an Intel driver issue. The fix is to roll back to driver 24.20.100.6025. Download Legacy Intel® Graphics Driver for Windows® 10 Version: 24.20.100.6025 (Ref. BUG-225655.)
• If you have chat saving enabled, and have a large number of chat transcript files, these could be causing the freezes. (Ref. FIRE-11322.) Try moving your chat transcripts elsewhere and see if the freezing stops.
  You can find your chat transcripts by going to Preferences→ Network & Files -> Directories→ Conversation logs and transcripts location; click the Open button.
• Set Preferences → Network & Files → Directories → Cache Size to maximum (9984MB or the maximum space available, whichever is less)
• Ensure that your antivirus software is not scanning the viewer cache folder. See Whitelisting the Viewer in Anti Virus Software for more information.
• If you have ever enabled “Full Res Textures”, disable this setting. Top menu bar, Developer→ Rendering → Full Res Textures (dangerous). Ensure that this is NOT checked. (Ctrl-Alt-Q to enable Developer, if it isn't.)
• Advanced → Debug Settings → Set FastCacheFetchEnabled to FALSE - then relog.
  Ctrl-Alt-D to enable Advanced, if it isn't.
• Preferences → Graphics → Hardware Settings → Viewer Texture Memory Buffer - raise this as high as it will go. Then relog. (64-bit version only)
• Mac with Bitdefender: Refer to this SL bug report for a possible explanation: mac freezes if tabbing away after teleport since macOS Mojave 10.14.3
• Tip from a user: Windows users: If you're running CrashPlan, open the “Advanced” section of “Backup” settings and uncheck “Back up open files.”
• Tip from a user: Windows users: If you have “Magic Control Technology Display Utility” (MCTDUtil.exe), disable it. See https://www.file.net/process/mctdutil.exe.html.
• Tip from a user: Linux users: Turn off compositing, see if it helps.
• Freezes when another avatar enters/leaves region:
  • One version of this is an old bug, mostly gone now, that was sometimes solved by a region restart. We don't know if that will still help the problem, but you could try it.

For additional suggestions, see the page on Severe Lag.

PLEASE NOTE: Scripted attachments being broken is NOT a viewer issue. We are providing this page of tips as a courtesy to our users. If none of this works, please contact LL, or the maker of the item, for assistance with your broken attachments.

Possible reasons why HUDs or other scripted attachments may stop working:

• Disconnected during a teleport after restarting a region. See BUG-5034.

• Script (running) state is lost when logged out during forced teleport. See BUG-41379.

• There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.

Note: While this issue most commonly affects HUDs, it can also affect any and all other scripted attachments you were wearing when the breakage happened.

There are a few things you can try to get the items working again.

First of all:

• If you have RLV enabled, disable it (Preferences → Firestorm → Extras, top option), relog, then try again.
• Make sure you don't have other HUDs overlapping the one that's not working.
• Go to Top Menu → Avatar → Avatar Health → Refresh Attachments. See if that fixes the items.
• Relog then test the items again. That may be enough. If not, read on.

Things to try:

• Check for location issues:
  • Make sure you are in a region that has scripts enabled.
  • Go to other regions and test the items there. This will rule out technical problems with the original region.

Stay in a script-enabled region to do all of the following. You do not have to do the following steps in this order, but the simplest and less drastic steps are listed first:

• Attempt to get scripts running:
  • Try removing and reattaching the items.
  • If the items are modifiable, try resetting them or setting their scripts to running: Inventory, right-click the item → Edit, and while it is in Edit, go to Build menu → Scripts → Reset Scripts, or Build menu → Scripts→ Set Scripts to Running).

• Double check for interference:
  • Look in Inventory > Current Outfit folder, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached. (Temp HUDs have been known to freeze other HUDs on the same attachment point.)
  • Check that HUDs are not overlapping each other on the screen (and so preventing you from clicking).

• Check for issues with attachment points:
  • If any HUDs are sharing the same HUD attachment point, try moving them to separate HUD attachment points:
    Inventory → Right-click → Detach from Yourself, then Inventory → Right-click → Attach to HUD, and choose an unused point.
  • Even if they are not sharing attachment points, try moving them to different attachment points.

• Test basic functionality. To make sure that HUDs work for you at all, and work in your present location, do this:
  1. Rez a fresh cube
  2. Add the default script to it
  3. Take it into inventory
  4. Attach it to an empty HUD point
  5. Touch the HUD and see if there is script output in Local chat.
  6. If this doesn't work, then the problem is not with specific broken HUDs, but perhaps with your region, or some other unknown problem keeping you from running scripts.

• Identify broken items:
  • Try removing all the HUDs and other attachments and testing them one at a time: test each one, then remove it, then test another.
  • If you have original copies of the items, try detaching the ones you are currently wearing and using a fresh copy from the original.
  • If an item is no-mod and you can't get it to start running again, and you don't have another copy, you will need to request a new copy from the creator.
  • Note: If the non-working HUDs are for your mesh body parts (or other scripted attachments), you probably will need to use fresh copies of the original HUDS and the body parts – every part, from scratch (not copies of the broken ones you were wearing).

So you find yourself suddenly missing a window, perhaps inventory, or chat, or the edit window… How to find it?

A) First try these steps to see if you can find it hiding:

• Close all other windows, to make sure it isn't hiding under one of them.

• Hide the chat bar: Preferences→ Chat -> Typing→ Autohide main chatbar, and see if the window is under there.

• Compress all the buttons on the bottom toolbar to the right.
  Alternately, drag the toolbar buttons from their present location onto another toolbar;
  (Reminder: there are three available toolbars: bottom of the screen, right side, and left side. Buttons are dragged by left clicking, holding the left mouse button down, and dragging.)

• Go to Preferences→ User Interface → 2D Overlay, and lower the UI Scaling slider. The default setting is 1.0. You may find that setting it lower, temporarily, will reveal the missing window. If you find the missing window, move it to the center of the screen, then reset UI Scaling to 1.0 or your preferred value.

B) If those steps don't work, the window is probably far offscreen. Reset the window's position via Debug Settings. To do this,

1. Try to ensure that the missing window is closed. (You many be able to tell this if you are using a toolbar button and it is highlighted or not.) If you can't tell, proceed anyway.
2. Then open the Advanced menu (press Ctrl-Alt-D to enable Advanced, if it isn't already), and go to Show Debug Settings.
3. Consult the table below for the names of the two settings that match your missing window.
4. Find the first setting in the Debug Settings window; set it to 0 (zero).
5. Repeat for the second setting.
6. Relog before re-opening the window.

These are the debug values to use for step B (just above). Find the window you need in the left hand column and get the debug values from the other two columns.

C) If you already have created a backup of your settings, then try a restore of those settings as explained here.

D) Should none of these work, then you will have to wipe settings, as explained on this page.

There is an alternative to clicking a link in a browser to have it pass control to the viewer. Some actually find this work around to be faster and use it normally:

• right click the SLURL link in your web browser and copy to clipboard
• in the viewer, paste the link into your local chat and hit Enter.
• open local chat history
• click the link shown there; you will be shown the location info with the option to teleport direct to it.

Note: this is the opposite of the problem at the top of the page.

The first thing to check is the viewer settings: Preferences → Network & Files → Connections, in the Web Browser section, make sure Use the default system browser… is selected.

If you get an error saying that no program is associated with the action, or that it doesn't know how to hand that action, make sure your computer settings show that there is a default web browser. An easy way to tell is to open your browser; if you are asked to make it the default, then you need to do so.

These classes are based on our official Firestorm release and are conducted in text except when otherwise noted. There's no need to talk, but you may want to be able to hear. We also usually have help available to answer questions in text. This schedule is subject to change.

Note that it is best if you are on Firestorm for the classes.

Locations are indicated in the far right column as follows:

• FS: Firestorm Support region classroom, * Firestorm Classroom

Class times and days change regularly. Classes may be held any day of the week, with start times from 8 am to 7 pm SLT. Nonetheless, if the class times are still inconvenient you may prefer to watch recorded versions of some of these classes on YouTube.

Unscheduled classes may also be held on an impromptu basis. If this happens, a notice will be sent in Firestorm Support English. secondlife:///app/group/3a1be8d4-01f3-bc1a-2703-442f0cc8f2dd/about

*All times SLT*

This window is accessed via Preferences→ Move & View -> Movement→ Joystick Configuration (button).

“Joystick” refers to compatible USB input devices, which can be used to control Second Life in exciting ways for exploration, moviemaking, and more. Examples are the 3Dconnexion SpaceNavigator, other joysticks, gamepads, and so on.

Assuming you have a 3D movement device installed and configured, Joystick Flycam mode is enabled by pressing Alft-Shift-F. This moves your camera, rather than your avatar.

This window is fairly technical, although the default settings generally work well with no or minimal changes. For details, see this SL Wiki page.

One user, Xente Aeon, makes the following recommendations for the SpaceNavigator (in this JIRA):

• In the preferences of the SpaceNavigator, apply “reverse” on the button called “zoom” that actually controls the movement up and down.
• In the Joystick preferences, change some, like this:
  • X Axis Mapping: 0
  • Y Axis Mapping: 1
  • Z Axis Mapping: 2
  • Pitch Mapping: 3
  • Yaw Mapping: 4
  • Roll Mapping: 0
  • Zoom Mapping: -1
• Leave unchecked: Direct 3D Zoom and Cursor, but check “Auto Level”

Refer to this page in the SL wiki for other info, including known issues.

One user, Kentdavis Edman, makes the following recommendations for the Steelseries 3GC Controller:

See the official SLLogitech Gamepad page.

Linux users do not need a 3dconnexion driver in order for the device to work in Firestorm. In fact, if you have a driver installed, it will conflict with the built-in support for the 3dconnexion device. So if you do not need the 3dconnexion device for anything else, uninstall the driver.

Alternately,you can stop it before running Firestorm. If you are using the free spacenavd driver, you can stop it by giving the following command in terminal:

sudo /etc/init.d/spacenavd stop

Latest drivers for current products 3dConnexion Drivers
Archived Drivers and Software 3dConnexion Archived Drivers

Note: Some have reported that uninstalling their drivers makes it possible to use Space Navigator with Firestorm. See the comments at the end of Huck’s guide to making machinima in Second Life part three: camera movement.

This is a collection of error messages seen in SL. Some are system messages; some are viewer-generated. The list is by no means complete.

If you get an error message that is not on this page, please:

• Report it in Firestorm Support English (in-world support group)
• Or File a Jira alerting us to it (please provide the complete, exact wording of the message; a screenshot is also helpful).
• If you found a solution or explanation, please let us know that too.

Thanks!

Please note that Marketplace has nothing to do with the viewer. These messages are noted simply for convenience.

Notes:
(1) Tested using Debian 8 (Jesse) and Ubuntu 18.04. Some success has also been seen with Arch.
Some additional libraries are required; see this page for more information.
(2) GPU technical specifications for equivalence.

NOTE: A clean install is not usually needed when updating to a new Firestorm version. For normal updates, see How to Update Firestorm.

If you are having problems with the viewer, you may need to clean install. The following explains how to do a proper clean install - which is more than simply removing the viewer and reinstalling it.

For the current release, go to the Downloads page.
For any previous supported version, go to the Older Downloads page.

If you save chat transcripts, they are by default saved in your per-account settings folder (named for your avatar). Before you delete that folder (below), you will need to identify the chat files and move them. See here for steps to relocate your chat transcripts. This only needs to be done once if you then backup your settings. But you must log in on each account (i.e., alts) to save that account's chat files.

As a just-in-case measure for any situation, and to make upgrading or downgrading your viewer much easier, make a backup of your settings. It's a good idea to make a backup right before upgrading, downgrading or otherwise wiping settings so that the backup is current (teleport history, contact sets, etc. can change dynamically). You must log in on each account (i.e., alts) in order to back up that account's settings.

REMINDER: If you want to save chat transcripts and or settings, make sure you do Steps 1 and 2 before deleting your settings.

Firestorm settings can become corrupt, particularly if you recently crashed; the files may not save completely, so important information can become “scrambled”. And when installing a different version of the viewer, using settings from the previously installed version may cause undesirable behavior in the viewer.

Here is how to remove the old settings:

• Launch the viewer but do not log in.
• Click the Viewer menu at the top, choose Preferences, then Network & Files, then Directories.
• Click the Open Settings Folder button.
• Close the viewer.
• In the file window, navigate up one folder, to the Firestorm* folder. If you see a folder called user_settings and one or more named for your avatars, you're in the right place.
• Select everything in that Firestorm folder and delete it.

*Note that the Firestorm folder name may differ slightly.

Note also that if you have both a 32-bit and 64-bit version installed, you will only be deleting settings for the version that you launched at the beginning of this step. You would have to repeat this step if you want to delete settings for the other version that's still installed.

You will need to use a file manager (like Windows Explorer for Windows system, Dolphin, the Mac Finder, or some such) to locate the settings folder. In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Refer to this page to locate your settings folders.

Clearing cache should only be done when there is a problem with the cache, or when there is a significant change in the viewer that requires it (such as a change to the KDU render code). The viewer will automatically clear cache in such cases, but manual clearing may be quicker.

When downgrading, you should always clear the cache.

If you have to clear cache in order to use the viewer version you are about to install, please see this page.

Having done all those steps, you may now install Firestorm. Installing Firestorm is done in pretty much the same way as any other application on your computer.

Go to Adobe Flash Player, select your operating system, then select the appropriate flash player.

Once you have the viewer installed or reinstalled, you will want to make sure the viewer is operating correctly:

• Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Don't change any settings.
• Test any functions that didn't work for you in the previous version that had been reported fixed.
• If downgrading, test any functions that failed in the newer version.
• If you needed to clear cache in Step 5 above, open your Inventory and wait for it to fully populate.

At this point, if the viewer is performing as it should, you can restore your settings and again relog. You must log in on each account (i.e., alts) to restore that account's settings.

Log back in to SL once again and confirm that the viewer is still performing as it should; then you can adjust any new or changed settings and then back those up.

Note that some settings are not restored, such as graphics. This is because the graphics settings could be incorrect and may cause problems.

Choose your Linux distribution for specific applicable steps. If your distribution is not listed, choose one that is closest, adapt as needed and, optionally, submit your adaptation to us for inclusion

• Ubuntu 18.04
• Ubuntu 17.04
• Ubuntu 17.10
• Ubuntu 16.04 / LinuxMint 18
• Ubuntu 14.04 / LinuxMint 17
• openSUSE 13.1/13.2
• Gentoo

Before continuing it is recommended that you Backup Settings. You may skip this step if you choose, however, if there is a problem during or after the update and you do not have a Back-Up then you could lose any changes you have made to your settings.

Updating your viewer need not be a daunting task. The Method explained below is for a straightforward Update. DO NOT follow this method if you are reverting to an earlier version.

For the current release, go to the Downloads page.

If you want to install a previous release, we recommend you use the steps in Clean Install

Having done all those steps, you may now install Firestorm. Installing Firestorm is done in pretty much the same way as any other application on your computer.

Go to Adobe Flash Player, select your operating system, then select the appropriate flash player.

Assuming you cannot log in on your viewer because it is blocked, this page will guide you through the old manual process.

By default, viewers store chat transcripts in the same directory as it does settings and configuration files (Contact Sets, teleport history, etc.). This wiki will help you change where your transcripts are stored and offer some management tips to help minimize the lag caused by keeping transcripts.

For this process, we will use the Desktop. This is not intended as a permanent location, but could be if you so desire.

• Open your file explorer, navigate to your Desktop directory and create a directory in there named FS-Chat or something similar. In there, create a subfolder for each of your avatar accounts.

• Navigate to the folder that stores the application data for the viewer - if you do not see this folder, you may need to show hidden folders.

• In the file explorer, you should see several directories, one named for your avatar. That's your per-account settings. Open that directory

• Your chat files are plain text files (.txt if your explorer displays extensions), they're named either chat for Nearby Chat, or named for each avatar's or group's chat you've seen. Select all those chat files and press Ctrl-X (Mac: Cmd-X) to “cut” them.

• Navigate back to your new chat logs location, which you selected above. Click into the correct account folder and press Ctrl-V (Mac: Cmd-V) to move all your chat files in.

Repeat this for for each avatar for which chat transcripts will be saved.

You can't really back up settings manually. But you can preserve most of them.

• Navigate to the folder that stores the application data for the viewer - if you do not see this folder, you may need to show hidden folders.

• In the file explorer, you should see several directories, one named for your avatar. That's your per-account settings. Open that directory

• Locate the file called settings_per_account.xml and delete it. If you desire, you can move this to a different place and open it with a text editor if you want to manually restore any of the settings (autoresponses, for example). Repeat this for all of your avatar directories.

• Navigate back and then into the user_settings directory

• Locate the file called settings.xml and delete it. If you desire, you can move this to a different place and open it with a text editor if you want to manually restore any of the global settings.

Since your current version of Firestorm is blocked, there is also a good chance that the cache-related functions have changed enough that clearing cache is advised. Normally, clearing cache should only be done when there is a problem with the cache, or when there is a significant change in the viewer that requires it. Refer to this page.

Ideally, use the Programs & Features Control Panel [Vista, Win7, Win8, Win10], or Add/Remove Programs Control Panel [XP] to remove the Firestorm application. If you have a Firestorm folder in your Start Menu, there may be an Uninstall link there (32-bit Firestorm only).

Navigate to Applications and trash the Firestorm App.

The Firestorm install directory will be wherever you extracted the download archive. Typically this will be in your home directory somewhere, such as ~/Phoenix-Firestorm_*. Delete this directory and everything inside it.

If you used the install script as root, look in your /opt directory. You will need to su root or sudo rm to delete the firestorm directory there.

Having done all those steps, you may now install Firestorm. Installing Firestorm is done in pretty much the same way as any other application on your computer.

Get the installer: For the current release, go to the Downloads page.
For any previous supported version, go to the Older Downloads page.

Run the downloaded installer. The 32-bit installer will offer you the chance to change the destination directory; the 64-bit installer shows the destination when you click the Options button.
The installer will create a shortcut icon on the desktop.

Note: Choose No if you are prompted to start the viewer.¹⁾

Find the .dmg file you just downloaded and double-click it to mount it. Then drag the Firestorm app icon into your Applications folder. More detailed instructions can be found here

Extract the downloaded tar.bz2 or tar.xz into any directory and run the firestorm script inside that directory to launch it. You can optionally install by running the install script inside that directory. And you can optionally create a desktop launcher. Refer to the README files for more information.
If installing the 32-bit version of Firestom on a 64-bit version of linux, refer to this page for guidance on required compatibility libraries.
Some Ubuntu users may need to modify how Nautilus handles scripts.

Once you have the viewer installed or reinstalled, you will want to make sure the viewer is operating correctly:

• Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Don't change any settings.
• Test any functions that didn't work for you in the previous version that had been reported fixed.
• Open your Inventory and wait for it to fully populate.

At this point, if the viewer is performing as it should, and you have a backup of your settings, you can then restore them.

If you do not have a backup set, you can begin re-doing your settings manually. Once that's done, you should relog and confirm that the changes are still there, then backup your settings and again relog.

Log back in to SL once again and confirm that the viewer is still performing as it should; then you can adjust any new or changed settings and then back those up.

Note that some settings are not restored, such as graphics. This is because the graphics settings could be incorrect and may cause problems.

If you did step 1 and moved your chat files, you can reverse that process to move them back, or you can set Firestorm to always use that location. Refer to this page for more details about managing chat files.

This section covers issues related to audio, video and some aspects of search.

• For situations where you cannot hear audio, be it streaming music, or the audio from a movie/video, the first thing to do is check that:
  • May 2018: If you had a recent Windows update, see this page.
  • streaming music and/or media are enabled in Preferences→ Sound & Media -> Sounds;
  • volumes for music and media are not at minimum;
  • audio is configured correctly in your operating system (ie, Windows, linux, OSX), that sound is going to the correct device (i.e., speakers or headset), and so on (this may require you to adjust settings in your sound mixer or other similar software);
  • You have not blocked the stream/video; check Preferences → Sound & Media → Media → Manage Media Sites.
  • for streaming music, test the music URL in your external web browser, to make sure that the URL actually works.

• If you have plugged in a USB sound device, you may need to relog so that the viewer can use it.
• HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

• Relog Firestorm and open the Search window
• Go to your computer processes and look for “slplugin.exe”
  • For Windows users, go to Task Manager → Processes Tab
  • For Mac users, go to Activity Monitor → My Processes (usually by default, but you can check top right drop down)
  • For Linux users, go to Command Terminal, and type “ps aux”
  • You may see four instances of the slplugin running (that is normal behavior)
  • If you do not see any instances of slplugin running, that is the cause of media failing
• If slplugin is not running, disable all firewall and virus protection (including anti-virus software and windows or other operating system firewalls). Do this check also for llceflib_host.
• Relog and attempt video playback again
• If it works, you will need to stop your firewall/virus protection from blocking the slplugin and/or llceflib_host files by granting appropriate permissions in your firewall/virus protection software
• NOTE: If you have several viewers installed, you will have to allow to each one access through your firewall, as well as to SLPlugin and llceflib_host for each one.
• If all of the above does not resolve the issue, you can try downloading the latest SL Viewer 2 viewer and replacing your Firestorm slplugin file with the one from Viewer 2.

• In Preferences → Sound & Media → Sounds, make sure the “Enabled” checkbox to the right of the “Media” slider is checked
  (For audio, check “Streaming Music”)
• In Preferences → Sound & Media → Media, check “Allow inworld scripts to play media”
• In Preferences → Network & Files -> Connection, make sure the Maximum Number of Web Browser Windows dropdown is set to Five, Ten or Unlimited
• Make sure the issue is not with the specific television you are using, by attempting to view videos on a television that plays video normally for other Firestorm users.
• Make sure that “Enable plugins” is ticked in Preferences → Network & Files -> Connection, else the external media plugin can not be executed, and you may see a message saying: Adobe Flash Player or an HTML5 supported browser is required for video playback.

• Windows users:
  • In order to play Flash format videos (e.g., YouTube videos), you must have the Opera & Chromium version of the Adobe Flash plugin installed. Unless you already have this specific version of Flash installed already, you will need to get the Opera & Chromium Flash plugin from Adobe.

• Linux users
  • You need to have the pepperflash plugin installed, which can be satisfied by installing pepperflashplugin-nonfree for Chromium

• Mac users
  • Mac users currently need the Safari & Firefox version of Adobe Flash plugin installed. Download it from Adobe.

• All users: Test your Flash
  • To make sure you have successfully installed the correct version of Flash and that it is working, use the in-world Flash game to test it.
    • Open the Developer menu: CTRL-Alt-Q. (Close this after testing; it's best not to leave this menu open.)
    • Then type CTRL-SHIFT-Z to open the internal browser.
    • Once the browser loads, click the Home icon in the upper left of the browser window.
    • Click “Flash game” (3rd column, 4th row).
    • A bubble-shooter game should load.

• NOTE: If you experience graphics driver crashes on nVidia cards when viewing Flash media (for example Youtube) both in-world and on a website and/or severe drops in your GPU clock mhz on any card then you will need to disable hardware acceleration on Flash Player. To do this, go to Youtube and Pick any video. Right click the video play area to bring up the options and follow the instructions here.

QuickTime is no longer needed for Windows users (and never was for linux users). Mac users, however, still need to have it.

• If YouTube videos suddenly will not play, and you just get a white screen, go to Preferences→ Privacy -> General, and click on Clear History, then try again.
• See also the Flash section, above.

Go to Preferences→ Sound & Media -> Sounds and make sure the volume sliders for streaming music and media are not all to the left and that there is no mute symbol (red no entry sign) on the speaker icon next to those. Make sure the Master Volume is not all to the left.

Check that Sound Source rolloff distance (Media tab) is correct; set back to default, if you changed it (5m and 30 respectively for min and max).

Go to Preferences→ Sound & Media -> Sounds and check that you have the Sounds and UI sliders up high enough and that there is no mute symbol (red no entry sign) on the speaker icon next to those.

Go to the top menu bar→ Advanced → Use Plugin Read Thread, and disable it, if it is enabled - or vice versa. (If you cannot see Advanced on the top menu, press Ctrl-Alt-D.)

If that doesn't help, first ensure that you have your bandwidth set correctly. Also, test the audio stream in your regular media player, and/or try a different audio stream in-world.

If the music volume fades as you cam around or edit objects, check the sound equalization settings in your operating system. For example, this may be caused by “Loudness equalization” being enabled in your speaker properties on Windows 7. (Refer to http://jira.phoenixviewer.com/browse/FIRE-19885.)

This error is due to Flash not being installed, or not installed correctly. See above.

Maintenance, Premium - Assorted crash fixes, improvements and new features from LL.

Catznip RLVa 2.2 Release Notes

Release Notes for v6.3.8. (538264) - Second Life Viewer Released on Thursday, March 12, 2020.
https://releasenotes.secondlife.com/viewer/6.3.8.538264.html

Premium Enhancements

Benefits information is now provided at login, for the current user and for all publicly available benefits packages. This viewer bases all UI and other logic on these values, replacing an assortment of values previously received via other mechanisms or hardcoded into the viewer.

This viewer also has some UI improvements.

Release Notes for v6.3.7. (535996) - Second Life Viewer Released on Friday, February 7, 2020.
https://releasenotes.secondlife.com/viewer/6.3.7.535996.html

Maintenance: Yorsh

Yorsh (Also known as Mora Grogg) (Russian: Ёрш which means “Ruffe”) is a Russian mixed drink consisting of beer thoroughly mixed with an ample quantity of vodka. It is traditionally drunk in a social setting, typically with a toast followed by downing a full glass of it at one go.

Vodka is a neutral spirit which does not greatly alter the flavor of the beer, but does greatly increase its alcohol content.

Probably the first evidence of presence of such a mix in Russian drinking culture is the Tale of Woe and Misfortune, an anonymous 17th century-poem. The early version of yorsh described there included mead, however.

Release Notes for v6.3.6. (535003) - Second Life Viewer Released on Tuesday, January 28, 2020.
https://releasenotes.secondlife.com/viewer/6.3.6.535003.html

Maintenance: Xanté

Xanté (“Xanté Poire au Cognac”) is a pear liqueur based on cognac, produced by The Xanté Company. It has 38% ABV. Xanté is pronounced santé, just as if the x were an s, which is the French expression for “cheers!”.

Release Notes for v6.3.5. (533275) - Second Life Viewer Released on Wednesday, December 4, 2019.
https://releasenotes.secondlife.com/viewer/6.3.5.533275.html

Maintenance: Wassail This Viewer uses Viewer Manager 2.0.531000

Wassail is a beverage of hot mulled cider, drunk traditionally as an integral part of wassailing, a Medieval Christmastide English drinking ritual intended to ensure a good cider apple harvest the following year.

Release Notes for v6.3.4. (532299) - Second Life Viewer Released on Monday, November 4, 2019.
https://releasenotes.secondlife.com/viewer/6.3.4.532299.html

Ordered Shutdown This viewer has changes intended to make crashes on shutdown less likely. This should have no changes to existing features. For anyone interested in the code details: we use singleton classes extensively for “manager” classes that are only supposed to have one instance each. These are created during startup, with the order determined by when they are needed. Such classes now have the ability to keep track of their creation order and dependencies, so that the destruction process on shutdown can reverse this process systematically. So far only a subset of singleton classes have been modified to take advantage of ordered shutdowns, with more coming in future releases.

Release Notes for v6.3.3. (531811) - Second Life Viewer Released on Friday, October 18, 2019.
https://releasenotes.secondlife.com/viewer/6.3.3.531811.html

Voice This viewer improves voice detection when you’re speaking ( VOICE-56 ). If you’ve been having trouble with your voice is breaking up, then this may be the solution.

Release Notes for v6.3.2. (530962) - Second Life Viewer Released on Tuesday, October 15, 2019.
https://releasenotes.secondlife.com/viewer/6.3.2.530962.html

Maintenance: Vinsanto This Viewer uses Viewer Manager 2.0.529188

Vinsanto is an ancient winemaking tradition of Santorini that dates back thousands of years and represents an important part of Santorini’s history.

FMOD Studio 2.00.07 (updated Windows, Linux, Mac)

KDU v7.10.7 (Windows, Linux, Mac)

Voice Server Version: Vivox Version 4.10.0000.32327 (Windows and Mac)
Voice Opensim 4.6.0017.22050 (Windows and Mac)
Linux uses native voice files Version: Vivox 4.10.0000.32327

LibVLC Version: 2.2.8

Chromium Embedded Framework (CEF) Dullahan:

• Dullahan: 1.1.1320
• CEF: 3.3626.1895.g7001d56
• Chromium: 72.0.3626.121
• Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

FIRE-6264 - [BUG-227497] Logs aren't separate for Users and Groups with same name.
FIRE-6605 - Firestorm AO gets stuck in a swim animation after entering and then flying out of the water
FIRE-7606 - [SL-9116] llSetSoundRadius() does not affect sound
FIRE-8099 - Flying out of water retains swim animation
FIRE-8257 - Console Text Cut Off on Left Side
FIRE-14925 - Firestorm AO: Animations Get Stuck on Cycle (Especially in Sitting/Grund Sit)
FIRE-15059 - After sitting on a cube, turning the Firestorm AO off then on again will put you in a default serverside stand while still sitting.
FIRE-15350 - FS AO uses hover underwater
FIRE-16230 - Firestorm AO incorrectly sits
FIRE-21937 - Teleport Home from underwater on same sim leaves falling AO animation
FIRE-22471 - Turning on Override Sits in built in AO *while sitting* fails to turn off the sit animation after standing from object
FIRE-22943 - [BUG-225229] [SL-1777] Newly Uploaded Items - Focus goes to wrong tab
FIRE-23591 - [Opensim] Map search ignores results that don't start with the supplied search string
FIRE-24114 - Original items can be moved to Outfits folder when contained in a folder
FIRE-24294 - [SL-11727] [PATCH] Fix build warnings relating to polymorphic types and complex copy-assignmentsin GCC 8.3.0+
FIRE-28984 - Discord show username broken
FIRE-28993 - BOM Viewer Crash while editing scripts
FIRE-29020 - Firestorm AO Animation Priority Jitter Bug
FIRE-29031 - Crash when using RLV @interact=n and touching alpha masked attachment
FIRE-29038 - [BUG-227731] [SL-12104] In high-resolution snapshots, the image appears broken up in segments
FIRE-29070 - Pick Radius setting name is misleading
FIRE-29078 - Tabbing out of AO Set Name input field does not rename AO set
FIRE-29134 - Build failure after latest commits
FIRE-29188 - alt+shift+u does not hide Vintage UtilityBar
FIRE-29192 - AO user interface comes up blank when on screen at login
FIRE-29194 - <nolink> tags in offline inventory offers are inserted incorrectly when a single apostrophe is present
FIRE-29207 - Linux Compile Error Changeset 58499
FIRE-29230 - [BUG-228038] [SL-12505] Projectors not working (Maint-Xante regression)
FIRE-29244 - Regarding Keyword alerts. Avatar Names in Local Chat no longer key an alert
FIRE-29294 - Commit r58534:83a9e1d45057 freezing/crashing avx2 builds win/linux
FIRE-29310 - Spelling error
FIRE-29311 - [PATCH] Building with OpenAL on Windows is broken

FIRE-23495 - Clarify Display of Avatars Exceeding max. Texture area
FIRE-29000 - F1 still tries to open wiki.phoenixviewer.com
FIRE-29009 - Remove Facebook from always_showable_floaters debug setting
FIRE-29080 - Change “Group Notices and Chiclets in Top Right” to radio button
FIRE-29082 - Help Browser link - Scripts - Avatar Menu - Avatar Health
FIRE-29253 - Unable to Multi-Select Member Names from a Group Profile Panel

FIRE-24179 - [BUG-227333] [SL-11651] Add Inventory Filter to Search Whole Word Only

If you haven't logged into the Aditi Grid recently, you will likely need to contact LL Support to gain access as well as have your inventory synced. Please review this page carefully http://wiki.secondlife.com/wiki/Aditi. Also ensure you have this viewer setting enabled in Preferences - Advanced - Allow login to other grids.

Note that many libraries cannot be installed using Synaptic or the Software Center; use apt in a terminal instead.

The Firestorm core binary has no unmet dependencies. However, SLVoice, SLPlugin and dullahan_host require additional libraries to do their work.

Install the additional libraries

NOTE: The libraries cannot be installed using Synaptic or the Software Center. They must be installed via apt or aptitude.

sudo apt install libidn11:i386 libstdc++6:i386 libuuid1:i386 zlib1g:i386

These two packages provide support for voice and media services.

sudo apt install gstreamer1.0-pulseaudio:i386 pepperflashplugin-nonfree

If you run across the media_plugin_cef failure message, installing these packages may help:

sudo apt install libnss3:i386 libnspr4:i386 libxtst6:i386 libgconf-2-4:i386 libxss1:i386

Regardless of the method you choose, rebooting at this point can ensure that the OS is properly updated, though it should inform you if a reboot is required.

http://www.firestormviewer.org/linux/

In a terminal, type:

cd # Your home directory by default
mkdir Firestorm
tar xf Phoenix_Fire{tab to expand} -C Firestorm --strip-components=1

At this point, you can launch Firestorm from a terminal:

cd ~/Firestorm
./firestorm

And watch the output, optionally copy it for analysis since not all of it made its way to the viewer log.

You can also create a desktop shortcut, either manually or by running this script in a terminal:

~/Firestorm/etc/refresh_desktop_app_entry.sh

If you crash continually, it will be helpful to get a backtrace, like so:

cd ~/Firestorm
sed -i "/^#export .*gdb/ s/^#//" ./firestorm # This enables gnu debug
./firestorm

At the (gdb) prompt, type r to launch Firestorm. When Firestorm crashes, you should be back at a (gdb) prompt.
Type bt to get a backtrace (there may be several pages, press Enter until you get the gdb prompt again). Copy everything from the terminal screen to a text file.
Type q to exit gdb.
Create a Support Request on our Jira and attach the backtrace as well as crash logs. JIRA can guide you through the process.

NOTE: You can turn off debugging with:

sed -i "/^export .*gdb/ s/^export/#export/" ./firestorm

Default Linux voice files function, but may not on your particular system. As a workaround, install wine and use the Windows 32-bit voice files:

sudo apt install wine-stable
WINEARCH=win32 
winecfg

Once WINE is configured to your satisfaction, launch Firestorm and log in, disable voice, then press Ctrl+Alt+Shift+S to open Debug Settings. Search for FSLinuxEnableWin32VoiceProxy, set that to TRUE, then close Debug Settings. For good measure, relog, then enable and test voice.

Note that using WINE means there is a slight delay connecting to voice as the WINE system starts up. As well, WINE needs a little time to shut down when you disconnect voice. This may cause a race condition if you toggle voice, where a new connection tries to start before the previous one shuts down. This can affect both instances of WINE, and a relog may be required to restore voice functions.

• Cat Herder:Jessica Lyon
• Manager:Miro Collas
• HR Manager (FSG Helpers):Dorrie Bellman
• Land Manager:Flossy Andrew
• Assistant Managers:Coral Sharpshire, Kio Feila
• RolePlay and Scifi Portal manager:Teresa Firelight

• Abinathra
• akafox
• Alexegram
• Angela Kwak (Dutch)
• ChuckPC
• Fayleen Bellios
• FrankASinatra
• ImaLuckygirl
• Jolie Serendipity
• Kitty Beery (Dutch)
• LegitBonzai (Dutch)
• Liliana Darwinian (Portuguese)
• MacMaccee (German)
• maiyasaeria
• MarcSeven Lubitsch
• meady212
• PassionateAviator
• Pim Peccable
• Sparkle Weatherwax
• Synthetic Mode
• Tracy Argus
• Webbi Jonson (German)

• 0079Galadriel
• briannainchains
• Hilary Querrien
• MarcSeven Lubitsch
• nuttidoxieg4 merryman
• panterapolnocy
• Starwolff2000
• Varahi Lusch

• Education:Alexegram, Dorrie Bellman, ImaLuckygirl
• Avatar Education:Kio Feila, Tracy Argus
• Small Events Planner:Jolie Serendipity
• FS Tour Guide:Fayleen Bellios

This window is used to customize the layout of the on-screen buttons. The window is accessed by right clicking any of these buttons.

You can drag and drop buttons to and from this window, from the tool bars. Tool bars exist on both sides of the screen, and at the bottom.

The buttons will be displayed according to each toolbar's settings: icons, text labels, or both.

The following toolbar buttons are available:

• About Land
• Animation Overrider
• Appearance
• Area Search
• Asset Blacklist
• Avatar
• Beacons
• Block List
• Build
• Camera Controls
• Chat
• Contact Sets
• Conversation Log
• Conversations
• Create Landmark
• Debug Settings
• Destinations
• Discord
• Favorite Wearables
• Flickr
• Fly
• Gestures
• Grid Status
• Ground Sit
• Group Titles
• How To
• Inventory
• Map
• Marketplace
• Mini-Map
• Mouselook
• Movelock
• Nearby Voice
• People
• Phototools
• Phototools Camera
• Picks
• Places
• Pose stand
• Preferences
• Profile
• Quick Prefs
• Radar
• Region Tracker
• Region/Estate
• Report Abuse
• Resync animations
• Search
• Show Friends Only
• Snapshot
• Snapshot to Disk
• Sound Explorer
• Speak
• Statistics
• Stop Animations
• Teleport History
• Twitter
• Walk / run / fly
• Web Browser

Below are these three buttons:

• Clear all toolbars will remove all buttons from all toobars.
• Restore defaults will restore buttons as they would be on a clean install.
• Locked: If you enable this, it will prevent you from accidentally moving or removing buttons from the toolbars.

See this video for a tutorial.

What is chat? Chat is essentially how we communicate with other residents in Second Life. There are two major categories of chat; Text chat and Voice chat. This page will focus on text chat. For info about voice chat, go here Voice.

There are 4 types of chat:

• Local chat is where everyone within chat range can hear you.
• Group chat is where you can talk to a group as a whole.
• Instant messaging (IM) is where you can talk privately one on one to another individual.
• Ad Hoc (Conference) calls where you can talk to a group of people you select in an IM.

• Normal chat has a range of 20 meters. To use normal text chat, input your text in either the main chat bar at the bottom or in the nearby chat window.
• Shout has a range of 100 meters. To use shout, press ctrl + enter keys after inputting your text.
• Whisper has a range of 10 meters. To use whisper, press shift + enter keys after inputting your text.
• Instant messages, group chats and conference calls are grid wide.

Alternatively, you can choose to show the “send” button at the end of the nearby chatbar which you can select the chat type (whisper, say, or shout) but it will remain in whatever chat type until you change it. To enabled this “send” button, go to Preferences→ Chat -> Typing→ Show chat type / send chat button in chat bar.

The viewer has the ability to translate text into a language that you choose but you need to set up an account with Bing or Google to do so. See here for more information. Previously, Google provided free translation services, but this has now ended, and you must establish your own account with Bing or Google which may incur a cost. Please be aware that chat translation only works in nearby chat and not in IMs or group chat.

There are several ways to start an instant message:

• To talk to a nearby avatar, right click on any part the avatar (not their attachments) or their name tag and select IM from the menu.
• From the friends list in the contacts window, select on the person’s name and press the IM/call button.
• From the friends list in the People Panel, select the person’s name and press the IM button at the bottom of that window.
• If person is already chatting, click on the name in the chat window, this will bring up a quick profile window, and press the IM button.
• In a person’s profile, press the Instant Message button.

Provided you are allowed to join a group chat, go to group tab in Contacts window and either double click on the group or select the group and press the IM/call button.

If you are in the group tab in the People Panel, double clicking on the group will start chat or you can right-click on the selected group and select chat.

To close the group chat window for the duration of the login session, press the X button at top right of that group window. If you want to close it temporarily, press the Zz button at top right to put the group in “snooze” mode. Snooze mode will close the chat for a set duration and after that duration is done, any new chat in that group will make that group's chat window open again. Chat group duration default time is set to 900s but can be changed in Preferences> Chat> Chat Window.

A conference is a private conversation with two or more Residents. It is similar to group chat, but more dynamic, since everyone on your friends list can be invited, as well as everyone where you got a calling card from.

To start a conference chat:

• Go to Conversations window → Contacts Tab → Friends and select each friend you want to include in the conference by pressing Ctrl + left click on mouse on each friend’s name and then press the IM/Call button.
• Go to the People Panel→ Friends tab and select each friend you want to include in the conference by pressing Ctrl + left click on mouse on each friend’s name and then right-click and select IM.
• If you already have an IM going with someone and want to add another resident, you have two ways to do this:
  • go to Inventory→ Calling Card folder and drag that resident’s calling card into the IM, or
  • press the “add someone to this conversation” button at top of the IM.
  • Drag and Drop the selected avatar in the current IM. Can drag and drop from the following windows:
    • Radar
    • Nearby Avatar tab in People window
    • Friends tab in People window
    • Friends tab in Contacts tab (Conversations window)
    • People Search tab in Search window
    • Contact sets

Note: Conferences are limited to twenty participants.

The terminology has changed so please read here.

To save or not save your chat logs and transcripts (nearby, IM/Group), go to Preferences→ Privacy -> Logs & Transcripts and select the options under Save:.

The location for the saved chat logs and transcripts depends on your operating system but can be found and changed in Network & Files -> Directories→ Conversation logs and transcripts location. Press the Set button to change it to a different folder.

If you are offline and an IM is sent to you, the IM is backlogged and will appear as a set of notification icons in the upper right or lower left of your Viewer when you log in.

The backlog is capped at 15 messages, unless the account has a Premium Subscription, in which case the cap raises to 80 message, including inventory transfers, group invitations, and group notifications. If someone gives you an inventory item (generating an IM message), the message is placed in your inventory's Trash folder, and you can retrieve it when you return. If a scripted object sends the inventory, it is deleted immediately. Note: If Automatically accept new inventory items Automatically accept new inventory items is enabled, then all inventory offers, even above 15 (or 80 in the case of Premium members), go directly to inventory and do not count against the cap on offline messages.

Second Life will keep the IMs in the backlog for 31 days. If you do not log in within the 31 days to view your IMs, they will be deleted.

To ensure you get your offline IMs and not get them capped, they can be sent to the email address that is connected to your contact information. To enable this option, go to Preferences→ Chat -> Notices→ check Email me IMs when I'm offline.

If you send a reply to an offline IM via email, the original sender will receive it as an IM. The email reply is limited to 1023 characters and must be sent within 5 days.

There are several ways to have your chat windows set up to your liking.

Docked in the conversations window:

• Go to Preferences→ Chat -> Chat Windows→ . Next to “Show IMs in”, tick Tabs and then relog.

As separate windows:

• Go to Preferences→ Chat -> Chat Windows. Next to “Show IMs in”, tick Separate Windows and then relog.

How to dock/undock the chat windows:

• There is a “tear off” button next to the 'x' (Close). Press that to dock and undock the chat window.

How to rearrange the IMs:

• Select and drag the IM tab to the order that you choose.

How do I make the group chat look like the old style chat?

• In Preferences, go to Chat -> Chat Windows, and check Use V1 style chat headers.

How do I change the size of the font in chat?

• In Preferences, go to Chat -> Chat Windows, and select the size that you prefer in “Chat window font size”

How do I get my Contacts window back:

• If your Contacts window is not showing, go to the top menu bar→ Comm menu → Contacts (Ctrl+Alt+Shift+F).
• If Contacts window is showing but undocked and there is no tear off button showing, go to top menu bar→ Preferences→ Advanced (Ctrl+Alt+D) → Debug Settings → Search for ContactsTornOFF and set to False.

The purpose of this section is to provide help for those new to Second Life, irrespective of the viewer used or their entry point into SL. Given that different viewers are available, where possible, the information given assumes that the official Second Life viewer is the being used.

If you are looking for information on Firestorm features and functions, click here. If you need help with Firestorm viewer, click here. We also offer classes on how to use the Firestorm viewer. See this page for the schedule and in-world locations.

You can join Second Life via the web page given here:

• Create Second Life Account

If you want to invite friends to join, then please do share the link above with them.

• What is Second Life?
• Huck’s absolute beginner’s guide to Second Life for the coronavirus curious

• How Does Clothing Work?
• How Do I Mod My Shape?
• Where Can I Get Good Free Stuff?
• How Do I Use Furniture?
• How Do I Use the Camera?
• How Can I Earn L$ in SL?
• Why Am I Wearing a Box? (Unpacking Boxes)
• How Do I Talk to People?
• How Does My Inventory Work?
• How to Make a Landmark/Set Home
• What Are Groups?
• What Should I Know About Mesh Bodies, Heads and Omega Appliers?
• What Do All Those Acronyms Mean?
• Why Do I See Some People as Colored Blobs?
• How Can I Defend Against Bad People?

• SL Knowledge Base
• Second Life YouTube Channel

• Getting Started in Second Life
• Chat, IMs, Voice
• Appearance Mini-Series Videos
• Shopping & Buying Linden Dollars
• Getting a Home in Second Life - Premium Members
• How To Get Help

• Exploring Second Life
• Popular Entertainment
• Firestorm Gateway Scifi Portal
• Games Made in Second Life - Tabletop Gaming in Virtual Worlds
• Learning Made in Second Life - CNDG
• Tyrah and the Curse of the Magical Glytches
• Horizons Adventure
• Paleoquest