openSUSE ended support for the transitional package of ia32-libs. And because both the 32-bit and 64-bit viewers have 32-bit dependencies, viewers may not perform as expected, or at all in some cases.

sudo zypper install libxml2-2-32bit libfreetype6-32bit libgobject-2_0-0-32bit libGLU1-32bit libgtk-2_0-0-32bit \
libgthread-2_0-0-32bit libapr-util1 libdb-4_8-32bit libuuid1-32bit libQtWebKit4-32bit libpangox-1_0-0-32bit

gstreamer0.10 is required; gstreamer1.0 is not yet supported.

You may need to install additional plugins:

sudo zypper install gstreamer-0_10-plugins-base-32bit gstreamer-0_10-plugins-bad-32bit gstreamer-0_10-plugins-good-32bit \
gstreamer-0_10-plugins-ugly-32bit

NOTE: one or more of these packages may attempt to remove their 64-bit counterpart. Consult your distribution's help documents and/or forums to see if there is a means of installing both.

Current versions of Firestorm require the PPAPI version of the flash player. This is part of Google Chrome, but the plugin itself is not in the default repositories. To install it, refer to this page.

Growl is a desktop service that puts notifications on your desktop. Firestorm can make use of that service and show you notifications while the viewer is not in focus. Linux normally has this service by default, called libnotify. You may need to install the 32-bit package to get notifications from 32-bit viewers

zypper install libnotify4-32bit

NOTE: This may attempt to remove its 64-bit counterpart. Consult your distribution's help documents and/or forums to see if there is a means of installing both.

Firestorm for Linux

cd ~/Downloads
mkdir Firestorm

# For xz compressed files
tar xf Phoenix_Fire{tab to expand} -C Firestorm --strip-components=1

# For bz2 compressed files
tar xjf 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.

NOTE: Qpainter errors can be safely ignored.

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. This wiki page 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.

Using your file manager (dolphin or whatever), locate the Firestorm install directory), and inside that the shell script called firestorm. Open this with a text editor (Kate, or whichever you prefer).

Find the line, '#export LL_BAD_OPENAL_DRIVER=x', in the 'firestorm' script, and take out the '#', to make the line look like 'export LL_BAD_OPENAL_DRIVER=x', save the script.

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

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: being logged out (disconnected), and crashing.

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:

• The region you are in is going down.
• During teleport, the SL servers may fail to hand you over to your destination and so log you out; help on that is given here.
• Your network connection has gone down.
• Your network connection has become poor or unreliable and SL has lost contact with your avatar.

Things to try - in order:

• reboot your router/modem, then your computer;
• make sure your bandwidth is set correctly - follow the instructions hereexactly as given;
• shut down any other programs that are making heavy use of your network connection, such as torrents;
• If you use Mac with Yosemite, see if this might be your case.
• If the problems persist still, try changing your DNS to Google, as explained here.

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.

• Update your Operating System. See the advice from LL, and the reasons behind it, here.

• (Windows-only)
  • If you are using an ATI (AMD) graphics card, then please refer here for known problems with these cards.
  • For nVidia users, please refer to this page.
  • Also for nVidia: if you recently updated your drivers and are experiencing crashes, try reverting to an older driver that worked for you.

• (Mac-only)
  • If you have Sierra plus Nvidia graphics, see http://wiki.phoenixviewer.com/mac_sierra
  • If you have El Capitan plus Nvidia graphics, see http://wiki.phoenixviewer.com/mac_el_capitan
  • If you crash when uploading images to SL or when saving snapshots to your hard drive, see http://wiki.phoenixviewer.com/mac_crash_upload

• In Preferences → Graphics → General:
  • Reduce Draw Distance by half (or more).
  • Reduce Max # non-impostor avatars.
  • Reduce Maximum Complexity by half (or more).

• Disable VBO: Run Firestorm and before logging in, press Ctrl-P to bring up the Preferences window. Then click on Graphics → Hardware Settings tab. Make sure that “Enable OpenGL Vertex Buffer Objects” is not checked.

• Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example:
  • RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
  • TextureLoadFullRes should never be enabled.

• (Grids other than SL only!) Disable HTTP Get Textures: Open the preferences window, then click on Graphics → Rendering tab. Make sure “Use HTTP Textures” is not checked. Please clear your cache if you change this setting.

