If you get a black screen when opening Search, Web Profiles, or Destinations, then try the following:

• Sometimes the window opens minimized at the top left; check to see if this is the case.
• Go to Preferences→ Network & Files -> Connection and ensure that the following are all enabled:
  • Enable Plugins
  • Enable cookies
  • Enable Javascript
• If this is not enough to get search working then go to Preferences→ Privacy -> General and click on Clear History (top of the window). Then relog.
• If this still doesn't help, then make sure that your anti-virus software hasn't flagged, and possibly deleted, SLPlugin.exe, which is required for search to work. Try disabling your anti-virus completely, then reinstalling Firestorm to a different folder. Once done, re-enable your anti-virus and make sure you set it to exclude SLPlugin.exe from being scanned.

Some other issues affecting search are covered here.

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:

• Your ISP is throttling or blocking the voice service;
• failure of the Vivox service;
• voice issues on the region you are on;
• voice being throttled by bandwidth set incorrectly - please check it by following the instructions here;
• voice hardware (mic, headset) not configured correctly in your operating system settings;
• voice hardware not configured correctly in the viewer;
• another application has your voice hardware in use (example, Skype);
• your anti virus software has “mangled” the voice application; see steps on this page: here.
• your firewall is blocking slvoice. Add slvoice to your firewall's exclusion/allow list.

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.

Steps:

• Go to Preferences → Sound & Media → Voice, and untick “Enable Voice.”
• Relog.
• Wait 10-20 seconds, or until the viewer has finished rezzing the scene.
• Re-enable voice.

Most voice connection issues happen when the viewer tries to connect to voice during the login process. The workaround is to disable voice before you log out, and then only enable it after logging in when you need it. You can toggle Voice from the Media Controls at the top of the viewer (not enabled by default for Vintage or Latency skins) by hovering over the speaker icon and then checking or unchecking the last checkbox, or by going to Preferences ⇒ Sound & Media ⇒ Voice and checking or unchecking the top option.

If you have issues hearing but not being heard, or vice versa, then make sure that you headset is properly connected to your computer. Unplug it, then plug it back in, making sure it is fully inserted.

And on a related note, if you plug your headset in while logged into SL, you will very likely have to relog to get it to be recognised.

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.

A bit more specifically, for Windows and linux, check in Mixer that SLvoice is listed, and not muted. Check that input and output devices are correct. For Mac, look in the Sound Preference pane.

• Go to Preferences→ Sound & Media -> Sounds. Find the Voice Chat slider and make sure it is not all to the left. Try increasing the volume.
• Make sure that Voice chat is enabled on that preferences tab.
• go to Preferences→ Sound & Media -> Voice. Click on Audio Device Settings. For Input and Output, use the dropdowns to select your voice devices (headset, microphone, whatever you use). It is best not to leave these at Default.
• Close Preferences and locate the Mic button on the button bar. Click the Lock checkbox then the actual button, and try speaking (hopefully, you went to Voice Echo Canyon so you can test).

Try reinstalling the drivers for your sound card, if you have one. Sometimes, these drivers conflict with the sound component of graphics card drivers. Similarly, you may have success by reinstalling your graphics card driver.

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:

• Open Preferences, and go to Sound & Media → Voice, and click Reset (circular arrow).

• Shut down all applications that use, or can use, voice - like Skype, etc. Then relog.

• What sometimes helps to get voice working is disabling voice in Preferences→ Sound & Media -> Voice, hitting Ok, waiting a minute and then enabling voice and click Ok. When these methods fail (assuming voice usually works for you) it is usually the Vivox voice servers that are the problem.

• If this does not work at your current location, go to a region where other people are able to use voice at this time. One possibility is Firestorm Social, but any region where voice is known to be functioning is fine. Disable voice in Preferences→ Sound & Media -> Voice. Relog, using the last location selection on your login screen. Wait a couple of minutes. Reenable voice. Wait another couple of minutes (in other words, give the connection time to be established). If voice comes on, then the problem may have been the region you were in before. Was voice disabled there? If not, a region restart might solve the problem.

• Go to Preferences → Network & Files -> Connection and reduce your bandwidth setting to 500 (if it is not already set there). Repeat the above step to toggle voice off and back on. See here for more information on setting your bandwidth properly, but bear in mind that lower levels than those calculated there may be necessary for troubleshooting purposes.

• Log out of the viewer, then check Task Manager (or equivalent) and see if SLVoice is still running. If so, kill the process, restart the viewer and see if voice connects.

• Try a relog, or even a reboot of the computer.

• Sometimes device settings can reset, so check in Preferences→ Sound & Media -> Voice→ Audio Device Settings, to be sure that the input and output are set correctly.

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

• Does your headset/microphone work outside of SL? ie when using Skype, Yahoo or MSN

• Does your headset/microphone work in Preferences→ Sound & Media -> Voice→ Audio Device Settings?

