

If this occurs, chance are good that the inventory cache is corrupt. Deleting it should solve the problem.
Windows only: If the above doesn't work, then click the speaker icon in the system tray, then touch the volume slider, just enough to change the volume slightly. It may be that the Windows sound system has stalled; this should “give it a kick”.
If the above fails, then try doing a full wipe of all settings.
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:
<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>
Issues outside of Firestorm can, and often do, result in viewer crashes….
If you are using Windows 10, and have an Intel 2000/3000 or older graphics card, please refer to this page if you cannot start Firestorm without crashing.
If you crash during login, then try setting Firestorm to XP compatibility:
If you get a User Account Control security popup, then please see this page.
If you have just installed Firestorm on a linux system and it will not start, it is highly likely that you are missing some required libraries. You need to verify if this is the case.
You need to open Terminal and cd to the Firestorm install directory. If you are unsure how to locate it, use your linux file manager to find it first; it will help you locate the install directory. Useful shorcuts:
so for example, from terminal, you would do something like this:
cd ~/Firestorm
Assuming that Firestorm is installed in the directory called Firestorm, in your home.
Once there, copy the following into Terminal:
LD_LIBRARY_PATH="./lib:${LD_LIBRARY_PATH}" ldd bin/do-not-directly-run-firestorm-bin
This will spit out a long list of libraries. Check to see if any are marked as “not found”. If so, you will need to install these with your package manager.
See this page for documentation on Firestorm 4.7.1 (45325) and earlier.
Windows only: We have now have a software that makes it very easy to adjust your SLURL settings, in order to open any viewer you have installed.
See here for details
Other suggestions below.
In Firefox, goto Tools → Options → Applications Tab and scroll to Secondlife. Look to see if Firestorm is listed, if not, select “other”, then browse your hard drive to find the Firestorm.exe, click on it, select Open, then click Ok. (Reference: Applications panel—Set how Firefox handles different types of files.)
OR
Download and install the regular SL viewer - but don't run it.
OR
Try this if the above does not work:
http://www.linuxforums.org/forum/gaming-games-multimedia-entertainment/104105-how-firefox-calls-secondlife-slurls.html
Download and install the regular SL viewer - but don't run it.
The application that handles a URL is a system-wide setting, not tied to any one browser. You can change the setting like this:
secondlife
in the list on the left. Click on it.Information gleaned from this page.
There is an alternative to clicking a link in a browser to have it pass control to the viewer. Some actually find this work around to be faster and use it normally:
The fist thing to check is the viewer settings: Preferences → Network & Files → Connections, in the Web Browser section, make sure Use My Browser… is selected.
If you get an error saying that no program is associated with the action, or that it doesn't know how to hand that action, make sure your computer settings show that there is a default web browser. An easy way to tell is to open your browser; if you are asked to make it the default, then you need to do so.
The current release version of Firestorm is available here.
“n/a” in the table below means “not available”.
Version | 32/64-bit | Grids | Havok | Level of Support | Download |
Windows | |||||
Windows 32-bit Havok | 32 and 64 | SL only | X | Full release | Firestorm 4.7.7.48706 32 bit Windows setup.exe SHA1 Checksum: D77B40B49370CEC519BAC68542C50FD328F33D53 |
Windows 32-bit OpenSim | 32 and 64 | SL and other grids | Full release | Firestorm 4.7.7.48706OS 32 bit Windows setup.exe SHA1 Checksum: A3743695BE456B34538FD94AB5BD5830276AC452 | |
Windows 64-bit Havok | 64-bit only | SL only | n/a | n/a | |
Windows 64-bit OpenSim | 64-bit only *Does not work on Vista | SL and other grids | Full release | Firestorm 4.7.7.48706OS 64 bit Windows Setup.exe SHA1 Checksum: 6D9A61497D6367BFBDF7B253B8BE35DE0B89DD3A | |
Mac | |||||
Mac 32-bit Havok | 32 and 64 | SL only | X | Full release | Firestorm 4.7.7.48706 Mac.dmg SHA1 Checksum: A7E4D135A750F561360457AC2ED4BC5CEA3702DB |
Mac 32-bit OpenSim | 32 and 64 | SL and other grids | n/a | n/a | |
Mac 64-bit Havok | 32 and 64 | SL only | n/a | n/a | |
Mac 64-bit OpenSim | 32 and 64 | SL and other grids | Full release | Firestorm 4.7.7.48706OS 64 bit Intel Mac.dmg SHA1 Checksum: 01F700859F4FD84815A21F6CCDC156EF6B5F98F6 | |
Linux | |||||
Linux 32-bit Havok | 32 and 64 | SL only | X | Full release | Firestorm 4.7.7.48706 32 bit Linux.tar.bz2 SHA1 Checksum: 3039FDF660CF10061BB48D18106E8F615EF2762B |
Linux 32-bit OpenSim | 32 and 64 | SL and other grids | Full release | Firestorm 4.7.7.48706OS 32 bit Linux.tar.bz2 SHA1 Checksum: E1D6571D2FB6767D967CD4DC876EE2E8AB5F38D3 | |
Linux 64-bit Havok | 64-bit only | SL only | n/a | n/a | |
Linux 64-bit OpenSim | 64-bit only | SL and other grids | Full Release | Firestorm 4.7.7.48706OS 64 bit Linux.tar.bz2 SHA1 Checksum: 4B8BFC2A8BCC4AB18A767F1F24977A1BDB16B5C3 |
“n/a” in the table below means “not available”.
Version | 32/64-bit | Grids | Havok | Level of Support | Download |
Windows | |||||
Windows 32-bit Havok | 32 and 64 | SL only | X | Old release | Firestorm 4.7.5.47975 32 bit Windows setup.exe SHA1 Checksum: 4BBCA7B524903E85D44F9CCB90C9F8BF2DB0E786 |
Windows 32-bit OpenSim | 32 and 64 | SL and other grids | Old release | Firestorm 4.7.5.47975OS 32 bit Windows setup.exe SHA1 Checksum: 21F6BE62E349FB11D70FFD543BF8CFD87D1BCC42 | |
Windows 64-bit Havok | 64-bit only | SL only | n/a | n/a | |
Windows 64-bit OpenSim | 64-bit only | SL and other grids | Old release | Firestorm 4.7.5.47975OS 64 bit Windows Setup.exe SHA1 Checksum: 62A42665593DE240E427E5EEAC631392AEBCE5DF | |
Mac | |||||
Mac 32-bit Havok | 32 and 64 | SL only | X | Old release | Firestorm 4.7.5.47975 Mac.dmg SHA1 Checksum: 9604B6EE2E074A836C545AEE864E005AB72DA51B |
Mac 32-bit OpenSim | 32 and 64 | SL and other grids | n/a | n/a | |
Mac 64-bit Havok | 32 and 64 | SL only | n/a | n/a | |
Mac 64-bit OpenSim | 32 and 64 | SL and other grids | Old release | Firestorm 4.7.5.47975OS 64 bit Intel Mac.dmg SHA1 Checksum: 6B6F14A6D206797B1940B8BFD0F921E70DD2BDE6 | |
Linux | |||||
Linux 32-bit Havok | 32 and 64 | SL only | X | Old release | Firestorm 4.7.5.47975 32 bit Linux.tar.bz2 SHA1 Checksum: 1F81BA7A92D1EDDAD80D9B93ACE13871BC2FE72D |
Linux 32-bit OpenSim | 32 and 64 | SL and other grids | Old release | Firestorm 4.7.5.47975OS 32 bit Linux.tar.bz2 SHA1 Checksum: 6321EF05C6085196565476336829156C11C0A447 | |
Linux 64-bit Havok | 64-bit only | SL only | n/a | n/a | |
Linux 64-bit OpenSim | 64-bit only | SL and other grids | Old release | Firestorm 4.7.5.47975OS 64 bit Linux.tar.bz2 SHA1 Checksum: 4C81A6403E88BFFB400D185A51FBFD471B0825A1 |
NOTE: This version of Firestorm is only being offered for MacOS. It should only be used in cases where more recent versions don't work well for you. But please note that, given the many changes in SL since 4.4.2 was released, 4.4.2 will be badly broken for you anyway.
Also, Mac OSX 10.5 is not compatible with Firestorm 4.4.2.
Version | 32/64-bit | Grids | Havok | Release Type | Download |
Mac 32-bit Havok | 32 and 64 | SL only | X | Old release | 4.4.2.34167 Intel Mac Download SHA1 Checksum: ded94ad865d4c5897bb12ba28d663cf14d5ae15e |
Mac 32-bit OpenSim | 32 and 64 | SL and other grids | Old release | 4.4.2.34167OS Intel Mac Download SHA1 Checksum: bd8a9313c0f023c505e9ae85c8ec654df06a41ed |
These classes are based on our official Firestorm release and are conducted in voice and text except when otherwise noted. There's no need to talk, but you may want to be able to hear. We also usually have help available to answer questions in text. This schedule is subject to change.
Note that it is best if you are on Firestorm for the classes.
Locations are indicated in the far right column as follows:
Class times and days change regularly. Classes may be held any day of the week, with start times from 8am to 7pm SLT. Nonetheless, if the class times are still inconvenient you may prefer to watch recorded versions of some of these classes on YouTube.
*All times SLT*
Monday | August 15 | 12:00PM – Menus 2 (TEXT ONLY) We will cover the Advanced and Develop menus in the top bar. | FS |
Wednesday | August 17 | 11:00AM – Odds & Ends 2 Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more. | FS |
Thursday | August 18 | 12:00PM – Contact Sets (TEXT ONLY) There is a cool feature called Contact Sets that lets you organize your contact list. We will cover how to set them up and use this epic feature. | FS |
Friday | August 19 | 7:00PM – Odds & Ends 1 This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems. | FS |
Saturday | August 20 | 4:00PM – Reporting Bugs, Requesting Features Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need. | FS |
Monday | August 22 | 12:00PM – Preferences Set 2 (TEXT ONLY) We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release. | FS |
Tuesday | August 23 | 4:00PM – Odds & Ends 2 Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more. | FS |
Thursday | August 25 | 12:00PM – Preferences Set 1 (TEXT ONLY) We will cover some of the Firestorm preferences (General, Chat, Privacy), based on our current release. | FS |
Friday | August 26 | 2:00PM – Backing up Settings and Logs This class covers how to save your settings and chat logs on your computer. Recommended to take this before the Clean Install class. | FS |
Monday | August 29 | 12:00PM – Clean Install (TEXT ONLY) Learn how to correctly and quickly perform this most fundamental and important of tasks. Recommended to take Settings Backup class first. | FS |
Tuesday | August 30 | 11:00AM – QuickPrefs Customization + Lag Two mini-classes in one. One discusses the causes of lag in SL. The other explains how to customize your Quick Preferences. | FS |
Thursday | September 1 | 12:00PM – Menus 1 (TEXT ONLY) We will be covering the menus on the top bar, from Avatar through Help. | FS |
Friday | September 2 | 2:00PM – Animation Overrider On Firestorm, you can save scripts and HUD space by running your AO animations through the viewer. Learn how to set up and get the most out of this feature. | FS |
Monday | September 5 | 12:00PM – Odds & Ends 1 (TEXT ONLY) This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems. | FS |
For general information about Avatar Complexity (“jellydolls”), please see:
Go to Avatar → Appearance and look at the bottom right of the window.
Two methods:
These are the default settings that determine the threshold at which you view avatars fully rendered or as jellydolls. They correspond with the “Quality and Speed” slider located in Preferences → Graphics → General. When the settings are left at these defaults, avatars whose complexity numbers are below these thresholds will be visible, while avatars with higher complexities will appear as jellydolls to you.
Under Construction
The #Firestorm → AO folder is protected; this means it cannot be deleted, nor can items in it be removed.
If you have inadvertently dragged something into this folder (or a subfolder), then proceed as follows:
If you had a functioning FS AO and it is now empty, it is possible that the #Firestorm → #AO folder has accidentally moved to another location.
To find the moved #AO folder, do an inventory search either for “#AO” (probably the simplest way), or in case that doesn't work, for one of the known animation names. The search will reveal both the original animation and any link to it. The link should reveal the location of the moved #AO folder. Check to see that the moved folder contains all the expected subfolders and animations.
To move the full #AO folder back into the correct location,
There is no official support for compiling or operating self-compiled viewers. Unofficial support options are listed at the bottom of this page.
This procedure is used for building a non-standalone viewer on 32-bit Ubuntu 16.04 LTS systems and was tested on a fresh installation within a virtual guest. This procedure assumes that your Ubuntu system has been properly updated, and also assumes any derivative system (eg.: Mint) includes all the standard Ubuntu libraries.
This is needed for compiling any viewer based on the LL open source code and only needs to be done once.
The required tools are:
bison | bzip2 | cmake | curl | flex | g++ 4.7 | m4 (for make) | mercurial (for hg) | python newer than 2.4.3 but not 3.0 | python development | pip | llbase |
sudo apt-get update # to make sure the repository list is current sudo apt-get upgrade # to make sure all installed packages are current sudo apt-get install --install-recommends bison bzip2 cmake curl flex g++-4.7 m4 mercurial python python-dev python-pip sudo pip install --upgrade pip # The version in the repository is not the latest version sudo pip install llbase
(the –install-recommends flag tells apt-get to install all packages recommended by each named package.)
In case you have multiple versions of g++ installed, which is possible, we need to identify 4.7.x as the default version.
update-alternatives --remove-all gcc update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.7 47 --slave /usr/bin/g++ g++ /usr/bin/g++-4.7 --slave /usr/bin/gcov gcov /usr/bin/gcov-4.7 update-alternatives --config gcc
It doesn't hurt to run those commands if you only have one g++ version installed.
These libraries may be included with your distribution, and some may be automatically installed as dependencies for the tools you just installed:
libc.so (libc6-dev) | libGL.so (libgl1-mesa-dev) | LibGLU.so (libglu1-mesa-dev) | libstdc++.so.6 (libstdc++6) |
libx11.so (libx11-dev) | libxinerama.so (libxinerama-dev ) | libxml2.so (libxml2-dev) | libXrender.so (libxrender-dev) |
sudo apt-get install --install-recommends libc6-dev libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \ libx11-dev libxinerama-dev libxml2-dev libxrender-dev
You can optionally install doxygen to eliminate related errors, but it is not needed to build Firestorm
sudo apt-get install --install-recommends doxygen
Autobuild is a Linden Lab resource that does all the hard work. For Firestorm, you will need a modified version of autobuild from one of our Developers.
sudo hg clone https://bitbucket.org/NickyD/autobuild-1.0 /opt/autobuild ln -s /opt/autobuild/bin/autobuild /usr/bin/autobuild
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. This document will refer to src in your home directory, ~/src.
cd ~/src
There are several repositories but the one we are 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 choose a different destination folder by adding that folder's name to the end of the command, such as:
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source
The rest of this document will assume the default directory, phoenix-firestorm-lgpl
Cloning the Firestorm repository can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help:
#!/bin/bash cd ~/src hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl cd phoenix-firestorm-lgpl for i in {15000..40000..5000} do echo "Grabbing to change $i" hg pull -u -r $i done echo "Grabbing to tip" hg pull -u cd ~/src
cd ~/src/phoenix-firestorm-lgpl autobuild configure -c ReleaseFS_open
This will set up to compile with all defaults and without third party 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 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE autobuild configure -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 outside the viewer development itself. And if you use the –clean switch, you will re-download them all.
autobuild build -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 -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.</WRAP>
Create the desktop launcher
cd ~/src/phoenix-firestorm-lgpl/build-linux-i686/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-i686/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-i686/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 author (preferred) or discuss on IRC.
There is no official support for compiling or operating self-compiled viewers. Unofficial support options are listed at the bottom of this page.
This procedure is used for building a non-standalone viewer on 64-bit Ubuntu 16.04 LTS systems and was tested on a fresh installation within a virtual guest. This procedure assumes that your Ubuntu system has been properly updated, and also assumes any derivative system (eg.: Mint) includes all the standard Ubuntu libraries.
This is needed for compiling any viewer based on the LL open source code and only needs to be done once.
The required tools are:
bison | bzip2 | cmake | curl | flex | g++ 4.7 | m4 (for make) | mercurial (for hg) | python newer than 2.4.3 but not 3.0 | python development | pip | llbase |
sudo apt-get update # to make sure the repository list is current sudo apt-get upgrade # to make sure all installed packages are current sudo apt-get install --install-recommends bison bzip2 cmake curl flex g++-4.7 m4 mercurial python python-dev python-pip sudo pip install --upgrade pip # The version in the repository is not the latest version sudo pip install llbase
(the –install-recommends flag tells apt-get to install all packages recommended by each named package.)
In case you have multiple versions of g++ installed, which is possible, we need to identify 4.7.x as the default version.
update-alternatives --remove-all gcc update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.7 47 --slave /usr/bin/g++ g++ /usr/bin/g++-4.7 --slave /usr/bin/gcov gcov /usr/bin/gcov-4.7 update-alternatives --config gcc
It doesn't hurt to run those commands if you only have one g++ version installed.
These libraries may be included with your distribution, and some may be automatically installed as dependencies for the tools you just installed:
libc.so (libc6-dev) | libGL.so (libgl1-mesa-dev) | LibGLU.so (libglu1-mesa-dev) | libstdc++.so.6 (libstdc++6) |
libx11.so (libx11-dev) | libxinerama.so (libxinerama-dev ) | libxml2.so (libxml2-dev) | libXrender.so (libxrender-dev) |
sudo apt-get install --install-recommends libc6-dev libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \ libx11-dev libxinerama-dev libxml2-dev libxrender-dev
You can optionally install doxygen to eliminate related errors, but it is not needed to build Firestorm
sudo apt-get install --install-recommends doxygen
Autobuild is a Linden Lab resource that does all the hard work. For Firestorm, you will need a modified version of autobuild from one of our Developers.
sudo hg clone https://bitbucket.org/NickyD/autobuild-1.0 /opt/autobuild ln -s /opt/autobuild/bin/autobuild /usr/bin/autobuild
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. This document will refer to src in your home directory, ~/src.
cd ~/src
There are several repositories but the one we are 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 choose a different destination folder by adding that folder's name to the end of the command, such as:
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source
The rest of this document will assume the default directory, phoenix-firestorm-lgpl
Cloning the Firestorm repository can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help:
#!/bin/bash cd ~/src hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl cd phoenix-firestorm-lgpl for i in {15000..40000..5000} do echo "Grabbing to change $i" hg pull -u -r $i done echo "Grabbing to tip" hg pull -u cd ~/src
cd ~/src/phoenix-firestorm-lgpl autobuild configure -c ReleaseFS_open
This will set up to compile with all defaults and without third party 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 -m64 configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE autobuild -m64 configure -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 outside the viewer development itself. And if you use the –clean switch, you will re-download them all.
autobuild -m64 build -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 -m64 build -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-i686/newview/packaged ./firestorm
You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged to another location if you choose, and then launch firestorm from there. Example:
mkdir ~/Firestorm64 cp -a ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/* ~/Firestorm64 cd ~/Firestorm64 ./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 author (preferred) or discuss on IRC.
Please note: Viewers play a minor part in voice functionality. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons:
Please go to Voice Echo Canyon when trying to get voice to work. If voice is working correctly for you, anything you say there will be echoed back to you. Once there, relog to last location.
Since 4.7.9, voice has not always connected to the voice servers. This is due to some coding issues that we inherited from the official SL viewer and that code's interaction with the latest voice files. The issue is documented on LL's Jira. A workaround is to disable and then re-enable voice. But if you're presented with the voice connection failure message that tells you “Voice communications will not be available”, you may need to disable voice and then relog before voice will try to reconnect.
Due to the many different versions of each operating system (Windows, linux distros, Mac OSx's), it is very difficult to give specifics for each one. Nonetheless, make sure that your operating system is correctly configured for voice: that voice is going to your headset (or speakers, as you prefer), and that your mic is enabled and configured.
If voice still does not work, then continue working through this page.
If you find that voice cuts in and out, particularly right after a TP, and at the same time, you notice that things are not rezzing in for you very well (avatars, objects, etc), then the likely cause is that your router is being “overwhelmed” with texture transfers. So reboot your router/modem, and then your computer, and see if the problem is solved.
You can also try adjusting your bandwidth as explained here.
If that does not help, then proceed with the section below.
Chances are good that the problem lies with the SL servers or the voice provider, Vivox. Still, there are things you can try:
Don't do this section if using Firestorm 4.6.5.40833.
Some have issues with voice on Firestorm - specifically, “stuttering”, or SLVoice crashing when you unplug a USB device. The only work-around currently is to swap out the voice files.
Try disabling compatibility mode, if enabled:
On Windows 7, if you find yourself being able to talk but not hear what others say, then a possible solution is to use the sound drivers from Vista. (This needs further confirmation.)
Check that slvoice.exe is not muted in the speaker/headphones icon (located in the notification area) → mixer.
Every linux distro is different; and each distro may have more than one window manager to further complicate things. So tips can't be “absolute”; you will need to experiment and see what works for you. The following have been suggested by some as effective. But first….
In the Firestorm install directory, there's a text file (originally from LL) with tips on getting voice to work in linux. If you haven't read that, then you can try to see if it helps.
#export LL_BAD_OPENAL_DRIVER=x
Below are results for selected linux distros, based on input from Phoenix and Firestorm users. This will be updated as more information becomes available.
sudo apt-get install gstreamer0.10-pulseaudio:i386 libidn11:i386 libuuid1:i386 libstdc++6:i386
If you are unable to connect to voice and you are also having problems with teleporting and/or loading your friends list, perhaps along with other things, then see the “Mac-specific” section of this page for instructions and more explanation.
Some Mountain Lion users experience a problem with voice output, while input works fine (that is, you can hear but you can't speak). To fix this, open the voice preferences for your viewer (Preferences→ Sound & Media -> Voice in Firestorm). Click the device settings button and select “built-in microph” as the audio input device and click OK. (OK is important, Apply doesn't work.) Reopen Preferences and go back to the device settings button to ensure you're getting sound in on the mic.
See this page for documentation on Firestorm 4.6.9 (42969) and earlier.
If you find that you are crashing frequently, then perhaps the suggestions here will be helpful. Please don't skim the page - read it carefully.
It is important to distinguish between two things….
If a small window appears, saying that you have been logged out of SL, this isn't a crash. Rather, SL is disconnecting you, for one of a number of reasons, including:
Things to try - in order:
If you are being logged out when you edit appearance, or edit shape, or use the Appearance toolbar button, did you drop items into the Outfits folder that were not created via the Outfits/Appearance window? If so, remove those items.
Firestorm itself has crashed. The remainder of this page offers possible solutions.
If you have eliminated all the possible causes for the crash and you are still crashing, it's time to submit a Support Request on our jira. In that request, you can include screenshots or videos, if they will help clarify your description, as well as your sysinfo and viewer event logs. Follow the steps in this link to create the request and add your logs.
Things to try:
Stay in a script-enabled region to do all of the following:
Inventory, right-click the item → Edit
, and while it is in Edit, go to Build menu → Scripts → Reset Scripts
, or Build menu → Scripts→ Set Scripts to Running
).Inventory > Current Outfit folder
, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached.2)Inventory → Right-click → Detach from Yourself
, then Inventory → Right-click → Attach to HUD
, and choose an unused point.