About land is a window that allows you to view and customize various aspects of a parcel of land. It is both a land management tool and tool for finding out various information about the parcel.

The window comprises several tabs; use the navigation bar above to read about them.

If you would like an overview of parcels you own, then go to the top menu bar→ World → Show Owned Land to display the Owned Land window.

For example, say you have a few links to a hair item. You then at some point rez out that hair item to edit it, then take it back into inventory. The item will have a new UUID, so all your links to that item will be broken. To fix those links, proceed as follows:

• locate one of the links in your inventory
• right click the link and select Replace Links
• a window like the one to the right will open, showing the name of the link, and how many links like it are in your inventory
• now locate in your inventory, the item you wish these to link to (using the example above, the hair item which you rezzed out)
• drag this item into the box labeled New
• click on Start.

NOTE: This function is also handy if you have broken links in inventory that you wish to repair.
NOTE: If you have a lot of outfits, use caution with the Refresh button. This can result in duplicate copies of the item you are attempting to replace.

You may have occasion to remove a link from several or all outfits. For example, you converted your AOHUD to the FS client AO, and want to delete the AOHUD from your outfits. To delete those links, proceed as follows:

• locate one of the links in your inventory
• right click the link and select Replace Links
• a window like the one to the right will open, showing the name of the link, and how many links like it are in your inventory
• now put a check in the box beside Delete links only
• click on Start.

You may wish to add a link to some or all of your Outfits.
There isn't a viewer option as such, but there is an easy way to do it.

1. Right click the item you want to add to an Outfit → select Copy.
2. Go to your Inventory Outfits folder. Select a number of Outfits using Shift+Select (will select all Outfits in a group)…
3. …or Ctrl+Select (will select only certain Outfits).
4. Press Ctrl+V to paste. (Do not right-click to paste; this will not work in this situation.)

• 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 Debian 10.x (buster) - AlexIvy updated 2020/03/31
• 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
• 64-bit Ubuntu 20.04 (AlexIvy) updated 2020/07/01
• Gentoo

This page describes all necessary steps¹⁾ to build the Firestorm viewer for Linux on Ubuntu 20.04, using Linden Lab's project Alex Ivy infrastructure. It assumes you are using Ubuntu 20.04 Focal Fossa, that your normal user has sudo privileges and that all standard updates have been applied using apt *upgrade*.

To successfuly compile Firestorm your computer must have at least 4GB RAM with 4GB+ swap, a modern dual-core CPU and 32GB available HDD space. However we strongly recommended you have 8GB or more RAM, a modern CPU with 4 or more real cores and 32GB available HDD space. You may require more HDD space if you compile different viewers, or different variations of Firestorm.

We're going to follow some conventional ideas on compiling software. Primarily, we will create a directory to contain all the source files. Open a terminal (in which we will work from here on).

cd #to jump to the home directory
mkdir -p src/sl/vorbis src/python-pip
cd src

Now to install the various programs used to build the viewer.

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

The required tools, some of which may already be installed, are:

sudo apt install --install-recommends make cmake curl doxygen gdb git python2 python2-dev python-all

(the –install-recommends flag tells apt to install all packages recommended by each named package.)

Pip for Python 2.7 is not available to Ubuntu 20.04, so it takes a couple extra steps to install it

cd ~/src/python-pip
curl https://bootstrap.pypa.io/get-pip.py --output get-pip.py
sudo python2 get-pip.py
cd ~/src

In at least one case, a required symlink (/usr/bin/python) was missing. Ensure that it exists, and is pointing to Python 2.7.

sudo ln -f -s /usr/bin/python2 /usr/lib/python

These libraries may be included with your distribution, and some may already be installed:

sudo apt install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libpython-all-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that automates the configure and build processes.

sudo pip2 install autobuild

This will install autobuild and add a link in the exec path.

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.

cd ~/src/sl
git clone https://vcs.firestormviewer.org/fs-build-variables
source fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=$HOME/src/sl/fs-build-variables/variables

There are several repositories available, in but the one wea re after is the development repository. You can grab all the sources if you wish, but but keep in mind that each FS source requires around 110MB initially and around 4.3GB after the binaries have been built, plus possible compiling overhead.

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

Credit for the vorbis file goes to Marissa Orloff. She states that when recompiling this the following changes were made: in ogg_vorbis build.sh in line 91 needs to be edited to remove LL_release. aclocal and automake need symlinks 1.15 > 1.16

cd ~/src/sl/vorbis
wget https://fireandicegrid.net/downloads/ogg_vorbis-1.3.3-1.3.6.200930615-linux64-200930615.tar.bz2
cd ../phoenix-firestorm
autobuild installables edit ogg_vorbis platform=linux64 hash=d888b4916006c28471b4f103854526c3 url=file://$HOME/src/sl/vorbis/ogg_vorbis-1.3.3-1.3.6.200930615-linux64-200930615.tar.bz2

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 a free account to access the download section).

cd ~/src/sl
git clone https://vcs.firestormviewer.org/3p-libraries/3p-fmodstudio

• After you have cloned the repository, copy the downloaded FMOD Studio installer file to ~/src/sl/3p-fmodstudio
• Currently, FMOD Studio is at version 2.01.01, and that's what 3p-fmodstudio is expecting to use. If you plan to use a different version, 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="20101"
FMOD_VERSION_PRETTY="2.01.01"

cd ~/src/sl/3p-fmodstudio
autobuild build -A 64 --all
autobuild package -A 64

Near the end of the output you will see the package name written, including the path, and the md5 hash below it. For example:

