If you find that you are crashing frequently, then perhaps the suggestions here will be helpful. Please don't skim the page - read it carefully.

It is important to distinguish between two things….

If a small window appears, saying that you have been logged out of SL, this isn't a crash. Rather, SL is disconnecting you, for one of a number of reasons, including:

• The region you are in is going down.
• During teleport, the SL servers may fail to hand you over to your destination and so log you out; help on that is given here.
• Your network connection has gone down.
• Your network connection has become poor or unreliable and SL has lost contact with your avatar.

Things to try - in order:

• reboot your router/modem, then your computer;
• make sure your bandwidth is set correctly - follow the instructions hereexactly as given;
• shut down any other programs that are making heavy use of your network connection, such as torrents;
• If you use Mac with Yosemite, see if this might be your case.
• If the problems persist still, try changing your DNS to Google, as explained here.

If you are being logged out when you edit appearance, or edit shape, or use the Appearance toolbar button, did you drop items into the Outfits folder that were not created via the Outfits/Appearance window? If so, remove those items.

Firestorm itself has crashed. The remainder of this page offers possible solutions.

• Update your Operating System. See the advice from LL, and the reasons behind it, here.

• (Windows-only)
  • If you are using an ATI (AMD) graphics card, then please refer here for known problems with these cards.
  • For nVidia users, please refer to this page.
  • Also for nVidia: if you recently updated your drivers and are experiencing crashes, try reverting to an older driver that worked for you.

• (Mac-only)
  • If you have Sierra plus Nvidia graphics, see http://wiki.phoenixviewer.com/mac_sierra
  • If you have El Capitan plus Nvidia graphics, see http://wiki.phoenixviewer.com/mac_el_capitan
  • If you crash when uploading images to SL or when saving snapshots to your hard drive, see http://wiki.phoenixviewer.com/mac_crash_upload

• In Preferences → Graphics → General:
  • Reduce Draw Distance by half (or more).
  • Reduce Max # non-impostor avatars.
  • Reduce Maximum Complexity by half (or more).

• Disable VBO: Run Firestorm and before logging in, press Ctrl-P to bring up the Preferences window. Then click on Graphics → Hardware Settings tab. Make sure that “Enable OpenGL Vertex Buffer Objects” is not checked.

• 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:
  • RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
  • TextureLoadFullRes should never be enabled.

• (Grids other than SL only!) Disable HTTP Get Textures: Open the preferences window, then click on Graphics → Rendering tab. Make sure “Use HTTP Textures” is not checked. Please clear your cache if you change this setting.

• It is possible that your graphics settings are set higher than your computer can handle. To see if this is the case, go to Preferences → Graphics, and click on Reset (the circular arrow to the right of the quality slider). After doing this, you may still need to reduce Draw Distance and Max # non-impostor avatars, as mentioned above.

• If you have Shadows turned on, try turning them off. See this page for more side effects of shadows.

• Another thing you can try is: Develop → World → Dump Region Object Cache, then relog. (The Develop menu is revealed with Ctrl-Alt-Q, if you cannot see it.) This sometimes also helps deal with odd texture issues; it may need to be done several times.

• If clicking on a link or SLURL in Firestorm causes an instant crash: do you have AVG 2011 installed? If so, it probably flagged SLPlugin as malware. See here for more on this.

• If you have Webroot SecureAnywhere Antivirus, see Webroot Issues.

• If you are crashing when you try to upload a texture, please try disabling VBO, as described above. Also, if you are on Windows and running Microsoft SkyDrive, prefer refer here. If you are on a Mac, this workaround may fix the problem.

• If the above tips do not help, you might benefit from a cache clear or viewer clean reinstall.

• If you find that a full manual cache clear allows you to log in, and you crash unless you do this, then there is a good chance that you have one or more problems with certain inventory items; please see this page for how to deal with this.

If you have eliminated all the possible causes for the crash and you are still crashing, it's time to submit a Support Request on our jira. In that request, you can include screenshots or videos, if they will help clarify your description, as well as your sysinfo and viewer event logs. Follow the steps in this link to create the request and add your logs.

Why? Because here be dragons. And sometimes clearing your settings may be the best way to fix a weird problem. Keep in mind that settings are not cleared by uninstalling or installing new viewers.

If clearing settings solves your problem, then you might want to create a backup of your settings once you have restored them as you like them - and assuming that everything works. Click here for instructions.

• Go to Preferences–> Network & Files -> Directories
• Click the 'Open Settings Folder' button
• A window will popup. Keep this window open.
• Log off of the viewer.
• Delete everything you see inside the folder.
• Navigate up one level to the folder above.
• Now locate the folders which have the names of your avatar(s)
• In each of these folders, locate the file settings_per_account.xml and delete it

Assuming you are unable to log into the viewer, follow these steps.

• 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.

• Find the folder named “user_settings” and navigate inside it
• Delete everything
• Now locate the folders which have the names of your avatar(s)
• In each of these folders, locate the file settings_per_account.xml and delete it

Teleport can fail in several ways:

• you simply don't go anywhere but remain where you were
• you get disconnected
• you crash out

The first of these cases may often be due to simple things like the region you are trying to get to is full, or you have no access to it, or it has gone down. Try again after a few minutes.

Also, please note that the recent introduction of “teleport threading”, an attempt to mitigate the effects of mono memory leak, have led to an increase in TP failures, often resulting in your being logged out of SL altogether.

Things to try:

• Disable RLV: Go to Prefs → Firestorm → Extras → “Enable Remote Scripted Viewer Controls (RLVa)”, then relog. See if you can now teleport. If you can, you may have had an RLV restriction in place.

