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.

A Windows 10 update in mid May has resulted in many having audio problems with the viewer. This is actually a problem with the update, and needs to be fixed externally to the viewer.

• If your mic seems to have stopped working, try this: In your operating system, go to Settings → Privacy → Microphone and make sure “Allow apps to access my microphone” is ON.
• In addition: A user has kindly provided this link to help you check your settings in the new Windows software and resolve the issue.
• Further to this, you should also check Windows Mixer settings, since audio devices may have been reset.

If you're on an ASUS laptop and Sonic 3 is running, this is preventing FS from finding your driver. The solution is to disable Sonic 3.

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 Open Sound Settings.
2. Go to Input section and click on Device Properties.
3. Switch to the Advanced tab.
4. Under Default Format drop down menu, select: 2 channel, 16 bit, 44100 Hz (CD quality).
5. Switch to Enhancements tab.
6. Check “Disable All Sound Effects”
7. Press OK
8. Close the Setting window
9. 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

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

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

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

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

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

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

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

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:

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

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: 035B4C3B6896CDB5CEEB2B688207EC45E1B46152
• 32-bit non-Havok OS
  SHA-1: CC5EE45EF344E4CED98E683BD5BC86F45767AAE3

• Havok SL
  SHA-1: E72B3C6B99D7DA6C7EA5457D0F48CA79930AB366
• 32-bit non-Havok OS
  SHA-1: 2492C3FA0AC0E3637BDE886DB93637A8F947EF43

Firestorm 6.0.2 (56680) Animesh Release Notes

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

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

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

Firestorm 6.0.2, 5.1.7, 5.0.11 Release

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

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

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

Firestorm 6.0.2, 5.1.7, 5.0.11

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

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

for Linux only

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

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

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

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

Windows only

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

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

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

• Latest driverLast checked 16/02/2019 - Windows: 418.91 (2019.2.13 ) - Linux: 410.93 (2019.1.3)

• Latest driverLast checked 16/02/2019 - Windows: Adrenalin 2019 Edition 19.1.1 (1/21/2019) - Linux: 18.50 (2/7/2019)
  

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

https://hg.phoenixviewer.com/

NB : Les viewers jouent un rôle très mineur dans le fonctionnement de la voix. L'ensemble du support de voix est fourni par l'application externe SLVoice et fait par le fournisseur de voix SL, Vivox. Les échecs de la voix sont presque toujours dues à l'une de ces raisons :