wrote /home/user/src/sl/3p-fmodstudio/fmodstudio-2.01.01-linux64-201831958.tar.bz2
md5 a648d0a332768cab58b377566e415c88

cd ~/src/sl/phoenix-firestorm

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

autobuild installables edit fmodstudio platform=linux64 hash={md5 value} url=file://{wrote value}

For example:

autobuild installables edit fmodstudio platform=linux64 hash=a648d0a332768cab58b377566e415c88 url=file:///home/user/src/sl/3p-fmodstudio/fmodstudio-2.01.01-linux64-201831958.tar.bz2

 cd ~/src/sl/phoenix-firestorm
 autobuild configure -A 64 -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).

When passing one or more of the following options, they must be separated first with a double dash, which denotes the start of an options list.

• –fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps above for this to work.
• –package makes sure all files are added to a compressed tar file for easy distribution and storage.
• –chan <channel name> lets you define a custom channel name for the viewer
• –no-opensim removes opemsim support, limiting the accessible grids to SL's Agni and Aditi.
• –avx causes the viewer to build with the AVX CPU instruction support. Similarly, –avx2 enabled AVX2 support.
• -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 64bit viewer with a custom channel name, FMOD Studio and to create an installer package, run this command:

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

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

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

Make sure you include the same architecture parameter and switches (except clean) you used while configuring the viewer:

autobuild build -A 64 -c ReleaseFS_open

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -A 64 -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/sl/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

cd ~/src/sl/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged
./firestorm

Your file browser/file manager many not know how to execute a script. Check the settings for your file browser. In Nautilus, for example, open Preferences > Behavior tab, change the action for executable text files to either Run or Ask.

Copy or move the contents of ~/src/sl/phoenix-firestorm/build-linux-x86_64/newview/packaged to a place that can be access by the PC you want to install Firestorm on. Cloud-based storage, NAS or removable media would do.

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

• Self-Compilers peer supportFirestorm Self Compilers is free to join, fellow self-compilers may be able to offer assistance.
• IRC: The #phoenixviewer-dev channel is the best place to look for solutions.
  A lot of self-compilers and project developers hang out there and are ready to help you.

• Jira:JIRA may contain resolved tickets.
  Search using the error you encountered.

• Included documentation: In the Firestorm root folder are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date.

If you found a procedural error in this document, please let us know in as much detail as you can, either contact the author (preferred) or discuss on IRC.

• Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Debian repositories, so make sure you did not disable those. If you find that a library or application is in a different package for your system, contact the team with the name of the library or application, the name of its package and your Linux OS so that information can be checked and added here.

• Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

Linden Lab released the Environment Enhancement Project (EEP): Please read EEP is Out! Introducing the Environmental Enhancement Project for a full description!

This project revamps our Windlight system and among other things, includes

• support for 24-hr day cycles
• server-side support for parcel Windlight
• the ability to set custom sun, moon and cloud textures on your region or parcel that everyone using an EEP viewer can see.

The sections further down list known problems that have been encountered since the server EEP changes. These problems are still a work-in-progress and will hopefully be fixed once Firestorm releases with the EEP feature.

If you want to try EEP, you can do so using the Linden Lab viewer available from Second Life Viewer Downloads.

For discussion you can follow the EEP forum.

For those interested, you can see a filtered list of current issues with EEP in the official SL viewer here. Remember to log into the site using your SL user name and password.

Please don't swamp Firestorm support with questions about EEP. Read the pages linked above, test out the project viewer if you wish, and follow the forums to stay up to date on development. Once Firestorm includes EEP, we will be able to help you with its features. Thanks!

As of Tuesday, March 19, server-side support for EEP was rolled to all regions on the main grid. This means that all region Windlights in use were automatically converted over to the EEP system.

Firestorm Viewer does not yet have EEP support.

Viewing the new EEP skies on a viewer that doesn't yet have EEP support (like Firestorm 6.3.9 and older) may cause the skies to look slightly different in some cases.

• If you are have a specific Windlight sky set in your viewer (i.e., one you have chosen from Quick Prefs, Phototools, or World menu → Sun Position), then the sky will look the same.
• If you are on a parcel with a Firestorm parcel Windlight set, the sky will look the same because the viewer just reads the Windlight settings in the parcel description and applies those settings locally.
  • If you find the WL doesn't seem to work, first make sure that Use Region WL is not enabled in QuickPrefs
  • Add the “region override” tag to your parcel windlight description; see Windlight for details.
  • If that doesn't fix it, try adding altitude values; see this page for how to do that.
• However, if you are viewing a region Windlight (World → Sun Position → Estate Time) the sky will look different from how it used to.
  • If the sky has visible stars, the stars will look much larger and blotchy. If ALM is enabled, the stars will also look black instead of white.
  • The sun may be bigger or smaller than it should be.
  • There may be subtle lighting differences.

It appears that the server rollouts on this date have resulted in it being impossible to change windlight settings at region/estate level. If you attempt to set a new WL sky or water, the changes will not apply. Refer to this bug report.

Symptom: You receive a message that the system has “Failed to find [name of any item] in the database” every time you try to wear or remove something.

Please note: This is not always a viewer issue, but we have written this page to help users with a common problem.

We have identified a few causes of this. Please work through each one until the problem is solved, and if still having trouble, be sure to see “Otherwise,” at the bottom of the page.

Open your inventory (Ctrl-i) and check that the total inventory count looks correct.

• If the count is low, work through the inventory troubleshooting page until the count is correct.
• If the count is normal, go to Preferences → Network & Files → Directories and click the Clear Inventory Cache button.

