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.

In both cases, using a cleaner program like Revo/IOBit is completely useless as the hidden folders are not created during the install process but when you run Firestorm for the first time.

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.

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.

If you can turn in circles but not move forward/backwards, you probably have Movelock enabled.

• Go to the Avatar menu→ Movement submenu and make sure Movelock is not ticked.
• See Movelock info for more information or if you are unable to change the Movelock setting.

However, there are a few other things to try:

• Go to a different region and see if you are able to move there. If so, something at your original location is causing the problem.
• If you are using a LAQ mesh head, make sure you don't have the Pose feature turned on.
• Make sure you don't have some other HUD with a pose feature. (For instance, one user has reported this problem with the Lelutka Axis face HUD.)
• If you can't find what attachment is causing the problem, try going to Advanced menu (Ctrl-Alt-D ) → Release Keys.
  • Note: Release Keys will be greyed out if RLV has locked any of your attachments. To disable RLV, go to Prefs → Firestorm → Extras, untick the top item, and then relog.
• Make sure you don't have the Firestorm pose stand active.
  • If you have the Pose Stand button on your toolbar, make sure it's not “on.”
  • If you don't have the button, go to Avatar menu → Toolbar Buttons, drag the Pose Stand button out to your toolbar, and make sure it's not “on.”

• Tap your PageDn key and see if the animation stops. If it does, you were in crouch.
• Try Avatar menu → Avatar Health → Stop Animations & Revoke Permissions.
• Try right clicking your avatar → Reset Skeleton & Animations.
• If the above items did not work, go to a different region and try them again.
• If you have the animation in your inventory, play it from inventory, then click Stop.
• Remove attachments one by one until the animation stops. (This will eliminate worn items as a cause.)
  • Note: Animations can be in ANY attachment. Please don't assume that any particular attachment is not the problem. Take them all off.
  • Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Make sure the Firestorm AO is off:
  • On the AO button on your toolbar, untick the checkbox.
  • Note: The Firestorm AO can be active even if the button is not on your toolbar. If it is not on your toolbar, go to Avatar menu → Toolbar Buttons, drag the AO button out onto your toolbar, and make sure it is not ticked.

• If you know that a “sittable” item gave you the animation:
  1. Go to Preferences → Firestorm → Protection → Revoke Permissions.
  2. Temporarily set this to “Revoke on Sit and Stand.”
  3. Sit on the item, then stand. This should stop the animation.
  4. Change Preferences → Firestorm → Protection → Revoke Permissions back to either “Never” or “Revoke on Stand.”

• Try Advanced menu → Release keys. (After doing this, you will need to recreate the FS bridge: Avatar → Avatar health → Recreate LSL Bridge.)

• You may simply be experiencing lag: See Troubleshooting Lag for tips to reduce this.
• Many pose balls will request permission to animate you. If you did not see the animation request, look in your Notifications window for the message. Click “Accept.”
• Make sure you have not blocked the item or its owner: Look in Comm menu → Block List, see if the item or the item's owner is there, and remove the item/person from the block list.
• Go to Preferences → Firestorm → Protection → Revoke Permissions. For normal use, this should be set to either “Normal” (no protection) or “Revoke on Stand.” It should normally NOT be set to “Revoke on Sit” or “Revoke on Sit and Stand,” as both of these will prevent items from animating you when you are sitting.

Remove all attachments, then add one by one, testing in between to see if one causes the problem.

The TMP “Legacy” body HUD is known to cause this problem. Turn off the cam control located on the HUD.

“Rubber-banding” is when you try to walk forward and then suddenly snap back to a previous position. Sometimes you will seem unable to stop walking. This is caused by region lag, when the server can't keep up with processing avatar movement (collisions).

• For info about region lag see here: Region Lag
• For some things that region or parcel owners can do to reduce region lag see here: Reducing Server Lag.

This typically happens when you have two or more conflicting AOs (animation overriders) on.

• Start by removing known AOs until you are wearing only one known AO.
• If that doesn't help, start by removing other HUDs, then all other attachments, one by one, until it stops. Any worn item can contain an animation, so don't assume that some items are “ok.”
• Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Try turning the opposite direction to the spin.
• Try pressing BOTH right and left arrow keys at the same time, repeatedly.
• Relog.

• Remove other attachments that contain animations.
• Remove or turn off ankle-locks.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

For unknown reasons, some users need to change an additional setting:

Go to Preferences → Privacy → Lookat, and tick “Don't send any look at targets at all, even to myself”

• In most cases, pressing Ctrl-R to toggle run mode will get you back into walk (though it may in some cases be necessary to hit Ctrl-R more than once).
• If you are wearing a scripted AO (animation overrider), turn off any “running” features it has.
• If you are using the Firestorm built-in AO (animation overrider), make sure there are no running animations in the “Walking” or “Standing” categories.

After Strafe

Ref. BUG-6825

In one specific case, the above will not work. Specifically:

• You have Preferences → Move & View → Movement → Tap-tap-hold to run enabled.
• Press shift, then tap-tap-hold the left or right arrow key

That gets you running sideways. If you release shift before the arrow key, you will be stuck running.

To stop running, you have to repeat the sequence: press shift, then tap-tap-hold left or right arrow.

• Go to Preferences → Sound & Media → Voice, and deselect “Move Avatar Lips When Speaking.” Note: This is the only viewer feature that affects lip movement.
• If you are wearing a mesh head, turn off any animations in the head. For more help, ask the support group for that head.
• Go to Comm menu → Gestures. Tick “Active only” at the bottom of the window. Review the list for any gestures that might contain a face animation. If in doubt, turn them all off, one at a time, to find the one responsible for the lip movement.

This is a known SL bug also affecting the SL viewer. Refer to this SL bug report for more information.

Please note that this problem is not with Firestorm, or any viewer. We are providing this information here for your convenience. Refer to Second Life bug report BUG-225668.

The problem has a number of possible causes. Please work through the following:

Test One: Do you have more than one computer in the house connected to your home network? If so, are you getting the clock login error on all your computers or just one specific machine?

• If you get the error on only one computer, go to “A) Computer-Related Issues,” below.
• If you get the error on all your computers, skip to “B) Network or Internet Issues,” below.

Test Two: If you have a cell phone that has internet access, connect the problem computer to the cell phone's Internet connection (MiFi or mobile hotspot etc) & see if that allows you to log in to SL without getting the clock error.

• If you still get the error, go to “A) Computer-Related Issues,” below.
• If you no longer get the error, skip to “B) Network or Internet Issues,” below.

• Go to https://time.gov and double check that the time and date is in fact set correctly on your computer. (It should be within 5 seconds of accuracy to the official time.)
• Double check that the correct year is also set.

If you have the error on only one computer, test that your CMOS battery is still working. Ref: https://www.quora.com/What-is-a-CMOS-battery-What-are-its-functions

Other programs on your system may be injecting their own certificate.

There's a fairly easy way to confirm this:
1. Launch the Chrome web browser
2. Navigate to https://secondlife.com
3. Log in
4. Once logged in click on the padlock icon at the top left of the browser, in the URL entry field.
5. After clicking the padlock, click Certificate, then General tab.
6. The correct SL certificate is signed by Digicert for SecondLife.com and expires Oct. 21, 2019

(If you're using FireFox, it's a similar process.)

Test this by temporarily disabling your Anti-Virus/Firewall protections, rebooting the computer and then try to log in to Second Life. If you try this, please completely close all other open programs first so that nothing is trying to get on the internet while your security is disabled.

If you still get the computer clock login error, then something else is the problem.

“Search Awesome”: See

• https://community.secondlife.com/forums/topic/430438-login-issues/
• https://www.bleepingcomputer.com/virus-removal/remove-search-awesome-adware
• https://blog.malwarebytes.com/detections/adware-searchawesome/