• If you aren't crashing or disconnecting but aren't getting anywhere, try TPing to different locations. It may just be one region giving you trouble. “Puddle jumping” by going to a different one first might help you get around sim issues.

• Try opening the landmark you are trying to TP to and let the information in the LM load fully before clicking Teleport.

• Having your bandwidth set too high is a frequent cause of TP failure. Go to Preferences→ Network & Files -> Connection and set bandwidth to 300, and see if that improves things. If it does, you can increase gradually, up to a maximum of 1500. Please refer to this page for information on determining your optimum bandwidth setting.

• Mac users: If you crash or get logged out on all or most TPs, then you may need to add new DNS numbers in System Preferences on your Mac, especially if you are experiencing other issues like an empty friends list or trouble viewing rigged mesh. Please see the “Mac-specific” section of this page for instructions.

• 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.

• If you are using a firewall, try disabling it temporarily and seeing if that improves things. Norton products in particular have been known to severely impair various SL functions, including teleports and texture rezzing, but the same issues may appear with other firewalls as well. If this solves the problem, re-enable the firewall, and then configure it to allow Firestorm access to the 'net; for more on that, see here.

• Check your network performance. Go to Help → About Firestorm and scroll to the bottom of the window. There you will see something like “Packets Lost: 191/34581 (0.6%).” You would like to see this number as close to zero as possible. If this is more than a few percent, that is a likely cause for TP failure. You may have a poor connection to your ISP, or it might be that the sim you are on is overloaded and responding poorly. You can also view realtime packet loss in your Statistics Bar (Ctrl-Shift-1; if this does not open, make sure your Advanced menu is open with Ctrl-Alt-D and try again).

• Right-click your tag or a non-prim part of your avatar and select Script Info. If the number of scripts reported is in the triple digits, then it might be causing the TP fail. Try removing scripted prims. To determine which attachments contain the most scripts, go to World → Parcel Details, click Script Info at the bottom and then Avatar at the top. This will list your scripted attachments with their size in memory (not number of scripts) to help you know what to try removing first.¹⁾ Note that UNscripted prims have no effect on TP failing.²⁾

• If you have teleport screens disabled, try turning them back on: Preferences → Move & View -> Teleports→ Disable Teleport Screens … make sure it is NOT checked.

• If nothing above helps the issue, then there may be a problem with your connection, especially if you were seeing high packet loss. Log off and try resetting your router/modem. Unplug it for a minimum of two minutes. If it has a battery backup, remove the battery as well. It does not hurt to reboot your computer at this time. After at least two minutes have passed, plug the router/modem back in and/or replace the battery and log back in.

¹⁾ Often, scripts in worn attachments are old-style resizers, which use one script per prim. In 200-prim hair, that is 200+ scripts! Click on the hair, jewelry, shoes, or other attachment, and if there is a menu option to delete resize scripts, then make a copy of the item in your inventory and delete the scripts out of one copy. Wear the now-unscripted copy and save the scripted one in your inventory in case you need to resize it again in the future.

Naturally, you do NOT want to stop or remove scripts from HUDs or other items that perform useful functions, like AOs, Mystitool, combat HUDs, etc., though you can reduce your scripts further by setting up and using the built-in client-side Firestorm AO instead of an AO HUD.

²⁾IMPORTANT: Avatar Render Draw Weight (formerly Avatar Rendering Cost, which was calculated differently) is totally unrelated to script count. Low draw weight does not mean your script count is low. It is an indication of how much work your computer has to do to draw an avatar, no more. The association between draw weight/ARC and scripts is a myth, and totally false. Also, high draw weight does not interfere with TP; that too is a myth.

There are two ways to count worn scripts in Firestorm. One method allows you to view the total number of scripts on your avatar or in a selected attachment on your avatar. The other method shows you a list of all your worn scripted attachments with their script memory (not number of scripts) displayed.

For the total number of scripts you're wearing:

• Right-click your avatar tag or any non-mesh, non-prim part of your avatar.
• Select Script Info.
• In nearby chat, find a message like this: [10:37:32] Script info: 'Your Name': [7/9] running scripts, 528 KB allowed memory size limit, 0.010705 ms of CPU time consumed. (This message is only visible to you.)
• The numbers in brackets are how many scripts your avatar is wearing and how many are running. In this example, there are 7 scripts running out of a total of 9.

For the number of scripts in a specific attachment:

• Right-click the worn item. It may be mesh, prim, or a HUD.
• Select More → Script Info (pie menu) or just Script Info (non-pie menu).
• In nearby chat, find a message like this: [10:51:34] Script info: 'Item Name': [3/3] running scripts, 192 KB allowed memory size limit, 0.001745 ms of CPU time consumed. (This message is only visible to you.)
• The numbers in brackets are how many scripts your avatar is wearing and how many are running. In this example, there are 3 scripts running out of a total of 3.

Please note: Your Firestorm LSL Bridge is needed for Method 1 to work. If you do not see a message in nearby chat after following the above steps, then make sure it's worn and enabled:

• To check that it is worn, open the Current Outfit folder in your inventory and look for a link to #Firestorm LSL Bridge.
• To check that it is enabled, open your Firestorm Preferences (Ctrl-P or Avatar → Preferences in the menus) and go to Preferences → Firestorm → Extras. Make sure that there is a checkmark in the box alongside “Enable LSL-Client Bridge.”
• If it isn't worn, or if it's worn and enabled but still not working, then see our bridge page on how to recreate it.

• In the menus at the top of your screen, go to World → Parcel Details. This opens the About Land window.
• At the bottom of the About Land window, find and click Script Info. This opens the Script Information window.
• At the top of the Script Information window, select the Avatar tab.
• In this tab, you can view a list of scripted worn attachments and the script memory that applies to each. Note: “Size (kb)” refers to script memory, not number of scripts.