• Votre fournisseur d'accès internet régule le débit ou bloque le service voix;
• Échec du service Vivox;
• Problèmes de voix dans la région où vous vous trouvez;
• Débit de la voix réduit par un réglage de bande passante mal ajusté - voir les instructions de réglages ici;
• Le matériel audio (micro, casque, est mal configuré dans les options de votre système d'exploitation;
• Le matériel audio est mal configuré dans le viewer;
• Votre matériel audio est en cours d'utilisation dans une autre application (Skype, MSN, au autre);
• Votre anti-virus a détruit ou bloqué l'application voix; voir ici.

*MacOS 10.14 Mojave*: Pas de voice lorsque vous utilisez Firestorm-Beta 6.0.1. Voir (pour les anglophones) [Mac Mojave] SL Voice No Input on 6.0.1. Passez à la version 6.0.2 de Firestorm.

L'adresse IP du serveur 'www.bhr.vivox.com' a récemment été changée en 74.201.103.238, par conséquent quiconque rencontre un problème peut vérifier quelle adresse le système affiche pour ce nom - toute adresse différente est incorrecte. Un redémarrage ordinateur peut suffire à résoudre ce problème. Si ce n'est pas le cas, voir Problèmes de DNS - Général.

Depuis la version 4.7.9, la voice a toujours eu des problèmes de connexion aux serveux Vivox, ceci à cause de problèmes de coda que nous avons hrités du viewer officiel SL, et de l'interaction de code avec les derniers fichiers voix. Ce problème est documenté sur ce Jira LL (en anglais).

Pour résoudre ce problème on peut essayer de désactiver/réactiver la voice. Mais si vous obtenez le message d'échec de la connexion voice qui dit “Voice communications will not be available”, vous devrez désactiver la voice, et vous déco/reconnecter avant de réactiver la voix :

• Allez dans Preferences → Sound & Media → Voice, et décochez “Enable Voice”
• Déco/reconnectez-vous.
• Attendez une vingtaine de secondes jusqu'à ce que le viewer ait fini de charger tout votre environnement
• Réactivez la voice.

Dans la version Version 5.1.7., la voice peut crasher lorsqu'on clique le bouton microphone. Voir les Jiras (en anglais)BUG-225293 et FIRE-22940
Problème résolu dans Firestorm 6.0.1.

NB : le fichier exécutable SLVoice dans ce viewer n'est pas compatible avec les versions plus anciennes du viewer; il n'est donc pas possible de copier/coller le fichier dans les anciennes versions.http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.8.518593

La plupart des problèmes de voix se produisent lorsque le viewer essaie de connecter la voix pendant le processus de connexion à SL. Essayez de désactiver la voix avant de vous déco, et ne la réactivez qu'après vous être connecté, lorsque vous en avez besoin. Vous pouvez “basculer” la voix “on/off” à partir des contrôleurs de médias en haut à droite de votre écran en passant votre souris sur l'icône haut-parleur et en cochant/décochant la dernière case à cocher, ou en allant dans Preferences ⇒ Sound & Media ⇒ Voice et en cochant /décochant l'option du haut.

Si vous entendez mais que les autres ne vous entendent pas, ou vice-versa, assurez-vous que votres casque est bien connecté à votre ordinateur. Débranchez/rebranchez-le.

Si vous branchez votre casque alors que vous êtes déjà connecté sur SL, vous devrez probablement vous déco/reco afin qu'il soit reconnu par le viewer.

Etant donné le grand nombre de versions de chaque système d'exploitation (Windows, Linux, Mac) il est difficile d'expliquer spécifiquement les choses pour chacun d'entre eux. Cependant, assurez-vous que votres système d'exploitation est correctement paramétré pour la voix : que la voix va bien vers votre casque, ou vers vos hauts-parleurs selon les cas, et que votre micro est actif et configuré.

Si vous entendez les autres mais qu'ils ne vous entendent pas,il est probable qu'il s'agit d'un problème venant de la région.

De manière plus spécifique, pour Windows et Linux, vérifiez dans le mélangeur de volume son que le processus SLVoice et bien listé et pas bloqué. Vérifiez aussi que les entrée et sortie son sont correctes. Sur Mac, regardez dans les Préférences Son.

Pour plus de détails, voir ci-dessous.

• Allez dans Préférences→ Son & Média -> Général. Trouvez le slider “Voice Chat” et assurez-vous qu'il n'est pas complètementà gauche. Essayez d'augmenter le volume.
• Vérifiez que la Voix est activée dans Préférences → Son & Média → Voice Settings
• Allez dans Préférences→ Son & Média -> Voice Settings. Cliquez sur le bouton “Audio Device Settings”. Pour l'Input (Entrée) et l'Output (Sortie) utilisez les menus déroulants pour sélectionner votre matériel (casque, micro, quoi que vous utilisiez). En général il vaut mieux ne pas laisser les paramètres sur défaut.
• Fermez les Préférences et trouvez le bouton Speak sur la barre de boutons. Cliquez la case à cocher puis (si par chance vous êtes à Echo Canyon vous pourrez tester votre voix).

Si votre voix refuse toujours de fonctionner continuez à lire.

Essayez de réinstaller les pilotes de votre carte son. Parfois certains pilotes se mettent en conflit avec des composants de pilotes de carte graphique. De la même façon, réinstaller le pilote de votre carte graphique peut être la solution.

Si la voice ne fonctionne toujours pas, continuez à lire cette page.

Si vous trouvez que la voix est “hachée”, particulièrement après une téléportation, et qu'en même temps les avatars et/ou les objets ne chargent pas très bien, il est probable que votre box/modem est débordé(e)par les transferts de textures. Redémarrez la box (laissez-la débranchée pendant 1 bonne minute au moins et rebranchez-la) puis redémarrez votre ordinateur.

Ajustez votre bande passante comme indiqué ici.

Si le problème persiste, passez à la section suivante.

Il y a de grandes chances que le problème provienne des serveurs SL ou du fournisseur de voix, Vivox. Cependant voici quelques petites choses à essayer :

• Ouvrez vos Préférences → Sound & Media → Voice, et cliquez Reset (la flèche circulaire).

• Fermer toutes les autres applications qui utilisent ou peuvent utiliser la voix - comme Skype, etc. Puis déconnectez/reconnectez-vous.

• Désactivez la voix dans Préférences→ Sound & Media -> Voice , pressez Apply, attendez une minute et réactivez la voix et pressez Apply de nouveau. Quand ces méthodes ne mènent à rien (si la voix fonctionne habituellement pour vous), la source du problème provient bien souvent des serveurs Vivox.

• Si cela n'a pas fonctionné sur la région où vous êtes, allez dans une autre région où d'autres personnes utilisent la voix. Une des possilibités est d'aller à Firestorm Social, mais n'importe quelle région où la voix est active fera l'affaire. Désactivez la voix dans les Préférences → Sound & Media → Voice. Déco/reconnectez-vous après avoir sélectionné “Last location” sur votre écran de connexion. Attendez deux minutes pour laisser le temps à la connexion de se faire. Si la voix s'active, le problème était la région sur laquelle vous trouviez, et elle a peut-être besoin d'être redémarrée.

• Allez dans Préférences > Configuration et réduisez le réglage de bande passante à 500. Refaites les étapes ci-dessus désactiver/réactiver la voix. Voir ici pour plus d'information sur le réglage de la bande passante, tout en vous rappelant qu'il est possible que des réglages inférieurs à ceux résultant des calculs soient nécessaires en cas de problèmes, au moins le temps de les résoudre.

• Déconnectez-vous, puis vérifiez votre Gestionnaire de Tâches (ou équivalent) et vérifiez si “SLVoice” est encore en train de s'exécuter. Si c'est le cas, tuez le processus, redémarrez le viewer et voyez si la voice se connecte.

• Essayez de vous déco/reconnecter, redémarrez votre box, puis votre ordinateur.

• Il arrive que la configuration du matériel se réinitialise lors d'un crash ou d'une mauvaise déconnexion du viewer. Vérifiez dans Préférences→ Sound & Media -> Voice→ Audio Device Settings, si la sortie (output) et l'entrée (input) sont toujours correctement configurées.

• Il est possible que le Protocole HTTP soit en train de surcharger votre box/modem; essayez les suggestions données ici. Si elles n'apportent aucune aide, annulez les changements opérés, puis continuez à lire.

• Votre casque/micro fonctionnent-ils en dehors de SL ? Par exemple dans Skype, ou Yahoo ?

• Votre casque/micro fonctionnent-ils dans Préférences→ Sound & Media -> Voice→ Audio Device Settings?

• Le volume de la voix est-il assez haut ?

• Le fichier SLVoice.exe (SLVoice pour Mac) qui se trouve dans le répertoire Firestorm est-il bien dans la liste d'exclusions ou d'applications autorisées de votre anti-virus/pare-feu ? Si votre anti-virus/pare-feu est désactivé, ajoutez SLVoice.exe (ou SLVoice) et réactivez-le.

• Vérifiez la bande passante que vous obtenez et ce que vous avez configuré dans Preferences → Configuration. Référez-vous à cette page pour plus d'information.

• Allez dans le menu Advanced → Show Debug Settings, et dans la fenêtre tapez : Cmdlinedisablevoice - puis assurez-vous que c'est réglé sur FALSE (pressez Ctrl Alt D si le menu Advanced ne s'affiche pas en haut de votre écran).