AMD Ryzen Series 3000 CPUs (and possibly others) appear to have problems that may cause this. Ref.:

• AMD Admits Ryzen 3000 Series CPUs are Broken, promises BIOS update
• AMD Ryzen 3000 series CPUs will not be able to boot modern Linux distributions for another "few" weeks
• Thread on the Linux Kernel Mailing List

If you fall into this category, make sure that:

• Your BIOS is up to date (software)
• The amd64-microcode package is present and up to date on your system.
• Try running Firestorm from the command line like this: “export OPENSSL_ia32cap=~0x4000000000000000 ; ./firestorm”

If you are logging into Second Life through a public wi-fi connection with a proxy or portal that requires you to log in or accept their Terms of Service before you can fully utilize their Internet, you must open a browser and try loading a website like “http://space.com” and then see if the portal opens. If so, log in to that first, and then try to log in to Second Life.

Consider whether you have changed anything at your end that coincided with this problem starting; for instance got a new computer, moved house, changed ISP, installed new router/cable modem hardware, changed any router firewall settings, changed antivirus or any other security software, or installed any new 3rd party software on your computer (especially anything that could affect your connection or security settings or anything that describes itself as “Game mode” or “Game optimizer”).

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.

Things to try:

• Disable RLV if you have it enabled. Go to Preferences → Firestorm → Extras → “Enable Remote Scripted Viewer Controls (RLVa)”, disable it if it is enabled, 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.

• There may be a problem with your connection. 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.

• If you crash or get logged out on all or most TPs, then you may need to add new DNS numbers in your system's networking settings. Mac users may also be experiencing other issues like an empty friends list or trouble viewing rigged mesh. Please see 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.

• 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 Avatar → Avatar Health → Scripts. 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.

¹⁾ 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 AOHUD.

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

For up to date information on how to manage your SL Marketplace listings, it is best to consult SL documentation directly:

• Selling in the Marketplace

There are several reasons why you would want to file a JIRA:

• To request a new feature
• To request an improvement
• To report a bug
• To request support

In order to do anything except view Firestorm issues, you will need an account on JIRA. Creating an account is very easy. Start by going to the Sign Up page and enter the following information:

• Username - This can be anything, but we prefer that it be your SL username. Don't use spaces, but you can use a period to separate words, such as beta.tester. This is what you will use to log into JIRA.
• Password - This needs to be at least 8 characters in length, and shouldn't be the same as any other password you use.
• Confirm Password - Type in your password again
• Full Name - This should be your full SL name. If your username was beta.tester, your full name would be Beta Tester. This is what everyone will see when you create a JIRA or comment on one, so do not use your real name.
• Email - Enter a valid email address. JIRA can send you emails when someone comments on your JIRA or on issues you've “watched”.

Click Sign up and you're all set. If JIRA complains, fix the entries it complains about and then click Sign up again.

No matter what kind of issue you want to create, the process is nearly identical and starts with going to the JIRA Dashboard and clicking the Create Issue link near the top of the page (every page), on the right side of the red menu line. If you don't see that there, you need to log in - click Log In at the top right, enter your username and password and then click Log In.

Clicking Create Issue opens a small box with Project and Issue Type selections. There are a lot of choices, here's a list of the most common:

• Requesting a new feature
  • Set the Project to Firestorm ¹⁾ and the Issue Type to New Feature.
• Requesting an improvement to existing code
  • Set the Project to Firestorm ²⁾ and the Issue Type to Improvement.
• Reporting a bug
  • Set the Project to Firestorm and the Issue Type to Bug.
• Requesting Support
  • Set the Project to Support and the Issue Type to Support Request.

Then click Create. This will bring up the Create Issue page. From here the fields and the information that goes in them are the same regardless of what type of issue you want to create.

• Summary - Enter a brief overview of the problem. You don't have to put everything here, just a few words to summarize the issue.
• Priority - By default this is set to Major, and it can remain that way. If you are reporting an issue that is preventing you from logging on at all with any of our viewers, you can choose Blocker. But if you spotted a typographical error, that's probably something minor or even trivial. If you put in the wrong priority, don't worry, we'll work with you as needed to set it correctly.
• SL Avatar Name - Set this to the name of the avatar that is affected.
• Patch Attached - If you're submitting a patch that would add a new feature, improve on an existing one or correct a bug of some kind, check this box. Otherwise, leave it unchecked.
• Reported In - Select the viewer that you're using. This can either be the one with the problem or some other version.
• Affects Versions - Here you would want to identify all the versions that you know are affected. For example, if you have a problem that shows up in every one of our Release versions of Firestorm, you would want to list them all. If you don't know, then list only the version you're using.
• Environment - This is very important for Support requests and bug reports. We need to know what your system looks like to the viewer. To get this information, open the viewer, click on the Help menu and select About, and then click Copy to Clipboard. Then click into the Environment field in the JIRA page, right-click and choose Paste (or press Ctrl-V).
  Note here that if you're creating anything other than a Support request, this information is visible to everyone. You can delete your location details if you wish.
• Description - Here is where you want to put as many details as you can about the issue. If you're reporting a bug, or if you have a problem that you can reproduce consistently, you want to include the steps you take to reproduce that. Also include details such as whether this affects only one avatar, whether it happens on more than one computer (we'd like system information for each computer in that case) and so on. If you get error messages, be sure to write the exact message (as closely as possible).
• Attachment - Add files that you have that can help further explain the issue, such as images or videos, use the Browse button to add them. Remember that the maximum file size is 10MB, and images must be either JPG or PNG.

Another very useful bit of information is your viewer logs. These can sometimes be very helpful in finding the root cause of a problem and crafting a solution. Logs should be collected after having logged out - or after a crash if that is your issue - and before restarting the viewer. If you log in again then the logs won't have any of the clues needed.

In its default location, the logs folder is hidden on most systems. To find it, you will need to show hidden folders. The logs folder is in:

Compress all the files in the folder named “logs”:

• Windows: Right-click on the folder and choose Send To > Compressed zip file
• Linux Gnome: Right-click on the folder and choose Compress
• Linux shell: tar -cjvf “Viewer_logs.tar.bz2” ./logs/
• Mac: Hold Shift while highlighting the contents of the folder and then Ctrl-click and choose Compress Items

You may want to move this compressed file to your Desktop.

NOTE 1: If you have a large number of accumulated files in your Logs folder, the compressed file may be too large to attach to the Jira ticket. If this happens, delete most of the subfolders starting with “dump,” keeping only the latest one.
NOTE 2: Alternatively, delete the entire Logs folder, log back in on Firestorm and reproduce your problem, log out, then compress the new Logs folder that has now been created.

To attach logs to an issue filed earlier, go to More Actions → Attach Files. Then click Select Files button, locate your compressed file (on your Desktop if you moved it there) and then click Open or OK. You may optionally add a comment at the same time. Finally, click Attach

Now that you have all fields filled, out go back and check to make sure you haven't left anything out and made all the selections needed. Once you are done checking it over click the Create button. If after double checking your ticket you decide not to file the ticket just click the Cancel button.

Once the JIRA has been created you'll be shown the issue number. It will be in the form of the project abbreviation, like SUP or FIRE, and a number (example: FIRE-1234). Only you and team members can view your own SUP issues.

You'll also get an email when someone comments, when something is attached or when some other action takes place. Click the link in the email (it looks just like the issue number you got initially) and comment in the issue itself. Do not reply to the email, it will not work.

If you don't get any emails, they could be filtered as spam or the email address you supplied is incorrect. You can confirm your email by going to your profile and then clicking the little edit pencil along the Details line.