• It is possible that your graphics settings are set higher than your computer can handle. To see if this is the case, go to Preferences → Graphics, and click on Reset (the circular arrow to the right of the quality slider). After doing this, you may still need to reduce Draw Distance and Max # non-impostor avatars, as mentioned above.

• If you have Shadows turned on, try turning them off. See this page for more side effects of shadows.

• Another thing you can try is: Develop → World → Dump Region Object Cache, then relog. (The Develop menu is revealed with Ctrl-Alt-Q, if you cannot see it.) This sometimes also helps deal with odd texture issues; it may need to be done several times.

• If clicking on a link or SLURL in Firestorm causes an instant crash: do you have AVG 2011 installed? If so, it probably flagged SLPlugin as malware. See here for more on this.

• If you have Webroot SecureAnywhere Antivirus, see Webroot Issues.

• If you are crashing when you try to upload a texture, please try disabling VBO, as described above. Also, if you are on Windows and running Microsoft SkyDrive, prefer refer here. If you are on a Mac, this workaround may fix the problem.

• If the above tips do not help, you might benefit from a cache clear or viewer clean reinstall.

• If you find that a full manual cache clear allows you to log in, and you crash unless you do this, then there is a good chance that you have one or more problems with certain inventory items; please see this page for how to deal with this.

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.

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:

• FS: Firestorm Support region classroom, http://maps.secondlife.com/secondlife/Firestorm%20Ghost%20Town/24/11/4000
• JU: Junkyard University, http://maps.secondlife.com/secondlife/Junkyard%20Blues%20South/68/124/22

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*

Canonical ended support for the transitional package of ia32-libs. And because both the 32-bit and 64-bit viewers have 32-bit dependencies, viewers may not perform as expected, or at all in some cases.

Note that most 32-bit libraries cannot be installed on 64-bit Linux 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

NOTE: These files can't be installed using Synaptic or Software Center.

sudo apt install libglu1-mesa:i386 libgtk2.0-0:i386 libidn11:i386 libpangox-1.0-0:i386 libpangoxft-1.0-0:i386 libqtwebkit4:i386

You may need to install additional plugins:

sudo apt install pepperflashplugin-nonfree

NOTE: one or more of these packages may attempt to remove their 64-bit counterpart. Consult your distribution's help documents and/or forums to see if there is a means of installing both.

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

Growl is a desktop service that puts notifications on your desktop. Firestorm can make use of that service and show you notifications while the viewer is not in focus.

sudo apt install libnotify-bin:i386

NOTE: libnotify-bin:i386 may attempt to remove its 64-bit counterpart. Consult your distribution's help documents and/or forums to see if there is a means of installing both.

If you find that you are running into problems running Firestorm, or are receiving a media-plugin-webkit error, Manwa Pastorelli recommends the following packages:

Install the following packages

Packages shown in red may attempt to remove other packages from your system, which may lead to system instability. Install these packages one at a time and observe any mention of packages to be removed.

Packages shown in green may be already installed as a result of installing one of the other packages listed on this page.

sudo apt install libstdc++-4.8-pic:i386 
sudo apt install libapr1:i386 libaprutil1:i386
sudo apt install libatk1.0-0:i386 libdb5.3:i386 libfontconfig1:i386 libfreetype6:i386 libuuid1:i386 libx11-6:i386 libxinerama1:i386 libxrender1:i386

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
env WINEARCH=win32 winecfg

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.

• Manwa Pastorelli
• Jean Horten
• ShortyObrien

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 17.04
• Ubuntu 16.04 / LinuxMint 18
• Ubuntu 14.04 / LinuxMint 17
• openSUSE 13.1/13.2
• Gentoo

Firestorm Avatar Physics lets you customise how your Avatar's breasts, belly, and butt move in response to your movements.
This feature in Firestorm is the same feature that is in Linden Lab Viewer and allows personal customisation and the ability to easily share your settings with friends by passing each other physics layers.
You can see a video of this feature in action here.
Note: This was filmed on an early development version of Viewer 2, but the effect is the same.

• Note: Make sure you have the Avatar Physics Detail option in Avatar → Preferences → Graphics
  up high enough before you begin to edit
• To add Avatar Physics to your avatar you must first make a Physics layer
• Open inventory
• Click the + button at the bottom left → New Clothes → New Physics
• Wear this New Physics layer
• Right click the Physics layer → Edit
• Now you are ready to choose your settings