For instructions for Phoenix, please refer here.

Some anti-virus programs will incorrectly flag a viewer - or necessary components of a viewer - as a virus or threat. They may remove the suspected part completely, rendering all or part of the viewer non-functional. There is nothing we can do about this. However, it should be possible for you to tell your anti-virus that the viewer is safe; you will need to whitelist the viewer program as well as some components.

The following is a list of anti-virus software and how to whitelist. Naturally we cannot provide instructions for all existing anti-virus software, and the information here may be outdated. Therefore, it is strongly recommended that you consult the software manual for the specific program you use, for accurate and up to date information.

Here are the steps to follow to reinstall and whitelist a viewer in such as way that the anti-virus program doesn't “mangle” the viewer yet again:

1. Uninstall the viewer normally.
2. Disable the anti-virus software completely (in a few cases, this requires rebooting to make sure that the AV is not running anymore).
3. Reinstall the viewer, but make sure you do not install it back to the default folder suggested; install to a new folder. This step is vital.
4. In your anti-virus program, whitelist the following, per the instructions below (or better, consult the manual for your anti-virus software):
   • the viewer install folder
     • inside this, the viewer itself (firestorm.exe), slplugin.exe, slvoice.exe and llceflib_host.exe (for FS 4.7.7 and later).
   • the viewer cache folder
     • In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Now you need to locate the cache folder:
       • Windows XP: C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Firestorm
       • Windows Vista/7/8/10: C:\Users\[USERNAME]\AppData\Local\Firestorm
       • Mac: /Users/[USERNAME]/Library/Caches/Firestorm
5. Run the viewer to ensure that it is working correctly; do a test of search and voice to ensure that both work, checking that the respective plugins get loaded. Log out of the viewer.
6. Re-enable your anti-virus software and run the viewer again, repeating the tests above.

• Open the Avast User Interface
• Click Real-time shields
• Click File system shield
• Click Expert Settings
• Click Exclusions
• Click Add
• Click Browse and navigate to the Firestorm install folder
• Click OK
• Repeat for the Firestorm cache folder
• Click OK all the way out

• Open the AVG user interface.
• Click Tools→Advance Settings.
• Resident Shield→Exceptions.
• The Add the program (or file, directory) you wish to be excluded from scans.

Please refer to this page.