Refer to this page.

If you have Intel HD 620 or Intel HD 630, and Windows 10 – This is an Intel driver issue. The fix is to roll back to driver 24.20.100.6025. Download Legacy Intel® Graphics Driver for Windows® 10 Version: 24.20.100.6025 (Ref. BUG-225655.)

If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.

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

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

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

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

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

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

Ref. FIRE-12339

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

Then, do the following:

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

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

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

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

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

“Jellydolls” are a new anti-lag feature created by Linden Lab. 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.

• Go to Avatar menu → Avatar Health → Show Avatar Complexity Information
• This shows complexity plus:
• * Rank (how close the avatar is to your camera; the closest is 1, next closest is 2…);
• * VisTris: recursively counts the number of triangles in every attachment at the current rendered LOD;
• * EstMaxTris: represents the sum of the estimated triangle count for each attachment to the avatar; and
• * attachment surface area in square meters.
• Note: The height of this hovertext cannot be adjusted.

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

Here are three ways to see an item's rendering weight:

• Avatar → Appearance → Wearing tab (Ctrl+O); look in the righthand column for the number.
• 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

A problem that is frequently reported is that worn rigged mesh attachments will sometimes be invisible to others after you have teleported. This can generally be fixed by selecting top menu, Avatar → Avatar Health → Refresh Attachments. Should that fail, then you will need to relog.