• Note: If your avatar is male, you can only modify your belly and butt.
• Playing a stationary walking animation or similar is a good way to test what your settings look like as you edit.
• Choose your settings then click “Save” top left to save to the same layer you are wearing, “Save As” bottom left to save to a new layer which will automatically be worn or “Undo Changes” to roll back anything changed since the last save.
• Exit Appearance.
• You are now wearing an Avatar Physics item. As you dance or move around, your Avatar's breasts, belly, and butt will move around in the way you specified.
• You can wear, take off, edit, and create physics items just like any other clothing item.

Bounce: Shaking vertically in response to your Avatar moving vertically.

Cleavage: Shaking side to side, but to the inside rather than to the outside, in response to your avatar moving forward and backwards.

Sway: Shaking side to side, but to the outside rather than to the inside, in response to your avatar moving side to side.

Max effect: Controls the maximum range of movement. If set to 0, the feature is off.
Think of this as a general amplifier of the “bounce” effect. The higher this slider, the higher the initial bounce impulse.
Firm when it's low, saggy when it's high.

Spring: Controls the speed of vibration.
A higher number means your body part will vibrate more quickly.
Think of this as a “centre spring”, it pulls the body part in question back to its neutral position.
If this value is low, the body part “swings” around the centre more. If it's high, there's not much bounce, rather a fast vibration.

Gain: Controls the size of the effect when movement is triggered.
A higher number causes a larger effect.

Damping: Controls how long it takes for movement to stop after it's triggered.
A higher number causes the movement to stop sooner. This works directly against any bounce.
A good analogy here is High Damping: Corset, Medium Damping: Swimwear, No Damping: bare breasts.

Breast/Belly/Butt Mass: Controls the modeled mass of the body part.
A higher number makes the body part look heavier. This parameter affects all the other parameters.

Breast/Belly/Butt Gravity: Controls the strength of the pull toward the ground.
A higher number means the pull is stronger.

Breast/Belly/Butt Drag: Controls the effect of air resistance.
A higher number increases the air resistance.

• With drag turned to 100%, if you jump up, your butt will sag tremendously.
• With drag turned to 0%, if you jump up, your butt may move down slightly.

Turning drag up is sort of like pretending that you're moving through jello, so as you move forward, your body parts refuse to come along with you (i.e. they 'drag behind'). “

• If you don't want to see any Avatar Physics movement, including your own, you can disable it in your Viewer.
• You can also lower the setting so it is less taxing on your computer.
• The settings to control this are under Avatar → Preferences → Graphics.

This controls the frequency of display updates for Avatar Physics:

• To make Avatar Physics movement smooth, move the slider to a high setting.
• To make Avatar Physics less taxing for your computer, move the slider to a lower setting.
  Avatar physics movement will be less smooth, and you will not see Avatar Physics movement of avatars who are far away.
  A lower setting decreases the update frequency, so Avatar Physics movement will be jerkier.
  A higher setting makes movement smoother but may decrease performance.

• To turn off Avatar Physics completely, put the Avatar Physics Detail slider at its lowest setting.
  This only prevents your Viewer from showing you Avatar Physics movement. If you disable Avatar Physics in your Viewer but your Avatar is wearing a physics item, others can still see your Avatar Physics movement in their Viewers.

• If you don't want others to see your Avatar Physics movement:
  • Don't wear a physics item, or
  • Wear a physics item, but set the slider for every Max Effect setting to 0.

Yes we can!

You can pick up ready made Avatar Physics Layers for free from our Marketplace store

Some members of the Phoenix Team have provided their own settings for you to experiment with.

Jessica Lyon