(derrived from https://community.f-secure.com/t5/Security-for-PC/How-do-I-exclude-a-file-or/ta-p/15398)

• Open Computer Security.
• On the main page of Computer Security, click Settings.
• Select Computer Security > Virus and spyware scanning.
• Select Other settings > Manual scanning.
• Click the Exclude files from the scan link. The Exclude from scanning dialog is displayed.
• Select the Objects tab.
• Select the Exclude objects (files, folders…) check box.
• Click Add.
• Navigate to and select the Firestorm install folder
• Click Add again
• Navigate to and select the Firestorm cache folder
• Click OK to close the Exclude from scanning dialog.

If Gatekeeper prevents you from opening Firestorm, there is a simple workaround: See “How to open an app from a unidentified developer and exempt it from Gatekeeper” on this page. Once you have allowed Firestorm to open via this method, Gatekeeper will not flag it on subsequent launches (until you reinstall Firestorm again).

For a longer-term method, please visit here for a tutorial on whitelisting using the Gatekeeper software.

In order to create an exclusion rule:

• Open application settings window.
• Select Protection on the left.
• Click the Trusted Zone button in the Exclusions block.
• Go to the tab Exclusion rules and click Add.
• Select an exclusion type in the Properties field: Object and/or Threat type.
  • Object
    Click select object and choose a file, folder or a mask to exclude.
  • Select a Component in the corresponding field. The rule will apply to the selected component.
  • Threat type. Click enter threat type to select a file, folder or a mask to exclude.

Rules can apply to the following protection components:

• Virus scan,
• File Anti-Virus,
• Mail Anti-Virus (Kaspersky Anti-Virus 6.0 for Windows Workstations 6.0.4.x only),
• Proactive Defense (Kaspersky Anti-Virus 6.0 for Windows Workstations 6.0.4.x only),
• Web Anti-Virus (Kaspersky Anti-Virus 6.0 for Windows Workstations 6.0.4.x only).

A scan if a disk or folder containing excluded objects scans the entire disk/folder except the excluded objects. Yet you can force scan excluded objects from the contextual menu (by right-clicking).

Also you can create an exclusion rule from within a report window:

• Right-click the report object you want excluded.
• Choose the option Add to Trusted Zone.

An Exclusion rule window will open. Make sure that you are satisfied with the new exclusion rule settings. Object name and threat type fields are assigned automatically on the basis of the report data. Click OK to create the rule.

For Win 10 (possibly also Windows 8.x):

• Open Settings and in the search field at the top right enter defender
• Click the Windows Defender Settings option.
• Exclude the cache
  • Click Add an Exclusion
  • Click Exclude a folder
  • Click in the address bar and type %LOCALAPPDATA% and press Enter
  • Click the Firestorm folder
  • Click the Exclude this folder button
  • Repeat this if you have more than one Firestorm folder (64-bit and 32-bit, for example)
• Exclude the viewer executables
  • Click the Exclude a .exe, .com or .scr process button
  • Navigate to C:\Program Files\Firestorm-Release64
  • Click Firestorm-bin
  • Click the Exclude This file button
  • Repeat this for SLPlugin and SLVoice - and llceflib_host (for FS 4.7.7 and later).
  • Repeat this for 32-bit Firestorm ( C:\Program Files (x86) )

Add exclusion to Auto-Protect and Risk scan

• Start Norton 360.
• Click Settings.
• Click Antivirus Protection.
• On the Scans and Risks tab, under Exclusion/Low Risks, click Configure next to Scan Exclusions.
• Under Scan Exclusions, click Add.
• Browse and select the disk drive or folder or file you would like to exclude and click OK. If you want to include subfolders within the folder, check Include Subfolders.
• Under Auto-Protect Exclusions, click Add.
• Browse and select the disk drive or folder or file you would like to exclude and click OK. If you want to include subfolders within the folder, check Include Subfolders.
• Click Apply > OK.
• Click Apply > Close

Norton Internet Security includes a feature called Download Intelligence. This works such that the user community reports downloads as good or bad. While this may be very helpful, it can also be unfairly detrimental to programs, especially when they are updated as they are then treated as totally new.

Therefore, if you use Download Intelligence, you are urged to disable it before attempting to download any of our viewers, in order to avoid them being incorrectly reported as infected with a virus. Refer to this page for instructions.

• Click on the “Antivirus” section of the UI.
• Click on “Advanced Settings” (bottom of the panel current version)
• Click on “Exclusions” tab
• Choose “Add”, then navigate to your Firestorm installation folder and put a check in the box to the left of slplugin.exe (and llceflib_host.exe for FS 4.7.7 and later), and everything else you want to exclude. Once you've checked something, the “exclude” button at the bottom of the panel is enabled. Click it when you've finished checking off everything you want to exclude.
• Click “OK” at the bottom of the “Exclusions” tab.

See this page for additional Panda tips for whitelisting files and folders: http://www.pandasecurity.com/homeusers/downloads/docs/product/help/is/2012/en/709.htm The page is out of date but the methods may still work.

• Right click PC Tools icon in taskbar → Open
• Go to Settings → Global action list
• Click “Add”, choose “File” & browse to your Firestorm installation folder & choose slplugin.exe - and llceflib_host.exe (for FS 4.7.7 and later).
• This will add the plugin(s) to the global whitelist.

To date (August 2015), there is no way to whitelist the entire cache folder in WebRoot. Therefore WebRoot may continue to cause severe problems including slow rezzing and viewer freezing.

If you test with WebRoot off and find your SL experience greatly improved, the only suggestion we have is to choose another antivirus program.

Some more more info on Webroot and the problems it has been known to cause, see this page.

For additional information:

• https://community.webroot.com/t5/Webroot-for-Business/how-to-set-file-and-folder-exclusions-in-the-webroot-console/td-p/189775
• https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/How-to-exclude-a-folder-from-being-scanned-in-the-latest-WSA-AV/td-p/78063

These classes are based on our official Firestorm release and are conducted in voice and 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, http://maps.secondlife.com/secondlife/Firestorm%20Social%20Island/250/6/4001
• JU: Junkyard University, http://maps.secondlife.com/secondlife/Junkyard%20Blues%20South/68/124/22

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

*All times SLT*

Firestorm supports both the new Region Windlight, introduced by LL, and Parcel Windlight, which was introduced with Phoenix Viewer. Both of these allow you to customize your in-world sky and water, but they operate at different levels: one is region-wide, while the other is restricted to single parcels.

Parcel Windlight allows individual parcel owners to customize their own land as they wish. Region Windlight is most effective on region-wide parcels, or where Region owners wish to provide a consistent experience to visitors.

There are several ways in which you can control you personal Windlight experience. You can opt to use whatever sky and water settings have been selected by region and/or parcel owners, or you can use your own. You can also create your own sky, water and day cycle settings.

General options concerning Windlight are set in Preferences→ Firestorm→ Windlight tab; please refer there for details.

If you wish to use your own day/night cycle, or set to a specific time of day, then use top menu bar→ World → Environment Editor → Environment Settings.

If you own a region or parcel, you can customize the Windlight settings for yourself, and for others visiting your land.

Region Windlight can only be changed by region owners or estate managers. It is set by going to the top menu bar and selecting Region Details. On the window that opens, select Environment. Regions can be set to use the default SL day cycle, a custom day cycle, or fixed time of day. See here for more on how to configure a region's Windlight settings.

Parcel Windlight sharing is a feature of Firestorm that allows land owners to specify a Windlight preset for the viewer to use while on their land at the parcel level.

The land owner just needs to put a plain text string at the end of the parcel description. Parcel description is set in the About Land floater, General tab.

/*Windlight Sky: "[name of the preset]"*/

Windlight water presets are also supported:

/*Windlight Sky: "[name of the preset]" Water: "[name of the WL water preset]"*/

Water settings can be used by its self just like sky if wanted.

Example: If the sky preset is to be [TOR] BIG SUN - Awwyeah and the water preset [TOR] Watermelon juice and the parcel's description is “My awesome place” then the parcel description would be like this:

My awesome place

/*Windlight Sky: "[TOR] BIG SUN - Awwyeah" Water: "[TOR] Watermelon juice"*/

Zones

Parcel WL settings also support zoned settings based on altitude. This allows skyboxes to have a different sky settings than ground level.

/*Windlight Sky @ [lower]m to [upper]m: "[name of preset]"*/

Example: If the parcel wide settings are to be [TOR] MIDDAY - Cheery cyan for the sky and [TOR] Ice-like for the water with a skybox between 500 meters and 600 meters using [TOR] NIGHT - Moony for its sky, the config line would like like so:

/*Windlight Sky: "[TOR] MIDDAY - Cheery cyan" Water: "[TOR] Ice-like" Sky @ 500m to 600m: "[TOR] NIGHT - Moony"*/

The parcel wide settings for sky and water are optional. Zones can be used by themselves leaving the rest of the land at region defaults.

NOTE: There is a 3 meter minimum distance between zones, zones should be at least 10 meters apart and over lap the desired area by a least 5 meters to allow for the 5 second delay on detecting changes.

If you have set region WL to use a fixed sky or a custom day cycle, region WL will always override parcel WL unless you use the RegionOveride flag

For example:

/*Windlight Sky: "[name of the preset]" Water: "[name of the WL water preset]"RegionOverride*/

Advanced

If there is not enough space in the description for the desired config line, there are several optional formatting and whitespace

/*Sky:"[preset]"Water:"[preset]"*/

Is the same as:

/*Windlight Sky:"[preset]" Water:"[preset]"*/

Zones can be shortened as well:

/*Sky@[lower]-[upper]:"[preset]"*/

Please refer to this page for details.

There are different kinds of problems with missing inventory that can take place; those that are controllable at the viewer or computer end are generally reversible. Problems caused by the Second Life asset server are not always fixable.

If items that you rezzed out in-world are missing, then refer to this page instead.

• If the number of items appears correct, but not everything is showing, reset your inventory filters. On most viewer skins, this means clicking the Gear menu at the bottom of your inventory and selecting “Reset Filters.” On Vintage skin (this is what you're using if you logged in with Phoenix Mode) or Ansastorm skin, click Inventory → Reset Filters in the inventory menu.
  Note: if you are looking for Marketplace items using Inventory search, and they are not showing, ensure that you have the Received items folder shown in inventory, rather than as a button: Preferences → User Interface → Interface Windows → Show the Received Items folder in normal inventory. Or, click the Received button to see what items are in there.

• In your inventory, type letters into the search filter. It doesn't matter what letters; the purpose is to prod the search into finding more items. If the fetch stalls again, pick a different letter.

• For any/all folders that appear to be missing inventory, try creating a new item, of the appropriate type, in the folder. So for example, if you appear to be missing things in the Clothing folder, right-click the folder name → New Clothes → New Shirt. Then relog.

• Try clearing your inventory cache.
  • On recent versions of Firestorm, open Preferences -> Network & Files -> Directories, then click the Clear Inventory Cache button, then relog.
  • On older versions, you will have to clear inventory cache manually, as follows:
    • Go to Preferences → Network & Files; beside Cache Location, click on Open. A window opens showing the contexts of the cache folder.
    • Leave that window open, and log out of Firestorm.
    • Make sure the folder is set to show file extensions.
    • Locate the file whose name ends in .inv.gz, and delete that file.
    • Log back in - preferably to one of the locations given above: at the log in screen, you can select log in location; type in one of the region names indicated above.
  • Additional notes: If clearing inventory cache does not fix the problem the first time you try it, then it probably won't work on additional attempts, so don't keep doing it (though multiple relogs without cache clears may help).

If your inventory is still not loading fully, then the issue may be a network or connection problem. General suggestions for problems that may be connection-related are:

• If you are on a wireless connection and are able to wire it in, do so.

• Reboot your router/modem, leaving it unplugged and unpowered for a minimum of two minutes before powering it back up again.
  • If you have access to a different connection, try connecting your computer to it temporarily.

• If the inventory is still not fetching all the way, view our page on bandwidth and speedtests to make sure your bandwidth is set optimally in the viewer. Although it may seem counter-intuitive, we have found that lower bandwidth settings usually allow for more reliable inventory loading than higher settings.

• 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.

• Please download the official SL viewer, install it, log in on it and see if the items show up there. If they do, then the problem is probably either loading or caching in Firestorm, and you can follow the set of suggestions below under “Advanced Method: Inventory Copy from SL Viewer.” If the items don't show up in any viewer, then there is a good chance they're missing from the asset server, which means the problem may not be fixable.
  

Back on Firestorm, if your inventory count still looks lower than it should be or stalls in the middle of fetching items, then:

• If the above steps have not worked for you, continue on to the next step:

Start by finding your avatar key while logged into Firestorm or another viewer that displays it - see the figure to the right; the UUID is highlighted in green.

It is a string of letters and numbers that appears in your legacy-style profile, though the exact location will vary because different skin options display it differently. If you use web profiles, you will need to switch into the legacy profile to find it. (In Firestorm, this is in Preferences -> User Interface -> Interface Windows→ Use web profiles by default.) You can return to the web profile style afterward. When you find your key, just copy it down somewhere.

Now you will need the latest release version of the SL viewer, so if you don't have it installed yet, download and install it. Then, log into the SL Viewer and get your inventory loaded in that viewer. This might work with any other viewer, as well, but the SL Viewer is the only one we've tested with. Once your inventory is loaded there, log out.

Locate your Second Life cache folder and your Firestorm cache folder on your hard drive. Our clearing cache page will help you locate where that is (just replace “Firestorm” with “SecondLife” in the path name. Don't clear either cache! Just use the paths shown to find the folders.

Note: You must be LOGGED OUT of both viewers before doing the next step.

In the Second Life cache folder, find the file named with your avatar key and ending in “inv.gz”. Drop or copy this file into your Firestorm cache folder. Allow it to replace the one there.

Log into Firestorm and check to see if your inventory is there.

Avoid clearing cache or you may need to do this process again.

Please note: Under normal circumstances, you should not share cache between viewers because it can cause other weird problems. This suggestion should not be read as an indication that setting your cache in different viewers to the same place would be useful. It won't be.

For additional ideas, also refer to the Second Life wiki page on Inventory Loss.

If this occurs, chance are good that the inventory cache is corrupt. Deleting it should solve the problem.

• Locate your cache folder. You will probably need to do this manually, if you are unable to log in. Use a file manager (like Windows Explorer for Windows system, Dolphin, or some such) to locate the cache folder. In its default location, the cache folder is hidden on most OSs. To find it, you will need to show hidden folders. Default cache locations are:
  • Windows XP: C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Firestorm
  • Windows Vista, 7, 8, 8.1, and 10: C:\Users\[USERNAME]\AppData\Local\Firestorm
  • Mac: ~/Library/Caches/Firestorm
  • linux: ~/.firestorm/cache
• In this folder, locate the files named data.db2.x.* and index.db2.x.* (where * is a digit: 0, 1, 2, etc; you may have more than one of each type of file)
• Delete all files that match these two names.
• Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Allow your inventory to repopulate fully.

Windows only: If the above doesn't work, then click the speaker icon in the system tray, then touch the volume slider, just enough to change the volume slightly. It may be that the Windows sound system has stalled; this should “give it a kick”.

If the above fails, then try doing a full wipe of all settings.

This indicates that a debug setting (a control) is missing a comment. It is unclear which comment is missing, but the fix is to reinstall Firestorm using the Clean Install procedures.

Ref. FIRE-12339

This is almost always caused by the MemoryPrivatePoolEnabled being set to TRUE. It should never be set to TRUE. But before you try to fix this, we could really use a copy of your crash logs to help us work on a fix. See here for steps to collect your crash logs, then attach those logs to FIRE-12339.

Then, do the following:

• Make sure hidden files/folders are set to show - see here for steps.
• Browse to your user_settings folder. This is located at -
  • Windows XP: C:\Documents and Settings [USERNAME] \Application Data\Firestorm\user_settings
  • Windows Vista, 7, or 8, 8.1, and 10: C:\Users [USERNAME] \AppData\Roaming\Firestorm\user_settings
  • Mac: User/Library/Application Support/Firestorm/user_settings
  • Linux: ~/.firestorm/user_settings
• In the user_settings folder, find the file named “settings.xml”
• Open settings.xml in a text editor - For Windows, Notepad++ is ideal for this
• Search settings.xml for the term MemoryPrivatePoolEnabled
  You will see a block of text like so:

<key>MemoryPrivatePoolEnabled</key>
<map>
<key>Backup</key>
<boolean>0</boolean>
<key>Comment</key>
<string>Enable the private memory pool management</string>
<key>Type</key>
<string>Boolean</string>
<key>Value</key>
<boolean>1</boolean>
</map>

• Near the bottom there, change the “<boolean>1</boolean>” line just above </map> to “<boolean>0</boolean>”
• Save changes to settings.xml and edit the text editor.
• Login.
• Profit.

Issues outside of Firestorm can, and often do, result in viewer crashes….

• Make sure your file system is not corrupt by running chkdsk or equivalent for your OS.
• On Windows, ensure that your registry isn't messed up by running CCleaner or similar.
• Reboot your PC and moder/router.
• Ensure that video drivers are current, as well as your OS.
• Do a Reinstall of Firestorm. Be sure to use a fresh download of the viewer; either clear your browser cache or use a different browser for the download.

• If the installer does not run at all, try the following steps (this solution was described for Vista SP1; it has not been confirmed for other Windows versions):
  • Right click the installer .exe
  • Click Properties
  • On the bottom of the general tab is a message “This file came from another computer and might be blocked to help protect this computer”
  • Click Unblock
  • Installer should run.
• You may have corrupt registry information; refer to this page. This is especially common for those rolling back from Win10 to an older version of Windows.
• If you crash at startup with an error like: “failed to initialise properly code (0x0150002)”, or you get an error that the “side-by-side” configuration is incorrect, or“Firestorm failed to start because the application configuration was incorrect. Reinstalling the application may correct the problem”, please download this and install it, as your system is likely incompatible with the Visual Studio C++ 2005 SDK DLLs: AppFix.exe
• Open the Firestorm install folder and search for any files named .config - delete any you find.
• Note that some anti-virus software will result in errors during installation; more information is here.
• If you are using an ATI (AMD) graphics card, then please refer here for known problems with these cards.
  For nVidia issues, plese refer to this page.

If you are using Windows 10, and have an Intel 2000/3000 or older graphics card, please refer to this page if you cannot start Firestorm without crashing.

If you crash during login, then try setting Firestorm to XP compatibility:

• Locate your desktop shortcut for Firestorm
• Right click on the icon and select Properties
• Select the Compatibility tab
• Check the “Run this program in compatibility mode for:” and select Windows XP from the drop down
• Click Apply.

If you get a User Account Control security popup, then please see this page.

If you have just installed Firestorm on a linux system and it will not start, it is highly likely that you are missing some required libraries. You need to verify if this is the case.

You need to open Terminal and cd to the Firestorm install directory. If you are unsure how to locate it, use your linux file manager to find it first; it will help you locate the install directory. Useful shorcuts:

• ~/ - is your home directory
• ~/Desktop - is your desktop directory

so for example, from terminal, you would do something like this:

cd ~/Firestorm

Assuming that Firestorm is installed in the directory called Firestorm, in your home.

Once there, copy the following into Terminal:

LD_LIBRARY_PATH="./lib:${LD_LIBRARY_PATH}" ldd bin/do-not-directly-run-firestorm-bin 

This will spit out a long list of libraries. Check to see if any are marked as “not found”. If so, you will need to install these with your package manager.

• Language default: Choose System Default or the language of your choice from the drop down menu.

• Content Maturity Rating: Allows you to choose what maturity level of content you are able to access in-world:
  • General, Moderate and Adult: Allows access to all content. You must be age verified to enable this option.
  • General and Moderate: Lets you access General and Moderate content.
  • General: Limits you to General content.

• Start Location: This allows you to choose what default login location shows on the login screen.
  • Show on login: Check this to enable the login location picker on the login screen.

• Name Tags: Here you choose how you display residents' tags. NOTE these apply to what you see, not others.
  • Off: Will set it so you do not see tags.
  • On: means tags will always be visible.
  • Show briefly: shows the tags temporarily.
    • And you can indicate how many second to show them; the default is 10.

• You can enable/disable the following:
  • My name: when unchecked, will not show your tag. Note this is for your view only, others still see it.
  • Group Titles: unchecked hides ALL group titles.
  • View Display Names: when checked shows display names.
  • Highlight friends: colors tags of those on your friends list.
  • Legacy nametag positioning: If enabled, the nametag will stay fixed at the avatar position and not follow the avatar head if it moves because of animations.
  • Show avatar complexity: Shows avatar complexity information in name tags. ¹⁾
    • Only if too complex: Only shows the information if the complexity value is above your maximum complexity setting, in Preferences → Graphics → General.
    • Show own complexity: Shows your own complexity in your name tag.
  • Usernames: when checked shows usernames names.
  • Hide own group title: If enabled, this will hide your current group title from others. (Versions after 3.2.2 only.)
  • Legacy names instead of usernames: will show legacy names instead of user names.
  • Trim 'Resident' from legacy names: self explanatory. (Greyed out if the option above is disabled.)
  • Show autorespond mode in nametag: This will show whether you have autorespond enabled, in your name tag.

• Away Time out: Will set you to away if there is no mouse or keyboard input for the minutes set:
  • 2 minutes
  • 5 minutes
  • 10 minutes
  • 30 minutes
  • 60 minutes
  • never
• Sit when away: Will sit your avatar when in away mode.

• Log out after being away: Will log you out after being away for the number of minutes you set here:
  • 2 minutes
  • 5 minutes
  • 10 minutes
  • 30 minutes
  • never

• Language default: Choose System Default or the language of your choice from the drop down menu.

• Content Maturity Rating: Allows you to choose what maturity level of content you are able to access in-world:
  • General, Moderate and Adult: Allows access to all content. You must be age verified to enable this option.
  • General and Moderate: Lets you access General and Moderate content.
  • General: Limits you to General content.

• Start Location: This allows you to choose what default login location shows on the login screen.
  • Show on login: Check this to enable the login location picker on the login screen.

• Name Tags: Here you choose how you display residents' tags. NOTE these apply to what you see, not others.
  • Off: Will set it so you do not see tags.
  • On: means tags will always be visible.
  • Show briefly: shows the tags temporarily.
    • And you can indicate how many second to show them; the default is 10.

• You can enable/disable the following:
  • My name: when unchecked, will not show your tag. Note this is for your view only, others still see it.
  • Group Titles: unchecked hides ALL group titles.
  • View Display Names: when checked shows display names.
  • Highlight friends: colors tags of those on your friends list.
  • Legacy nametag positioning: If enabled, the nametag will stay fixed at the avatar position and not follow the avatar head if it moves because of animations.
  • Show avatar complexity: Shows avatar complexity information in name tags. ¹⁾
    • Only if too complex: Only shows the information if the complexity value is above your maximum complexity setting, in Preferences → Graphics → General.
    • Show own complexity: Shows your own complexity in your name tag.
  • Usernames: when checked shows usernames names.
  • Hide own group title: If enabled, this will hide your current group title from others. (Versions after 3.2.2 only.)
  • Legacy names instead of usernames: will show legacy names instead of user names.
  • Trim 'Resident' from legacy names: self explanatory. (Greyed out if the option above is disabled.)
  • Show autorespond mode in nametag: This will show whether you have autorespond enabled, in your name tag.

• Away Time out: Will set you to away if there is no mouse or keyboard input for the minutes set:
  • 2 minutes
  • 5 minutes
  • 10 minutes
  • 30 minutes
  • 60 minutes
  • never
• Sit when away: Will sit your avatar when in away mode.

• Log out after being away: Will log you out after being away for the number of minutes you set here:
  • 2 minutes
  • 5 minutes
  • 10 minutes
  • 30 minutes
  • never

First of all, relog then test the HUD(s) 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 HUDs there. This will rule out technical problems with the original region.
  • If you have RLV enabled, disable it (Preferences → Firestorm, top option), relog, then try again.

Stay in a script-enabled region to do all of the following:

• Attempt to get scripts running:¹⁾
  • Try removing and reattaching the HUDs.
  • If the HUDs 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).

• Identify broken HUDs:
  • Try removing all the HUDs and testing them one at a time: test each one, then remove it, then test another.
  • If you have original copies of the HUDs, try detaching the ones you are currently wearing and using a fresh copy from the original.
  • If a HUD 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 HUDS and the body parts – every part, from scratch.

• 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.²⁾
  • 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:
  1. Rez a fresh cube
  2. Add the default script to it
  3. Take it into inventory
  4. Attach it to a HUD point
  5. Touch the HUD and see if there is script output in Local chat.

These classes are based on our official Firestorm release and are conducted in voice and 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, http://maps.secondlife.com/secondlife/Firestorm%20Social%20Island/250/6/4001
• JU: Junkyard University, http://maps.secondlife.com/secondlife/Junkyard%20Blues%20South/68/124/22

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

*All times SLT*

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:
  • 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 sounds is going to the correct device (ie, speakers or headset), and so on;
  • 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.

• 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.

• 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”
• 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 Flash Player or Quicktime can not be executed, and you may see a message saying: Adobe Flash Player or an HTML5 supported browser is required for video playback.

• 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)
• Relog and attempt video playback again
• If it works, you will need to stop your firewall/virus protection from blocking the slplugin file by granting it 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 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.

• 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.

• 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.

• The Quicktime plugin is bundled along with CEF in this version of Firestorm.
• You also must have Quicktime installed on your computer for the plugin to work in the viewer. Please note, however, that due to security issues with Quicktime (see this security alert), it is NOT advised for Windows users to have Quicktime installed.
• We expect that Linden Lab will soon be removing all support for Quicktime media.

If you are still using Quicktime media and you have issues watching movies (as opposed to YouTube videos) it might help to clear your QuickTime cache:

• Open the QuickTime player
• Click on Edit → Preferences → QuickTime Preferences → Advanced Tab → Empty cache
• Click on Apply then Ok and reboot your computer

• 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.)