Further reading: How to Report Bugs Effectively

Firestorm publishes our source code open source under the LGPL license for others to review, use, and improve. We've tried to make it as easy as possible to get involved and help make improvements. We believe that the more people work together, the faster the progress. We hope that people will contribute directly, but we're also happy when our work is reused in other new places. We hope that when people use our code in other projects they will do a few simple things that allow us to collaborate for mutual benefit.

If you're planning to use Firestorm's code in another project, please do contact us and say “hello”! It's good to know other people that may be able to answer particular questions, may have specific areas of expertise, or may otherwise be able to collaborate in new ways. We also might be able to provide additional information of interest to your project beyond what's on our wiki and code repository. You can email us at admin@phoenixviewer.com.

Credits are very important to open source developers! We would like to make sure we fully credit authors whose code we use, and hope that others will do the same.

If you use Firestorm's code, please make sure you preserve credits for the specific original author. The preferred way to do this would be:

• If there's a copyright © notice in the code you're using, please do not remove any part of the copyright line.
• If your project has a help/about window popup, please list the author there, otherwise list it in the places where you would normally list credits.
• If your project has a code repository, mention the original author in the appropriate commit message.
• If you use a Firestorm-derived feature and prominently mention the feature in promotional interview, journalist piece, web info page, or similar publication, please mention the original author.

If you can't determine the original author, ask us and we'll help you find out. Please do not just say “Firestorm” in your credits, always use the actual author's preferred name of record. It's polite, but not required, to also add “(Firestorm)” after the author's name if that code came from the project's source respositories.

We strive to follow the same guidelines with respect to other authors and other projects. If you have corrections or suggestions, please create a ticket at jira.phoenixviewer.com.

Firestorm uses Linden Lab's snowstorm repository under the LGPL license, and publishes our own code under the LGPL license in return. Similarly, many other snowstorm-based third party viewer projects also share their code under the LGPL so that we can share and maximally take advantage of each other's work.

We hope this convention continues, and projects that use our code will also choose to share back their work under the same license so others may benefit.

Firestorm makes our in-development repository public. However, we request that none of the in-development, unreleased features are copied from our repository and released elsewhere ahead of our release schedule, without permission. Generally if we are developing a new feature that doesn't exist anywhere, please don't copy our own code and release it ahead of us. We have agreements with other major third party viewer projects that we won't do this to each other.

If you don't know if a feature has been released or not, check the contents of /indra/VERSION in the respository at the time the feature was added. If the version number here is higher than our released binaries on www.firestormviewer.org, the feature is still in-development. You can also ask anyone on our team, which is a nice practice anyway.

If your project has a public source code repository and you're using Firestorm code, we'd appreciate if you commit Firestorm-derived changesets in a way that is clearly labelled. This helps us better find any interesting, useful improvements that you might have made, or just have another example of how the code can be used.

Please don't call your project something so similar to Firestorm that people would think our projects are related. Likewise, please don't use Firestorm icon logos in your projects.

Good luck, development neighbor! We hope to see you around!

This page describes all necessary steps to build the Firestorm viewer for Windows, using the updated build infrastructure introduced with Linden Lab's project Alex Ivy.

This is needed for compiling any viewer based on the Linden Lab open source code and only needs to be done once.

All installations are done with default settings (unless told explicitly) - if you change that, you're on your own!

• Install Windows 10 Pro 64bit using your own product key
• Alternatively: Install 8.1 Pro 64bit

• Install Visual Studio 2013 Professional
• Note: If you don't own a copy of Visual Studio 2013 Professional, you might consider installing the Community version (requires creating a Microsoft account if you do not already have one ) (If the download link for 2013 on visualstudio.com leads to a dead page even after logging in and out and back in again, try Googling “Visual Studio 2013 Community update 5 download” for a direct link. MS has recently changed things with accounts and the free subscriptions.)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • Uncheck all the “Optional features to install:” - they are not required

• Download and install DirectX SDK (June 2010)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • At the Installation Options screen, set everything except the DirectX Headers and Libs to “This feature will not be installed”

• Download and install TortoiseGit 2.9.0 or newer (64bit)
  • Note: No option available to install as Administrator
  • Use default options (path, components etc.) for Tortoise Git itself
  • At some point, it will ask you to download and install Git for Windows
    • You can install with default options EXCEPT when it asks for “Configuring the line endings conversion”: You MUST select “Checkout as-is, commit as-is” here!

• Download and install at least CMake 3.8.0
  • Run the installer as Administrator (right click, “Run as administrator”)
  • At the “Install options” screen, select “Add CMake to the system PATH for all users”
  • For everything else, use the default options (path, etc.)
  • Make sure that the following directory was added to your path:

    C:\Program Files (x86)\CMake\bin

• Download and install Cygwin 64 (64bit)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • Use default options (path, components etc.) *until* you get to the “Select Packages” screen
  • Add additional packages:
    • Devel/patch
  • Use default options for everything else
  • Make sure that the following directory was added to your path.:

    C:\Cygwin64\bin

• Download and install the most recent version of Python 2.7 (32bit)
  • Linden Lab advises to use the 32bit version as the VMP requires it. However, Firestorm currently doesn't use VMP, so the 64bit version might work (use at own risk!)
  • Note: No option available to install as Administrator
  • Use default options (path, components etc.) until you get to the “Customize Python” screen
  • Change “Add python.exe to Path” to “Will be installed on local hard drive”
  • Add the Python installation dir to the system path:

    C:\Python27

Confirm things are installed properly so far by opening a Cygwin terminal and enter:

cmake --version
git --version
python --version

If they all report sensible values and not “Command not found” errors, then you are in good shape.

• Install Boostrip pip
  • Download (Save As) get-pip.py and copy to a temp folder
  • Open Windows Command Prompt
  • Switch to that temp folder and execute it:

    python get-pip.py

  • Pip will be installed
  • Add the following directory to your path:

    C:\Python27\Scripts

• Install Autobuild
  • Open Windows Command Prompt and enter:

    pip install git+https://vcs.firestormviewer.org/autobuild-1.1#egg=autobuild

  • Autobuild will be installed. Earlier versions of Autobuild could be made to work by just putting the source files into your path correctly; this is no longer true - Autobuild must be installed as described here.

• Set environment variable AUTOBUILD_VSVER to 120

• Check Autobuild version to be 1.1.7 or higher:

  autobuild --version

• If you plan to package the viewer and create an installer file, you must install the NSIS from the official website.
• Not required unless you need to build an actual viewer installer for distribution, or change the NSIS installer package logic itself

In order to make it easier to build collections of related packages (such as the viewer and all the library packages that it imports) with the same compilation options, Autobuild expects a file of variable definitions. This can be set using the environmenat variable AUTOBUILD_VARIABLES_FILE.

• Clone the build variables repository:

  git clone https://vcs.firestormviewer.org/fs-build-variables <path-to-your-variables-file>

• Set the environment variable AUTOBUILD_VARIABLES_FILE to

  <path-to-your-variables-file>\variables

• Start the IDE
• Navigate to Tools> Options> Projects and Solutions> Build and Run and set maximum number of parallel projects builds to 1.

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. For this document, it is assumed that you created a folder c:\firestorm.

c:
cd \firestorm
git clone https://vcs.firestormviewer.org/phoenix-firestorm

This can take a bit, it's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

If you want to use FMOD Studio to play sounds within the viewer, you will have to download your own copy. FMOD Studio can be downloaded here (requires creating an account to access the download section).

c:
cd \firestorm
git clone https://vcs.firestormviewer.org/3p-libraries/3p-fmodstudio