• Avatar height: 1.87m (6'1)

• Belly Bounce: 6, 10, 9, 48
• Breast Bounce: 13, 15, 16, 49
• Breast Cleavage: 2, 10, 10, 50
• Breast sway: 8, 11, 10, 48
• Butt Bounce: 10, 13, 17, 50
• Butt Sway: 10, 11, 11, 50
• Advanced: 16, 14, 16, 15, 15, 16, 10, 11, 10

Miro Collas O-Rim™ butt bounce for guys

• Belly Bounce: 0, 0, 0, 0
• Butt Bounce: 14, 17, 19, 83
• Butt Sway: 11, 20, 15, 56
• Advanced: 0, 0, 0, 0, 45, 47

Whirly Fizzle

• Shape:
• Height: 74
• Breast Size: 69
• Breast Buoyancy: 8
• Breast Cleavage: 32
• Hip Width: 73
• Hip Length: 44
• Butt size: 50

• Belly Bounce: 5, 87, 30, 67
• Breast Bounce: 19, 33, 45, 64
• Breast Cleavage: 5, 28, 41, 53
• Breast Sway: 8, 15, 17, 36
• Butt Bounce: 7, 41, 12, 72
• Butt Sway: 8, 34, 15, 50
• Advanced: 12, 39, 9, 14, 6, 10, 10, 22, 61

Nisa Maverick

• Shape:
• Height: 6'3”
• Breasts size: 75
• Breast Buoyancy: 14
• Breast cleavage: 21

• Belly Bounce: 6, 10, 9, 48
• Breast bounce: 35, 30, 30, 67
• Breast Cleavage: 8, 25, 13, 61
• Breast Sway: 10, 15, 35, 50
• Butt Bounce: 25, 28, 25, 66
• Butt Sway: 17, 20, 19, 60
• Advanced: 13, 15, 13, 12, 8, 9, 13, 10, 11

Pudenta Magic

• Shape:
• Avatar height: 1.77m (5'9) including shoes
• Breast size: 56
• Breast Buoyancy: 31
• Breast Cleavage: 24
• Butt Size: 45

• Belly Bounce: 14, 2, 4, 70
• Breast Bounce: 8, 13, 16, 49
• Breast Cleavage: 2, 8, 10, 50
• Breast Sway: 8, 6, 10, 48
• Butt Bounce: 12, 2, 5, 50
• Butt Sway: 10, 9, 11, 50
• Advanced: 13, 15, 8, 18, 16, 10, 12, 14, 15

Mobius Ryba

• Shape:
• Height: 21/1.76m
• Breasts size: 15
• Breast Buoyancy: 35
• Breast Cleavage: 21

• Belly Bounce: 2, 8, 7, 67
• Breast Bounce: 3, 20, 16, 70
• Breast Cleavage: 3, 10, 10, 72
• Breast Sway: 3, 11, 10, 65
• Butt Bounce: 4, 13, 17, 65
• Butt Sway: 4, 11, 11, 62
• Advanced: 16, 14, 16, 14, 15, 16, 10, 11, 10

Thea Brianna

• Shape:
• Avatar Height: 1.89m (6'2“)
• Breast Size: 55
• Breast Buoyancy: 43
• Breast Cleavage: 20
• Butt Size: 30
• Hip Width: 60

• Belly Bounce: 3, 10, 27, 10
• Breast Bounce: 10, 11, 21, 45
• Breast Cleavage: 5, 8, 7, 22
• Breast Sway: 7, 6, 10, 32
• Butt Bounce: 7, 10, 12, 32
• Butt Sway: 6, 8, 9, 29
• Advanced: 10, 10, 8, 9, 8, 9, 9, 5, 10

Zi Ree

• Shape:
• Height: 1.67m
• Breasts Size: 72
• Breast Buoyancy: 45
• Breast Cleavage: 33

• Belly Bounce: 0, 10, 9, 20
• Breast Bounce: 25, 73, 23, 76
• Breast Sway: 22, 16, 31, 67
• Breast Cleavage: 17, 48, 33, 80
• Butt Bounce: 22, 100, 0, 80
• Butt Sway: 15, 27, 0, 20
• Advanced: 19, 64, 42, 0, 0, 10, 39, 27, 20

Tonya Souther

• Shape:
• Avatar height: 7'2” (2.18 meters)
• Breast Size: 85
• Buoyancy: 26
• Cleavage: 35
• Butt Size: 35

• Breasts Bounce: 33, 30, 30, 67
• Breasts Cleavage: 3, 10, 10, 57
• Breasts Sway: 10, 15, 35, 50
• Belly Bounce: 6, 9, 9, 48
• Butt Bounce: 25, 28, 25, 66
• Butt Sway: 17, 20, 19, 60
• Advanced: 18, 15, 16, 12, 8, 9, 13, 10, 11

Lette Ponnier

• Shape:
• Height: 1.96m (6'5“)
• Breast Size: 63
• Breast Buoyancy: 48
• Breast Cleavage: 33
• Hip Width: 54
• Butt Size: 44

• Belly Bounce: 6, 5, 5, 39
• Breast Bounce: 19, 13, 19, 84
• Breast Cleavage: 11, 11, 16, 79
• Breast Sway: 5, 13, 6, 50
• Butt Bounce: 6, 5, 5, 39
• Butt Sway: 12, 11, 11, 70
• Advanced: 16, 12, 16, 7, 7, 10, 10, 11, 12

• When I'm laggy, My Physics do strange things: Unfortunately this can happen but the strange effects you see are totally client side. Only you see this. You will still look correct to others. If your FPS drops low, your Physics may start to behave in an “interesting” way. Similarly, extremely high FPS (over 60) can give strange client side effects. The fact that Avatar Physics can bug out at very low or high FPS is a known issue to LL and they are working on improvements to address this. The main factor here seems to be the gain setting. If gain is high, it'll get “wiggly” when FPS drops too low. Details can be found on these LL JIRA issues: VWR-25545, VWR-25585, VWR-25584.
  
  You can limit your framerate if it goes too high by going to Preferences > Graphics > Rendering and enable Limit Framerate, then set the slider to between 30 and 60.

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.

• Mac users: If you crash or get logged out on all or most TPs, then you may need to add new DNS numbers in System Preferences on your Mac, especially if you are experiencing other issues like an empty friends list or trouble viewing rigged mesh. Please see the “Mac-specific” section of 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.

• Check your network performance. Go to Help → About Firestorm and scroll to the bottom of the window. There you will see something like “Packets Lost: 191/34581 (0.6%).” You would like to see this number as close to zero as possible. If this is more than a few percent, that is a likely cause for TP failure. You may have a poor connection to your ISP, or it might be that the sim you are on is overloaded and responding poorly. You can also view realtime packet loss in your Statistics Bar (Ctrl-Shift-1; if this does not open, make sure your Advanced menu is open with Ctrl-Alt-D and try again).

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

• If nothing above helps the issue, then there may be a problem with your connection, especially if you were seeing high packet loss. 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.

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

If you have certain Intel HD graphics, and have upgraded your PC to Windows 10, your graphics card will not be fully supported by Intel. If you have this issue, you will be unable to log in. You will get the following error dialog box:

This is not a function of the viewer, but instead is a function of the drivers provided by Intel for your computer. However, we have developed a workaround that should help most users with this issue continue to have the ability to use the Firestorm viewer.

1. Verify that your graphics card is one of the affected versions. You can find a table of affected versions here: Graphics Drivers Supported Operating Systems, but most frequently we have seen Intel HD 2000 and Intel HD 3000. You should be able to verify your graphics in the system info of your computer.
2. Below, select the zip file that is correct for your download, either the 32-bit Havok version or the 32-bit OpenSim version, and download it to your computer. You will need to unzip the file and save it on your computer in a location you will remember.
3. On your computer, open File Explorer. (If it isn't on your taskbar you may need to use the search to find it.) When you open it, select the View tab at the top of the page and check the box on the right hand side that says File Name Extensions.
4. In File Explorer, navigate to This PC then Local Disk (C:) (or the location you normally download Firestorm, if it differs) and then navigate to Program Files (x86). Open Program Files (x86), locate the Firestorm folder, and open it. In the Firestorm folder, locate the Firestorm-Release.exe file and delete it.
5. Replace it with the Firestorm.exe file that was in the zipped folder you downloaded from the web site.

You should now be able to run Firestorm on your PC.

• Havok SL
  SHA-1: 78AD19AAFEBA16C9F83229CE6CB9E5A5AF88D7D4
• 32-bit non-Havok OS
  SHA-1: 2990917F75E09A233EAC32F305AB00238B5F6065

• Havok SL
• 32-bit non-Havok OS

• Havok SL
  SHA: 65BC45742DF72006E24FD279352460FDAD67B635
• 32-bit non-Havok OS
  SHA: 92532577419AFD643B5E6885F5344CA1FA9DB861

• Havok SL
  SHA: 26DDB29943DA9FD22193E55270D1244F4E39FD5A
• 32-bit non-Havok OS
  SHA: 13CC7B1462E9DE99DC85A8EF0CE62BC992381427