

Under Construction
To use the Restrained Love features built in to Phoenix, you need to follow a few simple steps:
CTRL-P
to open the Preferences
panel.Phoenix
Page 1
Misc
After this you have to restart Phoenix to get RLVa working. Additionally you usually need to get a so-called Relay. This is an attachment you wear that enables objects in-world to interact with your viewer. These Relays are usually free of charge and come as HUDs or pieces of jewelry you wear. It's recommended to get a “Multi Relay”, so you can be controlled by more than one device at the same time.
If you also want to enable traps and toys to put folders into your inventory, you need go through a few additional steps:
Phoenix
menuShow Advanced
Advanced
menuRLVa
Forbid Give to #RLV
CTRL-I
)My Inventory
New Folder
#RLV
(be sure to use uppercase letters, exactly as shown here)
Now you should be able to accept inventory from traps and toys, which will automatically be moved into the #RLV
folder tree.
Note that the latest Phoenix supports 2.2.0 of the RLV spec.
Under Construction! This page is very experimental. Don't rely on it unless you want to do a lot of pioneering yourself.
There is no official support for compiling or operating self-compiled viewers. There may be unofficial support as listed at the bottom of this page.
These instructions only apply to Firestorm version 5.1 and above. For older versions, please see this page.
This procedure is used for building a 64-bit version of Firestorm 5.1 on 64-bit Debian systems. It was tested and verified on Debian 9.3. This procedure assumes that your system has been properly updated.
This procedure may not work on older versions of Debian, nor has it been tested on any other version of Debian or any other distribution/variant/derivative.
The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommded 8GB or more RAM, quad-core CPU and 32GB available HDD space.
This is needed for compiling any viewer based on the LL open source code and only needs to be done once.
Firestorm requires version 4.9 or 4.8 of the gcc/g++ compiler. This is not available in Debian 9's default repositories, so we need to add a Jessie repo.
sudo add-apt-repository "deb http://ftp.us.debian.org/debian/ jessie main" sudo apt update
The required tools, some of which may already be installed, are:
bison | bzip2 | cmake | curl | doxygen | flex | g++ | gdb | m4 (for make) | mercurial (for hg) | moreutils (for additional build tools | pkg-config | python | python-dev | python-pip |
sudo apt upgrade # to make sure all installed packages are current sudo apt install --install-recommends moreutils bison bzip2 cmake curl doxygen flex g++-4.9 gdb m4 mercurial pkg-config python python-pip
(the –install-recommends flag tells apt-get to install all packages recommended by each named package.)
The build environment need to know to use gcc 4.9:
sudo update-alternatives --remove-all gcc sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 49 \ --slave /usr/bin/g++ g++ /usr/bin/g++-4.9 \ --slave /usr/bin/gcov gcov /usr/bin/gcov-4.9 sudo update-alternatives --config gcc
Note that this will “hide” the current gcc from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.
Firestorm 5.1, like the AlexIvy release of the Linden Lab viewer, is built with the USESYSTEMLIBS flag set, so that the libraries are installed on the user's system as needed and not shipped with - or maintained by - the viewer. This means that a large number of development libraries must be installed on the build system.
These libraries may be included with your distribution, and some may already be installed:
libalut-dev | libapr1-dev | libaprutil1-dev | libatk1.0-dev | libboostall-dev | libcairo2-dev | libcollada-dom2.4-dp-dev | libcurl4-openssl-dev | libdbus-glib-1-dev | libfreetype6-dev |
libGL.so (libgl1-mesa-dev) | LibGLU.so (libglu1-mesa-dev) | libgtk2.0-dev | libjpeg-dev | libjsoncpp-dev | libnghttp2-dev } libogg-dev | libopenal-dev | libpangox-1.0-dev | libpng-dev | libsdl1.2-dev |
libssl-dev | libstdc++.so.6 (libstdc++6) | liburiparser-dev | libvorbis-dev | libX11.so (libx11-dev) | libxinerama-dev | libxml2.so (libxml2-dev) | libxmlrpc-epi-dev | libXrender.so (libxrender-dev) |
sudo apt install --install-recommends libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev libcairo2-dev \ libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev libgl1-mesa-dev \ libglu1-mesa-dev libgtk2.0-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev libogg-dev libopenal-dev \ libpangox-1.0-dev libpng-dev libsdl1.2-dev libssl-dev libstdc++6 liburiparser-dev libvorbis-dev libx11-dev \ libxinerama-dev libxml2-dev libxmlrpc-epi-dev libxrender-dev zlib-dev
Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild form Linden Lab, version 1.1 or above.
pip install --upgrade pip pip install autobuild
This will install autobuild and add a link in the exec path.
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, I will assume ~/src.
cd ~/src
There are several repositories 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.
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl
It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source
The rest of this document will assume the default directory, phoenix-firestorm-lgpl
This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:
#!/bin/bash cd ~/src hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl cd phoenix-firestorm-lgpl for i in {15000..50000..5000} do echo "Grabbing to change $i" hg pull -u -r $i done echo "Grabbing to tip" hg pull -u cd ~/src
Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.
cd ~src hg clone https://bitbucket.org/Ansariel/fs-build-variables
Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.
cd ~/src/phoenix-firestorm-lgpl source ../fs-build-variables/convenience Release export AUTOBUILD_VARIABLES_FILE=~/src/fs-build-variables/variables
Unlike previous versions of autobuild, version 1.1 requires the address size switch after the command, not before it. If you want a 32-bit build, you must specify that; there is no default any longer.
cd ~/src/phoenix-firestorm-lgpl autobuild configure -A 64 -c ReleaseFS_open
This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.
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.
TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE
Examples:
autobuild configure -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE autobuild configure -A 64 -c ReleaseFS_open -- --clean
The first time you configure, several additional files will be downloaded from Firestorm and Second Life sources. These are mostly binary packages maintained outisde the viewer development itself. And if you use the –clean switch, you will re-download them all.
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.</WRAP>
Create the desktop launcher
cd ~/src/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/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged ./firestorm
You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged to another location if you choose, and then launch firestorm from there. Example:
mkdir ~/Firestorm cp -a ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/* ~/Firestorm cd ~/Firestorm ./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher
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.
If you found a procedural error in this document, please let us know in as much detail as you can, either contact the team (preferred) or discuss on IRC.
For basic information on how to get help, click here.
This page covers issues and problems which you might encounter with Firestorm; for topics concerning how to use the viewer, you are instead directed to the main Firestorm documentation page.
The topics here are divided into issues which are directly related to the viewer, and those which are really SL issues or bugs.
Should this not be helpful, then please contact support. The best place to get fast help is in one of the in-world groups. Otherwise, you may contact any of our support team. We will do our best to assist you.
If you believe you have found a genuine bug - or have a feature request, then you can file a JIRA.
For an introduction to the basics of troubleshooting, please refer to this page.
Phoenix has some video tutorials on YouTube; you may want to visit and bookmark the Phoenix Viewer channel.
The pages below have been updated to reflect changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.3 goes to public release.
AlexIvy 64bit - Fully merged up to LL's AlexIvy viewer https://community.secondlife.com/blogs/entry/2290-64-bit-viewers-for-all/ for Windows and Mac. As a result of this update, there is no Linux viewer available. The Linux community is working to resolve this and accordingly, there is no way to anticipate when a Linux viewer will be available for testing.
Chromium Embedded Framework (CEF) Dullahan updated Dullahan: 1.1.820 / CEF: 3.3071.1634.g9cc59c8 / Chrome: 59
FMOD Studio 1.10.04
KDU updated to v7.10.4. KDU updates force a texture cache clear on first run. You may wish to do this manually if you have a slow system or network.
Voice Update: Vivox Version 4.9.0002.27586
BUG
FIRE-6155 - Previewing an animation to upload while walking/sitting/flying results in the avatar getting stuck in that animation
FIRE-9070 - build window xyz colors not changing for rotate and size
FIRE-12249 - Develop - Render Metadata - Avatar Hitboxes makes eyes disappear
FIRE-13474 - Saving .dae with brackets in filename fails
FIRE-17518 - [CEF] Opening Preferences from the login screen breaks the login page layout.
FIRE-19704 - [Mac] Crash when upload Mesh 50499 - Calculate Weights and Fees (Mac El Capitan) - LLModelgetJointInfluences(LLVector3 const&)
FIRE-21974 - recovered script after crash is empty
FIRE-22175 - [Mac] [BUG-202965] [MAINT-8208] Firestorm crashes when I use a cube as physic when uploading a mesh model
FIRE-22179 - Preprocessor warning when last line in lsl include is a comment: generic lexer warning: Unterminated C++ style comment
FIRE-22214 - Script Editor - Missing Line numbers, Vintage Skin
FIRE-22241 - Copy paste inserting timestamps unexpectedly
FIRE-22268 - Firestorm crashing when deleting items
FIRE-22281 - [BUG-214575] [MAINT-8289] Deleting inventory directory while keeping [Delete] key preesed
FIRE-22288 - [Mac] [BUG-214585] [MAINT-8287] Creating an admin group role is back. While creating a role, in a new group, once you tick the manage ban list you crash.
FIRE-22297 - [Mac and Linux only?] FPS limiter not working (do not move to Support)
FIRE-22330 - Crash when taking photos
FIRE-22346 - [Opensim] Remove Avination from Grid Manager
FIRE-4963 - using animation upload window disables physics wearables
FIRE-5686 - undocked IM window does not stays at his place after relog and undock again
FIRE-16651 - Animation upload/preview breaks eye movement
FIRE-20866 - @stopim returns The other party is not under a @startim restriction when they are
FIRE-21719 - Copy-Paste a Folder doesnt copy the links to the new folder
FIRE-22148 - Group profile icons unload when Group Titles is opened
FIRE-22164 - Black Text against very dark background Firestorm Skin Dark Scheme Experience Edit WIndow.
FIRE-22167 - Show in Main View fail in 2nd Inventory Window
FIRE-22187 - Typo in Prefs - Chat - Visuals
FIRE-8784 - Align tool not working on some prims
FIRE-9561 - Items worn from Marketplace Tab do not show up as worn items
FIRE-21425 - [CEF] Problem with drop-down menus in internal web browser.
FIRE-21579 - [BUG-202634] [MAINT-8023] Missing support for internationalized domain names.
FIRE-22383 - Links in 1st life profile tab disappear after second save
IMPROVEMENT
FIRE-15266 - Toolbar Button for Beacons
FIRE-20959 - Update in-world browser cipher suites
FIRE-22331 - [Opensim] Mesh uploaded with Analyze likely to render invisible
FIRE-22334 - Reset All Settings button misleading
FIRE-4595 - Paste as Link - in system generated folders like outfits
FIRE-16207 - [Starlight CUI] Contact Sets Panel text
FIRE-22116 - Pennys Windlight Presets
FIRE-5974 - Allow SEARCH to include Received Items Folder
FIRE-22354 - Beyond chat range diminish factor slider is confusing
NEW FEATURE
FIRE-19520 - Add per-item render-weight display to Appearance window
FIRE-20809 - HUD Management, Favorite Wearables Folder (protected) and Toolbar Button
FIRE-20818 - Option to adjust font size in script editor
FIRE-21078 - Show Rendering Cost per attachment
FIRE-22115 - Jeans Windlight Presets
Under Construction! This page is very experimental. Don't rely on it unless you want to do a lot of pioneering yourself.
There is no official support for compiling or operating self-compiled viewers. There may be unofficial support as listed at the bottom of this page.
These instructions only apply to Firestorm version 5.1 and above. For older versions, please see this page.
This procedure is used for building a 64-bit version of Firestorm 5.1 on 64-bit Ubuntu 16.04 LTS systems. It was tested and verified on Ubuntu 16.04.4. This procedure assumes that your system has been properly updated.
This procedure may not work on older versions of Linux, nor has it been tested on any other current or LTS version of Linux/Ubuntu or any other distribution/variant/derivative.
The build process requires at least 6GB RAM (8GB recommended) with swap, a modern quad-core CPU and at least 24GB available disk space.
This is needed for compiling any viewer based on the LL open source code and only needs to be done once.
The required tools, some of which may already be installed, are:
bison | bzip2 | cmake | curl | doxygen | flex | g++ | gdb | m4 (for make) | mercurial (for hg) |
moreutils (for additional build tools | pkg-config | python | python-dev | python-pip |
sudo apt upgrade # to make sure all installed packages are current sudo apt install --install-recommends bison bzip2 cmake curl doxygen flex g++-4.9 gdb m4 \ mercurial moreutils pkg-config python python-dev python-pip
(the –install-recommends flag tells apt to install all packages recommended by each named package.)
The build environment needs to know to use gcc 4.9:
sudo update-alternatives --remove-all gcc sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 49 \ --slave /usr/bin/g++ g++ /usr/bin/g++-4.9 \ --slave /usr/bin/gcov gcov /usr/bin/gcov-4.9 sudo update-alternatives --config gcc
Note that this will “hide” the current gcc from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.
Firestorm 5.1, like the AlexIvy release of the Linden Lab viewer, is built with the USESYSTEMLIBS flag set, so that the libraries are installed on the user's system as needed and not shipped with - or maintained by - the viewer. This means that a large number of development libraries must be installed on the build system.
These libraries may be included with your distribution, and some may already be installed:
libalut-dev | libapr1-dev | libaprutil1-dev | libatk1.0-dev | libboostall-dev | libcairo2-dev | libcollada-dom2.4-dp-dev | libcurl4-openssl-dev | libdbus-glib-1-dev |
libfreetype6-dev | libGL.so (libgl1-mesa-dev) | LibGLU.so (libglu1-mesa-dev) | libgtk2.0-dev | libjpeg-dev | libjsoncpp-dev | libnghttp2-dev } libogg-dev | libopenal-dev | libpangox-1.0-dev |
libpng-dev | libsdl1.2-dev | libssl-dev | libstdc++.so.6 (libstdc++6) | liburiparser-dev | libvorbis-dev | libX11.so (libx11-dev) | libxinerama-dev | libxml2.so (libxml2-dev) |
libxmlrpc-epi-dev | libXrender.so (libxrender-dev) | zlib1g-dev |
sudo apt install --install-recommends libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev \ libcairo2-dev libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev \ libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev libogg-dev \ libopenal-dev libpangox-1.0-dev libpng-dev libsdl1.2-dev libssl-dev libstdc++6 liburiparser-dev \ libvorbis-dev libx11-dev libxinerama-dev libxml2-dev libxmlrpc-epi-dev libxrender-dev zlib1g-dev
Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild form Linden Lab, version 1.1 or above.
sudo pip install --upgrade pip sudo pip install autobuild
This will install autobuild and add a link in the exec path.
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, I will assume ~/src.
cd ~/src
There are several repositories 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 1.1GB initially and around 12.4GB after the binaries have been built, plus possible compiling overhead.
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl
It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source
The rest of this document will assume the default directory, phoenix-firestorm-lgpl
This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:
#!/bin/bash cd ~/src hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl cd phoenix-firestorm-lgpl for i in {15000..55000..5000} do echo "Grabbing to change $i" hg pull -u -r $i done echo "Grabbing to tip" hg pull -u cd ~/src
Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.
cd ~src hg clone https://bitbucket.org/Ansariel/fs-build-variables
Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.
cd ~/src/phoenix-firestorm-lgpl source ../fs-build-variables/convenience Release export AUTOBUILD_VARIABLES_FILE=~/src/fs-build-variables/variables
Unlike previous versions of autobuild, version 1.1 requires the address size switch after the command, not before it. If you want a 32-bit build, you must specify that; there is no default any longer.
cd ~/src/phoenix-firestorm-lgpl autobuild configure -A 64 -c ReleaseFS_open
This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.
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.
TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE
Examples:
autobuild configure -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE autobuild configure -A 64 -c ReleaseFS_open -- --clean autobuild configure -A 64 -c ReleaseFS_open -- --chan="My-Build" # sets the viewer name to "Firestorm-My-Build"
The first time you configure, several additional files will be downloaded from Firestorm and Second Life sources. These are mostly binary packages maintained outisde the viewer development itself. And if you use the –clean switch, you will re-download them all.
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.</WRAP>
Create the desktop launcher
cd ~/src/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/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged ./firestorm
You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged to another location if you choose, and then launch firestorm from there. Example:
mkdir ~/Firestorm cp -a ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/* ~/Firestorm cd ~/Firestorm ./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher
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.
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 may contain resolved tickets.
Search using the error you encountered.
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 team (preferred) or discuss on IRC.
At present, voice does not work. There are two workarounds:
Download this tarball and extract the contents to your Nightly or Tip's /bin folder. It is in a win32 folder because that's what the viewer is looking for.
Launch the viewer but don't log in. Open the Debug menu (if you don't see it, Preferences > Advanced, enable Show Advanced Menu), and select Show Debug Settings. In there, search for FSLinuxEnableWin32VoiceProxy and set that to TRUE. Close Debug Settings.
Note that you can change FSLinuxEnableWin32VoiceProxy while logged in, but make sure voice is disabled first.
In Release, in its /lib folder, locate “libvivoxoal.so.1” and copy that to your Nightly or Tip's /lib folder.
Make sure you set the FSLinuxEnableWin32VoiceProxy debug setting to FALSE for this workaround.
Autobuild.xml refers to a newer – and broken – version of openjpeg for 64-bit Linux. The workaround is to modify autobuild.xml as follows:
Locate autobuild in the Firestorm source folder and open it with a text editor.
Search for openjpeg-1.5.1.180841553-linux64-180841553.tar.bz2
and replace it with http://downloads.phoenixviewer.com/openjpeg-1.4.201505150222-r26-linux-x64-201505150222-r26.tar.bz2
Just above that line is the hash 6098e555296583336b02f1a78b41b93a
, replace that with f8a5ed12a0b45e0c48e04642ee736426
Save the file, then configure with the –clean option.
This may occur if you did not or could not install the listed packages. The packages do exist in the default Ubuntu 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.
This is a collection of error messages seen in SL. Some are system messages; some are viewer-generated. The list is by no means complete. If you get an error message that is not on this page, please report it in Firestorm Support English (in-world support group) or File a Jira alerting us to it (please provide the complete, exact wording of the message; a screenshot is also helpful).
Error | Remedy |
---|---|
“PERMISSION_TRIGGER_ANIMATION permission not set” | This message usually comes from an AO or other scripted item, dropped in world. It can also come from a badly scripted object that doesn't check it has perms before animating, such as a badly written poseball. |
Error | Remedy |
---|---|
“You can't attach multiple objects to one spot” message when detaching from avatar. | That will happen if the user somehow has a coalesced object in their current outfit folder. Delete it. |
“The outfit folder contains no clothing, body parts, or attachments.” | See Empty Outfits |
Error | Remedy |
---|---|
“Unable to find a valid certificate” | See Second Life: Unable_to_find_a_valid_certificate. |
Error | Remedy |
---|---|
“We were unable to decode the file storing your saved login credentials” (or) “Failed to decode login credentials” | See Failed to Decode Login Credentials |
Error | Remedy |
---|---|
“Unable to connect to Second Life. Often this means that your computer's clock is set incorrectly. Please go to Control Panels and make sure the time and date are set correctly.” | See Second Life: Clock is set incorrectly. |
Error | Remedy |
---|---|
“Unable to establish a secure connection to the login server” | See Second Life: Unable to establish a secure connection to the login server . |
“Second Life has detected corruption in either your network transmissions or the files it's attempting to read on your hard drive. You might also be logging in from an invalid location.” | See Second Life: Mangled network data. |
Error | Remedy |
---|---|
“Unable to create item that has caused problems on this region.” | 1) Have the region restarted; this will usually fix it. 2) If a region restart doesn't clear it up, the sim owner may need to ask LL to move the sim to another server channel. |
“We are sorry, Linden Lab has discovered degraded performance on your connection to the region you are on. You will need to restart Second Life and log into a new region for the next 30 minutes to an hour. We apologize for the inconvenience.” | Delete landmarks, especially favorite landmarks. If they point to an invalid location, it can cause this message. This may also mean exactly what it says; follow the instructions. |
Error | Remedy |
---|---|
“Do you want the application 'SLVoice' to accept incoming network connections?” | Mac – This is a message from your computer's firewall. You should choose “Allow” for voice to work. |
Error | Remedy |
---|---|
Sorry, you do not have access to that teleport destination. |
Error | Remedy |
---|---|
“# of textures discarded” message usually followed by a crash | See Textures Discarded. |
Error | Remedy |
---|---|
“Firestorm is unable to run because your video card drivers did not install properly or are out of date, or are for unsupported hardware. Please make sure you have the latest video card drivers, and even if you do have the latest, try reinstalling them. If you continue to receive this message, contact the Second Life Support Portal” | See Intel Fix 32-Bit |
Error | Remedy |
---|---|
“Index out of range: 34 not in [ 0, 11]” | From the login screen, open the Debug Menu - Show Debug Settings - RenderDebugGL. Set to FALSE. Relaunch the viewer and login. |
“newview/llappviewer.cpp(1838): Unhandled exception caught in bool” _cded LLAppViewer::frame(void): No diagnostic information available | If the error happens in only one region, clear cache |
“Must supply a comment for control content” | The installation is corrupt. Uninstall Firestorm, delete the installer, clear your web browser's cache (or use a different browser) and download a fresh installer from http://www.firestormviewer.org/downloads/ and install that. |
Wiki pages in other languages | ||||||
---|---|---|---|---|---|---|
Deutsch | Español | Francophone | Italiano | Nederlands | Polski | Русский |
See this page for documentation on Firestorm 4.6.7 (42398) and earlier.
If you're looking for how to get your own event in the Firestorm Message of the Day, click here.
If you're looking for a missed MotD or more information on the current MotD rotation, keep reading!
Oh hi! I didn't see you come in! You're probably here because you missed the message of the day. It went by to fast, it was to long, or you clicked a link in a goofy motd set up to get you here!
Anyway, if you missed the message of the day and would like to see it again;
At the top of your screen find the “Content” menu and click it.
In the menu that drops down, way down at the bottom select, “Message of the Day”.
There it is, in your local chat as a system message.
[11:28:02] [Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd]
You can also scroll down this page and see ALL the current messages of the day in the “events, tips, help and gateway” message of the day rotation. (I keep this page bookmarked as a fast reference to important wiki pages.)
The Firestorm Message of the Day is currently running on a rotation of thirty eight preset tips, help, gateway and fun messages and/or a varying amount of event messages of the day. All of which are displayed at random when you log in depending on which “MotD Cartridge” is loaded. Go ahead, try it, relog, and unless the message of the day is promoting a special event1) you'll see something different.
The preset messages of the day are split between tips to make your Firestorm Viewer experience more efficient and enjoyable, help topics to help resolve common Firestorm Viewer issues, gateway to spread information about the Firestorm Gateway and fun just because.
I'll list the message of the day presets below so you can see what's in the rotation.
These are the current messages of the day for events which are currently running and have been approved for a Firestorm message of the day;
MOTD: EVENT: 2018 SciFi Expo Registration
The SciFi Expo in support of The American Cancer Society's RFL of SL is now accepting applications for their event running May 12 to 20! Click to sign up! https://slscifiexpo.wordpress.com
MOTD: EVENT: 2018 Rock Your Rack Registration
Rock Your Rack 2018 supporting the National Breast Cancer Foundation is now taking designer registrations for their October event! Click for more! https://rockyourrack.wordpress.com/about/designers/
These are displayed randomly and are broken down into three groups;
Tips: Which provide tips on how to get the most out of the Firestorm Viewer and are meant to improve your Second Life experience in some way.
Help: Which provide assistance on self resolving common Firestorm problems which are seen the most in the Firestorm Viewer help groups. These may have also been requested by the Firestorm Support Team at some point.
Gateway: Coming soon! These provide information on what's going on at the Firestorm Gateway, events, event spaces, classes and more.
I'll break them into the same groups below;
MOTD: TIP: Firestorm Classes 1Temporarily removed from the rotation.
Did you know Firestorm has classes on how to use the Firestorm viewer? We even have an open question and answer session after each class! http://wiki.phoenixviewer.com/firestorm_classes
MOTD: TIP: Firestorm Classes 2Temporarily removed from the rotation.
Did you know Firestorm offers classes on how to get the most out of the Firestorm viewer? Click to find out more about these classes and when they are! http://wiki.phoenixviewer.com/firestorm_classes
MOTD: TIP: Avatar Complexity
Firestorm tip! Why is my friend a colored shape? What is this complexity popup thingy? Click here to find out more about this lag reducing feature! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings
MOTD: TIP: Complexity and the Slideshow
Firestorm tip! Are you at a busy club or event and Firestorm is running like a slide show? Try lowering your avatar complexity setting! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings
MOTD: TIP: FS Bridge, Trolls Not Included
Firestorm Tip! The Firestorm BRIDGE is enhancing your SL experience and you may not even know it! Click here to find out how! http://wiki.phoenixviewer.com/fs_bridge
MOTD: TIP: Can Not Log in to SL
Firestorm Tip! Can't log into Second Life? STOP! DO NOT reinstall firestorm! Save yourself a lot of trouble and check here first for possible grid issues https://status.secondlifegrid.net/
MOTD: TIP: Contact Sets
Firestorm Tip! Contact Sets allow you to organize friends and non friends into manageable groups and categories! Learn more about them at http://wiki.phoenixviewer.com/fs_contact_sets
MOTD: TIP: IM Tab Sorting
Firestorm tip! Did you know you can click and drag your IM tabs in the conversations window to sort them to your liking. For more chat tricks see http://wiki.phoenixviewer.com/fs_chat
MOTD: TIP: Customizable Quickprefs
Firestorm tip! Did you know you can add your most commonly used settings to the Quick Prefs? http://wiki.phoenixviewer.com/fs_quick_preferences
MOTD: TIP: Missed the MotD
Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd
MOTD: TIP: Outfits
Firestorm tip! Did you know the Outfits feature can help you quickly change what you're wearing without digging around in your inventory? http://wiki.phoenixviewer.com/my_outfits_tab
MOTD: TIP: Camera Controls
Firestorm tip! Something catching your eye? Hold down your ALT key and click it, then roll your mouse wheel! Interested in more? See http://wiki.phoenixviewer.com/fs_movement_and_camera#view
MOTD: TIP: Toolbars
Firestorm tip! Did you know you can add many of your commonly used Firestorm windows and floaters to the toolbars? http://wiki.phoenixviewer.com/toybox
MOTD: TIP: SL World Search
Firestorm tip! Looking for something in world but, can't find it? Try a search! http://wiki.phoenixviewer.com/floater_search
MOTD: TIP: Replace Links
Firestorm tip! Gah my inventory links are borkened! Have no fear, Replace Links are here! Fix those broken links, http://wiki.phoenixviewer.com/fs_linkreplace
MOTD: TIP: Skins
Firestorm tip! Wanna change the way firestorm looks? Then change it! http://wiki.phoenixviewer.com/preferences_skins_tab
MOTD: TIP: Settings Backup
Firestorm tip! Better safe than… NOOOOOOO! You should regularly back up your Firestorm settings. You never know when…. http://wiki.phoenixviewer.com/backup_settings
MOTD: TIP: Auto Replace
Firestrom tip! Firestone? Firestorm! If only Firestorm had an auto replace… Oh wait! It does! http://wiki.phoenixviewer.com/fs_auto_correct
MOTD: TIP: Preference Search
Firestorm tip! Is a Firestorm setting playing hide and seek and causing you to pull out your hair? Find it fast with preference search! http://wiki.phoenixviewer.com/fs_preferences
MOTD: TIP: Chat Shortcuts
Firestorm tip! Did you know when chatting you can hold down your ctrl key when you press enter to shout and the shift key to whisper? http://wiki.phoenixviewer.com/keyboard_shortcuts
MOTD: TIP: Keyword Alerts
Firestorm tip! Did you miss a message in chat? Did someone say your name while you were doing something else? Check out Keyword Alerts! http://wiki.phoenixviewer.com/preferences_chat_tab#keyword_alerts_tab
MOTD: TIP: FS Wiki
Firestorm Tip! Did you know Firestorm has its own wiki? Find out how features work, how to fix common viewer issues and more! Check it out, bookmark it, study it! http://wiki.phoenixviewer.com/
MOTD: TIP: Inventory Count
Firestorm Tip! Do you have more inventory than you thought you had? Inventory count now includes folders! Click for more http://wiki.phoenixviewer.com/my_inventory_tab
MOTD: TIP: Elements
Firestorm Tip! Elements? What is this, chemistry class? No silly, Elements is the count of Items/Folders in that folder! Click for more http://wiki.phoenixviewer.com/my_inventory_tab
MOTD: HELP: Bakefail Badness
Firestorm Help! Are you feeling overly misty as an orange cloud? Are you missing your avatar? Are you thinking, clouds belong in the sky, not on me! Click here to fix the cloud http://wiki.phoenixviewer.com/fs_bake_fail
MOTD: HELP: Camera Messed Up
Firestorm Help! HALP! I know my head looks awesome but I'm stuck staring down at the top of it! Why am I staring at my butt? What is wrong with my camera?! click click clickie! http://wiki.phoenixviewer.com/fs_camera
MOTD: HELP: Teleporting Woes
Firestorm Help! What is up with these teleport fails? Disconnected?! OMG again! Click here to help prevent TP issues! http://wiki.phoenixviewer.com/fs_tp_fail
MOTD: HELP: Slow Rezzing
Firestorm Help! Did you know many common rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/slow_rez
MOTD: HELP: Slow Rezzing Mesh
Firestorm Help! Did you know many common mesh rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/mesh_issues
MOTD: HELP: Getting Help NAO
Firestorm Help! HALP! My Firestorm is broken and I need help NAO! Have no fear, click here! http://wiki.phoenixviewer.com/getting_help
MOTD: HELP: Getting Help Dont Panic
Firestorm Help! Sudden viewer problems? Not sure what to do? Don't panic! check out our wiki: http://wiki.phoenixviewer.com/getting_help
MOTD: HELP: Voice Issues
Firestorm Help! Have you lost your voice? Firestorm voice not working for you? Why not drink a tall glass of http://wiki.phoenixviewer.com/fs_voice
MOTD: HELP: Rick and Morty Lost Login Info
Oh geez, Rick, Firestorm lost my login info again! Well, Morty, try starting here to fix it, http://wiki.phoenixviewer.com/fs_stored_passwords#failed_to_decode_login_credentials
MOTD: HELP: Help Help Help You
Firestorm Help! Need help? Help us help you! Learn how to use the Firestorm support group to get the best help! http://www.firestormviewer.org/firestorm-help-groups-tips-rules-and-guidelines/
MOTD: HELP: Second Life Account Questions
Firestorm Help! Need help with your Second Life account matters? Go to Avatar Menu - Account, or login to your Dashboard at https://secondlife.com/my/account/
MOTD: HELP: Dont Clear Your Cache
Firestorm Help! Having viewer problems? Please don't clear your cache or reinstall the viewer as the first thing you try. Instead, see this page for how to get help http://wiki.phoenixviewer.com/getting_help
MOTD: HELP: Missing Inventory
Firestorm Help! Ummmm, I know I had more things in my inventory than this! Help! I'm missing inventory! what can I do? http://wiki.phoenixviewer.com/fs_missing_inventory
MOTD: GATEWAY:
Keep an eye here for upcoming information regarding the Firestorm Gateway!
MOTD: FUN: Rhubarb Pie
Firestorm fun! Feeling hungry? try a Rhubarb Pie, Firestorm style! http://wiki.phoenixviewer.com/rhubarb_pie
This section is changing as we speak!
* if a main MOTD is set, that one is always shown
* if random MOTDs are set and no main MOTD is set, they will be randomly shown at login and during TP
* if an event MOTD is set, that is always shown at login and then, during TP either the main MOTD or one of the random MOTDs
Here, you can enable/disable three special shortcuts:
Each of the above can, optionally, play an alert sound, which you can change by specifying your own sound clip UUID. You an hear the sound by clicking the button labelled 'P', or revert the sound to the default by clicking the 'D'.
Note that the names shown by radar, in the nearby chat window, can be clicked to open a profile.
Note: Because Group Chats are prevented from appearing when either When Receive Group Notices is disabled, Disable Group Chat As Well or Disable All Group Chats are enabled (see above), no alerts are triggered.
See this page for a tutorial video.
All of the commands below can be changed from the supplied defaults.
There are a few other commands which are not shown here (and therefore cannot be changed). These include:
See this page for documentation on Firestorm 5.0.7 (52912) and earlier.
There is no real fix for this crash (the fix will need to come from Apple); however, switching over to using the Nvidia web drivers will stop the crashes. There is a chance of the viewer running with poorer performance.
(This crash has continued on Sierra.)
This problem affects other games, too; for example, see constant crashes - OS X 10.11 El Capitan and OSX El Capitan 10.11 Beta (15A21). The same workaround appears to fix the problem in other games also; that is, to switch over to using the Nvidia web drivers instead of the Nvidia driver that Apple provides.
Please note that this is not a viewer-specific crash. Refer to this Firestorm Jira: [BUG-10302] [Mac El Capitan] Firestorm crash/incompatibility with Mac OS 10.11 and this SL Jira: BUG-10302 Frequent Crashes in Mac OS X 10.11 El Capitan.
If some characters now display as boxes, you can edit the fonts.xml file within Firestorm to cause the characters to load properly.
<os name=“Mac”>
, insert this line: <file>ヒラギノ角ゴシック W3.ttc</file>
<os name="Mac"> <file>ヒラギノ角ゴシック W3.ttc</file> ///(only insert this line and leave everything else as is.)/// <file>ヒラギノ角ゴ Pro W3.otf</file> <file>ヒラギノ角ゴ ProN W3.otf</file> <file>AppleSDGothicNeo-Regular.otf</file> <file>AppleGothic.dfont</file> <file>AppleGothic.ttf</file> <file>华文细黑.ttf</file> </os>
NOTE: This is only necessary for Firestorm versions 4.7.3 and older.