• Open your Inventory and look in your Current Outfit folder (must be the “Current Outfit” folder and not the “Worn” tab; this is important).
• Look for any broken or unworn links in the folder, particularly for the item that is named in the “Failed” warning you're receiving.
• Delete any and all broken or unworn links in the folder.

Explanation: This error happens when the broken link gets “stuck” in the folder for some reason. When the viewer tries to update the Current Outfit folder – which happens whenever you wear or remove a body part or clothing item – it detects the link in there and thinks you want to be wearing that item. So it tries to put it on you, but it can't because the link is broken, and the “Failed” message pops up. An unworn link in Current Outfit can also cause an issue; the viewer thinks the link is worn but the server does not, or vice versa.

If deleting broken/unworn links doesn't help, or if there were none, then make a temporary folder in your inventory. In it, put a copy of a system skin, system shape, system hair base, and system eyes - nothing else - and not the ones you are already wearing. Then right-click the folder name, replace outfit (not add or wear). Then check Current Outfit folder (not Worn tab) and delete any links showing as not worn. Then relog. (Please follow these steps exactly as given - it matters.)

• If the error message has gone away, you can try putting on your usual body parts and clothing.
• If the error message returns when you try to put on your usual items, one of them may be corrupted on the server.
• If the error message has NOT gone away, proceed to the next section.

• Check in Lost & Found folder and delete any system layers named “new”—“New skin,” “New eyes,” “New pants,” or similar.
• If you are wearing the item, remove it (if a clothing layer) or change to a different body part, whichever applies, and try deleting the item again.

Explanation: If a worn system clothing layer or system body part is not found at login, that layer/body part will be replaced with a default asset that is created and placed in Lost & Found. You will continue to get the error message until the “new” item is deleted from Lost & Found.

• If the error message has gone away, you can try putting on your usual body parts and clothing.
• If the error message has NOT gone away, proceed to the next section.

(Windows only)

This feature has been known to cause problems.

The NetBooster tool is a feature in System Mechanic Pro. This NetBooster feature does not always execute, so there is an element of randomness to reproducing these SL connectivity problems when System Mechanic Pro is installed on the system.

• Uninstalling System Mechanic Pro does not appear to revert the changes made by the NetBooster feature.
• The solution is to go into the NetBooster tool and selected “Restore original settings”.
• This restores Windows default settings and everything in SL works again.

For more information and additional symptoms, see this SL bug report.

If none of these steps help, then please test using the official LL viewer, which can be downloaded here. If you have the same problem there, file a support ticket with LL.

Firestorm 6.3.9 Only There is a bug in the Firestorm 6.3.9 AO that will cause you to crash in certain situations. Please see here for more information

If you have Intel HD 620 or Intel HD 630, and Windows 10 – This is an Intel driver issue.
The easiest fix is to use Firestorm Version 6.2.4. or newer.
If you are using Firestorm Version 6.0.2, use another viewer to remove the jacket layer.
(Ref. BUG-225655 and BUG-227078)

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.

If you don't have the above graphics and this occurs, chances are good that some part of cache is corrupt. Deleting it should solve the problem.

• Locate your cache folder. You will probably need to do this manually, if you are unable to log in. Use a file manager (like Windows Explorer for Windows system, Dolphin, or some such) to locate the cache folder. In its default location, the cache folder is hidden on most OSs. To find it, you will need to show hidden folders. Default cache locations are:
  • Windows 7, 8.1, and 10: press [Win] + [R] and type %localappdata%, then look for the Firestorm folder. (This method avoids having to un-hide folders.)
  • Mac: ~/Library/Caches/Firestorm
  • Linux: ~/.firestorm/cache or ~/.firestorm_x64/cache
• Delete the cache folder you located.
• Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Allow your inventory and cache to repopulate fully.

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

One other possibility concerns starting the viewer on a secondary monitor rather than the primary. So if you are starting it on the secondary, try the primary instead.

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

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

Please see Recent Crashes on Windows, following a Driver Update for this issue.

Ref. FIRE-12339

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

Then, do the following:

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

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

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

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

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

Note: this is a list of standard keyboard shortcuts for these menu functions. Your keyboard may differ.

Note: The Developer menu must be enabled for these key combos to work: use CTRL-Alt-Q to enable it.

Key = Key Sequence

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:

Region problems can get in the way of saving a lot of things, including outfits. So TP to a known low-lag region such as Hippo Hollow or Cyclops (open the World Map [ctrl-M] and type in the name), and try again to save the outfit.

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 a different copy of that item, if you have a backup of it, or notify the creator of the problem.

Firestorm 6.3.9 (58205) Release Notes

“n/a” in the table below means “not available”; see the boxed note above.

More information about the 64-bit builds can be found here.

Firestorm 6.3.9 (58205) Release Notes

“n/a” in the table below means “not available”; see the boxed note above.

• SLURLs not working in your browser, or choose to open with a different viewer (Windows)
  • SLURL Proxy.zip
  • Instructions are included, but can also be seen on the Wiki here.

Please read https://support.microsoft.com/en-au/help/4520411/adobe-flash-end-of-support before considering installing flash. Flash has a LONG history of very serious security issues. If someone is providing content that only works with flash, please contact them and let them know that flash will be end of life in the near future, this means there will be NO security updates from the vendor beyond that point. Nobody should be forcing flash on anyone in this day and age, it is 2020, not 2001 anymore.

• Windows - Download in Firefox or Chrome to play Flash media inside Second Life.
  Choose the correct operating system under Step 1.
  Choose FP 32 for Opera & Chromium - PPAPI under Step 2.
  Install Flash.