Refer to this page for all Win10 issues.

Please ensure that you have the most recent version of Flash for Safari installed. You can get this via the normal update process, or from Adobe.

For streaming music on OS X 10.9 Mavericks, please refer to this page.

For users on Sierra, there are reports of media features (such as MOAP, TVs, web search, and web profiles) working more slowly. Ref. BUG-40552.

Both the 32-bit and 64-bit versions of Firestorm for Linux require 32-bit libraries to function. See this page for a link to your Linux flavor to verify you have all the needed audio-related packages installed and to troubleshoot stream issues.

For an introduction to the basics of troubleshooting, please refer to this page.

Phoenix has some video tutorials on YouTube; you may want to visit and bookmark the Phoenix Viewer channel.

• Firestorm 64-bit

• Updating the viewer

• Crashing During Install or Startup

• Crashing While Running Firestorm

• Login Failures

• Texture Discarded Due to Insufficent Memory

• Graphics Glitches and Crashes

• How to Manually Clear Cache

• Clearing settings manually

• Full Clean Install of Firestorm

• Media Related

• Web Feed Items (Search, Web Profiles, or Destinations) Don't Work, Remain Black

• Voice Related

• Bridge Issues

• Camera is Pointing Wrong

• Friends/Groups Detached from Conversations

• Nearby Chat Detached from Conversations