In order to reduce the chance of this happening, you should ensure that all worn rigged mesh items are attached to a different body attachment point (make sure NOT to attach to HUD, or only you will see the item on yourself). Many creators leave item attachment points at the default, which is right hand. This can result in many attachments being stacked on this point, making the above described issue far more likely to occur. So when wearing an outfit, check each rigged mesh part, and if attached to right hand, reattach to a different spot, and one not in use by something else. (You only need to do this once with newly acquired clothing, as the newly selected attachment point is remembered.) Having done that, and as explained below in “Changes to Attachments,” detach the item after having done this, so that the change saves.

Refer to FIRE-17998.

This is a side effect of the same bug described above. When you are crossing many regions or after a TP, some of your attachments may become “ghosted” in such a way that the viewer still thinks they are attached (so you see the attachments in your viewer), but as far as the region is concerned, the affected attachments are detached. No observer will see them and also no scripts in those ghosted attachments will run.

At a later time, if you make a change to what you are wearing by adding or removing something, this can sometimes cause your attachments to refresh to the “correct” state that the region sees. When this happens, some or all of those ghosted attachments will also be detached locally (in your viewer).

Refer to FIRE-22970 and FIRE-17998.

A somewhat common occurrence: changes you made to an attachments, either by manual editing, or by the use of an applier, will revert if you subsequently crash.

This is due to how SL works. Changes to attachments only save when you detach the item, or when you relog. So in order to avoid this situation, any time you make any change to an attachment (and this includes hiding/showing parts of a mesh body), detach the item, count to 10, then re-attach.

Attachments which are visibly seen as worn may not show as worn in inventory. As a result, attempting to detach them by right clicking the inventory item name is not possible.

Different solutions are suggested… please try these, one at a time, in the order given, until one fixes you.

1. Right click the attachment on your avatar, and detach it via the pie menu.
2. If the above fails, go to a low lag region, such as this one, log out there, then log in to last location. At that point try to detach, either the usual way, or as described above.
3. Try the Replace Outfit procedure described below.

If you find that when you log in, attachments are being detached and then reattached, sometimes several on the same spot, then try the following procedure:

• Make a temporary folder somewhere you can find it easily
• In that folder, put a copy of your skin, shape, hair/bald base and eyes - and perhaps a pants and top layer - no prims!
• Right click the folder name and select Replace outfit. Not Wear, not Add, Replace. This step is VITAL
• Now relog
• Once you are logged back in, you can put your usual extras back on, hair included. And hope that it holds.

If you find that attachments disappear (or partly disappear) after a teleport, but only in your view, not to others, then enable teleport screens if you have them disabled: Preferences → Move & View → Teleports → Disable teleport screens; uncheck. Ref. this JIRA.

If a scripted attachment (such as a HUD) stops working following a TP, this may be because the attachment has actually fallen off during TP. You may see it on your screen, but the server thinks it is detached, so the scripts won't run. Try the following:

• Avatar Menu - Avatar Health - Refresh Attachments (Alt+Shift+R).
• Detach and reattach the item. It may help to relog before and/or after.
• In addition, if the HUD attaches to the Center 2 HUD point, try changing it to a different HUD attachment point. Attachments may be less likely to “fall off” of other attachment points.

Note: this is related to this bug.

Look in the Avatar menu and make sure that “Show HUD Attachments” has a checkmark.