• Mac - Ensure that you have the most recent version of Flash for Safari installed. You can get this via the normal update process, or from Adobe.
  Choose the correct operating system under Step 1.
  Choose FP 32 for Safari and Firefox – NPAPI under Step 2.
  Install Flash.

• Linux - You need to have the pepperflash plugin installed, which can be satisfied by installing Google Chrome.

• Windows - Quicktime does not need to be installed to play media on Firestorm 5.0.1 or later.

• Mac - Quicktime to play streaming videos. (iTunes is not needed)

for Linux only

• Info for download to play streaming videos. (Please read page for info on installing GStreamer for your particular distribution.)

• Growl for Windows– As of November 2018 this site is dead. Users who already have Growl installed can continue to use it for the time being. Windows users may be able to download a copy from its github release page.

• Mac– This site will lead you to the Mac App Store for downloading. Please note the reviews and the update status of Growl before purchasing; Firestorm cannot guarantee its functionality.

• Linux: Growl is implicit in libnotify, which should come already installed in most distros. However, if you are on a 64-bit Linux, you may need to install the 32-bit version of libnotify. For ubuntu and similar (like mint), run the following command:
  sudo apt-get install libnotify4:i386

Windows only

• DX runtime April 2011 to help increase performance and stability. For all versions of Windows. Please refer to this page.

Mac drivers are included with OS upgrades. However, to determine what card you have, select “About this Mac” from the Apple menu, then click “More Info”. Under Hardware select Graphics/Displays.

If you are not sure what type of video card you have, use GPU-Z found (Windows only) here. For Linux, in a console use:
lspci | grep VGA

• Latest driverLast checked 24/05/2020 - Windows: 445.87 (2020.4.15) - Linux: 440.82 (2020.4.7)

• Latest driverLast checked 24/05/2020 - Windows: Adrenalin 2020 Edition 20.2.2 (3/5/2020) - Linux: 20.10 (4/16/2020)
  

• Intel driver download page Intel does not have a universal driver set. Please go to Intel's site and use the auto-detect feature.

https://vcs.firestormviewer.org/

Notes:
(1) Tested using Debian 8 (Jesse) and Ubuntu 18.04. Some success has also been seen with Arch.
Some additional libraries are required; see this page for more information.
(2) GPU technical specifications for equivalence.
(3) Only x86-based CPUs, such as AMD and Intel, are supported. Firestorm will not run on ARM-based systems.

See here for a description of what a cache is.

Clearing your cache this way will “cure” certain kinds of texture or inventory issues caused by problems with the cache files stored on your hard drive. It will not solve server problems, lag, or other non-cache-file issues. A full cache is almost always better than an empty one.

You can clear just parts of the cache, depending on the issue you're trying to resolve:

• Open Preferences→ Network & Files -> Directories.
• Go to the first path “Cache Location” and click the “Open” button behind the path. This will open a file explorer (Mac Finder) window displaying your current cache location.
• Log out (close the viewer).
• Did you log out? It's important.
• Log out.
• Then delete everything inside the folder currently displayed in your file explorer (or Mac Finder).
• Should you not be able to start the viewer to bring up Preferences, then locate the folder manually. In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Now you need to locate the cache folder:

Delete everything inside that folder, OR delete the specific folder/files listed in the table above.

Now continue as follows:

• Log back into SL, to a quiet region (try the Firestorm Support parcel or a Linden water region such as aich or hatton). On your inventory window, click “Recent Items”.
• Wait for your inventory to repopulate fully. The process may be sped up, if necessary, by typing random letters into the search bar.
• While inventory repopulates, do not teleport anywhere, and do not attempt to access anything in your inventory. Talk to people or surf the web.
• Watch as it repopulates. as long as you can see (Fetched…) at the top of the inventory window, it is still loading.
• Once inventory has repopulated, log out of SL once more, then log back in.

At this point, you should be back to normal… whatever “normal” happens to be that day in SL.

This version of Firestorm has a bug in the AO code which will result in a crash in either of these situations:

• logging out with the AO floater (window) open.
• creating an AO set for the first time with this version of the viewer - if you already have one or more sets defined before updating, then you're fine.

There are two workarounds:

If you still have Firestorm 6.3.2 (or earlier) available:

1. Log in with Firestorm 6.3.2 (or earlier) which is available here
2. Open the Firestorm AO interface
3. If you don't normally use the Firestorm AO, delete all AO sets that are defined
4. Otherwise, make sure that exactly one of your AO sets is marked as “Default”

1. Log in with the Linden Lab Second Life viewer
2. Open your Inventory
3. Navigate to your #Firestorm folder
4. Open the #AO folder inside there
5. If there are any empty folders under #AO, delete them
6. If there are no folders left under #AO, you can stop here
7. Otherwise, check if there is exactly one folder under #AO that ends in :** (for example, Female AO:**)
8. If not, add the :** to the AO set that you normally use

After this, you should be able to log in with 6.3.9 once again.

An Alliance for Independent Ships/Stations That Want to Partner with Firestorm Gateway

Firestorm Gateway Starfleet (FGS) is an alliance of independent ships, stations, and roleplayers who wish to retain their autonomy but be part of a larger group that provides resources and identity. FGS respects each group’s right to determine their storyline, their Trek timeline/time-frame, their decisions on ranks and promotion criteria, etc. It also provides access to new-to-SL individuals who are interested in Trek RP.

FGS provides some resources for member-ships and stations. These include:

• free duty uniforms (with Omega appliers for those avatars who have mesh bodies)
• a weapons system that works even in no-rez areas
• a sophisticated combadge system
• the ability to send notices to a group of over 2000 people who are interested in scifi RP
• A direct Transporter form the Gateway Starship to your starship
• a system to teleport interested new-to-SL residents from Firestorm Gateway to your ship during your RP times.

It also provides the occasional shared ceremonies presided over by the Jessica Lyon, president of the United Federation of Planets (and team leader for Firestorm). And possibly most important, it gives you an opportunity to meet people who might become interested in joining your crew.

1. You must be “newbie friendly” at all times, as the purpose of this project is to introduce new-to-SL individuals to Trek RP and get them linked in with existing groups, so that they make connections and want to keep coming back to SL.
2. You MUST provide a 1-hour (or more if you want it to be longer) RP a week at a scheduled time on the Firestorm Gateway grounds. Newbies may drop in on the RP at any time during that hour, so you need to provide enough crew to sustain a small RP—but at the same time be flexible to allow the new people to join in if they so desire.
3. You must dress/talk/behave in a G manner while on the Firestorm Gateway.
4. Absolutely No Drama. Also no badmouthing other Trek groups or individuals.

Interested? Please contact Teresa Firelight.

If you have a non–Trek SciFi RP group and are comfortable using the Tempus station or Epsilon Ship, you are also welcome to join in. You will have the same resources and requirements that the Trek groups have, but your weekly roleplay does not have to be even remotely Star Trek—but the RP on Firestorm's Scifi Portal still needs to happen weekly at your scheduled time.

You are most welcome to partner with Firestorm to promote Trek RP and to introduce new-to-SL folks to your organization. However, we have a different mechanism for the larger established groups than we have for the independent ships. Please see Firestorm Gateway Roleplay Partners for more information.

So you have the latest viewer and still can't see mesh - what's the deal?

Well, it isn't necessarily automatic. Depending on your specific hardware, certain settings that need to be enabled for mesh, may be set off by default.

Go to Preferences→ Graphics -> General; then enable Basic Shaders.

If this remains greyed out, then increase the level of Render Quality until Basic Shaders becomes enabled and can be checked.

Make sure you have a reasonable draw distance. If you have difficulty rendering mesh, lower it; if your draw distance is over 128, set it to 128, or less. (The optimal value for draw distance is entirely dependent on your own hardware; you will need to experiment to find what works best for you.)

In some cases, worn mesh attachments will not render properly still. Go to Preferences→ Graphics -> Rendering and disable both of the Alpha Mask Rendering options.

There are also rare instances of glitches where mesh that you are wearing appears worn by another avatar (yes, it is bizarre!). In that case, try going to Preferences → Graphics → General, and enable Hardware Skinning.

In some cases, low-end graphics cards or very old graphics drivers may require you to turn hardware skinning off rather than on. Before doing this, please try updating your graphics drivers and review the other options on this page, as turning hardware skinning off may reduce your performance.

If you have Webroot SecureAnywhere Antivirus, see Webroot Issues. For other antivirus apps, see our Whitelisting Guide, and be sure to whitelist all parts of the viewer. This may need to be done from scratch each time you upgrade to a new version.

If mesh is simply slow to appear, but does appear eventually, that is not necessarily a problem with mesh itself; please work through this page: Slow Rezzing.

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 none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, type in Mesh2MaxConcurrentRequests and gradually decrease (not increase) the value. (If Advanced is not visible on the top menu bar, press Ctrl-Alt-D.) If it does not help, try increasing the value from the default. Under no circumstances should you increase this beyond 64. Please see this comment on a related JIRA ticket for an explanation of the possible drawbacks of increasing this setting. Additionally, we recommend returning it to default once the mesh you're trying to see is visible.

In most cases, this is due to the mesh item being made low LOD so as to reduce its land impact. You should never try to resolve this by increasing LOD above the maximum allowed in Preferences → Graphics → General (4), as that would result in greatly increased memory use, usually leading to a significantly increased rate of crashing. Rather, the issue is inherent in how the mesh item was made. So you either live with it, or replace the item.

The opposite effect of what was described above. This happens when mesh objects have far too many triangles in the high LOD models. The viewer is overloaded and cannot render anything else. To resolve this, you will need to remove some nearby items, preferably the ones that are too complex. You can try to determine which those are by editing each item, looking at the Object tab, and look at the mesh information on the right. Any mesh item – or group of mesh items – with an excessively high number of triangles is possibly causing your problem.

Reference this SL JIRA issue for more information, where you can see that it is considered expected behavior.

This happens more frequently for those using ATI/AMD graphics and drivers, but has been seen occasionally with Nvidia graphics and drivers as well. Visit Graphics Glitches for ways to address this.

If you can see most mesh fine but a specific mesh item fails to render and/or displays a pyramid, triangle, or ducky when it's first worn or rezzed, then read on. This is caused by mesh that fails to load, and in many cases is a result of having too high a draw distance in the presence of a lot of complex mesh.

• Reduce draw distance significantly, then relog. That often clears the problem.
• If that doesn't help, reboot all your network hardware and then your computer.
• (If the problem occurs only on selected regions, it could simply be a symptom of region lag–see this page for information. In this case, there may be nothing you can do about it.)

If this still doesn't help, then:

• Back up your settings - see this page
• Wipe your settings manually, as explained in this page
• Log back in and see if the mesh renders correctly. If it does…
• Restore your settings (see the backup page above), then check the mesh again.