• Firestorm Locks Up on "Initializing VFS"

• Hands Flickering

• I Can't See Worn Mesh

• I Cannot Log in Unless I Clear Cache First

• Clicking on a SLURL Doesn't Activate Firestorm

• AO Folder issues

• Finding a Missing Window

• My Friends List is Empty!

• The Viewer Seems to Freeze Every So Often

• How do I Get Rid of all this Debug Stuff?

• Issues Related to Shadows

• Large Flexi Prims, Like Tree Fronds, Vanish

• Objects Vanish

• Small Prims Vanish Even when Quite Close

• Making WindLight Setting Persist after Teleport

• How do I Derender/Re-render things?

• Restore to Last Position - Workaround

• My avatar won't move

• My saved outfit is empty

• My HUDs Aren't Working

• Attachments Detach then Reattach at Login

• Current Outfit Folder Corruption

• My feet are in the ground, or I'm floating

• I Am Missing Inventory

• Rezzed Items Have Vanished

• Help! I'm Wearing my Entire Inventory!

• Failed to Find Item in Database

• Fixing Avatar Issues - Cloud, Ruth, Clothing not rezzing

• I Can't Log In Because It Says I am Already Logged In

• Persistent Typing Animation

• Stuck Inventory Folders Work-Around

• I am Stuck Running