• Is your voice chat volume turned up and not muted?

• Is the SLVoice.exe (simply SLVoice on Mac) that is in the Firestorm folder in the exceptions/allowed list for your firewall? If your firewall is turned off, turn it on and add the SLVoice.exe (or SLVoice) anyway.
  If your Firewall has SLVoice listed twice, then remove both instances, and allow it again. For Win10, make sure that SLVoice has Private unchecked, and Public checked. If you had these set differently, change them, then close the window, log out of SL, reboot.

• Check the bandwidth you are actually getting and what you have set in Preferences → Network & Files → Connection. Please refer to this page for specifics.

• Go to top menu, Advanced → Debug Settings, and in the window that opens, type: Cmdlinedisablevoice - then ensure this is set to FALSE. (Use Crtl-Alt-D to enable the Advanced menu, if it isn't.)

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.

• To this end, download this file; save it to your hard drive. Make sure you do not have Firestorm running. Then extract the files to your Firestorm install folder. (For Firestorm 32-bit viewer, this is typically located at C:\Program Files\Firestorm on 32 bit Windows, and C:\Program Files (x86)\Firestorm on Windows 64-bit. For Firestorm 64-bit Viewer, this is typically located at C:\Program Files\Firestorm.) When prompted, allow the replacement of existing files.

Try disabling compatibility mode, if enabled:

• Locate your desktop shortcut for Firestorm (if you use the pinned application on the task bar, make sure you pin the Firestorm shortcut, not the running viewer)
• Right click on the icon and select Properties
• Select the Compatibility tab
• Find “Run this program in compatibility mode for:” if it is set then disable this
• Make sure “Run as Administrator” is enabled (if this is greyed out, then you're probably already running as administrator, so you can ignore this step).
• Click Apply.
• Now log back into the viewer, and see if voice works (do you have the white dot over your head?). If not, go to Preferences→ Sound & Media -> Voice and disable voice; wait a few moments, then re-enable. ¹⁾

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

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.

• Make sure you have ALSA and/or FMODEX available. FMODEX is supplied with Firestorm, normally. If you look at Help → About Firestorm, you should see a line that resembles this:
  Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.11.753 / OpenAL Community / OpenAL Soft: PulseAudio Software
  If that says “none” then you have no audio driver available to Firestorm and need to install one.

• Edit the firestorm shell script and remove the #. That will force LL to use FMOD rather than ALSA. Some say this is how to get voice working.

#export LL_BAD_OPENAL_DRIVER=x

• Some swear that the problem is PulseAudio, so you can try to remove that from your system. Be warned, however, that this could cause more problems than it solves. Make sure you remove only Pulse and not half the OS.
• Be sure to have the correct devices select in Firestorm for voice:
  
  Preferences → Sound & Media → Voice → Audio Device Settings (button) … input and output may not work if left at default; they may need to go to a specific device like “ALSA Capture on [device name]”.

Below are results for selected linux distros, based on input from Phoenix and Firestorm users. This will be updated as more information becomes available.

• ubuntu 16.04 64 bit + FS64: The following command installs a few 32-bit libs and voice works after. Maybe you need fewer 32-bit libs but that needs further investigation.
  Apparently, arch requires these as well - or some of them - though the exact lib name may be different.

sudo apt-get install gstreamer0.10-pulseaudio:i386 libidn11:i386 libuuid1:i386 libstdc++6:i386

• A new option is a debug setting, FSLinuxEnableWin32VoiceProxy, which when enabled will cause Firestorm to launch the Windows version of SLVoice.exe via WINE. To use this, you need to ensure that WINE is installed; install WINE with your package manager. An existing WINE profile/prefix is not needed, but will be used if present. Depending on your system, it may take several seconds before voice comes up.
  NOTES:
  * If you disable voice and then re-enable too quickly, WINE may not successfully restart and voice may fail to re-enable. If you get the warning that there was a problem connecting, you will need to relog before voice will re-enable. Thirty seconds between disable and enable should be enough.
  * There is a known related issue here
  * To speed up the initial loading of voice, use

  wine-preloader $HOME/path/to/firestorm/bin/win32/SLVoice.exe

  before launching Firestorm

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. Reopen Preferences and go back to the device settings button to ensure you're getting sound in on the mic.

So you find yourself suddenly missing a window, perhaps inventory, or chat, or the edit window… How to find it?

• Close all other windows, to make sure it isn't hiding under one of them.

• Hide the chat bar:Preferences→ Chat -> Typing→ Autohide main chatbar, and see if the window is under there.

• Compress all the buttons on the bottom toolbar to the right.
  Alternately, drag the toolbar buttons from their present location onto another toolbar;
  (Reminder: there are three available toolbars: bottom of the screen, right side, and left side. Buttons are dragged by left clicking, holding the left mouse button down, and dragging.)

• Go to Preferences→ User Interface → 2D Overlay, and lower the UI Scaling slider. The default setting is 1.0. You may find that setting it lower, temporarily, will reveal the missing window. If you find the missing window, move it to the center of the screen, then reset UI Scaling to 1.0 or your preferred value.

• Try to ensure that the missing window is closed. Then open the Advanced menu (press Ctrl-Alt-D to enable Advanced, if it isn't already), and go to Show Debug Settings. Then locate the pair values for the default window position, for the window that is “missing”. Consult the table below for the names of these settings. Set both values to 0 (zero), then relog.

• If you already have created a backup of your settings, then try a restore of those settings as explained here.

Should none of these work, then you will have to wipe settings, as explained on this page.

It is possible to make an object or avatar “invisible” - for you only. It is useful in many situations, such as photography, for example, if an object is in your view and you do not wish it in the picture.

NOTE: There is a tutorial video on this topic here.

This is permanent derender; it will survive teleports and relogging. For more information, see the Asset Blacklist.

• To derender an object: Right click it and select Derender → Blacklist from the menu.
• To rerender an object:
  • From the top menu bar, select World → Asset Blacklist. Find the item you wish to remove, click it to highlight it, then click the Remove selected items from blacklist button.
  • You will then need to force a view refresh: TP out and back OR relog. Changing your active group may also work.

Temporary derendering will last until a view change is forced in some way.

• To derender an object: Right click it and select Derender → Temporary from the menu.
• To rerender an object: Simply teleport out of the region, wait a minute or two for your viewer's memory to clear, and then tp back; or relog. Changing your active group may also work.

Note that in Preferences→ Move & View -> View, there is Re-render temporary derendered objects after teleport, which controls whether temporarily derendered obejcts will re-render after TP or not until after a relog.

Attachments get new UUIDs every time they are reattached; therefore, derendering an attachment will only be effective until the wearer detaches the item.

If you find that your feet are in the ground - or conversely that you are floating above the ground, you can adjust your height to get yourself back where you should be.

There are two ways to do this:

• Method One: Use the newer Hover Height adjustment:
  • Either: Right click your avatar, select Appearance, then Hover Height. A window opens. Use the slider to adjust your height above the ground, then close the window.
  • Or: go to Quick Prefs > Hover Height, and adjust the slider there.

• Method Two: Use the old setting in your Shape: Right click yourself, select Appearance → Edit Shape. In the Body tab, scroll down to Hover. Adjust the value till your feet are touching the ground. Save changes by clicking the Save button.
  Naturally, your shape must be moddable for this to work. ¹⁾ You can find some useful tips at I Was Floored: Frequently Asked Support Question.

If your avatar will not stop typing despite having “Play typing animation when chatting” unchecked in Preferences→ Chat -> Typing, disable typing override in your AO, if that option is available.

If that does not work, please do the following:

• Check with the creator of your AO for any updates since the rollout of LL server 1.42 (the new servers included a change in how LSL manages the typing state of an avatar). Absent such an update, please continue through these steps
• Remove your AO. Rez it to the ground (unless your AO has different directions for add/remove animations); \ \physically remove the actual typing animations from your AO;
  remove any references to typing animations on the notecard in your AO (assuming your AO has a notecard that includes what animations it is to use);
  reset the scripts;
  take the AO back into your inventory
• Go to top menu, Advanced → Show Debug Settings (Press Ctrl-Alt-D to enable Advanced, if it isn't); type Playtypinganim, and set to TRUE, then back to FALSE
• Relog and reattach your AO

If instead your hands and arms are moving while using voice, then you have speech gestures active. They can be found in the Library, in the Gestures → Speech Gestures folder. Deactivate them.

Teleport can fail in several ways:

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

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

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

Things to try:

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

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

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

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

• There may be a problem with your connection. Log off and try resetting your router/modem. Unplug it for a minimum of two minutes. If it has a battery backup, remove the battery as well. It does not hurt to reboot your computer at this time. After at least two minutes have passed, plug the router/modem back in and/or replace the battery and log back in.

• If you crash or get logged out on all or most TPs, then you may need to add new DNS numbers in your system's networking settings. Mac users may also be experiencing other issues like an empty friends list or trouble viewing rigged mesh. Please see this page for instructions.

• HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

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

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

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

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

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

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

One aspect of SL that is often underestimated is the importance of your network bandwidth setting. Having this too high or too low can lead to all kinds of problems, from simple TP failure to being disconnected - among other things. So it is advisable to not rely on the bandwidth stated by your provider, but to check for yourself.

• Log out of Firestorm if you are currently logged in
• Measure your download speed to the city where SL has servers¹⁾, by clicking this link, then select YOUR PREFERRED SERVER; make note of the download speed they indicate at the end of the test:
  Tucson, AZ. ²⁾³⁾
• The speeds are given in Mbps; multiply the speed you get by 800
• Set your Firestorm bandwidth to 1500, or the result you got above - whichever is smaller: in Firestorm, go to Preferences→ Network & Files -> Connection; Maximum Bandwidth is at the top.

Based on our experience, we strongly recommend the following maximum settings for bandwidth - unless the calculations above suggest lower values:

• Any type of wireless connection, including home wireless: 500
• Hardwired DSL: 1000
• Hardwired cable or better: 1500.

SpeedTest will give some indication of the quality of your connection. But another very useful indication is ping and packet loss.

You can determine these from within the viewer by accessing the statistics bar (press Shift-Ctrl-1). Look for Packet Loss and Ping SIM. Ideally, these should be 0.0% and under 150ms, respectively. The stats bar gives data based on your present location in the SL grid.

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 are on Windows 10, and get an error such as this:

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

…then refer to this page.

If you are on Windows 10, and get this error:

Load Library failed with error 1114, Dynamic Link Library (DLL) initiation routine failed

Check first for switchable graphics card: Dual Graphics Issues
If you have Intel graphics only, then use the instructions on this page: Intel Fix 32-bit.

This is a known issue with recent Intel graphics drivers, affecting other graphics applications besides SL viewers.

• Many people have received this graphics driver update without realizing it.
• The problem sometimes appears after a crash.
• Many users on HP laptops with OEM drivers are having this problem, although it is also affecting others.

What to do:

• Try rolling back to a previous driver that worked for you.

1. Method 1 https://www.intel.com/content/www/us/en/support/graphics-drivers/000008628.html for instructions. If the Roll Back Driver button is grayed out; see
2. Method 2 FIRE-21264 Roll Back Driver Steps

• If you are unable to rollback to older drivers, contact your laptop manufacturer for support. Here's a list of sites if you need it https://www.intel.com/content/www/us/en/support/topics/oems.html?wapkw=manufacturer+support Explain the issue, and tell them you need Windows Graphics Driver Version: 21.20.0016.4627, OpenGL Version: 4.2.0 - Build 21.20.16.4627 which is the last known non-buggy driver.

• Some users have reported that the following newer driver fixes the problem: Intel® Graphics Driver for Windows* [15.46] Version: 15.46.05.4771 (Latest) Date: 8/23/2017. Download from https://downloadcenter.intel.com. This driver may or may not be available to you depending on your computer.

• Workaround: Run the viewer in Full Screen Mode. Preferences → Graphics → General → Fullscreen Mode, then relog.

More information: Please refer to FIRE-21264 for more information and to report any additional details about the issue.

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

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

If you have Intel HD 2000 or 3000 graphics, refer to this page.

If your laptop has an Intel CPU and also has either an AMD or Nvidia graphics system, it may have the ability to switch between the Integrated Intel graphics (for power savings) and the AMD/Nvidia (for performance). But sometimes Firestorm isn't automatically configured to use the high-performance graphics.

You can confirm this issue by looking at Help → About Firestorm and checking the name of the graphics card listed. If it says Intel, please follow the steps on this page.

This mysterious flashing problem has been reported numerous times now and after some investigation we believe we finally have a repro for what's causing the issue. We do not yet know the specifics of exactly which systems are affected.

Typically the issue arises when Worn Rigged Mesh is in view and has at least one texture containing alpha and set to alpha blend mode. Alpha masking and emissive mask do not reproduce the problem.

We have also verified that this reproduces using the Official LL Viewer.

The Following Table shows which systems and drivers we have tested and whether they reproduce the Flashing Issue.

The Driver Version linked in the above table (DRIVER VERSION: 15.40.14.64.4352 & 15.40.14.32.4352) Has not reproduced the issue for us and is the Driver we recommend that you download direct from Intel.

If you receive the following Message when installing the Intel Driver:

This is an indication that you have an OEM Driver installed by the manufacturer. This Leaves you with two options:

• Check the website (or contact support) of your specific PC manufacturer and check for updates.
• Uninstall the OEM Driver and install the Intel Driver direct from Intel. This method is carried out At Your Own Risk

If decide to wait for an update from your computer manufacturer, or are simply uncertain about removing an installed driver, the following steps may help to make things more tolerable for you until your drivers are updated.

• If ALM is disabled the flashing will always reproduce unless Hardware skinning is disabled.
• If ALM is enabled the flashing will only reproduce when the avatar wearing the alpha blended rigged mesh is standing in Linden water.
  • If Hardware Skinning is disabled, the flashing stops in this case too.

Note: If you install the recommended driver above and still experience issues please read the related jira FIRE-17290 and add your details to the comments. Instructions for using the Jira can be found HERE

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.

This issue is the result of recent updates of Win10, specifically KB3176938, KB3189866, KB3193494 and KB3194496.

Many users have reported that updating their graphics drivers has fixed the problem:

• If you use nVidia graphics, try updating your drivers to at least Nvidia 373.06 released October 6, 2016.
• AMD/ATI users can try updating to at least driver 16.10.1.

Should you not be able to upgrade the driver, read on.

• To uninstall these Windows updates, go to Programs & features > view updates > click and uninstall. Please be advised that uninstalling any update marked as a security update is done at your own risk.
• To keep windows from downloading the update again download this tool and run it to “hide” the update: https://support.microsoft.com/en-us/kb/3073930?utm_source=twitter#bookmark-1607.
• Note: “Hiding” one update will not prevent other, later updates. The FPS problem may return as other updates are installed and until Microsoft fixes this issue.

Please refer to this LL JIRA and this FS JIRA page for details and other suggestions.

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

1. Right click the Speakers icon on your system tray and select Recording Devices.
2. Right click the Microphone and select Properties.
3. Switch to the Advanced tab.
4. Under Default Format drop down menu, select: 2 channel, 16 bit, 44100 Hz (CD quality).
5. Untick “Enable Audio Enhancements”
6. Press OK and OK.
7. Relog if needed.

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

1. Right click the Speakers icon on your Windows PC system tray and select Playback Devices.
2. Right click the Speakers (or your chosen audio output) and select Properties.
3. Switch to the Advanced tab.
4. Under Default Format drop down menu, select: 16 bit, 44100 Hz (CD quality).
5. Click Apply and OK.
6. Relog if needed.

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

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

Error 0xc000007b when launching 64 bit Firestorm:

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

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

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

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

If you have Intel HD graphics, refer to this page.

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

Some Windows 10 users have experienced difficulty installing current versions of Apple's Quicktime software on their systems. Version 7.7.6 of Quicktime has been confirmed to install correctly on Windows 10 systems. You can download version 7.7.6 from the link below:

Quicktime 7.7.6 (link will take you to the 7.7.6 download page on Apple's website)

**Unfortunately the above link seems to no longer be valid as a source for Quicktime 7.7.6, as such the recommended alternative to allow playback of media streams that were previously handled by Quicktime is to upgrade to a newer version of Firestorm (version 5.0.1.52150 or newer), as these newer versions of Firestorm no longer depend on Quicktime to handle stream playback.

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

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

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

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

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

Reported on Linden Lab's bug tracker BUG-139291

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.

• Find the list of Nvidia web drivers here, with download links directly from Nvidia: Nvidia Web Driver updates for El Capitan.
• Follow these instructions on how to install Nvidia web drivers: NVIDIA Releases Alternate Graphics Drivers for OS X 10.11.3.
• You can switch between using the Apple Nvidia driver and the Nvidia web driver (needs a reboot after each change).

If some characters now display as boxes, you can edit the fonts.xml file within Firestorm to cause the characters to load properly.

• Log out of Firestorm.
• In a Finder window, go to your Applications folder.
• Right click on your Firestorm application and choose “Show Package Contents.”
• Navigate to Contents/Resources/fonts/fonts.xml.
• Open fonts.xml with Text Edit.
• From there, scroll down to the section where it shows hiragana.
• After the line <os name=“Mac”>, insert this line:
  <file>ヒラギノ角ゴシック W3.ttc</file>
  so that the page looks like this:

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

• Be sure to save and exit.
• Open Firestorm and toggle to your Japanese keyboard or type in Japanese. It should now work as expected.

NOTE: This is only necessary for Firestorm versions 4.7.3 and older.

“Jellydolls” are a new anti-lag feature created by Linden Labs. You can use this feature to reduce your lag and to protect yourself against graphics-crashing devices worn by others.

For general information about Avatar Complexity (“jellydolls”), please see:

• Torley Linden's short video tutorial:

This will give you a good overview of how jellydolls work and how they can help you. Don't try to find the settings the way Torley describes, since those are the official SL viewer settings! See the rest of this page for the Firestorm settings.

• The official Second Life announcement: https://community.secondlife.com/t5/Featured-News/Why-are-all-these-people-made-of-colored-jelly/ba-p/3031255

• Inara Pey's blog: https://modemworld.me/2016/08/09/firestorm-4-7-9-50527-i-see-jelly-people/

• The Second Life wiki page: http://wiki.secondlife.com/wiki/Avatar_Rendering_Complexity

Please note: the official Second Life pages (above) describe how to find the settings in the official SL viewer. See the descriptions below for how to find them in Firestorm.

• This determines which avatars will appear as jellydolls to you, based on their complexity.
• Go to Preferences → Graphics → General → Maximum Complexity.
• Note: Lowering this slider will decrease your lag and turn more avatars into jellydolls; raising the slider may lag you but more avatars will be fully visible.
• Note: Moving this slider all the way to the right is not advised, as this sets this setting to “No Limit” — which means that no avatars will render as jellydolls to you, but you will be subject to lag and worn graphics crashers.

• Right click on the avatar's name tag and choose from the menu:
  • Render Normally – avatar will be affected by your complexity slider (above)
  • Do Not Render – avatar will be a jellydoll for you
  • Render Fully – avatar will be rendered fully even if over your complexity slider setting
• In the pie menu, these options are under More → More → Render.

Go to the top menu bar> World menu and select Always show Friends normally.

Go to the top menu bar> World menu and select Avatar Render Settings. Here you can change how avatars render for you. Refer to this page for details.

• Go to Preferences → General and set “Show Avatar Complexity,” “Only if too complex,” and “Show own complexity” as you wish.

• This appears in the top right of your screen.
• Go to Preferences → Notifications → Alerts, and move “Warn me if my avatar complexity may be too high” to the “Always show” box or to the “Never show” box, as you prefer.

• This appears in the top right of your screen when you change clothes/accessories.
• Go to Preferences → Notifications → Alerts, and move “Warn me about my avatar complexity changes” to the “Always show” box or to the “Never show” box, as you prefer.

• This shows complexity plus rank and area in hover text over avatars.
• Go to Avatar menu → Avatar Health → Show Avatar Complexity Information
• Note: The height of this hovertext cannot be adjusted.

Go to Avatar → Appearance and look at the bottom right of the window.

Two methods:

• Wear the item and then remove it, noting the change to your avatar complexity in the upper right of the viewer.
• Wear the item. Edit it → in the Build floater, click “more info” → and see the number listed for “Display.”

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.

• Low: 35,000
• Low-Mid: 100,000
• Mid: 200,000
• Mid-High: 250,000
• High: 300,000
• High-Ultra: 350,000
• Ultra: 350,000

“Jellydolls” are a new anti-lag feature created by Linden Labs. You can use this feature to reduce your lag and to protect yourself against graphics-crashing devices worn by others.

For general information about Avatar Complexity (“jellydolls”), please see:

• Torley Linden's short video tutorial:

This will give you a good overview of how jellydolls work and how they can help you. Don't try to find the settings the way Torley describes, since those are the official SL viewer settings! See the rest of this page for the Firestorm settings.

• The official Second Life announcement: https://community.secondlife.com/t5/Featured-News/Why-are-all-these-people-made-of-colored-jelly/ba-p/3031255

• Inara Pey's blog: https://modemworld.me/2016/08/09/firestorm-4-7-9-50527-i-see-jelly-people/

• The Second Life wiki page: http://wiki.secondlife.com/wiki/Avatar_Rendering_Complexity

Please note: the official Second Life pages (above) describe how to find the settings in the official SL viewer. See the descriptions below for how to find them in Firestorm.

• This determines which avatars will appear as jellydolls to you, based on their complexity.
• Go to Preferences → Graphics → General → Maximum Complexity.
• Note: Lowering this slider will decrease your lag and turn more avatars into jellydolls; raising the slider may lag you but more avatars will be fully visible.
• Note: Moving this slider all the way to the right is not advised, as this sets this setting to “No Limit” — which means that no avatars will render as jellydolls to you, but you will be subject to lag and worn graphics crashers.

• Right click on the avatar's name tag and choose from the menu:
  • Render Normally – avatar will be affected by your complexity slider (above)
  • Do Not Render – avatar will be a jellydoll for you
  • Render Fully – avatar will be rendered fully even if over your complexity slider setting
• In the pie menu, these options are under More → More → Render.

Go to the top menu bar> World menu and select Always show Friends normally.

Go to the top menu bar> World menu and select Avatar Render Settings. Here you can change how avatars render for you. Refer to this page for details.

• Go to Preferences → General and set “Show Avatar Complexity,” “Only if too complex,” and “Show own complexity” as you wish.

• This appears in the top right of your screen.
• Go to Preferences → Notifications → Alerts, and move “Warn me if my avatar complexity may be too high” to the “Always show” box or to the “Never show” box, as you prefer.

• This appears in the top right of your screen when you change clothes/accessories.
• Go to Preferences → Notifications → Alerts, and move “Warn me about my avatar complexity changes” to the “Always show” box or to the “Never show” box, as you prefer.

• This shows complexity plus rank and area in hover text over avatars.
• Go to Avatar menu → Avatar Health → Show Avatar Complexity Information
• Note: The height of this hovertext cannot be adjusted.

Go to Avatar → Appearance and look at the bottom right of the window.

Two methods:

• Wear the item and then remove it, noting the change to your avatar complexity in the upper right of the viewer.
• Wear the item. Edit it → in the Build floater, click “more info” → and see the number listed for “Display.”

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.

• Low: 35,000
• Low-Mid: 100,000
• Mid: 200,000
• Mid-High: 250,000
• High: 300,000
• High-Ultra: 350,000
• Ultra: 350,000

The world map allows you to view a large section of the Second Life grid in a window. The grid is divided into squares called regions (or popularly, and often incorrectly, “sims”). ¹⁾

You can use your mouse to click and drag the map view around, and thus pan round the entire grid. You can zoom in or our with your mouse scroll wheel or using the slider at the bottom right of the map.

If you click on any part of the map, a small red circle appears, and below it is show the location of the circle: the region name, followed by the coordinates of the circle relative to the region. The information to the right is also updated; more on that later. ²⁾

At the lower left of each region square, you can see the name of the region, and then in brackets, how many avatars are currently in the region, followed by the region maturity rating.

The map itself will have icons and colored areas, depending on options you can select, in the Legend section, upper right of the window. Thus you can opt to display (or not) avatars, infohubs, land for sale, and events. You, and your home location, will always be shown (assuming the locations are visible on the map you are currently viewing).

To shift the map to your location, click the Me button. To quickly teleport home, click the Home button (note that you can also TP home quickly by pressing Shift-Ctrl-H).

The next section on the right is Find on Map. You can find various things this way:

• Friends online - assuming they have granted you the ability to see their location in-world.
• Landmarks - This will show a sorted but uncategorized list of all the landmarks in your inventory; selecting one will move the map to the respective region and zero in on the exact location.
• Region - you can type in a region name here and there click Find. All regions containing the word(s) you typed will be shown in the list below; click on any one to view that location on the map.

Below the list noted above, you may type in coordinates local to the region you are looking at.

Finally, there are buttons that act on the exact location of the small red circle mentioned previously:

• Teleport: Click this to teleport to the selected location.
  Note that you can also teleport simply by double-clicking anywhere on the map. This can be disabled in Preferences→ Move & View -> Map & Minimap→ Enable double click teleports on the world map.
• Copy SLurl: Copies the SLURL of the location to your clipboard. Useful, for instance, if you wish to include it on a web page you are writing, to allow others to visit.
• Show Selection: Centers the map on the red circle.
• Track Region: Adds the selected region to the Region Tacker.
  Note that this button is unavailable until you use the Find function, in the Find on Map area above.

Please refer to the LSL Portal on the SL Wiki.

gstreamer0.10 was deprecated in Ubuntu after their 16.04 LTS release, but Firestorm 5.0.11 and older still requires gstreamer0.10 for audio services. In order to hear audio, see (some) media and use voice, you must install several gstreamer0.10 packages from the Xenial repositories.

The easiest way to manage this is to create a separate list for the xenial (16.04) repositories.

Use your favorite text editor to create /etc/apt/sources.list.d/xenial.list (you must be root when you do this) Enter the following lines:

xenial.list

# Added Xenial repos
deb http://archive.ubuntu.com/ubuntu xenial main universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-updates universe
deb http://security.ubuntu.com/ubuntu/ xenial-security universe multiverse
deb http://archive.canonical.com/ubuntu/ xenial partner

Save and close the file, then

sudo apt update

Note that many libraries cannot be installed using Synaptic or the Software Center; use apt in a terminal instead.

Ensure 32-bit architecture support is enabled

sudo dpkg --add-architecture i386
sudo apt update

Install the base libraries and apps

NOTE: The libraries cannot be installed using Synaptic or the Software Center. They must be installed via apt or aptitude.

sudo apt install libidn11:i386 libstdc++6:i386 libuuid1:i386 gconf2 zlib1g:i386

These packages provide media support (gstreamer0.10 comes from the 16.04 “xenial” repositories):

sudo apt install gstreamer0.10-pulseaudio:i386 gstreamer0.10-plugins-base:i386 gstreamer0.10-plugins-good:i386 pepperflashplugin-nonfree

Additionally, depending on your particular Linux and hardware setup, you may need to locate and install some additional packages:

If you run across the media_plugin_cef failure message, installing these packages may help:

sudo apt install libnss3:i386 libnspr4:i386 libxtst6:i386 libgconf-2-4:i386 libxss1:i386

Regardless of the method you choose, rebooting at this point can ensure that all required 32-bit libraries are referenced, though this may not be necessary.

http://www.firestormviewer.org/downloads/#synved-tabs-1-2

cd ~/Downloads
mkdir Firestorm
tar xf Phoenix_Fire{tab to expand} -C Firestorm --strip-components=1

At this point, you can launch Firestorm from a terminal:

cd ~/Downloads/Firestorm
./firestorm

And watch the output, optionally copy it for analysis since not all of it made its way to the viewer log.

You can also create a desktop shortcut, either manually or by running this script in a terminal:

~/Downloads/Firestorm/etc/refresh_desktop_app_entry.sh

If you crash continually, it will be helpful to get a backtrace, like so:

cd ~/Downloads/Firestorm
sed -i "/^#export .*gdb/ s/^#//" ./firestorm # This enables gnu debug
./firestorm

At the (gdb) prompt, type r to launch Firestorm. When Firestorm crashes, you should be back at a (gdb) prompt.
Type bt to get a backtrace. Copy everything from the terminal screen to a text file (there may be several pages, press Enter until you get the gdb prompt again).
Type q to exit gdb.
Create a Support Request on our Jira and attach the backtrace as well as crash logs. JIRA can guide you through the process.

NOTE: You can turn off debugging with:

sed -i "/^export .*gdb/ s/^export/#export/" ./firestorm

Log out of Firestorm.

cd ~/Downloads/Firestorm
sed -i "/^#export .*BAD_OPENAL/ s/^#//" ./firestorm
./firestorm

Now run Firestorm and try streaming audio. You may experience a delay in in-world sounds; if so, relogging might help.

Default Linux voice files may not properly connect as it may depend on obsolete audio libraries. As a workaround, install wine and use the included Win32 voice files:

sudo apt install wine-stable
winecfg

Once WINE is configured to your satisfaction, launch Firestorm and log in, disable voice, then press Ctrl+Alt+Shift+S to open Debug Settings. Search for FSLinuxEnableWin32VoiceProxy, set that to TRUE, then close Debug Settings. For good measure, relog, then enable and test voice.

Choose your Linux distribution for specific applicable steps. If your distribution is not listed, choose one that is closest, adapt as needed and, optionally, submit your adaptation to us for inclusion

• Ubuntu 18.04
• Ubuntu 17.04
• Ubuntu 17.10
• Ubuntu 16.04 / LinuxMint 18
• Ubuntu 14.04 / LinuxMint 17
• openSUSE 13.1/13.2
• Gentoo

Did you know that many first time visitors to SL are interested in SciFi and/or Roleplay? Because of that, the Firestorm Gateway has developed a SciFi Portal. The portal provides explorers with the following:

• An interesting SciFi environment to explore and interact with
• A place to either observe or join in SciFi RolePlay
• HUD-driven quests to allow a person to complete a series of tasks as a space station security guard or as a starship engineer.
• A place for new-to-SL and new-to-RP individuals to get free SciFi uniforms, skins or whole avatars so that they can create their own SciFi look.

Do you love SciFi and also love to explore? The SciFi portal can keep you busy for hours and hours. There is a large Trek Starship (the USS Gateway), a generic scifi spaceship (the Epsilon) and a huge space station (ISS Tempus). You can visit a working holodeck, fly a shuttle in open space, work out in the station's gym (stocked with interactive exercise equipment), have a drink at Callahan's bar, play poker or greedy, dance on a futuristic dance floor, pilot a Federation Starship, etc. There is also a tutorial section for those new to RP, and two supply decks. You can get uniforms on the Starship Supply Deck, and Scifi Avatars and/or Alien skins on the station supply deck (located on the lower level of Callahans bar.)

Get started at the SciFi Portal: SciFi Portal

Once you arrive, find the sign that says “Click here to select a SciFi Destination.” Choose your destination from a pulldown menu, and *poof* you will be there.

Here is a video of someone exploring it… just to give you an idea:

There is so much to be said about the Roleplay that it has its own page. Please see Firestorm Gateway Roleplay for more details.

A quest is an adventure where you have to complete a series of tasks. (They are also a great way to get a self-guided tour of either the Starship or the Space Station.)

The quests are on a terminal on the wall just to the right of the transporter. You can choose between the following

• Starship Quest - This allows you to be an engineer on the Trek Starship, USS Gateway. You will be given a series of engineering challenges to complete that move you around the Starship. This quest usually takes 15-20 minutes to complete.
• Station Quest - This allows you to be a security guard on patrol of the station. You will have to deal with issues such as feeding prisoners detained in the brig, dealing with contraband and stolen supplies. You will also have to patrol much of the station, getting a great tour of this large station. This quest usually takes about 1/2 hour to complete.

The quests use a HUD. You can get the HUD from the dispenser in the SciFi Portal. Here are the instructions for using the HUD:

1. Touch the Quest HUD Giver sign for the HUD.

2. Find the HUD in inventory and wear.

3. When you are prompted for permission for this quest to Attach To Your Avatar, say “YES”

4. The HUD will be a red oval on your viewscreen near the top center. Text instructions from it will display above the HUD and also in local chat.

5. Left touch HUD and select “Start Quest”

6. A submenu will appear. Select the quest listed in the submenu.

7. Watch the hud for instructions. If you miss something, you can find it in local chat as well.

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 event¹⁾ 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/

MOTD: EVENT: SL15B Event Applications
Second Life Turns 15! SL15B is now accepting applications for Exhibitors, DJs, Live performers, Auditorium and Volunteers! Click for more! http://www.slcommunitycelebration.info/apply-now/

MOTD: EVENT: Fantasy Faire
Fantasy Faire has been Extended! Supporting Relay For Life with 15 regions of arts, entertainment and shopping running now to may 7th! Click for more https://fantasyfairesl.wordpress.com/

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

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