In Preferences → Graphics → General, make sure Basic Shaders and Hardware Skinning are enabled.

Modern mesh bodies and heads often use a lot of smaller pieces to make up the whole item, so parts can be hidden under clothing. Sometimes the rigging information for one or more of these pieces gets corrupted during download and stuck in the viewer's cache. Currently, the best way to fix this issue is to clear cache.

Please note: this only applies when parts look broken or incomplete. For mesh parts that look ok but that are simply floating in space, see Slow Rezzing.

If certain mesh objects are invisible on Firestorm 5.0.11 on OpenSim grids, set the debug setting FSEnforceStrictObjectCheck to False. To change that setting:

1. Go to top menu, Advanced (Ctrl-Alt-D to enable Advanced, if it isn't), Show Debug Settings
2. Type in FSEnforceStrictObjectCheck, set to False
3. Close the DebugSettings window.

On OpenSim grids, mesh should never be uploaded using “Analyze”. Analyze should only be used on grids that support Havok.
On Firestorm 5.0.11, mesh uploaded with Analyze is likely to render invisible when FSEnforceStrictObjectCheck is set to true.

Doubled chat posts, doubled transactions, or other instances of doubling are caused by some kind of interference with your connection.

1) The problem mostly commonly has been caused by Norton Antivirus:
Uninstall Norton per https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us then reinstall. (Refer to SL BUG-11891.)

2) The problem has also been traced to Comodo Antivirus:
Test by turning off Comodo then rebooting your computer. See if the problem stops. If it does, you may need to use a different antivirus, or contact Comodo about the problem.

3) Sometimes this is a temporary network glitch:
Reboot your modem/router: Unplug them from all power and leave them unplugged for at least two minutes. Then reboot your computer too.

4) If you are on wifi, try wiring up to your router to see if that fixes it.

5) Doubled interactions recently attributed to ExitLag. Refer to FIRE-28965 Viewer Interactions Doubled

“Out of the box” you should be able to run more than one copy of Firestorm without doing anything. If you try and it doesn't work, then go to Preferences→ Advanced and make sure that “Allow Multiple Viewers” is enabled. If it wasn't, enable it and relog.

Mac does not really like to open two instances of Firestorm at once - you will notice it wants to bring the already-open one to the front. The standard way of duplicating the application is fairly resource-heavy, so here are two alternatives. Use Method 1 if you want to create a new instance right away. Method 2 requires more disk space. Method 3 requires some advance preparation, but once you have it set up, you'll be able to access Firestorm with any of your accounts quickly and easily.

Ctrl-click on Firestorm Viewer in your Applications folder and select “Show Package Contents.” In the folder that opens, go into “Contents” and then “MacOS.” In the MacOS folder, you'll find another Firestorm with a black box icon. Double-click this to open your new instance of the viewer. Terminal will open as well; you can let that run in the background.

You can run multiple viewers by copying the Firestorm application multiple times into the Applications folder.

1. Open a new Finder window and navigate to your Applications folder. Typically, this is on the left sidebar of the Finder window.
2. Find the Firestorm app and press the Command key and C (Cmd + C) at the same time to copy it to the clipboard. This is the same as copying text in a Word document.
3. While still in the Applications window, press the Command key and V (Cmd + V) to paste a new copy of the viewer into the folder just like you would paste copied text in Word. The Mac OS will automatically append an extension to the end of the copy of the viewer. For example, it may read something similar to “Firestorm_Releasex64 copy” to differentiate the copy from the original.
4. Double click on the copy of the viewer to run it like normal. Keep in mind that it will use the same cache folder as the original version, so things may take a little extra time to load.

With this method, you will spend some time setting yourself up, but once the work is done, logging into the viewer will never have been easier.

• Open Apple's Script Editor - it's in Utilities, in Applications. It will open a new script for you.
• Copy and paste the following into it:

do shell script "\"/Applications/Firestorm-Release.app/Contents/MacOS/Firestorm\" -multiple -login yourName yourPass"
quit

• Change yourName and yourPass to the correct name and password for your avatar.
• Change Firestorm-Release.app as needed for the version you use.
• Save. Give it a memorable name - you'll need a different one for each av, so have the avatar's name in there somewhere.
• Set the file format to Application, leave the other check-boxes clear (except 'hide extension', which is optional; whether you want it to say .app or not makes no difference to the functionality).
• Save it somewhere you can find it easily.
• Double-click to launch Firestorm for that avatar.

For more avatars, change the details and Save As…

Should you need to modify it in future, drop this “applet” onto Script Editor and it will open as editable text again.

There are many ways of getting great free stuff in SL to make your avatar look fantastic! There are many landmarks on this page; a G, or M indicates if the region is rated General or Moderate. To go to these shops, click on the landmark, a new web page will open, then click on teleport.

Free Dove has lots of quality stuff- look around carefully when you are there, because they usually have “hunts” with gifts from very good designers - these will be in small boxes or objects hidden everywhere in the shop.

The Bazaar Linden-support free stuff place, which anyone can contribute to. Mostly older things, but still much that may be helpful in getting started in SL.

The Stay at Home Club: Started during the COVID-19 crisis, this sites lists places offering free items in a number of categories. Click here to visit the site, then on Gifts at the top.

You can find a lot of free stuff on the marketplace. A good idea is to include the word “gift” in your search. Some items you might find useful:

• Female AO (to make your avi move naturally)
• Male AO
• Makeup
• Skins: type “skin gift” in the search slot and you'll get quite a lot - mostly female but some for the boys too!