• After you have cloned the repository, copy the downloaded FMOD Studio installer file to C:\Firestorm\3p-fmodstudio
• If you downloaded a different version of FMOD Studio that is currently used in the viewer, you will have to modify the file build-cmd.sh in the root of the repository. Right at the top, you find the version number of FMOD Studio you want to package (one short version without separator and one long version). Change these values to the version you downloaded:

FMOD_VERSION="20003"
FMOD_VERSION_PRETTY="2.00.03"

Continue on the Windows command line:

c:
cd \firestorm\3p-fmodstudio
autobuild build --all
autobuild package

While running the Autobuild build command, Windows might ask if you want to allow making changes to the computer. This is because of the FMOD Studio installer being executed. Allow these changes to be made.

Near the end of the output you will see the package name written and the md5 hash below it:

wrote C:\firestorm\3p-fmodstudio\fmodstudio-{version#}-windows-{build_id}.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

where {version#} is the version of FMOD Studio (like 2.00.03) and {build_id} is an internal build id of the package.

cd \firestorm\phoenix-firestorm
cp autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Copy the FMOD Studio path and md5 value from the package process into this command:

autobuild installables edit fmodstudio platform=windows hash=<md5 value> url=file:///<fmodstudio path>

For example:

autobuild installables edit fmodstudio platform=windows hash=a0d1821154e7ce5c418e3cdc2f26f3fc url=file:///C:\firestorm\3p-fmodstudio\fmodstudio-2.00.03-windows-192171947.tar.bz2

Open the Windows command prompt.

If you are building with FMOD Studio and have followed the previous FMOD Studio setup instructions AND you are now using a new terminal you will need to reset the environment variable first by entering

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then enter:

 c:
 cd \firestorm\phoenix-firestorm
 autobuild configure -c ReleaseFS_open

This will configure Firestorm to be built with all defaults and without third party libraries.

autobuild configure -v -c ReleaseFS_open

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• -A <architecture> sets the target architecture, that is if you want to build a 32bit or 64bit viewer (32bit is default if omitted).
• –fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps in FMOD Studio using Autobuild for this to work.
• –package makes sure all files are copied into viewers output directory. You won't be able to start your compiled viewer if you don't enable package or do 'compile' it in VS.
• –chan <channel name> lets you define a custom channel name for the viewer
• -LL_TESTS:BOOL=<bool> controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.

Examples:

• To build a 32bit viewer with FMOD Studio and to create an installer package, run this command in the Windows command window:

  autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

• To build a 64bit viewer without FMOD Studio and without installer package, run this command:

  autobuild configure -A 64 -c ReleaseFS_open -- --chan MyViewer -DLL_TESTS:BOOL=FALSE

There are two ways to build the viewer: Via Windows command line or from within Visual Studio.

If you are building with FMOD Studio and have followed the previous FMOD Studio setup instructions AND you are now using a new terminal you will need to reset the environment variable with

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then run the Autobuild build command. Make sure you include the same architecture parameter you used while configuring the viewer:

autobuild build -A 64 -c ReleaseFS_open --no-configure

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling will take quite a bit of time.

Inside the Firestorm source folder, you will find a folder named build-vc120-<architecture>, with <architecture> either being 32 or 64, depending on what you chose during the configuration step. Inside the folder is the Visual Studio solution file for Firestorm, called Firestorm.sln.

• Double-click Firestorm.sln to open the Firestorm solution in Visual Studio.
• From the menu, choose Build → Build Solution
• Wait until the build is finished

Older versions of the viewer before the merge of Linden Lab's project Alex Ivy use Autobuild 1.0 that is incompatible with the build process as it is now. By default it is not possible to install two different versions of Autobuild on the same computer at the same time. Making use of virtualenv will overcome this problem, allowing simultaneous installations of Autobuild 1.0 and Autobuild 1.1 in two distinct “virtual” Python environments.

Install virtualenv by opening a Windows command prompt and enter:

pip install virtualenv

This requires the Boostrip pip already installed. After virtualenv has been installed, you can create virtual Python environments using the command

virtualenv <virtual-environment-name>

This will create the directory <virtual-environment-name> within the Python installation folder and add some required folders and files. Among these files is a batch file called activate.bat in the folder Scripts. To switch to the newly created virtual environment execute the activate.bat batch file. After switching to the virtual environment, your command prompt will be prepended by the name of the virtual environment.

In this example we will create a virtual environment called “Autobuild11”:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat

Your command prompt should look like this now:

(Autobuild11) C:\

After you switched to a particular virtual environment, you can now install as described in Set up Autobuild and Python.

Complete example:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat
pip install hg+https://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild

Configuring and building the viewer from the Windows command line is basically identical as described in Building from the Windows command line with the difference that you now have to call the activate script first:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE
autobuild build -A 64 -c ReleaseFS_open --no-configure

If you plan to build the viewer from within Visual Studio, you will have to configure the viewer the same way as if you were to build from the Windows command line:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

To be able to build from Visual Studio, you will have to set a Windows environment variable called VIRTUAL_ENV pointing at the virtual Python environment to use, in our example “C:\Python27\Autobuild11”. Now open the Firestorm Visual Studio solution to start Visual Studio and build the viewer.

When trying to execute the Autobuild build command, you might encounter an error similar to

../build.cmd.sh line 200: SystemRootsystem32: unbound variable

This error is caused by the order of the items in the Windows “path” environment variable. Autobuild exports all paths set in the “path” environment variable into Cygpath names and variables. Since these Windows “paths” can also contain variables like %SystemRoot% and they can also depend on each other, it is important to keep the dependency order intact. Example:

%SystemRoot%
%SystemRoot%\system32
%SystemRoot%\System32\Wbem

The following screenshot shows the correctly ordered paths containing variables and depending on each other.

• Windows updated 2020/02/07
• Mac OSX
• 64-bit Debian 8.x (jessie) - AlexIvy updated 2019/09/11
• 64-bit Debian 9.x (stretch) updated 2019/09/11
• 64-bit Debian 9.x (stretch) - AlexIvy updated 2019/09/11
• 64-bit Ubuntu 14.04 updated 2019/09/11
• 64-bit Ubuntu 16.04 updated 2019/09/11
• 64-bit Ubuntu 16.04 (AlexIvy) updated 2019/09/11
• Gentoo

If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.

A Windows 10 update in mid May 2018 (and reported as recently as May 2019) has resulted in many having audio problems with the viewer. This is actually a problem with the update, and needs to be fixed externally to the viewer.

• If your mic seems to have stopped working, try this: In your operating system, go to Settings → Privacy → Microphone and make sure “Allow apps to access my microphone” is ON.
• In addition: A user has kindly provided this link to help you check your settings in the new Windows software and resolve the issue.
• Further to this, you should also check Windows Mixer settings, since audio devices may have been reset.

If you're on an ASUS laptop and Sonic 3 is running, this is preventing FS from finding your driver. The solution is to disable Sonic 3.

If you suddenly sound like a man (and you aren't), or your friend suddenly sounds like a demon (and isn't), or you are hearing other forms of distorted voice, try this:

1. Right click the Speakers icon on your system tray and select Open Sound Settings.
2. Go to Input section and click on Device Properties.
3. Switch to the Advanced tab.
4. Under Default Format drop down menu, select: 2 channel, 16 bit, 44100 Hz (CD quality).
5. Switch to Enhancements tab.
6. Check “Disable All Sound Effects”
7. Press OK
8. Close the Setting window
9. Relog if needed.

If you suddenly find that sounds do not play, things like button sounds or in-world object sounds, the possible cause is your default output format. Try this:

1. Right click the Speakers icon on your Windows PC system tray and select Open Sound Settings.
2. Click on Device Properties in the Output section.
3. Click on Additional device settings under Related Settings.
4. Switch to the Advanced tab.
5. Under Default Format drop down menu, select: 16 bit, 44100 Hz (CD quality).
6. Click Apply and OK.
7. Relog if needed.

If some characters now display as boxes, you will need to reinstall Windows font packs. Some of the more common font packs are Chinese, Japanese and Korean, though if you installed those and still see boxes, you will want to ask the person using those characters to tell you what language (or symbol set) they are so that you can install the appropriate font pack.

1. Log out of Firestorm.
2. Go to the Windows Start menu and choose Settings.
3. In the window that opens, click in the search field at the top right and type in “language”
4. Select Add a language from the search results.
5. Click the + Add a language option and select the language from the list. The contents of the window scrolls left and right.
6. Back in the Add a language section, click the newly added language and choose Options.
7. Click the top Download button. The language will download and install, and it may take some time.
8. Repeat this for each language pack you wish to install.
9. Now log into Firestorm; you should see the missing characters correctly rendered.

Error 0xc000007b when launching 64 bit Firestorm:

Try following these steps to get the Firestorm installer to reinstall the Visual C++ redistributables that come packaged with it:

1. First make sure you have the Firestorm installer handy in a place where you can easily access it when you get to the step where it's needed below. (You can download it from here, or from here if you need an older version than the current release.)
2. Go to the Windows Start Menu and choose Settings.
3. In the window that opens, click on “System Display, notifications, apps, power.”
4. In the next window go down to “Apps & features.”
5. Scroll down to the entry for “Microsoft Visual C++ 2010 x86 Redistributable.” Click on it and choose “Uninstall” (the list won't necessarily update to show that it is uninstalled, but it is).
6. Click on “Microsoft Visual C++ 2010 x64 Redistributable” and once again choose “Uninstall.”
7. Close that window.
8. Re-run the Firstorm installer. The installer window will now say “Modify Setup” (since FS is already installed) and will give you 3 options: “Repair”, “Uninstall” and “Close.” Click on “Repair.” Firestorm will reinstall the Microsoft Visual C++ 2010 Redistributables that it ships with.
9. Restart your computer. You should be able to launch Firestorm without getting the error message now.

If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.

If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.

If you have Intel HD graphics, install the 32bit version of the viewer.

The most common cause for this is a non-default DPI value, or screen scaling. Refer to this page for tips on setting DPI/scaling to default.

First try increasing Preferences → User Interface → 2D Overlay → UI Scaling. Another possibility is Preferencess → User Interface → Font → Font size adjustment.

This is most often caused by a high DPI scaling setting, usually 125% on most 2k displays. A viewer set to the same width as the display resolution (1920, for example), would extend beyond the display border. To correct this:

• Log out of Firestorm
• Right click the Firestorm shortcut and choose Properties
• In Properties, click the Compatibility tab
• Near the bottom, find and check “Disable display scaling on high DPI settings”
• Click OK and Apply

When you launch Firestorm, it should display at the default DPI scale, 100%

Some Windows 10 updates change the machine ID used to create login credentials, resulting in Firestorm reporting “Failed to Decode Login Credentials”. The best way to deal with this is to wipe the stored credentials file, as explained here. Naturally, you will then have to retype the user name and password for all your accounts, when first logging in after deleting the credentials file.

Reported on Linden Lab's bug tracker BUG-139291

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

From the squid web page: Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid has extensive access controls and makes a great server accelerator. It runs on most available operating systems, including Windows and is licensed under the GNU GPL.

Squid can be used to have a local texture cache bigger than the viewer maximum. Use a spare 500GB drive or even a 1TB drive to cache all those SL textures for reduced bandwidth and speed up rezzing. The cache can be shared by the whole house. No more downloading the same texture for each SL user in the house.

Install or make sure Perl is working, many Linux distributions come with Perl installed. http://www.perl.org/ or the support site of your Linux install. http://www.perl.org/get.html has links for a windows version of Perl available.

Many Linux distributions come with squid proxy available by the package manager. Consult the support site for that Linux distribution (distro for lazy people) for more info.

Install squid proxy version 2.7 from http://www.squid-cache.org/ Windows binary available at http://squid.acmeconsulting.it/ Squid proxy version 3 will not work; it is missing a feature that is required to work with HTTP texture fetching. There is plenty of documentation on the squid web site and tutorials around the net on how to install squid. There is even a book on it.

Once you have squid installed or unpacked, and tested with a browser that it is working. Shut it down in order to make the following changes.

Create a file somewhere on the system, I used /etc/squid/store_url_rewrite Put in that file the following:

store_url_rewrite

#!/usr/bin/perl 
$|=1; 
while(<>){chomp;if(m/sim(.*?)\.agni\.lindenlab\.com(.*?)\/cap\/(.*?)\/\?texture_id=(.*)/){print"http://agni.lindenlab.com/texture/".$4."\n";goto STOP;}if(m/sim(.*?)\.agni\.lindenlab\.com(.*?)\/cap\/(.*?)\/\?mesh_id=(.*)/){print"http://agni.lindenlab.com/mesh/".$4."\n";goto STOP;}if(m/asset-cdn\.agni\.lindenlab\.com(.*?)\/\?texture_id=(.*)/){print"http://agni.lindenlab.com/texture/".$2."\n";goto STOP;}if(m/asset-cdn\.agni\.lindenlab\.com(.*?)\/\?mesh_id=(.*)/){print"http://agni.lindenlab.com/mesh/".$2."\n";goto STOP;}print$_."\n";
    STOP:}

• For Windows users: Save the code above into a file called “store_url_rewrite.pl” and move it to C:\squid\etc\
• For Linux users: Save the file and then make it executable with “chmod +x /etc/squid/store_url_rewrite”

Wanted: A python version of this script and other languages. Contact Liny Odell if you wish to submit a script in a different language.

Navigate to the directory you installed or unpacked squid to, example: C:\squid\etc and duplicate mime.conf.default and squid.conf.default.
Then rename these 2 files so their ending is “conf”.

Now to make the following config changes in squid.conf:

Search for the following lines and place a “#” in front of them to disable the config lines.

http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports

The should look like this or completely removed.

#http_access deny !Safe_ports
#http_access deny CONNECT !SSL_ports

If you tested squid with your browser, and received an access denied error message, then you may have to add another line to allow localhost.
See the last line in the following section:

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost  #this line was required for me to get it running

Look for the refresh_pattern section and add “refresh_pattern /cap/ 259200 20% 302400” as the first one, like this:

refresh_pattern /cap/          259200  20%     302400
refresh_pattern asset-cdn\.agni\.lindenlab\.com/.*       259200  20% 302400
refresh_pattern ^ftp:          1440    20%     10080
refresh_pattern ^gopher:       1440    0%      1440
refresh_pattern -i (/cgi-bin/|\?) 0    0%      0

The refresh line is set up to cache texture for six months. Due to LL not using Last Modify: headers, there no way for squid to tell if the texture has been changed or not. Since LL doesn't change textures at all, store them for however long is needed. The “20%” and “302400” have no effect due to when squid check freshness on a file, it has to re-download the entire file. Blame LL for this. The “302400” need to be greater then the first column, “259200”

• For Windows users:
  Copy & paste the lines below to the end of your squid.conf file, and modify paths to resemble those on your system accordingly:

# 64 GB cache size, can make larger later.
cache_dir ufs c:/squid/var/cache 64000 16 256

# disable range requests due to LL fail. No Last Modify header.
range_offset_limit -1

# this is a local cache, prevent possible error
visible_hostname MyBigCache

# this is the magic, convert the URL into something more static.
storeurl_rewrite_program C:/strawberry-perl/perl/bin/perl.exe c:/squid/etc/store_url_rewrite.pl
# increase the children to handle the default Phoenix Viewer client of 32 HTTP texture fetches in the queue.
storeurl_rewrite_children 32

# what domains to apply the store url rewrite too.
acl store_rewrite_list dstdomain .agni.lindenlab.com
storeurl_access allow store_rewrite_list
storeurl_access deny all

# dont tell http-in we are proxying or it wont work right
header_access Via deny all
header_access Forwarded-For deny all
header_access X-Forwarded-For deny all

#dont cache baked textures
acl bakeserver dstdomain bake-texture.agni.lindenlab.com
cache deny bakeserver

• For Linux users:
  Add the following lines to squid.conf

# 64 GB cache size, can make larger later.
cache_dir ufs /var/cache/squid 64000 16 256

# disable range requests due to LL fail. No Last Modify header.
range_offset_limit -1

# this is a local cache, prevent possible error
visible_hostname MyBigCache

# this is the magic, convert the URL into something more static.
storeurl_rewrite_program /etc/squid/store_url_rewrite
# increase the children to handle the default Phoenix Viewer client of 32 http texture fetches in the queue.
storeurl_rewrite_children 32

# what domains to apply the store url rewrite too.
acl store_rewrite_list dstdomain .agni.lindenlab.com
storeurl_access allow store_rewrite_list
storeurl_access deny all

# dont tell http-in we are proxying or it wont work right
header_access Via deny all
header_access Forwarded-For deny all
header_access X-Forwarded-For deny all

#dont cache baked textures
acl bakeserver dstdomain bake-texture.agni.lindenlab.com
cache deny bakeserver

After saving squid.conf, on Windows systems, open a cmd window, and run this command to initialize your previously defined cache directory:

C:\squid\sbin\squid.exe -z

Start up squid proxy (c:\squid\sbin\squid.exe on Windows).

• Start up Firestorm.
• Ctrl-p to bring up Preferences.
• Under the Network & Files -> Connection tab, click on the Adjust proxy settings button; this opens the window shown below.
  

• Enable Use HTTP Proxy for Web Pages
• Add the hostname or ip-address of the squid proxy to the HTTP Proxy field; if on the same computer, add “localhost”.
• Set Port number to “3128”.
• Under Other HTTP traffic proxy, set to Use HTTP Proxy.
• Click “Ok” to save and close the preference window.
• Click “Ok” and restart the viewer.

After starting the viewer back up, you should see the login splash page. If not, re-check the setting and make sure squid proxy and perl are working. You can test this by using a normal browser configured to use the proxy.

Return of The Squid: how to build a terabyte texture cache using Squid 3

So you recently saved an outfit, but when you look in that outfit's folder, it's empty. This can happen now and then, and it's caused either by something you're wearing, or something you aren't wearing. That does tend to cover any and all possibilities, but it will be made clear in the solution below.

NOTE: If the outfit had links in it in the past (in other words, you successfully created it originally), but is suddenly empty now, refer to the Missing Inventory help page.

First, try a simple relog and check the outfit folder again. If the folder is still empty, proceed with the following steps, and please do them in this order:

If you use RLVa there is a chance that it has restrictions that are interfering with the wearing or removing of items that can cause this empty outfit problem, so it is recommended that, temporarily, RLVa be disabled.

• Open Preferences → Firestorm → Extras
• At the top is Allow Remote Scripted Viewer Controls. If this is enabled (checked), uncheck it.
• If you had to uncheck this setting, click OK at the bottom and relog; otherwise, close Preferences.

In case the problem is caused by something you're wearing, it is recommended that you detach all objects and wear “default” body parts. The easiest and quickest way to accomplish this is to go to the Avatar menu > Avatar Health submenu and click Reset Default (male or female).

This may take a moment or two, depending on the availability of the asset server, your connection quality to the server, and your viewer performance. If it takes a long time, or appears to never happen, try relogging. If you had to relog for the RLV step above, try going to a different region, such as Hippo Hollow.

If your avatar still doesn't change, there may be other issues, and the Bake Fail page may help resolve them.

There are two folders, at a minimum, that are involved in your avatar's appearance. The first is the Current Outfit folder. This folder contains links to all the items that you are wearing. If it contains a broken link, or a link not worn, this can cause an outfit save to fail. So, open that folder and delete any broken links, or links that are not shown as worn.

The second folder, in this case, is the outfit's folder itself. Being empty, you have to delete that folder now.

A third folder may be involved if you are having a particular kind of bake failure: the Lost & Found folder. Normally, Lost & Found contains only objects, linksets and coalesced object sets. If you find any wearables in that folder, delete them. If they are worn, take them off first, then delete. If you cannot detach these wearables, relog, or try going to a different region, such as Hippo Hollow.

At this point, you should be ready to create and save an outfit. For an extra measure of sanity, it is recommended that you relog now. But you don't have to; you can attempt step 5 without relogging. However, if it fails a relog may help.

To ensure that you only wear the items you want in your outfit, manually select and wear each item. Don't try wearing an outfit that you want to modify, as it may contain something causing the problem. Instead, wear one item at a time from that outfit; anything that may cause a problem may then self-identify.

Once you are wearing all you want for that outfit, try to save it again, then check the outfit's folder for content.

If you have identified an item that causes a problem, that item may be corrupt in the SL database. You can try wearing an different copy of that item, if you have a backup of it, or notify the creator of the problem.

If your camera is suddenly pointing straight up - or straight down - or some impossible direction, then try these:

• Disable RLV and/or detach your collar or other RLV scripted items.

• Press the Escape (Esc) key a few times. Pressing Escape will clear focus from any windows that have focus, and finally, will reset camera position to your current settings.

• Press Shift-Escape (Esc), once or twice, to reset camera angle to Firestorm default settings. If Shift-Esc did not work, then go to the top menu, Advanced (Ctrl-Alt-D, if not enabled) → Shortcuts → Reset Camera Angles.

• Press Ctrl-9 - this will reset camera zoom. If the zoom did not reset, then go to the top menu, Advanced (Ctrl-Alt-D, if not enabled) → Shortcuts → Zoom default.

• Go to the top menu, World → Photo & Video → Camera Tools. Click all the buttons with the label 'D', on all tabs.

• Go to Advanced (Ctrl-Alt-D if the Advanced menu is not visible) → Show Debug Settings and enter “FocusOffsetRearView” ¹⁾ in the input field. Click “Reset to default” at the bottom.

• If that doesn't work, hold down Shift or Control, then use the mouse wheel to change the camera angle.

• Detach all worn HUDs and other attachments. (This means *everything* with a box icon in inventory–yes, body, hair, everything.) Sometimes worn items can control your camera perspective. If this fixes the problem, then re-add your items back on one at a time until you find the one causing the problem. (The TMP/MeshProject “Legacy” body HUD has such a setting to control the camera.)

• If all of these fail to work, then the only remaining solution is to reset all your settings to defaults.

• Try pressing the left and right arrows on your keyboard at the same time, several times.

• If you are using a mouse/keyboard sharing program, such as Synergy, or running Parallels on your Mac, then go to Advanced menu (ctrl-alt-d, if not showing) → Show Debug Settings → search for MouseWarp and set to True.

• Other Mac users may also find that disabling MouseWarp helps (see above).

• This can happen when you have a non default value set for Font DPI within Windows operating system settings.
  • Windows 10: Right click your desktop → Display settings → Display → Change the size of text, apps, and other items → Make sure this is set to 100%.
  • Windows 8: Right click your desktop → Personalise → Display → Adjust font size (DPI) → Make sure this is set to the default value of 96.
  • If prompted, reboot or sign out and back in.

• One user has reported that the software or driver for a pen tablet caused this problem and uninstalling the software fixed it.

Many thanks to Crypticzynergy for much of this information.

• Windows 10:
  • Right click your desktop → Display settings → Display → Change the size of text, apps, and other items → Set this to the scaling you prefer (default is 125%).
  • Click Apply, then click Sign Out Now
• Windows 8:
  • Right-click on desktop and select “Personalize → Display → Adjust Font Size (DPI)”. Click “Continue” to verify making changes to the settings.
  • Click on the “Custom DPI…” button. (Win8: This will be in a “DPI Scaling” window that pops up,)
  • A “Custom DPI Setting” window is displayed. Set your DPI as you would like it and ensure that the “Use Windows XP Style DPI scaling” is CHECKED.
  • Click on the “OK” button to close the “Custom DPI Setting” window.
  • OK the request to Restart computer.

• Right-click on the viewer's shortcut/icon/executable on your desktop (or in Windows Explorer) and select “Properties.”

• Go to the “Compatibility” tab. Place a check in the box that says, “Disable display scaling on high DPI settings.”

• Click “OK” to save the changes and close the popup window.

• Log into SL and verify that Mouselook View now works as intended. You're done!

“Windows XP style DPI scaling” does not actually scale a program's GUI; it only scales/enlarges the system fonts and other system UI elements at higher DPI settings. Basically any text drawn using system fonts is suddenly bigger.

Windows Vista's method is ambiguously called “display scaling”, or better known as “DPI virtualization”. Windows still performs “XP style scaling” when this option is enabled, but programs/software that can handle high DPI settings are now expected to tell Windows they can handle it by setting a “DPI-aware” flag. If that flag is missing, Windows first renders the entire program window to an internal bitmap using 96 DPI (the default setting), and then scales up that bitmap to the current DPI setting before finally displaying it on your screen.

Apparently, having the checkbox marked ENSURES the EXCLUSIVE use of the legacy “Windows XP style DPI scaling” method and DISABLES the additional use of “DPI Virtualization” for programs that lack the DPI-aware flag. Microsoft/Windows dislikes non-conformity by 3rd party programs to the point where it won't play nice with said software/programs, like SL! This is where the tantrum comes – in the form of Mouselook view issues. (Basically when the checkbox is unchecked, you're actually enabling the newer method – DPI virtualization.)

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.

If you can turn in circles but not move forward/backwards, you probably have Movelock enabled.

• Go to the Avatar menu→ Movement submenu and make sure Movelock is not ticked.
• See Movelock info for more information or if you are unable to change the Movelock setting.

However, there are a few other things to try:

• Go to a different region and see if you are able to move there. If so, something at your original location is causing the problem.
• If you are using a LAQ mesh head, make sure you don't have the Pose feature turned on.
• Make sure you don't have some other HUD with a pose feature. (For instance, one user has reported this problem with the Lelutka Axis face HUD.)
• If you can't find what attachment is causing the problem, try going to Advanced menu (Ctrl-Alt-D ) → Release Keys.
  • Note: Release Keys will be greyed out if RLV has locked any of your attachments. To disable RLV, go to Prefs → Firestorm → Extras, untick the top item, and then relog.
• Make sure you don't have the Firestorm pose stand active.
  • If you have the Pose Stand button on your toolbar, make sure it's not “on.”
  • If you don't have the button, go to Avatar menu → Toolbar Buttons, drag the Pose Stand button out to your toolbar, and make sure it's not “on.”

• Tap your PageDn key and see if the animation stops. If it does, you were in crouch.
• Try Avatar menu → Avatar Health → Stop Animations & Revoke Permissions.
• Try right clicking your avatar → Reset Skeleton & Animations.
• If the above items did not work, go to a different region and try them again.
• If you have the animation in your inventory, play it from inventory, then click Stop.
• Remove attachments one by one until the animation stops. (This will eliminate worn items as a cause.)
  • Note: Animations can be in ANY attachment. Please don't assume that any particular attachment is not the problem. Take them all off.
  • Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Make sure the Firestorm AO is off:
  • On the AO button on your toolbar, untick the checkbox.
  • Note: The Firestorm AO can be active even if the button is not on your toolbar. If it is not on your toolbar, go to Avatar menu → Toolbar Buttons, drag the AO button out onto your toolbar, and make sure it is not ticked.

• If you know that a “sittable” item gave you the animation:
  1. Go to Preferences → Firestorm → Protection → Revoke Permissions.
  2. Temporarily set this to “Revoke on Sit and Stand.”
  3. Sit on the item, then stand. This should stop the animation.
  4. Change Preferences → Firestorm → Protection → Revoke Permissions back to either “Never” or “Revoke on Stand.”

• Try Advanced menu → Release keys. (After doing this, you will need to recreate the FS bridge: Avatar → Avatar health → Recreate LSL Bridge.)

• You may simply be experiencing lag: See Troubleshooting Lag for tips to reduce this.
• Many pose balls will request permission to animate you. If you did not see the animation request, look in your Notifications window for the message. Click “Accept.”
• Make sure you have not blocked the item or its owner: Look in Comm menu → Block List, see if the item or the item's owner is there, and remove the item/person from the block list.
• Go to Preferences → Firestorm → Protection → Revoke Permissions. For normal use, this should be set to either “Normal” (no protection) or “Revoke on Stand.” It should normally NOT be set to “Revoke on Sit” or “Revoke on Sit and Stand,” as both of these will prevent items from animating you when you are sitting.

Remove all attachments, then add one by one, testing in between to see if one causes the problem.

The TMP “Legacy” body HUD is known to cause this problem. Turn off the cam control located on the HUD.

“Rubber-banding” is when you try to walk forward and then suddenly snap back to a previous position. Sometimes you will seem unable to stop walking. This is caused by region lag, when the server can't keep up with processing avatar movement (collisions).

• For info about region lag see here: Region Lag
• For some things that region or parcel owners can do to reduce region lag see here: Reducing Server Lag.

This typically happens when you have two or more conflicting AOs (animation overriders) on.

• Start by removing known AOs until you are wearing only one known AO.
• If that doesn't help, start by removing other HUDs, then all other attachments, one by one, until it stops. Any worn item can contain an animation, so don't assume that some items are “ok.”
• Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Try turning the opposite direction to the spin.
• Try pressing BOTH right and left arrow keys at the same time, repeatedly.
• Relog.

• Remove other attachments that contain animations.
• Remove or turn off ankle-locks.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

For unknown reasons, some users need to change an additional setting:

Go to Preferences → Privacy → Lookat, and tick “Don't send any look at targets at all, even to myself”

• In most cases, pressing Ctrl-R to toggle run mode will get you back into walk (though it may in some cases be necessary to hit Ctrl-R more than once).
• If you are wearing a scripted AO (animation overrider), turn off any “running” features it has.
• If you are using the Firestorm built-in AO (animation overrider), make sure there are no running animations in the “Walking” or “Standing” categories.

After Strafe

Ref. BUG-6825

In one specific case, the above will not work. Specifically:

• You have Preferences → Move & View → Movement → Tap-tap-hold to run enabled.
• Press shift, then tap-tap-hold the left or right arrow key

That gets you running sideways. If you release shift before the arrow key, you will be stuck running.

To stop running, you have to repeat the sequence: press shift, then tap-tap-hold left or right arrow.

• Go to Preferences → Sound & Media → Voice, and deselect “Move Avatar Lips When Speaking.” Note: This is the only viewer feature that affects lip movement.
• If you are wearing a mesh head, turn off any animations in the head. For more help, ask the support group for that head.
• Go to Comm menu → Gestures. Tick “Active only” at the bottom of the window. Review the list for any gestures that might contain a face animation. If in doubt, turn them all off, one at a time, to find the one responsible for the lip movement.

This is a known SL bug also affecting the SL viewer. Refer to this SL bug report for more information.

This happens if you turn off this setting: Preferences → Chat → Typing → “Play typing animation when chatting.”

* To stop the head-bobbing, go to Preferences → Chat → Visuals, and disable “Play avatar animations (such as shouting).”

Note: If you can't get your avatar to stop typing, see Turning Off Typing.

Submitted: %G-%m-%d

User name: @@User name@@
URI: @@Your account UUID@@
Skype: @@Discord name@@
Email: @@Email (preferably one that does not reveal personal information)@@

How long have you been active in second life?
@@How long have you been active in second life?@@

Why do you want to be a helper?
@@Why do you want to be a helper?@@

Name three places in SL that wow you
@@Name three places in SL that wow you@@

What special interests do you have in SL (ie: building, designing clothes, photography,etc)
@@What special interests do you have in SL (ie: building, designing clothes, photography,etc)@@

What frustrates you most about Second Life?
@@What frustrates you most about Second Life?@@

What do you like most about Second Life?
@@What do you like most about Second Life?@@

What is your timezone?
@@What is your timezone?@@

What languages do you speak/write?
@@What languages do you speak/write?@@

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 the following:
  • Windows users: see this page.
  • Make sure streaming music and/or media are enabled in Preferences→ Sound & Media -> Sounds.
  • In the same place, check that volumes for music and media are not at minimum.
  • Make sure audio is configured correctly in your operating system (i.e., 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, volume mixer, and/or other similar software.
  • Confirm that you have not blocked the stream/video: open Preferences → Sound & Media → Media → Manage Media Sites and see if the problem URL is listed there; if so, remove it.
  • 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.

• The Dullahan Plugin (for those who have questions): Dullahan is a headless browserSDK that uses the Chromium Embedded Framework (CEF). In addition to playing media, Dullahan is also used for:
  • Websearch
  • Web profiles
  • Built-in browser
  • Splash Screen when the viewer is launched
  • Media-based HUDs
  • Avatar Menu - Choose an Avatar
  • Destination Guide
  • Wiki Help pages (when clicking the ? in a floater)

• 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 dullahan_host.exe.
• Relog and attempt video playback again
• If it works, you will need to stop your firewall/virus protection from blocking the slplugin and/or dullahan_host.exe 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 dullahan_host.exe for each one.
• If all of the above does not resolve the issue, you can try downloading the latest SL Viewer and replacing your Firestorm slplugin file with the one from SL Viewer.

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

In-world videos (on TVs and Prim Media, a.k.a. Media-on-a-Prim) are independent streams from the source to each person watching. The only way to synchronize them is for each person to click Play at the exact same time, and even then the streams can get out of sync depending on lag, connection, buffering, and other network & computer issues.

If you have Parcel Media rights, Parcel Media is an alternative. Like a music stream, it will generally be sync'd for everyone watching (World menu > Parcel Details > Media tab). Click the ? at the top of the Media tab page or see here for more information on how to configure Parcel Media.

Embedded MP4s no longer are supported by Second Life. Consult your TV maker to determine if they use this format. Refer to BUG-224979, as well as this blog post.

The Flash plugin is not installed with Firestorm; you have to install it yourself. However, you need specific plugin versions:

• 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 the Media tab, at top.
    • Click “Flash game.”
    • 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).

1) Check viewer settings

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

2) Check your audio drivers

