Regarder la vidéo ci-dessous pour une information visuelle de ce qu'est cette nouvelle particularité :

• https://www.youtube.com/watch?v=PxWrqd0o3dc&feature=youtu.be

Allez dans Avatar → Appearance et regardez en bas à droite de la fenêtre.

• Il déterminera quels avatars apparaîtront comme des silhouettes (“jellydolls”) dans votre viewer, sur la base de leur propre complexité.
• Allez à Preferences → Graphics → General → Maximum Complexity
• Notez bien : baisser ce paramètre à l'aide du slider réduira le lag graphique et affichera plus d'avatars en tant que silhouettes ; augmenter le réglage est susceptible de causer plus de lag mais plus d'avatars seront entièrement visibles.
• Notez aussi : il n'est pas recommandé de régler ce slider complètement à droite car cela supprime toute limite - ce qui signfie qu'aucun avatar ne s'affichera en tant que silhouette pour vous, mais vous serez à la merci du lag et des crashers graphiques.

• Cliquer droit sur le nom de l'avatar (sur son tag) et choisir à partir du menu:
• More > More > Render > Normally– l'avatar sera affecté par votre slider de complexité (voir ci-dessus)
• More > More > Never– l'avatar restera une silhouette sur votre écran
• More > More > Fully– l'avatar s'affichera entièrement même si votre slider de complexité est bas