• Why Does Teleport Fail so Much?

• Worn Attachment not Showing as Worn in Inventory

• HTTP Inventory Issues

• Determining Optimal Bandwidth Setting

• HTTP Fetching Issues

• I See Everything Grey

• Why am I so Laggy?

• ATI Graphics Issues

• Intel Graphics Issues

• Nvidia Graphics Issues

• Everything is Black

• I See Things Like Stars in the Sky

• My CPU is Always at 100%

• Laptop Dual Graphic Card Issues

• Crashing While Editing or Wearing Mesh

• Edit Rotation Guides Missing

• Problems Navigating in Mouselook

• Firestorm Won't Open on my Secondary Monitor

• Windows 10 Issues

• Webroot and SL Viewers

• Viewer Not Responding - Vista/Win7 64-Bit

• "Display driver stopped responding and has recovered" error in Windows

• I Get a User Account Control (Security) Pop-up

• Frame Load Interrupted by Policy Change

• Copy/Paste No Longer Works

• Clicking on a Link in Firestorm Causes a Crash

• Error Importing itdownload.dll

• Failed to Decode Login Credentials

• Firestorm Flagged as a Virus or Malware

• No Mouse Cursor - Vorpx Incompatibility

• Mac OS X 10.5 Leopard Problems

• Mac OS X 10.9 Mavericks Problems

• Mac OS X 10.10 Yosemite

• Mac OS X 10.11 El Capitan

• Mac Sierra (10.12) Issues

• Crash on Upload

• Linux: Left Mouse Button Stops Working

• Alt-Click Not Working on Ubuntu

• Linux: Wrong Browser being opened

• 32-bit Firestorm on 64-bit Linux

• How to Minimize Firestorm when Running Fullscreen in Linux

• Screen Tearing with Ubuntu 14.04 (or derived, like Mint 17)

• Chat Lag

• "Couldn't convert the image to jpeg2000"

• DNS Fail when Trying to Log in

• I Can't Sit on Things

• How to Get Inventory Back

• Logging in at 10,10,10

• The "ExDepart Virus"

• Offline Instant Messages not delivered to email

• Web Profiles Not Displaying Properly

• Deleting Stored Passwords