A HUD's orientation data (position and rotation) data is stored with the HUD when it's detached. It is relative to the attach point, not to the viewer. (Any attached object has its orientation data saved when it's detached) When you attach a HUD to a new attach point, the previous position data is applied relative to the new attach point and the rotation data is reset to zero, and this can cause the HUD to be out of position or rotated incorrectly. To fix a HUD's position:

• Attach the HUD to its original attach point
  or
• Edit the HUD (right click it in Inventory, choose Edit) and set the position data to zero and then adjust from there
  or
• Edit the HUD and then scroll down with the mouse wheel to zoom out the HUD Layer, represented by a white rectangle. Drag the HUD so that it's inside the rectangle, then zoom in and finish adjusting.

If the HUD can't be seen but its position is correct, you may have to adjust the rotation. Edit the HUD, then change the rotation values or drag the rotation rings.

Possible reasons why HUDs or other scripted attachments may stop working:

• Disconnected during a teleport after restarting a region. See BUG-5034.

• Script (running) state is lost when logged out during forced teleport. See BUG-41379.

• There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.

Note: While this issue most commonly affects HUDs, it can also affect any and all other scripted attachments you were wearing when the breakage happened.

There are a few things you can try to get the items working again.

First of all:

• If you have RLV enabled, disable it (Preferences → Firestorm → Extras, top option), relog, then try again.
• Go to Top Menu → Avatar → Avatar Health → Refresh Attachments. See if that fixes the items.
• Relog then test the items again. That may be enough. If not, read on.

Things to try:

• Check for location issues:
  • Make sure you are in a region that has scripts enabled.
  • Go to other regions and test the items there. This will rule out technical problems with the original region.

Stay in a script-enabled region to do all of the following. You do not have to do the following steps in this order, but the simplest and less drastic steps are listed first:

• Attempt to get scripts running:
  • Try removing and reattaching the items.
  • If the items are modifiable, try resetting them or setting their scripts to running: Inventory, right-click the item → Edit, and while it is in Edit, go to Build menu → Scripts → Reset Scripts, or Build menu → Scripts→ Set Scripts to Running).

• Check for interference:
  • Look in Inventory > Current Outfit folder, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached. (Temp HUDs have been known to freeze other HUDs on the same attachment point.)
  • Check that HUDs are not overlapping each other on the screen (and so preventing you from clicking).

• Check for issues with attachment points:
  • If any HUDs are sharing the same HUD attachment point, try moving them to separate HUD attachment points:
    Inventory → Right-click → Detach from Yourself, then Inventory → Right-click → Attach to HUD, and choose an unused point.
  • Even if they are not sharing attachment points, try moving them to different attachment points.

• Test basic functionality. To make sure that HUDs work for you at all, and work in your present location, do this:
  1. Rez a fresh cube
  2. Add the default script to it
  3. Take it into inventory
  4. Attach it to an empty HUD point
  5. Touch the HUD and see if there is script output in Local chat.
  6. If this doesn't work, then the problem is not with specific broken HUDs, but perhaps with your region, or some other unknown problem keeping you from running scripts.

• Identify broken items:
  • Try removing all the HUDs and other attachments and testing them one at a time: test each one, then remove it, then test another.
  • If you have original copies of the items, try detaching the ones you are currently wearing and using a fresh copy from the original.
  • If an item is no-mod and you can't get it to start running again, and you don't have another copy, you will need to request a new copy from the creator.
  • Note: If the non-working HUDs are for your mesh body parts (or other scripted attachments), you probably will need to use fresh copies of the original HUDS and the body parts – every part, from scratch (not copies of the broken ones you were wearing).

(Texture Rejetée pour Insuffisance Mémoire“)

Cette erreur est suivie d'un nombre, qui indique combien de textures ont été rejetées. Une fois que le message est apparu vous verrez que d'autres texture ne pourront pas charger, et bien souvent, le viewer crashera peu de temps après.

Le message signifie que vous avez utilisé toute la mémoire disponible - la mémoire graphique plus spécifiquement. Certains diront “mais j'ai 2GB, ça devrait suffire”. En fait non, puisque de toutes manières aucun viewer n'utilise plus que 512MB ¹⁾.

Il se peut également que cette erreur vous arrive si votre mémoire graphique dédiée est basse.Consultez le mode d'emploi de votre ordinateur pour savoir combien de mémoire graphique dédiée vou avez; moins de 512MB sera très probablement source d'ennuis. Moins vous avez de mémoire graphique dédiée, plus vous avez de chances d'avoir cette erreur.