Most designers have a group for their shop, which they use to send people news about new releases and events - if you join their group you will get gifts, generally on a monthly basis, but sometimes more often. Sooo… when you visit a shop, look out for group gifts - there is usually a group joiner next to them, and clicking on it you get instructions in local chat how to join the group. Some groups have a join fee, sometimes quite expensive, but many are free. Also, you'll find lucky chairs and lucky boards - if your name starts with the letter displayed on them, you win the prize.

Some stores offer free items for the Residents new to Second Life, with an age limit to be eligible to collect these gifts - eg:- Under 30 days of age

• Free hair pack to New Residents (2 weeks and younger) Just send a notecard with your name and hairstyle choice & color to * No Match Owner
  No Match Store location :- * No Match Hair Store

• Some free clothing for men at this in-world location.

• SEmotions free AO Bento - SEmotions (90 Days and younger)

• TuTy's free AO Bento - TuTy's (no age limit)

Many others available please use your search.

Another good idea is to Join an Inworld freebie shopping group! Not only will you be kept updated with all the latest freebies, but you can also get help and support to find the shops you are looking for.

There are quite a few around, but this one is probably the most popular: (to join, right-click the “group joiner” below, select “Copy to Clipboard”, then paste it in local - then click on the link that will appear)
Group joiner

Some good blogs featuring a lot of freebies:

• Fabulously Free in SL
• The SL Fashionista
• Teleport Hub
• Go Dutch
• Scoop It

And last but not least, there are treasure hunts! These are a really fun way to find new places and shops and get awesome free stuff!

You'll find the info to get you started here:

• Seraphim Hunts & Games Register
• FabFree SL Hunt Guide

Start with this page EEP Basics

SL Knowledge Base - Environment Editor

Inara Pey: Living in a Modem World - ENVIRONMENT ENHANCEMENT PROJECT: A PRIMER

Inara Pey: Living in a Modem World - TUTORIAL: ENVIRONMENT ENHANCEMENTS PROJECT (EEP)

Second Life Community - Environmental Enhancement Project (aka EEP!) Feedback Thread

Second Life's Lab Gab Episode 23 - EEP Team!

Second Life Tutorial|EEP, Environmental Enhancement Project (Italian)

Second Life Environmental Enhancement Project

Importing old settings
You can import your old Windlight settings into EEP.
Note that approximately 200 Windlight settings have already been imported and can be found in My Environments - Library - Environments folder. These can be accessed via Quick Preferences. Otherwise, right-click and copy as desired to your Inventory - Settings folder.

1. Open an environment editor (Daycycle, Sky, or Water)
   
2. Select the Import button - This will open a file picker dialog
3. Navigate to where you have stored your Windlight XML files and select the file you would like to import:
   • C:\Program Files\Firestorm_64\app_settings\windlight
   • C:\Users\User\AppData\Roaming\Firestorm_x64\user_settings\windlight (personalized custom files)

You should import Windlights of the same type as the editor you have open (Daycycle, Sky, or Water) Windlight XML files are very sensitive to the directory structure. Files should be laid out as follows: ./windlight/days ./windlight/skies ./windlight/water

Group Ability If a group member other than the owner needs to apply an environment to a parcel, assign the ability under Parcel Settings - Modify environment settings and day cycle.

Ability to create Camera Presets

CEF Viewer which supports YouTube Live streams. CEF = Wikipedia - Chromium Embedded Framework

The pages below have been updated to reflect some of the changes since Firestorm 6.3.9. Please do not bookmark them, as they will disappear once 6.4.x goes to public release.

• See Jira updates below.

Catznip RLVa 2.2 Release Notes

Release Notes for v6.4.0. (540188) - Second Life Viewer Released on Friday, April 17, 2020.
https://releasenotes.secondlife.com/viewer/6.4.0.540188.html

Environmental Enhancement Project - EEP

Welcome to the Environmental Enhancement Project (aka EEP!) EEP is a major enhancement to the legacy Windlight environments, introducing new inventory object for defining the environmental settings. To properly experience EEP you will need ALM (Advanced Lighting Model) enabled under your graphics settings.

Highlights Shareable environmental objects that you can keep in your inventory. Parcel level control of environments. Up to four different sky layers that may be set independently. More options for customization. And much, much more

Personal Lighting This EEP RC includes a new Personal Lighting floater. When you open this floater it will snap an image of the current shared environment wherever you are standing. You are presented with a number of controls that allow you to make quick modifications to the environment, including sun and moon position, ambient lighting, and more!

These changes will persist until you log out or select “Use Shared Environment” from the World>Environment menu, so you can close the floater to get it out of your way.

Release Notes for v6.4.1. (540593) - Second Life Viewer Released on Monday, April 27, 2020.
https://releasenotes.secondlife.com/viewer/6.4.1.540593.html

Maintenance: Zirbenz

The Zirbenz Stone Pine Liqueur is a specially crafted beverage that comes from the Alps in Austria. The key ingredient from which this liqueur draws its flavor is the Arolla Stone Pine Fruit that is native to the Alps. Exceptionally smooth, slightly sweet and with a crisp floral finish – this Pine liqueur has been made the same way since 1797. Since this is an artisanal liqueur, it is not mass produced in any factory. Usually enjoyed as an after-ski drink, the liqueur is also used in various cocktails. It is made from completely natural ingredients. This liqueur was first made by Josef Hofer. It is handcrafted and bottled in a family distillery till date.

Release Notes for v6.4.2. (541639) - Second Life Viewer Released on Monday, May 11, 2020.
https://releasenotes.secondlife.com/viewer/6.4.2.541639.html