• Allez à Preferences → General et cochez “Show Avatar Complexity” (Afficher la complexité de l'avatar), puis choississez suivant votre souhait “Only if too complex” (seulement si trop complexe) et “Show own complexity” (afficher ma propre complexité)

• Cet avertissement apparaît dans le coin inférieur droit de votre écran.
• Allez à Preferences → Notifications → Alerts, et faites passer “Warn me if my avatar complexity may be too high” dans la liste du bas “Never show”.

• Ceci apparaît dans le coin supérieur droit de votre écran lorsque vous changez de tenue ou d'accessoires.
• Allez au menu Advanced → Show Debug Settings → ShowMyComplexityChanges, mettez la valeur sur 0 pour le masquer, ou à une valeur plus élevée pour l'afficher. Notez quelque part ce réglage au cas om vous voudriez le modifier de nouveau.

• Ceci affiche non seulement la complexité mais aussi le rang et la distance des avatars au-dessus de leur tête.
• Allez à Avatar → Avatar Health → Show Avatar Complexity Information
• Notez bien : la hauteur du texte n'est pas ajustable.

Il existe 2 méthodes :

• Porter l'attachement puis l'enlever, tout en notant le changement de complexité de votre avatar en haut à droite de votre écran.
• Porter l'attachement et éditez-le. Dans la fenêtre d'édition, cliquez sur “More Info” et regardez le nombre listé sous “Display”.

Voici les paramètres par défaut qui déterminent le seuil à partir duquel vous voyez les avatars s'afficher pleinement ou en tant que silhouettes. Ils correspondent au slider de qualité et vitesse graphique (“Quality and Speed”) dans Préférences → Graphics → General. Lorsque les paramètres sont laissés par défaut, les avatars dont la complexité est au-dessous de ces seuils seront visibles, alors que ceux à complexité supérieure du seuil s'afficheront en tant que silhouettes colorées.

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

Index Général

• Téléchargements
• Firestorm Release Notes

• Information de base pour obtenir de l'aide
• Questions & Réponses
• Diagnostic et solutions rapides
• Comment déposer un JIRA
• Comment contacter le Support
• Mon viewer est-il sûr ?
• Questions courantes

• Cours Firestorm (en anglais)

• Ecran d'accueil
• Modes du viewer
• Mise en page du viewer

• Chat
• Inventaire
• Profils
• Tenues vestimentaires
• Gestures
• Mouselook
• Modifier les shapes ou autres parties du corps
• Bouton Personnes on peut accéder à “Près de Vous” (Radar), “Mes Amis” et “Mes groupes” à partir d'ici
• Utiliser la Recherche
• Managing Groups
• Diffusion Audio et Video
• Voix

• Sauvegarder ses paramètres
• Préférences
• Quick Preferences
• Le Cache - Ce que c'est
• Raccourcis clavier

• Paramètres de Complexité de l'avatar
• Préréglages graphiques personnalisés

• Effets physiques de l'avatar
• AO intégré
• Le Bridge LSL
• Windlight

• Debug Settings
• Comprendre le lag

• Informations de base pour obtenir de l'aide
• How to Contact Support

• Firestorm In-World Groups
• Firestorm Classes
• Phoenix Hour Archive

• Firestorm Preview Interface Customization Tutorial Vid

The following videos are about the Firestorm AO:

• Import to AO part 1
• Customize your AO part 2
• Options in AO part 3

• Firestorm Licenses
• Firestorm Privacy Policy
• Firestorm Credits
• Firestorm Source repository
• Main website

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

All installations are done with default settings (unless told specific) if you change that your on your own

• Install Visual C++ 2010 Express (Web install)
• Install Microsoft Visual C++ 2010 Redistributable Package
• Install Windows SDK for Windows 7 and .NET Framework 4 (Web install) or Windows SDK for Windows 7 and .NET Framework 4 (ISO)
• Install DirectX SDK (June 2010)
• Run Microsoft Update, and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
  • For Windows Vista and Windows 7, you need to select “Get updates from other Microsoft products” to get the updates for Visual Studio.
  • For Windows XP, use the provided link above. The Windows Update menu item on your computer is not the correct updater to use.
  • During the update cycles make sure you have picked up Microsoft Visual Studio 2010 Service Pack 1 (Web install) or Microsoft Visual Studio 2010 Service Pack 1 (ISO)

The order of the following installations should not matter.
If the installer for a particular package does not update your PATH environment variable you will have to do this manually.

• CMake (download CMake)
  • This should be version 2.8.4 (or above in the 2.8.x series).
  • Make sure that the following directory was added to your path:

    C:\Program Files (x86)\CMake 2.8\bin (Windows 64bit) or C:\Program Files\CMake 2.8\bin (Windows 32bit)

• Python (Standard Python)
  • Version 2.7.1 works with the build scripts.
  • Add the Python installation dir to the system path:

    C:\Python27

• Mercurial (either TortoiseHg or Mercurial Hg)
• Cygwin (download Cygwin)
  • When you run the cygwin setup utility make sure you have selected to install unzip (under “Archives”), bison, flex¹⁾, patchutils (all located under “devel”), and curl (under “Web”), which are not part of the default install. Do not install Cygwin Python or Mercurial. You won't need to use the Cygwin shell for anything.
  • Add the following directory to the very end of your path and make sure it stays that way.

    c:\cygwin\bin

• Unicode NSIS (Nullsoft Scriptable Install System)
  • This is the package installer used to build a package
  • You only need this package if you are going to distribute the viewer you compile or if you want to install it locally.
• In the Configure VS2010 step below you will need to add a line in the Executable Directories section:
  • 64 bit systems use

    %ProgramFiles(x86)%\NSIS\Unicode

  • 32 bit systems use

    %ProgramFiles%\NSIS\Unicode

• Notepad++
  • You need to use an editor that conforms to the Coding standards. In particular, you must not check in files with DOS line endings except in very limited circumstances.

Autobuild is a Linden Lab resource that does all the hard work.

In a dos command do :

hg clone http://hg.secondlife.com/autobuild/

Modify your path statement after cloning to include the autobuild \bin directory

• Add an environment variable, so that autobuild doesn't default to using (or trying) older compiler versions:
  • Right-click “My Computer” and select Properties or press the windows logo key and the pause key at the same time.
  • For XP, when the Properties dialog opens, click the Advanced tab followed by the Environmental Variables button. This will open a new window with a list of System and User variables. For Vista and later, when the System Properties window opens, click the Advanced system settings on the left column, then click Environment Variables…
  • In the User section, click New. Set Variable Name to AUTOBUILD_VSVER and set Variable Value to 100.
  • Click the OK/Close buttons to close all the windows.

While you may choose to use autobuild for all your compiling you still need to establish certain settings internal to VC2010.

• Start the IDE
• Navigate to Tools> Options> Projects and Solutions> Build and Run and set maximum number of parallel projects builds to 1.
• (VC Express only) Enable Tools> Settings> Expert Settings to get the Build (and other) menus. If you already have a Build menu you do not need to perform this step.

The following steps require an open visual studio project. It does not matter which project you use, as you will only change some global settings used by all projects when they are opened. The open project itself won't be changed.

You need to set a number of paths.

• Open any existing project you may have or make a New Project.

At the bottom on the Solution Explorer you will see three tabs.

• Click the one on the right labeled Property Manager. (The name may be somewhat truncated.)
• On the left side click to expand any project and then click again to expand the Release folder.
• Right click on Microsoft.Cpp.Win32.user.
• Pick Properties> VC++ Directories.

This is where the build environment is pulled together into a functional VC2010 build system and also where much hand wringing, hair pulling, and fist pounding frustration takes place.

• Set Executable Directories to:

$(ExecutablePath)
$(DXSDK_DIR)
$(WindowsSdkDir)\Bin
C:\cygwin\bin
$(SystemRoot)

• Set Include Directories to:

$(WindowsSdkDir)\Include
$(WindowsSdkDir)\Include\gl
$(DXSDK_DIR)\Include

• Set Library Directories to:

$(WindowsSdkDir)\Lib
$(DXSDK_DIR)

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. For this document, I will assume c:\firestorm.

c:
cd /firestorm
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/

This can take a bit, it's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

Note: This typically needs to only be done once since FmodEX rarely changes.

c:
cd /firestorm
hg clone https://bitbucket.org/NickyD/3p-fmodex
cd 3p-fmodex
autobuild build --all
autobuild package

Near the top of the output you will see the package name written and the md5 hash below it:

wrote C:\firestorm\3p-fmod\fmodex-{version#}-windows-{yyyymmdd}.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

where {version#} is the version of FmodEX (like 4.44.18) and {yyyymmdd} is the date you created the package.

cd /firestorm/phoenix-firestorm-lgpl
cp autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Copy the FmodEX path and md5 value from the package process into this command:

autobuild installables edit fmodex platform=windows hash=<md5 value> url=file:///<fmodex path>

For example:

<code>autobuild installables edit fmod platform=windows hash=c3f696412ef74f1559c6d023efe3a087 url=file:///C:\firestorm\3p-fmodex\fmodex-4.44.18-windows-20111212.tar.bz2</code>

Note: Having to copy autobuild.xml and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to autobuild.xml and do not send up a modified autobuild.xml when you do an hg push.

• From All Programs Navigate into the Microsoft Visual Studio 2010 program menu
• Click on Microsoft Visual Studio Command Prompt (2010)

If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new terminal you will need to reset the environment variable with

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

   c:
   cd /firestorm/phoenix-firestorm-lgpl
   autobuild configure -c ReleaseFS_open
   

This will compile with all defaults and without third party libraries.

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• FMOD (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in Fmod_using_autobuild for this to work.
• LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.
• package makes sure all files are copied into viewers output directory. You won't be able to start your compiled viewer if you don't enable package or do 'compile' it in VS.

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE

Example:

autobuild configure -c ReleaseFS_open -- -DLL_TESTS:BOOL=FALSE -DFMOD:BOOL=TRUE --package

If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new terminal you will need to reset the environment variable with

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

autobuild build -c ReleaseFS_open --no-configure

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling will take quite a bit of time.

We are completing our summer series of entertainment with a Steam Punk Carnival to celebrate the 6th successful year of the Firestorm Project. We have a full afternoon of wonderful live musicians to liven up the day in our regions, so all we need is you to make it a great time. We hope you will come by to celebrate with us for a great time with music, games and gifts for all!!

In my opinion music is the food of the Second Life community. Music and art fills our spaces and the air we breathe, they are a large part of our existence and why we return.

Please come join all of us at the Gateway to learn about the SL community through one of our favorite past times, Music. The Firestorm Gateway Events are a way for us to introduce the entire SL Community to you and our region as well as a chance for some of our team to meet and greet you!

For more opportunities keep connecting to the Event Wiki for more surprising events and learn more about why so many are drawn to Second Life. You can experience of our community first hand by downloading the Firestorm Viewer to begin your own “Second Life.”

There is a wonderful group of creative individuals that meets on Friday and Sunday evenings at 6 PMSLT who actively roleplay on our Region. They welcome anyone from beginner to experienced role players to take part in the Sci Fi experience. Get your Trekie on with us at The Gateway!

Storytellers' Sandbox at the Firestorm Community Gateway showcases live voice stories and literature presentations, introducing new residents to the community of spoken word creators and enthusiasts in Second Life. Join us on Sunday, September 11, 2016 3 to 5 PMSLT when the Seanchai Library presents Spoken Word. This event features Story Tellers who will have a variety of Pirate tales to tell and share.

This Sandbox Event we are pleased to welcome to the Firestorm Community Gateway:

Pirate storytellers, each with unique stories, presented live in Voice.

Stop by and let the Story tellers wisk you off to special places with their “Spoken Words” at The Firestorm Gateway Small Event Space .

On occasion we are beginning to feature a few games, like Primtionary, Bingo and Trivia, from time to time at the Firestorm Gateway in our Small Event Space, just down the path from the Social Club House.

It is our hope you will come by to meet new friends and share some giggles while you learn more about Second Life, as well as its endless entertainment experiences that keep our community members coming back. Events Calendar

Watch our wiki to see what is happening next at the Gateway.

Thursday, July 28th The Gateway was once again honor with live singer, this time it was Luke Auster. He brought along his down home country charm, warm personality and great voice to or region. He has an excitingly infectious personality and style. Everyone had a great time with his stories and music. He did a few request for people in the audience and had them all begging for more.

On Tuesday, June 28th, 2016 live Blues performer JavaJoe MacIntyre graced our stage at The Firestorm Gateway. Joe's talent was truly heartfelt. All of us were impressed by his originals and mashups of popular songs like his versions of Eric Clapton's “Layla” and Cream's “White Room” to mention a couple of the many he played for us. Many “sang-a-long” (we do it in text of course) and stayed the entire show, including the Encore. His music is new yet strangely familiar. You can sample his vibes for yourself at www.jjmac.bandcamp.com or in Second Life by utilizing our viewer “Search” feature and “Events.”

Firestorm Team and The Firestorm Gateway celebrated anyone who has a Rez Day in June on Sunday, June 12th at noon SLT,

These events are for the entire SL Community to introduce you to our region as well as a chance for some of team to meet and greet you!

Guest Dj Yogi Enyo rocked everyone with some great 1980's Music. Yogi has been a Dj for 7 years in Sl and has a vast music collection.

The Celebration for June Rezzies Day continued with a live performance featuring “Da Bluez Preacher” SRV4U Conacher and his guitar “Wilma” played live on our stage. Preacher lit up the stage with live electric and acoustic blues that were high energy standards like SRV, BB King, Buddy Guy and the like.

He also debuted a version of a Happy Rez Day Song to all the June Rezzies. We all had ROCKING fun. The Firestorm Gateway

Please Come Celebrate Your July Rez Day at .

Watch for more amazing events at the Firestorm Gateway.

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

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.

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

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 apply, waiting a minute and then enabling voice and hitting apply. 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.

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

• 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 Advanced → Debug Settings, and in the window that opens, type: Cmdlinedisablevoice - then ensure this is set to FALSE.

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.

• Method One:
  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.

• Method 2 - Firestorm 4.7.3 Only:
  Download Firestorm 4.6.9 from here. If you current have FS 64-bit, get FS 4.6.9 32-bit - and vice versa. Go into your “computer” and find the the 4.6.9 Version Firestorm you downloaded.
  Copy the files below and replace them in your 4.7.3 Firestorm install folder:
  ca-bundle.crt
  ortp.dll
  SLVoice.exe
  vivoxoal.dll
  vivoxplatform.dll
  vivoxsdk.dll

Try disabling compatibility mode, if enabled:

• Locate your desktop shortcut for Firestorm
• 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.)

Check that slvoice.exe is not muted in the speaker/headphones icon (located in the notification area) → mixer.

Every linux distro is different; and each distro may have more than one window manager to further complicate things. So tips can't be “absolute”; you will need to experiment and see what works for you. The following have been suggested by some as effective. But first….

In the Firestorm install directory, there's a text file (originally from LL) with tips on getting voice to work in linux. If you haven't read that, then you can try to see if it helps.

• 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 in Firestorm 4.7.9 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. (OK is important, Apply doesn't work.) Reopen Preferences and go back to the device settings button to ensure you're getting sound in on the mic.

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

• Try to ensure that the missing window is closed. Then open Debug Settings via the Advanced menu (press Ctrl-Alt-D to enable Advanced, if it isn't already). 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.

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

This issue is the result of a recent update of Win10, specifically. KB3176938. Please refer to this JIRA page for details and 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 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)

First try changing Preferencess → User Interface → Font → Font size adjustment. If that doesn't help, read on. ¹⁾

1. Exit Firestorm.
2. Right-click the Firestorm application shortcut and select “Properties”
3. In the “Shortcut” tab, find the line marked “Target” and add --noprobe to the end. For example:

  (32-bit version)
  "C:\Program Files\Firestorm-Release\Firestorm-Release.exe" --set InstallLanguage en --noprobe
   
  (64-bit version)
  "C:\Program Files\Firestorm-Releasex64\Firestorm-bin.exe" --noprobe

4. In the “Compatibility” tab, find and UNCHECK the “Disable display scaling on high DPI settings” option
5. Click “OK” to apply and launch Firestorm as normal.

Notes:

• You may need to repeat this after Firestorm updates.
• Do not bring up the “Help → About Firestorm” menu option or you will need to repeat steps 1, 2, 4 and 5 above. Also, starting the viewer from the SL website dashboard will also undo the changes.

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%20Social%20Island/250/6/4001
• 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*

There are different kinds of problems with missing inventory that can take place; those that are controllable at the viewer or computer end are generally reversible. Problems caused by the Second Life asset server are not always fixable.

If items that you rezzed out in-world are missing, then refer to this page instead.

• If the number of items appears correct, but not everything is showing, reset your inventory filters. On most viewer skins, this means clicking the Gear menu at the bottom of your inventory and selecting “Reset Filters.” On Vintage skin (this is what you're using if you logged in with Phoenix Mode) or Ansastorm skin, click Inventory → Reset Filters in the inventory menu.
  Note: if you are looking for Marketplace items using Inventory search, and they are not showing, ensure that you have the Received items folder shown in inventory, rather than as a button: Preferences → User Interface → Interface Windows → Show the Received Items folder in normal inventory. Or, click the Received button to see what items are in there.

• In your inventory, type letters into the search filter. It doesn't matter what letters; the purpose is to prod the search into finding more items. If the fetch stalls again, pick a different letter.

• For any/all folders that appear to be missing inventory, try creating a new item, of the appropriate type, in the folder. So for example, if you appear to be missing things in the Clothing folder, right-click the folder name → New CLothes → New Shirt.

• Try clearing your inventory cache.
  • On recent versions of Firestorm, open Preferences -> Network & Files -> Directories, then click the Clear Inventory Cache button, then relog.
  • On older versions, you will have to clear inventory cache manually, as follows:
    • Go to Preferences → Network & Files; beside Cache Location, click on Open. A window opens showing the contexts of the cache folder.
    • Leave that window open, and log out of Firestorm.
    • Make sure the folder is set to show file extensions.
    • Locate the file whose name ends in .inv.gz, and delete that file.
    • Log back in - preferably to one of the locations given above: at the log in screen, you can select log in location; type in one of the region names indicated above.
  • Additional notes: If clearing inventory cache does not fix the problem the first time you try it, then it probably won't work on additional attempts, so don't keep doing it (though multiple relogs without cache clears may help).

If your inventory is still not loading fully, then the issue may be a network or connection problem. General suggestions for problems that may be connection-related are:

• If you are on a wireless connection and are able to wire it in, do so.

• Reboot your router/modem, leaving it unplugged and unpowered for a minimum of two minutes before powering it back up again.
  • If you have access to a different connection, try connecting your computer to it temporarily.

• If the inventory is still not fetching all the way, view our page on bandwidth and speedtests to make sure your bandwidth is set optimally in the viewer. Although it may seem counter-intuitive, we have found that lower bandwidth settings usually allow for more reliable inventory loading than higher settings.

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

• Please download the official SL viewer, install it, log in on it and see if the items show up there. If they do, then the problem is probably either loading or caching in Firestorm, and you can follow the set of suggestions below under “Advanced Method: Inventory Copy from SL Viewer.” If the items don't show up in any viewer, then there is a good chance they're missing from the asset server, which means the problem may not be fixable.
  

Back on Firestorm, if your inventory count still looks lower than it should be or stalls in the middle of fetching items, then:

• If the above steps have not worked for you, continue on to the next step:

Start by finding your avatar key while logged into Firestorm or another viewer that displays it - see the figure to the right; the UUID is highlighted in green.

It is a string of letters and numbers that appears in your legacy-style profile, though the exact location will vary because different skin options display it differently. If you use web profiles, you will need to switch into the legacy profile to find it. (In Firestorm, this is in Preferences -> User Interface -> Interface Windows→ Use web profiles by default.) You can return to the web profile style afterward. When you find your key, just copy it down somewhere.

Now you will need the latest release version of the SL viewer, so if you don't have it installed yet, download and install it. Then, log into the SL Viewer and get your inventory loaded in that viewer. This might work with any other viewer, as well, but the SL Viewer is the only one we've tested with. Once your inventory is loaded there, log out.

Locate your Second Life cache folder and your Firestorm cache folder on your hard drive. Our clearing cache page will help you locate where that is (just replace “Firestorm” with “SecondLife” in the path name. Don't clear either cache! Just use the paths shown to find the folders.

In the Second Life cache folder, find the file named with your avatar key and ending in “inv.gz”. Drop or copy this file into your Firestorm cache folder. Allow it to replace the one there.

Log into Firestorm and check to see if your inventory is there.

Avoid clearing cache or you may need to do this process again.

Please note: Under normal circumstances, you should not share cache between viewers because it can cause other weird problems. This suggestion should not be read as an indication that setting your cache in different viewers to the same place would be useful. It won't be.

For additional ideas, also refer to the Second Life wiki page on Inventory Loss.

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, 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 had 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 website.

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

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

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

• 32-bit Havok SL
  SHA: 90E5B454C06BED06A7A180ED60DCC2B49FFD23B1
• 32-bit non-Havok OS
  SHA: 75DF3EABA2979921DEAC2361A53C4F49788FAAC4

Key = Key Sequence

SI le viewer crash fréquemment, essayez les suggestion si-dessous. Ne survolez pas la page, lisez-la avec attention.

Il est important de faire la différence entre deux choses …

Si une fenêtre apparaît disant que vous avez été déconnecté de SecondLife, il ne s'agit pas d'un crash. SL vous a déconnecté pour une raison telle que les suivantes :

• Le serveur de la région où vous vous trouvez est en train de “tomber”;

• Pendant la téléportation les serveurs ne réussissent pas à vous envoyer à votre destination et vous déconnectent;

• Votre connexion internet est tombée;

• Votre connexion internet est devenue instable ou trop faible et SL a perdu le contact avec votre avatar.

Si vous êtes déconnecté quand vous entrez en mode “Modification de la silhouette” ou “Modifier la Tenue”, ou quand vous cliquez le bouton Apparence sur la barre de boutons, vérifiez que vous n'avez pas glissé des objets dans le dossier “Mes Tenues” qui n'ont pas été créés à travers la fenêtre d'Apparence. Si c'est le cas, supprimez ces objets.

Si Firestorm crash :

• (Windows uniquement) Si vous utilisez une carte graphique ATI (AMD), voir ici les problèmes spécifiquement liés à ces cartes.

• Désactivez les VBOs: Ouvrez Firestorm et avant de vous connecter, pressez Ctrl-P pour ouvrir les préférences. Puis allez dans Graphiques → onglet Hardware Settings. Décochez“Enable OpenGL Vertex Buffer Objects”.

• Il est possible que vos paramètres graphiques soient trop haut par rapport à ce que votre carte graphique peut faire. Vérifiez si c'est le cas : Préférences → Graphiques → Bouton “Reset”.

• Autre chose à essayer : Menu Développeurs → Monde → Vidage de Cache d'Objet de la Région, puis reconnectez-vous. (On rend le menu Développeurs apparent en pressant Ctrl Alt Q). Parfois ceci règle certains problèmes de bizarreries dans les textures. Il peut être nécessaire de le faire plusieurs fois.

• Si vous crashez lorsque vous cliquez un lien ou une SLURL : avez-vous AVG 2011 sur votre ordinateur ? Si c'est le cas il a probablement signalé le slplugin comme process malveillant. Voir ici pour plus d'information à ce sujet.

• Si vous crashez en téléchargeant une texture, essayez de désactiver les VBOs comme indiqué ci-dessus. Si vous êtes sous Windows et que vous avez Microsoft Skydrive, voyez ici.

• Il arrive que le cache soit corrompu, si cela arrive vous allez crasher fréquemment. Essayez de vider le cache et voyez si cela résout le problème. Il est recommandé de le faire manuellement de la façon indiquéeici.

• Si rien de tout cela n'a résolu le problème, essayez une réinstallation propre du viewer.

• Si vous vous apercevez que vider le cache est la seule chose qui vous permet de vous connecter, il y a de bonnes chances que vous ayez un ou plusieurs “mauvais gestures”; voir cette page.

SLURL Proxy is an application that will handle SLURLs on your Windows system. Clicking a slurl on the web, will open SLURL Proxy, which will forward the SLURL to the viewer you have chosen. Alternatively, SLURL Proxy gives you the option to set a viewer of choice directly, without using the proxy function.

Various Second Life viewers you might, or may already have installed, overwrite your registry settings and change the way slurls are handled on your system, but without asking you.

SLURL Proxy provides an easy and user friendly way to correct this, without you having to tamper with your registry, and whenever you feel like changing your settings.

You can download SLURL Proxy, and unpack it to a location of your choice. Double click SLURL Proxy.exe to start it.

Upon start up, SLURL Proxy will check to see if it's the default slurl handler. If it is not, it will inform you about that, and ask you if you'd like to use SLURL Proxy as default instead.

When you have set SLURL Proxy as default,(or even before that) you can simply drag one or more viewer shortcuts onto the application window, and they should be listed with viewer name, and icon. After this, you can close SLURL Proxy and it's ready to go.

SLURL Proxy allows you to add several viewers, and one always needs to be the default viewer to use. The default viewer is the one where the checkbox is checked. If you would like to change the default viewer, simply click the viewer of your choice in the list.

That's it.

Firefox or Chrome might be asking you what application to use when you click a slurl on the web, and if so, it will also display a choice of associated applications, in which the application you defined as default (for example SLURL Proxy or a Viewer.exe), will be highlighted.

Internet Explorer should simply be showing a dialog that informs you about the application that is trying to handle the clicked slurl, and if you want to allow that.

If you wish to set a viewer as default slurl handler instead of SLURL proxy, then you simply need to click Set other SLURL handler in the menu, and drag the shortcut of your favourite viewer onto the window.

Requires .NET 3.5 and only runs on Windows

The file you download, is a packaged as a zip archive.

• Start SLURL Proxy
• In the dialog asking if SLURL Proxy should be the default SLURL handler, click NO
• In the top menu, click “Set other SLURL handler”
• Drag your Firestorm short cut onto the SLURL Proxy Window
• You're done and can close SLURL Proxy

Please note : If you already have a Viewer running, then any SLURLs will open in that Viewer, regardless of your settings.

Regarder la vidéo ci-dessous pour une information visuelle de ce qu'est cette nouvelle particularité :

• https://www.youtube.com/watch?v=PxWrqd0o3dc&feature=youtu.be

Allez dans Avatar → Appearance et regardez en bas à droite de la fenêtre.

• Il déterminera quels avatars apparaîtront comme des silhouettes (“jellydolls”) dans votre viewer, sur la base de leur propre complexité.
• Allez à Preferences → Graphics → General → Maximum Complexity
• Notez bien : baisser ce paramètre à l'aide du slider réduira le lag graphique et affichera plus d'avatars en tant que silhouettes ; augmenter le réglage est susceptible de causer plus de lag mais plus d'avatars seront entièrement visibles.
• Notez aussi : il n'est pas recommandé de régler ce slider complètement à droite car cela supprime toute limite - ce qui signfie qu'aucun avatar ne s'affichera en tant que silhouette pour vous, mais vous serez à la merci du lag et des crashers graphiques.

• Cliquer droit sur le nom de l'avatar (sur son tag) et choisir à partir du menu:
• More > More > Render > Normally– l'avatar sera affecté par votre slider de complexité (voir ci-dessus)
• More > More > Never– l'avatar restera une silhouette sur votre écran
• More > More > Fully– l'avatar s'affichera entièrement même si votre slider de complexité est bas

• Allez à Preferences → General et cochez “Show Avatar Complexity” (Afficher la complexité de l'avatar), puis choississez suivant votre souhait “Only if too complex” (seulement si trop complexe) et “Show own complexity” (afficher ma propre complexité)

• Cet avertissement apparaît dans le coin inférieur droit de votre écran.
• Allez à Preferences → Notifications → Alerts, et faites passer “Warn me if my avatar complexity may be too high” dans la liste du bas “Never show”.

• Ceci apparaît dans le coin supérieur droit de votre écran lorsque vous changez de tenue ou d'accessoires.
• Allez au menu Advanced → Show Debug Settings → ShowMyComplexityChanges, mettez la valeur sur 0 pour le masquer, ou à une valeur plus élevée pour l'afficher. Notez quelque part ce réglage au cas om vous voudriez le modifier de nouveau.

• Ceci affiche non seulement la complexité mais aussi le rang et la distance des avatars au-dessus de leur tête.
• Allez à Avatar → Avatar Health → Show Avatar Complexity Information
• Notez bien : la hauteur du texte n'est pas ajustable.

Il existe 2 méthodes :

• Porter l'attachement puis l'enlever, tout en notant le changement de complexité de votre avatar en haut à droite de votre écran.
• Porter l'attachement et éditez-le. Dans la fenêtre d'édition, cliquez sur “More Info” et regardez le nombre listé sous “Display”.

Voici les paramètres par défaut qui déterminent le seuil à partir duquel vous voyez les avatars s'afficher pleinement ou en tant que silhouettes. Ils correspondent au slider de qualité et vitesse graphique (“Quality and Speed”) dans Préférences → Graphics → General. Lorsque les paramètres sont laissés par défaut, les avatars dont la complexité est au-dessous de ces seuils seront visibles, alors que ceux à complexité supérieure du seuil s'afficheront en tant que silhouettes colorées.

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

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.

L'implémentation du SSA a réduit de façon singificative les problèmes d'apparence (Skin ou textures ne chargeant pas, avatar en nuage, etc) Le SSA a complètement changé la façon dont les textures de l'avatar sont traitées, et le nouveau procédé est nettement moins enclin aux erreurs causées par les problèmes de connectivité ou de région.

Evidemment il peut y avoir des problèmes malgré tout. Cette page offre des solutions aux problèmes connus.

• Si vous avez activé le RLV, allez dans Préférences → Firestorm → Extras, désactivez-le, puis déconnectez-vous et reconnectez-vous.

• Allez à l'un des endroits suivants, et restez-y pendant que vous suivez cette page :
  • Hippo Hollow
  • Cyclops

• Votre inventaire doit avoir entièrement chargé avant que votre apparence ne soit normale. Cliquez l'onglet récent dans la fenêtre d'inventaire. Assurez-vous que le compte d'inventaire ne montre plus “nnnn articles récupérés” (ou “fetching”), mais juste le nombre d'articles. Tant que vous voyez “nnnn articles récupérés” (ou “fetching”), votre inventaire n'a pas fini de charger.
  S'il arrête de charger, essayez de taper des lettres au hasard dans la barre de recherche de l'inventaire ou cliquez alternativement sur les boutons “Réduire” (ou Collapse) et “Développer” (ou Expand) jusqu'à ce qu'il ait fini de charger. S'il refuse de charger, référez-vous à cette page.

• Faites un clic droit sur une autre tenue dans votre inventaire, et sélectionnez “Remplacer la tenue actuelle” (ou “Replace Current Outfit”).

• Remplacez les 4 parties basiques l'une près l'autre (Skin, shape, bald hairbase, yeux.

• Dans votre fenêtre d'inventaire, onglet “Mon Inventaire” (ou “Inventory”), dossier “Tenue Actuelle” (ou “Current Outfit”), assurez-vous que les 4 parties basiques apparaissent toutes portées : shape, skin, bald hairbase, yeux. SI vous ne les portez pas, cliquez droit dessus et portez-les.
  Si vous n'arrivez pas à porter les 4, faites un nouveau dossier dans votre inventaire glissez-y ces 4 parties de base, et une tenue (sans attachments, uniquement des layers). Cliquez droit sur ce nouveau dossier et sélectionnez Remplacer la Tenue Actuelle.

• Si vous êtes sur une connexion de téléphone mobile, tout et tout le monde d'affiche probablement en gris. Il vous faut une connexion internet correcte. Si possible passez donc une connexion sur box ou modem. Vous vous verrez alors normalement.

• Débranchez votre box/modem et éteignez votre ordinateur. Laissez-la box/modem débranché(e) pendant 1 bonne minute, puis rebranchez-la/le. Lorsqu'elle/il s'est réinitialisé(e), redémarrez votre ordinateur et reconnectez-vous.

• Si tout cela n'a pas résolu le problème, continuez ci-dessous.

Si vous utilisez plus d'un moniteur, exécutez Firestorm sur votre moniteur principal.

Toujours pas chargé? Continuez…

Egalement valable si vous êtes en nuage.

Le “Rebake” classique (Ctrl-Alt-R) ne fonctionnera plus dans ce cas. Faites un clic droit sur votre tag :

• Menu contextuel: sélectionnez “Texture refresh”
• Menu “Pie” :Sélectionnez Apparence → Tex. Refresh

Ceci peut venir d'un problème de connectivité, en général c'est ce qui arrive quand le viewer ne charge pas ou n'utilise pas toutes les données. Si le problème persiste, essayez d'aller sur un autre SIM, de préférence un qui soit low lag, comme : Hippo Hollow ou Cyclops.

Si vous comprenez l'anglais, il y a plus d'information dans ce JIRA.

La première chose à essayer est “Tex.Refresh” comme décrit plus haut.

Si le problème n'est pas résolu il est probable que l'une des textures que vous portez est corrompue :

• Enlevez toutes les “layers” que vous portez, puis faites un “Tex. Refresh” comme décrit plus haut.
• Si votre avatar apparaît correctement lorsqu'il est nu, commencez à ajouter les “layers” une par une. L'une d'entre elles apparaîtra probablement entièrement ou partiellement grise et a besoin d'être remplacée.
• Si votre avatar apparaît toujours entièrement ou partiellement gris en ne portant aucun vêtement, essayez une autre skin. Si votre avatar apparaît alors correctement, le fichier de votre skin est corrompu.

Pour plus d'info, si vous comprenez l'anglais voyez ce JIRA LL.

Ce problème peut aussi arriver si vous utilisez une connexion sur téléphone mobile pour vous connecter à SL. LL est encore en train de faire des recherches sur ce sujet. Si vous comprenez l'anglais, il existe un fil de discussion ici.

Cela peut aussi arriver si vous avez un problème de DNS. Les problèmes DNS se produisent d'une manière telle que le seul symptôme que vous verrez résultera dans des textures d'avatar grises et cela peut être intermittent.

La solution est d'utiliser Google Public DNS.

Si vous êtes le seul à voir vos changements de tenues, vous avez probablement ce problème : SUN-99. Ils semble que cela soit lié à l'utilisation d'un autre “Third party” viewer. Seul LL peut rédoudre le problème; vous devrez déposer un “ticket” ici : https://support.secondlife.com/create-case/

This issue is the result of a recent update of Win10, specifically. KB3176938. Please refer to this JIRA page for details and 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 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)

First try changing Preferencess → User Interface → Font → Font size adjustment. If that doesn't help, read on. ¹⁾

1. Exit Firestorm.
2. Right-click the Firestorm application shortcut and select “Properties”
3. In the “Shortcut” tab, find the line marked “Target” and add --noprobe to the end. For example:

  (32-bit version)
  "C:\Program Files\Firestorm-Release\Firestorm-Release.exe" --set InstallLanguage en --noprobe
   
  (64-bit version)
  "C:\Program Files\Firestorm-Releasex64\Firestorm-bin.exe" --noprobe

4. In the “Compatibility” tab, find and UNCHECK the “Disable display scaling on high DPI settings” option
5. Click “OK” to apply and launch Firestorm as normal.

Notes:

• You may need to repeat this after Firestorm updates.
• Do not bring up the “Help → About Firestorm” menu option or you will need to repeat steps 1, 2, 4 and 5 above. Also, starting the viewer from the SL website dashboard will also undo the changes.

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.

NOTE: For a video tutorial on backup and restore, see here.

If you've ever run into the situation where the fix for a problem is to clear your settings, you face a not insignificant task of redoing all those settings. It can be frustrating, especially if original problem doesn't go away.

What if you had a known-good backup of your settings? Then you could clear out the current ones and just pop in your good set. Easy.

IMPORTANT: Don't use backups for a different viewer. They're not compatible with each other.

With Firestorm, you can back up most settings directly from the viewer itself, via Preferences→ Backup. You may wish to backup to a thumb drive, for additional protection.

• Make sure you are logged into SL.
• Go to Preferences → Backup.
• Specify a path (folder) where the backup files should be saved, by clicking the Set button at the upper right, and selecting a folder. Ideally, make a new folder on your computer, specifically for Firestorm backups.
  Do not use the Firestorm settings or install folder for this; use a new folder.
  
• Note: You may want to name your folder something like “Firestorm Backup.” When you make the backup, Firestorm will automatically create a subfolder with your avatar name.
• Click on the Backup Settings button.

This will back up all global settings, and the settings for the account you logged in with. If you have multiple accounts, with different per-account settings, you should do the above for each account.

Note: All settings are backed up, regardless of which checkboxes are selected. You can restore selectively.

• Log in with the viewer (restore needs to know what account to restore to).
• Go to Preferences → Backup.
• If you have just wiped your settings, you will need to select the path (folder) where your backup files were saved, by clicking the Set button. Use the checkboxes in the 3 tables to select what settings you want restored; you can select all of them by clicking the Select All button at the upper right, and then browsing for the folder.
• Click on the Restore Settings button. NOTE: be careful NOT to click the “Backup” button or you will wipe out your backup!
• Log out of Firestorm, then restart it.

Settings backup will store all settings for the account you are logged in with, be they global settings (that is, those that affect all accounts on a given computer), or “per account” settings. If you run multiple accounts and wish to have a backup of its “per account” settings, you will need to log in with each one and do a backup.

It follows that you can backup settings from one account and restore to another, but this will only restore global settings, since the “per account” settings refer to a different account.

“Per account” Settings are backed up to a folder with that account's avatar name, inside the backup folder you specify.