• Look in Help menu → About Firestorm for the line that begins with “Audio Driver Version.” If that line says “Undefined,” reboot your computer and see if the Audio Driver Version appears.
• If this doesn't help:
  • Go into Windows device manager (https://support.microsoft.com/en-us/instantanswers/005a1acb-776e-4320-b9f2-3a2302a320da/open-device-manager) & see if there is a yellow triangle warning symbol against your Sound devices (or your display adapters).
  • Also make sure your sound card driver is up to date.
  • Reinstall your graphics driver; the drivers also include audio components.

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

Preferences - Sound & Media - Music - Enable Parcel Audio Fading - uncheck if checked. (reference for Support only https://jira.firestormviewer.org/browse/SUP-20376|SUP-20376).

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

There are two possible causes:

• Flash is not installed, or is not installed correctly. See Flash, above.
• Your antivirus has deleted or mangled the plugin. See Antivirus Whitelisting for instructions on how to fix this.

A problem that is frequently reported is that worn rigged mesh attachments will sometimes be invisible to others after you have teleported. This can generally be fixed by selecting top menu, Avatar → Avatar Health → Refresh Attachments. Should that fail, then you will need to relog.

In order to reduce the chance of this happening, you should ensure that all worn rigged mesh items are attached to a different body attachment point (make sure NOT to attach to HUD, or only you will see the item on yourself). Many creators leave item attachment points at the default, which is right hand. This can result in many attachments being stacked on this point, making the above described issue far more likely to occur. So when wearing an outfit, check each rigged mesh part, and if attached to right hand, reattach to a different spot, and one not in use by something else. (You only need to do this once with newly acquired clothing, as the newly selected attachment point is remembered.) Having done that, and as explained below in “Changes to Attachments,” detach the item after having done this, so that the change saves.

Refer to FIRE-17998.

This is a side effect of the same bug described above. When you are crossing many regions or after a TP, some of your attachments may become “ghosted” in such a way that the viewer still thinks they are attached (so you see the attachments in your viewer), but as far as the region is concerned, the affected attachments are detached. No observer will see them and also no scripts in those ghosted attachments will run.

At a later time, if you make a change to what you are wearing by adding or removing something, this can sometimes cause your attachments to refresh to the “correct” state that the region sees. When this happens, some or all of those ghosted attachments will also be detached locally (in your viewer).

Refer to FIRE-22970 and FIRE-17998.

A somewhat common occurrence: changes you made to an attachments, either by manual editing, or by the use of an applier, will revert if you subsequently crash.

This is due to how SL works. Changes to attachments only save when you detach the item, or when you relog. So in order to avoid this situation, any time you make any change to an attachment (and this includes hiding/showing parts of a mesh body), detach the item, count to 10, then re-attach.

Attachments which are visibly seen as worn may not show as worn in inventory. As a result, attempting to detach them by right clicking the inventory item name is not possible.

Different solutions are suggested… please try these, one at a time, in the order given, until one fixes you.

1. Right click the attachment on your avatar, and detach it via the pie menu.
2. If the above fails, go to a low lag region, such as this one, log out there, then log in to last location. At that point try to detach, either the usual way, or as described above.
3. Try the Replace Outfit procedure described below.

If you find that when you log in, attachments are being detached and then reattached, sometimes several on the same spot, then try the following procedure:

• Make a temporary folder somewhere you can find it easily
• In that folder, put a copy of your skin, shape, hair/bald base and eyes - and perhaps a pants and top layer - no prims!
• Right click the folder name and select Replace outfit. Not Wear, not Add, Replace. This step is VITAL
• Now relog
• Once you are logged back in, you can put your usual extras back on, hair included. And hope that it holds.

If you find that attachments disappear (or partly disappear) after a teleport, but only in your view, not to others, then enable teleport screens if you have them disabled: Preferences → Move & View → Teleports → Disable teleport screens; uncheck. Ref. this JIRA.

If a scripted attachment (such as a HUD) stops working following a TP, this may be because the attachment has actually fallen off during TP. You may see it on your screen, but the server thinks it is detached, so the scripts won't run. Try the following:

• Avatar Menu - Avatar Health - Refresh Attachments (Alt+Shift+R).
• Detach and reattach the item. It may help to relog before and/or after.
• In addition, if the HUD attaches to the Center 2 HUD point, try changing it to a different HUD attachment point. Attachments may be less likely to “fall off” of other attachment points. 1

Note: this is related to this bug.