Certains consateront que d'anciennes versions de Firestorm n'avaient jamais ce problème, qu'ils n'avaient jamais vu ce message d'erreur avant et qu'il doit donc s'agir d'un nouveau bug. S'il est vrai que les anciennes versions ne délivraient jamais ce message d'erreur, cela ne eut pas dire que le problème n'existait pas, mais plutôt qu'aucun message n'était délivré et aue vous crashiez toutt simplement sans savoir pourquoi. Au moins, l'ajout de ce massage d'erreur a au moins la vertu d'indiquer où e situe le problème, et par conséquent permet de résoudre le problème plus facilement : au lieu d'essayer tout un tas de solutions qui pourraient être sans rapport, il n'en reste que quelques unes.

Cela dépend …

Si vous avez utilisé Firestorm pendant un moment, et que vous n'avez eu cette erreur qu'une seule fois ou rarement, c'est probablement parce que vous vous trouvez dans un endroit très intensif graphiquement. La solution est donc de réduire la distance d'affichage avant d'aller dans de tels endroits, et de la garder relativement basse jusqu'à ce que vous repartiez.

Soyez conscients que le message, une fois qu'il est apparu, ne partira pas tout seul. Il faudra vous reconnecter. C'est préférable de toutes façons, puisque de nouvelles texture ne pourront pas charger.

Dans ce cas, Firestorm essaie d'utiliser plus de mémoire graphique que ce que vous avez de disponible (rappelez-vous la limite de 512MB mentionnée ci-dessus). Il faut que réduisiez votre utilisation de mémoire graphique. Par exemple :

• Si vous avez un système 64-bit et plus de 4 GB deRAM, essayez une des versions 64-bit de Firestorm. Elle sont moins sujettes à ce type de crash. Vous pouvez rapidement vérifier cette inforamtion dansle menu Help du viewer > About Firestorm

• Préférences→ Graphiques -> Hardware Settings→ Viewer Texture Memory Buffer - réduisez de 128 en 128MB.
  c'est-à-dire, si c'est actuellement réglé sur 512, réduisez à 384; si c'est sur 384, réduisez à 256, etc.
  Ne descendez pas au-dessous de 128.

• Reduisez votre distance d'affichage (draw distance).

• Préférences → Graphics → Hardware Settings → Enable OpenGL Vertex Buffer Objects - Désactivez ceci.

• Quick Preferences Réduire “Maximum Complexity” à 35,000.

• Quick Preferences Réduire “Max Avatars” à 3.

• Réduisez la taille de votre inventaire en commençant par vider la corbeille, en supprimant les choses que vous n'utilisez pas, en mettant dans des notecards vos photos, vos landmarks et vos scripts, en mettant dans des boîtes les choses peu utilisées ou anciennes, les sons, les gestures… ATTENTION : ne stockez jamais vos scripts dans une boîte, vous vous trouveriez peut-être dans l'impossibilité de les récupérer. Egalement, évitez d'ouvrir plusieurs fenêtres d'inventaire à la fois.

• IMPORTANT Ne faites pas ceci si vous avez un système d'exploitation 64-bit !
  Si vous n'avez activé pas le menu Avancé, activez-le en pressant Ctrl-Alt-D. Puis allez dans Avancé → Afficher les Paramètres de Débogage. Tapez FSDestroyGLTexturesImmediately et cochez TRUE.
  Vous utiliserez probablement plus de bande passante et cela signifie que les textures qui ont déjà été chargées deviendront grises quand vous vous détournez , mais cela devrait réduire la fréquence des crashes.

You may find that parts of jewelry items or shoes might disappear even when you are viewing them from a relatively close range, and that the only way to get them to show up is to right-click and edit them. In most cases, this can be dealt with as follows:

1. Via preferences:

• Top Menu Avatar → Preferences or Ctrl-P
• Click on the Graphics tab
• In the General tab, set Level of Detail (LOD) Distance Factors → Objects & Sculpts LOD to 2.

2. Via quick preferences (bottom button bar that has the phoenix logo in it):

• Move LOD Factor slider to 2.

Now cam away from yourself then back and you should find that the small prims are rendering better. You can experiment with the LOD Factor values. Be aware that going too low will make large prims (especially sculpted prims) start to look very strange even from relatively close up, so don't go too low; 2 is the recommended minimum. The suggested range is 2 to 3. But as always, your mileage may vary.

For much more detail on this, please read this blog post.

For unknown reasons, some users need to change an additional setting:

Go to Preferences → Privacy → Lookat, and tick “Don't Send My Selection Target Hints.”