Camera Presets

Improved camera controls, including the ability to save presets.

Release Notes for v6.4.3. (542964) - Second Life Viewer Released on Friday, May 29, 2020.
https://releasenotes.secondlife.com/viewer/6.4.3.542964.html

FMOD Studio

This viewer updates environmental and parcel audio playback to utilize the updated FMod Studio package.

Release Notes for v6.4.4. (543157) - Second Life Viewer Released on Tuesday, June 23, 2020.
https://releasenotes.secondlife.com/viewer/6.4.4.543157.html

CEF Update 2020

CEF Viewer which supports YouTube Live streams.

FMOD Studio 2.01.01 (updated Windows, Linux)
FMOD Studio 2.00.08 (Mac)

KDU v7.10.7 (Windows, Linux, Mac)

Voice Server Version: Vivox Version 4.10.0000.32327

LibVLC Version: 2.2.8

Chromium Embedded Framework (CEF) Dullahan:

• Dullahan: 1.7.0.202005311828
• CEF: 81.3.10+gb223419+chromium-81.0.4044.138
• Chromium: 81.0.4044.138
• Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

FIRE-23891 - [macOS] Mouse cursor jumps around when HiDPI is enabled and when using Pie menu
FIRE-24229 - Separate SL and Opensim settings folders / mixed up folders in appdata/roaming
FIRE-24311 - [BUG-228474] [SL-13082] [macOS] Blur when HiDPI Support Option Not Used
FIRE-29517 - [Mac] [Linux] Transitioning from third person view to mouselook freeze the view for a few seconds
FIRE-29567 - Potential crash caused by AO if floater is open at login
FIRE-29536 - media icon doesn't change when media is playing (MOAP)

Linden Lab Bug Tracker - EEP Issues Filter - requires login (SL username and password)

BUG-228882 - [EEP] Disabling glow rendering while ALM is off results in massive rendering flicker
BUG-228781 - [EEP] Specular color interpreted wrong (too bright) from point lights.
BUG-228581 - [EEP] Specular map reflections are way too weak.
BUG-228752 - [EEP] Sky turns black when render quality is lowered to Low-Mid
(Affects Windows and Mac. Unsure about Linux)
BUG-228586 - [EEP] Jumping glowing effect depending on the camera distance
(Really weird bug but on objects it repros on it's very jarring to see. Disabling glow with result in bug above)
BUG-228431 - [EEP] Water lighting is wrong at certain camera angles
BUG-226381 - [EEP] Low FPS on the Test DRTVWR-440 EEP project viewer
(How badly you are affected by this bug may depend if your system is CPU or GPU bound.)
BUG-228821 - Viewer stalls for a second or more 1 minute after teleporting to a different region.
BUG-228910 - Viewer freeze for several seconds after receiving a message from a large group.

No Jira issue filed. The default region environment on mainland looks dark & dingy and this is what any user on EEP will see by default on mainland.
It still looks fine on pre-EEP viewers.
See this forum post for an image: https://community.secondlife.com/forums/topic/453117-eep-finally-out/?do=findComment&comment=2129751
See Vir's explanation of the problem here: https://community.secondlife.com/forums/topic/453117-eep-finally-out/?do=findComment&comment=2130951

FIRE-5482 - [FS] Some panel opening resets the windlight function to region default.
FIRE-22897 - Using double click to teleport a short distance defeats RLV no TP
FIRE-22952 - Water rendering issues using advanced lighting with Firestorm 5.1.7 (55786)
FIRE-24072 - [Windlight bug] - changing it from like midnight to estate time causing tinting (same with sunset,sunrise,midday)
FIRE-24215 - @sittp:2=n can be defeated by double click
FIRE-29035 - [BUG-227534] [SL-11625] Skin won't load for Bakes on Mesh while editing shape
FIRE-29362 - Hover Tips on objects setting not honored.
FIRE-29477 - Error message when pasting in Outfits folder
FIRE-29603 - Crash when adding first AO set
FIRE-29605 - [BUG-228838] Unable to Save Outfits
FIRE-29608 - Disabling “Turn avatar towards camera direction on view reset” is ignored
FIRE-29614 - Console Fade Chat Cuts off at blank lines
FIRE-29623 - Crash - Unable to create error report - Please verify there is enough space in your TEMP folder
FIRE-29634 - [Starlight skin] Places Floater - Crash when trying to save a landmark
FIRE-29637 - [OpenSim][EEP] Cannot load settings for [NAME[ when entering OpenSim
FIRE-29638 - [OpenSim][EEP] No valid environment setting selected
FIRE-29642 - Area Search, Distance to HUD = Distance to <0, 0, 0>
FIRE-29649 - [BUG-228852] FS crash when trying to open Spell Check floater when “SpellCheck” is FALSE
FIRE-29661 - Compile Error Linux 6.4.4 OpenAL
FIRE-29672 - FPS are not visible in tool bar with italian language
FIRE-29678 - Unable to use Notecard Editor
FIRE-29679 - OPENSIM: 6.3.9.58205 crashes when rezzing a mesh with edit floater open
FIRE-29684 - EEP - Missing string “New Day”

FIRE-2099 - Better Camera Control - Expose Debug Settings via Preferences Panel

FIRE-29641 - Russian translation update
FIRE-29669 - Russian translation update
FIRE-29703 - French translation update
FIRE-29713 - Japanese translation update
FIRE-29745 - Russian translation small update (correction)

FIRE-29611 - [RLVa] @setcam_eyeoffset command needs to be adapted for camera presets

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