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, * Firestorm Classroom
• JU: Junkyard University, * Junkyard University Classroom

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.

Unscheduled classes may also be held on an impromptu basis. If this happens, a notice will be sent in Firestorm Support English. secondlife:///app/group/3a1be8d4-01f3-bc1a-2703-442f0cc8f2dd/about

*All times SLT*

If you can turn in circles but not move forward/backwards, you probably have Movelock enabled.

• Go to the Avatar menu→ Movement submenu and make sure Movelock is not ticked.
• See Movelock info for more information or if you are unable to change the Movelock setting.

However, there are a few other things to try:

• Go to a different region and see if you are able to move there. If so, something at your original location is causing the problem.
• If you are using a LAQ mesh head, make sure you don't have the Pose feature turned on.
• Make sure you don't have some other HUD with a pose feature.
• If you can't find what attachment is causing the problem, try going to Advanced menu (Ctrl-Alt-D ) → Release Keys.
  • Note: Release Keys will be greyed out if RLV has locked any of your attachments. To disable RLV, go to Prefs → Firestorm → Extras, untick the top item, and then relog.
• Make sure you don't have the Firestorm pose stand active.
  • If you have the Pose Stand button on your toolbar, make sure it's not “on.”
  • If you don't have the button, go to Avatar menu → Toolbar Buttons, drag the Pose Stand button out to your toolbar, and make sure it's not “on.”

• Try Avatar menu → Avatar Health → Stop Animations & Revoke Permissions.
• Try right clicking your avatar → Reset Skeleton & Animations.
• Remove attachments one by one until the animation stops.
  • Note: Animations can be in ANY attachment.
  • Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Make sure the Firestorm AO is off:
  • On the AO button on your toolbar, untick the checkbox.
  • Note: The Firestorm AO can be active even if the button is not on your toolbar. If it is not on your toolbar, go to Avatar menu → Toolbar Buttons, drag the AO button out onto your toolbar, and make sure it is not ticked.

• If you know what item gave you the animation:
  • Go to Preferences → Firestorm → Protection → Revoke Permissions.
  • Temporarily set this to “Revoke on Sit and Stand.”
  • Sit on the item, then stand. This should stop the animation.
  • Change Preferences → Firestorm → Protection → Revoke Permissions back to either “Never” or “Revoke on Stand.”

• You may simply be experiencing lag: See Troubleshooting Lag for tips to reduce this.
• Many pose balls will request permission to animate you. If you did not see the animation request, look in your Notifications window for the message. Click “Accept.”
• Make sure you have not blocked the item or its owner: Look in Comm menu → Block List, see if the item or the item's owner is there, and remove the item/person from the block list.
• Go to Preferences → Firestorm → Protection → Revoke Permissions. For normal use, this should be set to either “Normal” (no protection) or “Revoke on Stand.” It should normally NOT be set to “Revoke on Sit” or “Revoke on Sit and Stand,” as both of these will prevent items from animating you when you are sitting.

“Rubber-banding” is when you try to walk forward and then suddenly snap back to a previous position. Sometimes you will seem unable to stop walking. This is caused by region lag, when the server can't keep up with processing avatar movement (collisions).

• For info about region lag see here: Region Lag
• For some things that region or parcel owners can do to reduce region lag see here: Reducing Server Lag.

This typically happens when you have two or more conflicting AOs (animation overriders) on.

• Start by removing known AOs until you are wearing only one known AO.
• If that doesn't help, start by removing other HUDs, then all other attachments, one by one, until it stops. Any worn item can contain an animation, so don't assume that some items are “ok.”
• Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Try turning the opposite direction to the spin.
• Try pressing BOTH right and left arrow keys at the same time, repeatedly.
• Relog.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

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

• In most cases, pressing Ctrl-R to toggle run mode will get you back into walk (though it may in some cases be necessary to hit Ctrl-R more than once).
• If you are wearing a scripted AO (animation overrider), turn off any “running” features it has.
• If you are using the Firestorm built-in AO (animation overrider), make sure there are no running animations in the “Walking” or “Standing” categories.

After Strafe

Ref. BUG-6825

In one specific case, the above will not work. Specifically:

• You have Preferences → Move & View → Movement → Tap-tap-hold to run enabled.
• Press shift, then tap-tap-hold the left or right arrow key

That gets you running sideways. If you release shift before the arrow key, you will be stuck running.

To stop running, you have to repeat the sequence: press shift, then tap-tap-hold left or right arrow.

This is a known SL bug also affecting the SL viewer. Refer to this SL bug report for more information.

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 2018 (and reported as recently as May 2019) 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

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

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

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

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

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

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

• Reset the window's position via Debug Settings. To do this,
  1. Try to ensure that the missing window is closed. (You many be able to tell this if you are using a toolbar button and it is highlighted or not.) If you can't tell, proceed anyway.
  2. Then open the Advanced menu (press Ctrl-Alt-D to enable Advanced, if it isn't already), and go to Show Debug Settings.
  3. Consult the table below for the names of the two settings that match your missing window.
  4. Find the first setting in the Debug Settings window; set it to 0 (zero).
  5. Repeat for the second setting.
  6. Relog before re-opening the window.

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

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

Si votre portable a à la fois un processeur Intel et une carte graphique Nvidia ou ATI/AMD, il est parfois possible de commuter de la puce intégrée Intel à la carte graphique pour une meilleure performance. Cependant Firestorm ne sélectionne pas toujours automatiquement la carte graphique à haute performance.

Pour vérifier, regardez dans Aide > A propos de Firestorm et voyez le nom de la carte graphique. Si c'est Intel ou si le pilote n'est pas un pilote ATI/AMD ou Nvidia, suivez les étapes suivantes :

• Déconnectez-vous de Firestorm

• Faites un clic droit sur votre bureau et sélectionnez Panneau de Configuration Nvidia
• Sélectionnez Panneau de Contrôle Nvidia
• Allez dans Gérer les Paramètres 3D (à gauche)
• Allez dans l'onglet “Paramètres de programme” (à droite)
• Cliquez sur le bouton “Ajouter”
• Naviguez jusqu'au fichier .exe du dossier d'installation de votre viewer:
  C:\Program Files (x86)\Firestorm-Release\Firestorm-Release.exe for the 32-bit Havok
  C:\Program Files (x86)\FirestormOS-Release\FirestormOS-Release.exe for the 32-bit OpenSim
  C:\Program Files\Firestorm_Releasex64\Firestorm-bin.exe for the 64-bit.
  Au cas où les extensions de fichiers sont cachées, cherchez le fichier avec une icône Firestorm le plus volumineux. Il portera le nom du viewer que vous utilisez.
• Après avoir sélectionné ce fichier, utilisez le menu déroulant juste au-dessous (ou au-dessus, suivant les versions) de la liste de programmes pour sélectionner le “Processeur Nvidia haute performance”.
• Cliquez sur Appliquer et/ou Sauvegarder puis fermez le panneau de configuration Nvidia.
• Ouvrez le viewer et allez dans Help → A propos de Firestorm (Help → About Firestorm). Vérifiez que la carte graphique listée est bien votre carte Nvidia.

• Faites un clic droit sur votre bureau et sélectionnez “Paramètres Radeon”.
• Aller dans Préférences > Paramètres additionnels > Power > Switchable graphic application settings.
• Si vous avez utilisé Firestorm au moins une fois, il apparaîtra dans la liste des dernières applications
• Si ce n'est pas le cas, cliquez sur “Ajouter une application”.
• Cherchez le dossier d'installation de Firestorm et sélectionnez le fichier :
  C:\Program Files (x86)\Firestorm-Release\Firestorm-Release.exe pour la version 32-bit Havok
  C:\Program Files (x86)\FirestormOS-Release\FirestormOS-Release.exe pour la version 32-bit OpenSim
  C:\Program Files\Firestorm_Releasex64\Firestorm-bin.exe pour la version 64-bit. Cela ajoutera Firestorm à la liste et vous pourrez dorénavant le choisir.
• Dans la colonne Paramètres graphiques, assignez le profil Haute Performance à Firestorm.
• Si vous avez à la fois une version 32 et 64 bits de Firestorm, recommencez la procédure pour la 2ème version.
• Cliquez sur “Appliquer” au bas de la fenêtre et fermez le panneau à l’écran.
• Ouvrez Firestorm et allez dans Help → About Firestorm. Vérifiez que la carte vidéo AMD soit affichée dans la liste du matériel.

• Cat Herder:Jessica Lyon
• Manager:Miro Collas
• HR Manager (FSG Helpers):Dorrie Bellman
• Land Manager:Flossy Andrew
• Assistant Managers:Coral Sharpshire, Kio Feila
• RolePlay and Scifi Portal manager:Teresa Firelight

• Abinathra
• akafox
• Alexegram
• Angela Kwak (Dutch)
• Avalon Bouvier
• ChuckPC
• Fayleen Bellios
• FrankASinatra
• Grey Levasseur
• ImaLuckygirl
• Jolie Serendipity
• Khasumi
• Kitty Beery (Dutch)
• LegitBonzai (Dutch)
• Liliana Darwinian (Portuguese)
• LosAngelesGraff
• MacMaccee (German)
• MarcSeven Lubitsch
• PassionateAviator
• Pim Peccable
• Sparkle Weatherwax
• Talula Shippe
• Tracy Argus

• 0079Galadriel
• MarcSeven Lubitsch
• nuttidoxieg4 merryman
• panterapolnocy
• Starwolff2000
• Varahi Lusch

• Education:Alexegram, Dorrie Bellman, ImaLuckygirl
• Avatar Education:Kio Feila, Tracy Argus
• Small Events Planner:Jolie Serendipity
• FS Tour Guide:Fayleen Bellios

Firestorm has several folders with special purposes:

• #Firestorm, which contains:
  • #AO
  • #LSL Bridge
  • #Wearable Favorites
• #RLV

If your #FS, #AO, or #Wearable Favorites are suddenly empty, or you notice one of them in the wrong place in inventory, proceed as follows:

First: If you haven't yet, find the missing folder:

• Try typing the name of the folder in Inventory search. You will probably now see two copies of it, one empty and one with your contents.
• In the typical scenario, the empty ones will be inside the #Firestorm folder, and they will need to be deleted.
• The full ones will need to be moved back into their original location.

Second: Delete the empty folder(s) as follows:

1. Unprotect them by going to Advanced menu → Show Debug Settings. Search for ProtectAOFolders or ProtectWearableFavoritesFolders, as needed.
2. Set those debugs to FALSE.
3. Delete the empty folder(s).

Third:

1. Move the full folder(s) back into the #Firestorm folder
2. Protect the folder(s) by going to Advanced menu → Show Debug Settings. For any debug setting that you changed above, reset it to TRUE. (Note: if this doesn't work, a relog may be needed, followed by setting it to True.)

The Current Outfit Folder (abbreviated as COF) in your inventory is used to keep track of what you are currently wearing (as the name implies). It is also used to generate your visual appearance, via Server Side Appearance. It is a system folder - ie, not one you should ever place items into.

On rare occasions, this folder can become corrupted. Symptoms of this include:

• only one account is affected;
• you will crash or timeout disconnect at login, usually around “Downloading clothing…”;
• you will likely crash/disconnect on any V3 based viewer or a viewer that uses COF;
• Reinstalling the viewer, clearing cache, replacing outfit on a non-COF viewer will not fix you.

Examination of viewer logs will usually show:

INFO: newview/llappearancemgr.cpp(1998) : LLAppearanceMgr::updateAppearanceFromCOF: starting

Followed by (but not always) lots of:

WARNING: newview/llappearancemgr.cpp(2891) : WearablesOrderComparator::operator(): Warning # 0: either item1 or item2 is NULL

Please try the following steps, exactly as described:

• Login on Imprudence 1.3.2 stable version.
• Go to your Inventory Library → Clothing and drag one of the outfit folders onto your avatar eg) Boy next door. Wait until you see this default avatar appear.
• Logout of Imprudence
• Launch Firestorm but do not login yet.
• From the login screen, go to Viewer → Preferences → Advanced → Tick “Show Advanced menu” → Apply → Ok.
• You should now see a “Debug” option in the top menu bar. Go to Debug → Debug settings → VerifyInitialWearables → Set to TRUE
• Now login with Firestorm - Do not attempt to change anything you are wearing on your avatar yet.
• Open your Inventory and go to your “Current Outfit” folder and open it. Examine the list of items in your current outfit folder and you very possibly will have a lot of items in there showing as unworn.

Any item that shows as unworn, right click it and delete it. This will not delete the original item, only the link.

• Once all unworn items are removed from your current outfit folder, change outfits a few times and verify everything is behaving as expected.
• Go to Advanced (top menu bar) → Debug settings → VerifyInitialWearables → Set this back to FALSE, it is no longer needed.
• Relog.
• If login is successfull, you are now fixed and will be fixed on all Viewers

• VerifyInitialWearables makes the viewer notice that the server says you're wearing something that's not in COF which makes the viewer purge everything in COF and then recreate from what you're wearing
• VerifyInitialWearables is not in V3, only viewers containing RLVa.
• This will not work if you have inventory corruption somewhere other then COF. Currently only LL can fix this for (premium) users by running the inventory repair scripts

If your avatar is persistently gray or a cloud, and the usual methods of fixing bakefail aren't working, you may have a specific kind of COF corruption: duplicated Current Outfit folders. (In most cases you will see yourself as gray and observers will see you as a cloud.)

You may not be able to see the duplicated folders; in some cases only LL technical support can see them.

To test for this, please do the following:

• Remove all animesh attachments as they will confuse the readings we are about to look at.
• Open Advanced menu (Ctrl-Alt-D) → Debug Settings.
• Find DebugAvatarAppearanceMessage.
• Set that to TRUE.
• Examine the text floating above your head.
• In the middle of the text, you will see “cof” followed by three numbers. Example: “cof: 76,345 req: 76,345 rcv: 76,345”
• These numbers should match each other.
• If they do not match each other, you have duplicate Current Outfit folders.
• Contact LL support and ask them to look at your inventory for duplicate Current Outfit folders. http://community.secondlife.com/t5/English-Knowledge-Base/How-to-contact-customer-support/ta-p/739385

The introduction of Server Side Appearance (SSA) has resulted in a significant reduction of problems concerned avatar bake fail (ie, skin or layered clothing failing to rez, your avatar remaining a cloud, etc). SSA completely changes how avatar textures are handled, and the new process is far less prone to errors introduced by connection or region problems.

Nonetheless, problems may occur and are largely due to network connection problems. This page addresses the known issues and offers solutions.

If you receive a message that the system has “Failed to find [name of any item] in the database” every time you try to wear or remove something, please see this page first Failed to find in database.

• In your inventory, find a different shape from the one you normally use, and wear it, replacing the one you have on. If that doesn't fix the issue, then do the same thing for your
  • system skin
  • system eyes
  • system hair base
  • If that doesn't work, read on.

• If you have RLV enabled, in Preferences → Firestorm → Extras (top option), disable it and relog, then try the above step again.

• Go to one of the following locations, and remain there while working through the rest of this page:
  • Hippo Hollow
  • Cyclops

• Your inventory needs to be fully loaded before you will bake. Click on the Recent tab of the Inventory window. Make sure that the inventory count doesn't say “Fetched” or “Fetching”; if it does, your inventory is still loading. Let it finish. If it isn't moving, try typing random characters into the inventory search box.
  Should your inventory not fully load, please refer to this page for help on getting it to load.
  Once you have done that, try the first bullet point again.

• Select a different outfit in your Outfits folder and select Replace Outfit.

• Make sure that all of the 4 required system parts are worn:
  • Method 1: In your Inventory window, Inventory tab, Current Outfit folder, make sure the four required system parts all show as worn: shape, skin, eyes, hair base. If not, right-click them and wear them.
  • Method 2: Open the Appearance window (Avatar menu → Appearance), go to the Wearing tab, scroll to the bottom, and make sure that the last four items listed are your shape, skin, hair and eyes. If one of those items is missing, find it in inventory and wear it.
  • If you are unable to wear all 4 items, create a new folder in your inventory with the 4 basic items, plus system clothing if you wish (no attachments). Then right click the folder and select Replace Outfit.

• If you are connected via cellphone, you will most likely see yourself and everyone grey. You need to have a decent internet connection. So if possible, switch to that, then see if you rez in normally.

• Reboot your router/modem.

• If none of the above helps, then continue reading.

If you have more than one monitor, and run Firestorm on any but the primary, try moving the Firestorm window to the primary monitor.

If this doesn't help, continue with the next section.

This also applies if you are a cloud.

The best way to fix this is not via the usual rebake (Ctrl-Alt-R), but instead by right clicking your avatar name tag and selecting Tex.Refresh:

• Context menu: right click → Texture refresh
• Pie menu: Right click → Appearance → Tex refresh.

This is generally the result of the viewer not loading or using all the bake data - which may be a sign of a connectivity problem. If it persists, try going to a different region, preferably a known low lag one like Hippo Hollow or Cyclops.

For more info, you can refer to this JIRA.

The first thing to try is a Tex.Refresh, as described above.

If this does not help, chances are very good that one of the textures on the (layered) clothing you' re wearing, is bad.

• Remove all worn layered clothing, tattoos and alphas, then Tex.Refresh as described above.
• If this results in a fully baked, naked avatar, start re-adding the clothing layers, one at a time. One will probably show entirely or partly grey. This will be the one with the corrupted texture(s), and needs replacing.
• If you are still grey, or partly grey with no layered clothing worn, try a different avatar skin, see if that rezzes in correctly. If so, then the problem is with the avatar skin.

For more info, see this LL JIRA.

This issue can also occur if you are using a cellphone connection to access SL. This is currently under investigation by LL. For more, refer to this forum thead.

This issue can also occur if you are having DNS problems. The DNS problems usually occur in such a way that the only symptom you will see will be grey avatar textures and the problem can be intermittant. The workaround for this is to change your DNS to Google Public DNS.

See Duplicate Current Outfit Folders Causing Bakefail for one specific problem.

If you find that a change of outfit can be seen by you, but not by others, then you most likely are affected by this issue: SUN-99. This seems to be the result of using a certain other third party viewer. Only LL can fix this issue; you will need to file a support ticket with them.

This window opens when you have selected a sound clip to upload into SL. There are two fields you can edit:

• Name: The name of the clip. This auto-populates with the name of the file you selected.
• Description: An optional description of the clip.

Once done, click Upload to upload the file into SL. Your account will be debited 10L by SL. If you change your mind, click the Cancel button.

Se details on sounds clips and the required format, see here.