Généralement les cartes et pilotes graphiques Nvidia focntionnenet très bien sur Second Life.

Ce problème s'est produit avec le pilote Nvidia 378.49, lorsque “Advanced Lighting Model” est désactivé, uniquement sur les viewers 64-bit.

Le bug a été corrigé à partir du pilote 378.66.

Pour les anglophones : voir this JIRA issue pour plus d'information.

EN COURS DE TRADUCTION - MERCI DE VOTRE PATIENCE

Recent Nvidia updates, including driver version 381.65, may prevent Firestorm from launching. The crash is reported to occur on the “Detecting Hardware” step.

To solve this,

1) Try disabling Shadowplay in your Nvidia settings.

2) If this does not work, roll back to the last driver that worked for you. Be sure to completely uninstall the recent driver before installing the older one.

See also this page.

If you have Nvidia Shadowplay installed, disable it. Google “how to disable nvidia shadowplay” for instructions.

One user reports that on a recent Nvidia Experience version, turning off Share in the Settings menu disables Shadowplay without having to go through Windows controls.

There is a known Nvidia driver crash that occurs for some users on El Capitan and Sierra. See Mac El Capitan Nvidia Driver Crash and Mac Sierra Issues.

This page describes all necessary steps to build the Firestorm viewer for Windows, using the updated build infrastructure introduced with Linden Lab's project Alex Ivy.

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

All installations are done with default settings (unless told explicitly) - if you change that, you're on your own!

• Install Windows 10 Pro 64bit using your own product key
• Alternatively: Install Windows 7 or 8.1 Pro 64bit

• Install Visual Studio 2013 Professional
• Note: If you don't own a copy of Visual Studio 2013 Professional, you might consider installing the Community version (requires creating a Microsoft account if you do not already have one ) (If the download link for 2013 on visualstudio.com leads to a dead page even after logging in and out and back in again, try Googling “Visual Studio 2013 Community update 5 download” for a direct link. MS has recently changed things with accounts and the free subscriptions.)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • Uncheck all the “Optional features to install:” - they are not required

• Download and install DirectX SDK (June 2010)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • At the Installation Options screen, set everything except the DirectX Headers and Libs to “This feature will not be installed”

• Download and install TortoiseHg 3.2.3 or newer (64bit)
  • Note: No option available to install as Administrator
  • Use default options (path, components etc.)
  • Add the following directory to your path:

    C:\Program Files\TortoiseHG

• Download and install at least CMake 3.8.0
  • Run the installer as Administrator (right click, “Run as administrator”)
  • At the “Install options” screen, select “Add CMake to the system PATH for all users”
  • For everything else, use the default options (path, etc.)
  • Make sure that the following directory was added to your path:

    C:\Program Files (x86)\CMake\bin

• Download and install Cygwin 64 (64bit)
  • Run the installer as Administrator (right click, “Run as administrator”)
  • Use default options (path, components etc.) *until* you get to the “Select Packages” screen
  • Add additional packages:
    • Devel/patch
  • Use default options for everything else
  • Make sure that the following directory was added to your path.:

    C:\Cygwin64\bin

• Download and install the most recent version of Python 2.7 (32bit)
  • Linden Lab advises to use the 32bit version as the VMP requires it. However, Firestorm currently doesn't use VMP, so the 64bit version might work (use at own risk!)
  • Note: No option available to install as Administrator
  • Use default options (path, components etc.) until you get to the “Customize Python” screen
  • Change “Add python.exe to Path” to “Will be installed on local hard drive”
  • Add the Python installation dir to the system path:

    C:\Python27

Confirm things are installed properly so far by opening a Cygwin terminal and enter:

cmake --version
hg --version
python --version

If they all report sensible values and not “Command not found” errors, then you are in good shape.

• Install Boostrip pip
  • Download (Save As) get-pip.py and copy to a temp folder
  • Open Windows Command Prompt
  • Switch to that temp folder and execute it:

    python get-pip.py

  • Pip will be installed
  • Add the following directory to your path:

    C:\Python27\Scripts

• Install Autobuild
  • Open Windows Command Prompt and enter:

    pip install hg+https://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild

  • Autobuild will be installed. Earlier versions of Autobuild could be made to work by just putting the source files into your path correctly; this is no longer true - Autobuild must be installed as described here.

• Set environment variable AUTOBUILD_VSVER to 120

• Check Autobuild version to be 1.1.7 or higher:

  autobuild --version

• If you plan to package the viewer and create an installer file, you must install the NSIS from the official website.
• Not required unless you need to build an actual viewer installer for distribution, or change the NSIS installer package logic itself

In order to make it easier to build collections of related packages (such as the viewer and all the library packages that it imports) with the same compilation options, Autobuild expects a file of variable definitions. This can be set using the environmenat variable AUTOBUILD_VARIABLES_FILE.

• Clone the build variables repository:

  hg clone https://hg.phoenixviewer.com/fs-build-variables <path-to-your-variables-file>

• Set the environment variable AUTOBUILD_VARIABLES_FILE to

  <path-to-your-variables-file>\variables

• Start the IDE
• Navigate to Tools> Options> Projects and Solutions> Build and Run and set maximum number of parallel projects builds to 1.

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, it is assumed that you created a folder c:\firestorm.

c:
cd \firestorm
hg clone https://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).

If you want to use FMOD Studio to play sounds within the viewer, you will have to download your own copy. FMOD Studio can be downloaded here (requires creating an account to access the download section).

c:
cd \firestorm
hg clone https://bitbucket.org/Ansariel/3p-fmodstudio

• After you have cloned the repository, copy the downloaded FMOD Studio installer file to C:\Firestorm
• If you downloaded a different version of FMOD Studio that is currently used in the viewer, you will have to modify the file build-cmd.sh in the root of the repository. Right at the top, you find the version number of FMOD Studio you want to package (one short version without separator and one long version). Change these values to the version you downloaded:

FMOD_VERSION="11005"
FMOD_VERSION_PRETTY="1.10.05"

Continue on the Windows command line:

c:
cd \firestorm\3p-fmodstudio
autobuild build --all
autobuild package

While running the Autobuild build command, Windows might ask if you want to allow making changes to the computer. This is because of the FMOD Studio installer being executed. Allow these changes to be made.

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

wrote C:\firestorm\3p-fmodstudio\fmodstudio-{version#}-windows-{build_id}.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

where {version#} is the version of FMOD Studio (like 1.10.02) and {build_id} is an internal build id of the package.

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

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

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

For example:

autobuild installables edit fmodstudio platform=windows hash=c3f696412ef74f1559c6d023efe3a087 url=file:///C:\firestorm\3p-fmodstudio\fmodstudio-1.10.02-windows-180191431.tar.bz2

Open the Windows command prompt.

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

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then enter:

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

This will configure Firestorm to be built with all defaults and without third party libraries.

autobuild configure -v -c ReleaseFS_open

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.

• -A <architecture> sets the target architecture, that is if you want to build a 32bit or 64bit viewer (32bit is default if omitted).
• –fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps in FMOD Studio using Autobuild for this to work.
• –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.
• –chan <channel name> lets you define a custom channel name for the viewer
• -LL_TESTS:BOOL=<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.

Examples:

• To build a 32bit viewer with FMOD Studio and to create an installer package, run this command in the Windows command window:

  autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

• To build a 64bit viewer without FMOD Studio and without installer package, run this command:

  autobuild configure -A 64 -c ReleaseFS_open -- --chan MyViewer -DLL_TESTS:BOOL=FALSE

There are two ways to build the viewer: Via Windows command line or from within Visual Studio.

If you are building with FMOD Studio and have followed the previous FMOD Studio 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 run the Autobuild build command. Make sure you include the same architecture parameter you used while configuring the viewer:

autobuild build -A 64 -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.

Inside the Firestorm source folder, you will find a folder named build-vc120-<architecture>, with <architecture> either being 32 or 64, depending on what you chose during the configuration step. Inside the folder is the Visual Studio solution file for Firestorm, called Firestorm.sln.

• Double-click Firestorm.sln to open the Firestorm solution in Visual Studio.
• From the menu, choose Build → Build Solution
• Wait until the build is finished

Older versions of the viewer before the merge of Linden Lab's project Alex Ivy use Autobuild 1.0 that is incompatible with the build process as it is now. By default it is not possible to install two different versions of Autobuild on the same computer at the same time. Making use of virtualenv will overcome this problem, allowing simultaneous installations of Autobuild 1.0 and Autobuild 1.1 in two distinct “virtual” Python environments.

Install virtualenv by opening a Windows command prompt and enter:

pip install virtualenv

This requires the Boostrip pip already installed. After virtualenv has been installed, you can create virtual Python environments using the command

virtualenv <virtual-environment-name>

This will create the directory <virtual-environment-name> within the Python installation folder and add some required folders and files. Among these files is a batch file called activate.bat in the folder Scripts. To switch to the newly created virtual environment execute the activate.bat batch file. After switching to the virtual environment, your command prompt will be prepended by the name of the virtual environment.

In this example we will create a virtual environment called “Autobuild11”:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat

Your command prompt should look like this now:

(Autobuild11) C:\

After you switched to a particular virtual environment, you can now install as described in Set up Autobuild and Python.

Complete example:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat
pip install hg+https://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild

Configuring and building the viewer from the Windows command line is basically identical as described in Building from the Windows command line with the difference that you now have to call the activate script first:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE
autobuild build -A 64 -c ReleaseFS_open --no-configure

If you plan to build the viewer from within Visual Studio, you will have to configure the viewer the same way as if you were to build from the Windows command line:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

To be able to build from Visual Studio, you will have to set a Windows environment variable called VIRTUAL_ENV pointing at the virtual Python environment to use, in our example “C:\Python27\Autobuild11”. Now open the Firestorm Visual Studio solution to start Visual Studio and build the viewer.

When trying to execute the Autobuild build command, you might encounter an error similar to

../build.cmd.sh line 200: SystemRootsystem32: unbound variable

This error is caused by the order of the items in the Windows “path” environment variable. Autobuild exports all paths set in the “path” environment variable into Cygpath names and variables. Since these Windows “paths” can also contain variables like %SystemRoot% and they can also depend on each other, it is important to keep the dependency order intact. Example:

%SystemRoot%
%SystemRoot%\system32
%SystemRoot%\System32\Wbem

The following screenshot shows the correctly ordered paths containing variables and depending on each other.

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.

• First and very important: TP to a known low lag region to do any of the things listed below. Once there, reduce draw distance significantly, to reduce the load on your network connection. Stay there while working through this page. These locations are recommended:
  • Hippo Hollow
  • Cyclops
    
    Do not stay at your current location; it may be the source of your problem.

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

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

• If a system folder is missing, you may have opted to hide empty system folders: Preferences → User Interface → Interface Windows → Hide empty system folders from inventory.

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

• Try clearing your inventory cache.
  • Method 1: Open Preferences -> Network & Files -> Directories, then click the Clear Inventory Cache button, then relog to Hippo Hollow or whichever low-lag location you chose.
  • Method 2: If Method 1 did not work, clear the inventory cache manually:
    • Open Preferences -> Network & Files -> Directories
    • Click the Open button to the right of cache location. This should open a file picker window.
    • Locate the .gz file with YOUR avatar key. Your key can be found in your profile, under your name.
    • ESSENTIAL: Log out of Firestorm.
    • Delete the .gz file located above.
    • Log back in to Hippo Hollow.
    • Allow your inventory to fetch.
  • Note: If clearing inventory cache manually 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, unless you didn't delete the correct file the first time (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 to make sure that you aren't being misled by cached inventory on SL viewer, wipe inventory cache there as well, and then see if your inventory fully fetches. If it does, then the problem is probably either loading or caching in Firestorm, and you can follow the set of suggestions below under “Method 2: Inventory Copy from SL Viewer.”
  If the missing items do not show up on SL viewer either, then file a support ticket with SL for assistance, making sure to specify that you have the problem with SL viewer.

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.

Note: You must be LOGGED OUT of both viewers before doing the next step.

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.

Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example, go to the top menu, Advanced → Debug Settings (press Ctrl-Alt-D to enable Advanced, if it isn't):

• RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
• TextureLoadFullRes should never be enabled (in other words, it should be set to FALSE).

If you are advised to raise LOD above 4, please disregard that advice.

Similarly, there is a notecard going round which suggests settings to prevent graphics crashes. Sadly, those settings can often result in perfectly ordinary content refusing to render. So if you have changed debug settings per such a notecard, revert them.

For both the cases above, should you not remember what settings you changed, then proceed as follows:

1. Back up your settings as explained here.
2. Then wipe settings by following the instructions on this page.
3. Log back in and see if this fixes your problem. If it does, you can try a restore and see if the issue returns.
4. If the problem does return, wipe settings again and set them from scratch.

If you are getting the error in the title, then please refer to this page, this page or this page for those using Intel graphics for possible solutions.

With thanks to Skua Sarrasine for having found the first of these.

Symptom:“This is a bug thats only experienced with Firestorm running. Basically, at seemingly random, but very infrequent times, my dual screens will bug out, producing two displays of solid colour, randomly. Sometimes Windows will return saying it recovered from an error code 7 or 3.”

Some research turned up this for error code 7; it suggests setting physX to CPU. And that seems to have solved the issue.

Note also the (apparent) interaction with Chrome.

This is a known issue with Windows 7, 8.1, and 10 with a 64-bit operating system; it affects other programs in addition to Second Life viewers.

Please try the following - but NOT while logged in.

• Go to the Start button
• Type services.msc and then press enter.
• Wait until the services window pops up.
• You may have to expand the window a bit to see the services.
• Look for DesktopWindowManager.
  • If it is running, right click it and select Stop. Wait until it stops.
  • You will probably see your desktop transparency window borders go flat. No worries.
• Right click again and select Properties.
  • In the Startup type, select Manual. Click OK.

• Open the Task Manager, by one of the following methods…
  1. Right click the task bar and choose Task Manager.
  2. Click the Start button and type Task Manager, then click on the result.
  3. Press Ctrl+Alt+Del and choose Task Manager from the list.
  4. Press Ctrl+Shift+Esc.
• Click More Details link at the bottom if needed
• Look at the several column headers, they will show a percentage of use. Memory or Disk may show a high percentage when Firestorm is not responding.
• Click on one of the high-percentage column headers to sort the processes. The top one is likely the cause. If it's your antivirus, make sure you have whitelisted Firestorm and its cache (refer to this page for whitelisting guidance).

If you find the Firestorm seems to freeze up every so often, then try these things, one at a time, testing after each one:

• Viewer freezes while “Loading world…“– If you have Intel HD 620 or Intel HD 630, and Windows 10 – This is an Intel driver issue. The fix is to roll back to driver 24.20.100.6025. Download Legacy Intel® Graphics Driver for Windows® 10 Version: 24.20.100.6025 (Ref. BUG-225655.)
• If you have chat saving enabled, and have a large number of chat transcript files, these could be causing the freezes. (Ref. FIRE-11322.) Try moving your chat transcripts elsewhere and see if the freezing stops.
  You can find your chat transcripts by going to Preferences→ Network & Files -> Directories→ Conversation logs and transcripts location; click the Open button.
• Set Preferences → Network & Files → Directories → Cache Size to maximum (9984MB or the maximum space available, whichever is less)
• Ensure that your antivirus software is not scanning the viewer cache folder. See Whitelisting the Viewer in Anti Virus Software for more information.
• If you have ever enabled “Full Res Textures”, disable this setting. Top menu bar, Develop→ Rendering → Full Res Textures (dangerous). Ensure that this is NOT checked. (Ctrl-Alt-Q to enable Develop, if it isn't.)
• Advanced → Debug Settings → Set FastCacheFetchEnabled to FALSE - then relog.
  Ctrl-Alt-D to enable Advanced, if it isn't.
• Preferences → Graphics → Hardware Settings → Viewer Texture Memory Buffer - raise this as high as it will go. Then relog. (64-bit version only)
• Mac with Bitdefender: Refer to this SL bug report for a possible explanation: mac freezes if tabbing away after teleport since macOS Mojave 10.14.3
• Tip from a user: Windows users: If you're running CrashPlan, open the “Advanced” section of “Backup” settings and uncheck “Back up open files.”
• Tip from a user: Windows users: If you have “Magic Control Technology Display Utility” (MCTDUtil.exe), disable it. See https://www.file.net/process/mctdutil.exe.html.
• Tip from a user: Linux users: Turn off compositing, see if it helps.

For additional suggestions, see the page on Severe Lag.

So you recently saved an outfit, but when you look in that outfit's folder, it's empty. This can happen now and then, and it's caused either by something you're wearing, or something you aren't wearing. That does tend to cover any and all possibilities, but it will be made clear in the solution below.

NOTE: If the outfit had links in it in the past (in other words, you successfully created it originally), but is suddenly empty now, refer to the Missing Inventory help page.

First, try a simple relog and check the outfit folder again. If the folder is still empty, proceed with the following steps.

If you use RLVa there is a chance that it has restrictions that are interfering with the wearing or removing of items that can cause this empty outfit problem, so it is recommended that, temporarily, RLVa be disabled.

• Open Preferences → Firestorm → Extras
• At the top is Allow Remote Scripted Viewer Controls. If this is enabled (checked), uncheck it.
• If you had to uncheck this setting, click OK at the bottom and relog; otherwise, close Preferences.

In case the problem is caused by something you're wearing, it is recommended that you detach all objects and wear “default” body parts. The easiest and quickest way to accomplish this is to go to the Avatar menu > Avatar Health submenu and click Reset Default (male or female).

This may take a moment or two, depending on the availability of the asset server, your connection quality to the server, and your viewer performance. If it takes a long time, or appears to never happen, try relogging. If you had to relog for the RLV step above, try going to a different region, such as Hippo Hollow.

If your avatar still doesn't change, there may be other issues, and the Bake Fail page may help resolve them.

There are two folders, at a minimum, that are involved in your avatar's appearance. The first is the Current Outfit folder. This folder contains links to all the items that you are wearing. If it contains a broken link, or a link not worn, this can cause an outfit save to fail. So, open that folder and delete any broken links, or links that are not shown as worn.

The second folder, in this case, is the outfit's folder itself. Being empty, you have to delete that folder now.

A third folder may be involved if you are having a particular kind of bake failure: the Lost & Found folder. Normally, Lost & Found contains only objects, linksets and coalesced object sets. If you find any wearables in that folder, delete them. If they are worn, take them off first, then delete. If you cannot detach these wearables, relog, or try going to a different region, such as Hippo Hollow.

At this point, you should be ready to create and save an outfit. For an extra measure of sanity, it is recommended that you relog now. But you don't have to; you can attempt step 5 without relogging. However, if it fails a relog may help.

To ensure that you only wear the items you want in your outfit, manually select and wear each item. Don't try wearing an outfit that you want to modify, as it may contain something causing the problem. Instead, wear one item at a time from that outfit; anything that may cause a problem may then self-identify.

Once you are wearing all you want for that outfit, try to save it again, then check the outfit's folder for content.

If you have identified an item that causes a problem, that item may be corrupt in the SL database. You can try wearing an different copy of that item, if you have a backup of it, or notify the creator of the problem.

SLURL Proxy est une application qui gèrera les SLURLs sur votre système Windows. Cliquer sur une slurl sur le web ouvrira SLURL Proxy, ce qui transfèrera la slurl au viewer que vous avez choisi. SLURL Proxy vous donne également l'option de paramétrer directement un viewer de votre choix, sans utiliser la fonction proxy.

Les différents viewers Second Life que vous avez peut-être déjà installés réécrivent par-dessus vos paramètres de registre, et modifient la façon dont les slurls sont gérées sur votre système, ceci sans vous le demander.

SLURL Proxy fournit une manière très facile de corriger ceci, sans devoir toucher à votre registre.

Vous pouvez télécharger SLURL Proxy, et l'ouvrir à l'emplacement de votre choix.

Double cliquez SLURL Proxy.exe pour le démarrer.

Au démarrage, SLURL Proxy vérifiera s'il est le gestionnaire de slurl par défaut. Si ce n'est pas le cas, il vous en informera, et vous demandera si vous souhaitez utiliser SLURL Proxy par défaut.

Lorsque vous avez défini SLURL Proxy par défaut, (ou même avant ça) vous pouvez simplement faire glisser un ou plusieurs raccourcis de viewers dans la fenêtre de l'application, et ils seront ensuite listés avec le nom du viewer et son icône. Ensuite, vous pouvez fermer SLURL Proxy et il est prêt à l'utilisation.

SLURL Proxy vous permet d'ajouter un ou plusieurs viewers, l'un d'entre eux devant toujours être le viewer à utiliser par défaut.

Le viewer par défaut est celui dont la case à cocher est active. Si vous souhaitez changer de viewer par défaut, cliquez simplement le viewer de votre choix dans la liste.

C'est tout.

Firefox ou Chrome demanderont peut-être quelle application ils doivent utiliser lorsque vous cliquez une slurl sur le web; si c'est le cas, vous verrez s'afficher un choix d'applications associées, parmi lesquelles l'application que vous avez définie par défaut (par exemple SLURL Proxy ou un Viewer.exe, qui sera en surbrillance.

Internet Explorer devrait simplement afficher un dialogue vous informant que l'application est en train d'essayer de gérer la slurl cliquée, et vous demandant si vous l'autorisez.

Si vous souhaitez définir un viewer comme gestionnaire de slurl par défaut à la place de SLURL Proxy, cliquez simplement l'option dans le menu, et faites glisser le raccourci de votre viewer favori sur la fenêtre.

Nécessite .NET 3.5 et ne fonctionne que sur Windows

Le fichier que vous téléchargez est un fichier d'archive compressée au format ZIP.

• Démarrez SLURL Proxy
• Dansel dialogue demandant si SLURL Proxy devrait êtrele gestionnaire de slurl par défaut, cliquez NO
• Dans le menu en haut, cliquez “Définir un autre gestionnaire de slurl”
• Faites gisser le reccourci Firestorm sur la fenêtre de SLURL Proxy
• C'est tout, vous pouvez fermer SLURL Proxy.

NB : Si le viewer est déjàen train de s'exécuter, toutes les slurls s'ouvriront dans ce viewer, malgré vos paramètres.

The pages below have been updated to reflect some of the changes since Firestorm 6.0.2. Please do not bookmark them, as they will disappear once 6.2.0 goes to public release.

Catznip RLVa 2.2 Release Notes

Second Life Release Viewer version 6.1.0.524670
Release Notes for v6.1.0 (524670) - Second Life Viewer Released on February 26, 2019. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/6.1.0.524670

BugSplat viewer

Update changes This viewer introduces a revised updater, replacing the current Viewer Manager Process (VMP). Instead of running the VMP before every viewer session, we now run the updater as a child process of the viewer. Viewer notifications are used to alert the user to a pending update.

This viewer starts more quickly than with the VMP. It displays only one Taskbar or Dock viewer icon. Pinning that icon should behave exactly as expected, going forward.

Pinned icons for the Viewer Launcher and VMP-driven viewer may need to be deleted and recreated.

We still run the updater before _first_ launching a newly-installed Windows viewer, to address the potential problem of installing a 64-bit viewer on a Windows system that does not support it. Similarly, if you install a 32-bit viewer on a Windows system that can support the 64-bit viewer, it retrieves the 64-bit viewer instead.

Bugsplat If this viewer crashes, the crash report is sent to BugSplat rather than to Linden's internal crash reporting system.

(Third party developers: the existing Breakpad crash-reporting code is still present in the code base. BugSplat integration is enabled by a CMake variable.))

FMOD Studio 1.10.11 (updated Windows, Linux)

KDU v7.10.6 (Windows, Mac, Linux)

Voice Server Version: Vivox Version 4.9.0002.30313 (Mac and Windows)
Voice Opensim 4.6.0017.22050 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

Chromium Embedded Framework (CEF) Dullahan:

• Dullahan: 1.1.1080
• CEF: 3.3325.1750.gaabe4c4.513446
• Chrome: 65.0.3325.146
• Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

• FIRE-23692 - [BUGSPLAT] Viewer crashes in Vivox code after teleport

• FIRE-23012 - Windows 10's UTF8 beta breaks URL parsing
• FIRE-23401 - Firestorm locks up Win 7 on login - Malwarebytes
• FIRE-23641 - Show parcel name in world map feature fails if the parcel has a null name
• FIRE-23663 - crash on using world map, xui file floater_world_map.xml might be corrupt
• FIRE-23665 - starlightskin original teal - colors of some UI elements are from original orange
• FIRE-23667 - missing 3p package

• FIRE-23603 - [LINUX] autobuild line 3666
• FIRE-23657 - [OPENSIM] ViewerAsset on OpenSim

• FIRE-23592 - Update Japanese translation

If you haven't logged into the Aditi Grid recently, you will likely need to contact LL Support to gain access as well as have your inventory synced. Please review this page carefully http://wiki.secondlife.com/wiki/Aditi. Also ensure you have this viewer setting enabled in Preferences - Advanced - Allow login to other grids.

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*

Symptom: 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 note: This is not a viewer issue, but we have written this page to help users with a common problem.

We have identified three causes of this.

• Open your Inventory and look in your Current Outfit folder (must be the “Current Outfit” folder and not the “Worn” tab; this is important).
• Look for any broken links in the folder, particularly for the item with the name in the “Failed” warning you're receiving.
• Delete any and all broken links in the folder.

Explanation: This error happens when the broken link gets “stuck” in the folder for some reason. When the viewer tries to update the Current Outfit folder – which happens whenever you wear or remove a body part or clothing item – it detects the link in there and thinks you want to be wearing that item. So it tries to put it on you, but it can't because the link is broken, and the “Failed” message pops up.

If deleting broken links doesn't help, or if there were none, then make a temporary folder in your inventory. In it, put a copy of a system skin, system shape, system hair base, and system eyes - nothing else - and not the ones you are already wearing. Then right-click the folder name, replace outfit (not add or wear). Then check Current Outfit folder (not Worn tab) and delete any links showing as not worn. Then relog. (Please follow these steps exactly as given - it matters.)

• If the error message has gone away, you can try putting on your usual body parts and clothing.
• If the error message has NOT gone away, proceed to the next section.

• Check in Lost & Found folder and delete any system layers named “new”–“New skin,” “New eyes,” “New pants,” or similar.
• If you are wearing the item, remove it (if a clothing layer) or change to a different body part, whichever applies, and try deleting the item again.

Explanation: If a worn system clothing layer or system body part is not found at login, that layer/body part will be replaced with a default asset that is created and placed in Lost & Found. You will continue to get the error message until the “new” item is deleted from Lost & Found.

• If the error message has gone away, you can try putting on your usual body parts and clothing.
• If the error message has NOT gone away, proceed to the next section.

(Windows only)

The NetBooster tool is a feature in System Mechanic Pro. This NetBooster feature does not always execute, so there is an element of randomness to reproducing these SL connectivity problems when System Mechanic Pro is installed on the system.

• Uninstalling System Mechanic Pro does not appear to revert the changes made by the NetBooster feature.
• The solution is to go into the NetBooster tool and selected “Restore original settings”.
• This restores Windows default settings and everything in SL works again.

For more information and additional symptoms, see here.

If none of these steps help, then please test using the official LL viewer, which can be downloaded here. If you have the same problem there, file a support ticket with LL.

A short explanation: “Restore to Last Position” restores an object to the previously rezzed coordinates on a region *via* position 0, 0, 0 on the region. It doesn't use the region name or global coordinates, so this is lucky.

You must have rez rights at 0, 0, 0 on a region to use this command. If you do not have rez rights at that location, Restore to Last Position will fail; ref. SVC-7907.

To get rez rights at that location, contact your landlord or the sim owner to request rights.

The items must also be copiable.

If you do not have rez rights at 0, 0, 0 on your home region, and need to restore, for example, part of your house to its exact previous position, follow the steps below for a work-around to this.

• Take note of the approximate position the object should occupy.
• Go to a sandbox with rez rights given on the entire region. For example:
  here or here.
• Go to the approximate location your object will appear, and ground sit (Ctrl+Alt+S) or fly, if the position is in the sky.
• Make sure no innocent bystanders will be crushed under your object, and right-click, “Restore to Last Position”.
• Your object will first rez at position 0, 0, 0 then immediately move to its previously rezzed coordinates. After it appears, right-click, “Edit”.
• Go to the Object tab of the Build Tools floater, and click the C next to Position.
• Take the object into inventory (or delete it, since you should still have a copy in inventory).
• Teleport home, then rez the object by dragging it to the ground.
• Right-click, “Edit,” and on the Object tab of Build Tools, click the P button next to position. The object will be placed exactly where it had been.

Naturally, this becomes much more complex with coalesced objects, as you have to rez them out then do the above steps one object at a time.

The Covenant Tab shows you the basic rules set by the owner(s) of the Region. These rules are not set by Linden Labs and are enforced by the Region owners. It also displays basic information about the region and restrictions on transfer of land.

• Estate: The name of the estate. (For an overview of what regions and estates are, and the types of region, please refer to this SL Wiki page.)

• Owner: The Resident who “owns” the estate.

• Covenant: A Text Box displaying the Estate covenant. The covenant may be changed by region/estate owners or managers in the Region Details window, Covenant tab.

• Last Modified: Date and time the covenant was last edited (shown on right)

• Region: Each region has a unique name; names can only be changed via ticket on the Second Life website.

• Type: Regions may be Mainland or Estate, and Full, Homestead, or Openspace. Mainland regions may be owned in units of less than a full region, while Estate regions are only sold in full region units. Limits on number of objects and avatars are set according to type. Full regions may have 22,500 objects (mainland), 22,000 (private estate) and 40-100 avatars, Homesteads may have 5,000 objects and 20 avatars, and openspaces may have 1,000 objects and 20 avatars.

• Rating: The maturity rating of the region determines the kind of activity and content is allowed in the region. It is one of General, Moderate, or Adult, and is set by the estate owner, or Linden Lab for mainland regions.

• Resale: Shows whether the parcel tenant may resell land to other residents.

• Subdivide: Shows whether the parcel tenant can subdivide land into smaller parcels. (See Terraforming, which includes information on how to join and subdivide parcels.)

The General Tab shows basic information about the current parcel. It can be accessed by first clicking the parcel's name in the top-bar of the client. The general tab also allows parcel owners to customize various essential aspects of their land.

• Name: The name of the parcel which will show on the top of the viewer when you are on the parcel, and in search if the parcel is set to show in search.
• Description: An additional description of the parcel which is visible in this window and in search results if the parcel is set to show in search. This also can be used to place keywords about the land to increase search results.
• Type: The type of region the parcel is located on (types being: Mainland or Estate/Full Region, Homestead, or Openspace).
• Rating: The maturity rating of the region, which can be: General, Moderate, or Adult. Depending on the rating, certain ages or those that are not age verified will not be permitted to enter.
• Owner: Indicates who “owns” the parcel, usually a specific resident, or group. Normal users do not actually have ownership rights like in real life. They have control over the parcel as long as they pay monthly maintenance fees directly or indirectly to Linden Lab (usually a premium and tier), who actually own the servers the region is hosted on. In this sense it is more like a lease in real life. The info (the “I” icon”) button will open the 'Profile' floating window for the listed owner.
• Group: In some cases it may become necessary to have a parcel set to a group (for instance, to grant access to a club based on who is in the VIP group). The Set button will open the Groups tab of the Communicate or Contacts window in order to set or change the group assignment.
• Allow Deed to Group: Allows the landowner to sell the parcel to the assigned group. The owners of the group become the new owners of the land. The Deed button opens the 'Deed to Group' window in order to transfer ownership. (See Group Land Ownership.)
• Owner Makes Contribution With Deed: When transferring ownership to a group, this check box also assigns land area from the owner's land allowance to the group at the same time. (See Tier for more information).
• For Sale: This shows for sale or not for sale status. If for sale, it shows price and whether for sale to anyone, or a specific person. If you own the land, buttons to set for sale, not for sale, or abandon the land will appear.
• Claimed: The date and time the current owner became the owner of the parcel.
• Area: The horizontal area of the parcel. Sloped land is measured in the XY horizontal plane, not along the slope. Land is divisible into units of 4×4 meters in size, so the minimum parcel area is 16 sq.m., and can be any multiple of 16 up to the full area of a region (256x256m or 65,536 sq.m.). A single parcel must be entirely within the boundaries of one region, but may consist of discontinuous pieces.
• Traffic: The number of avatar-minutes present on the parcel over the last measurement interval. Thus one avatar present for one hour = 60 traffic. The normal measurement interval is over the previous 24 hours, and is updated 2 times a day. (See Land Traffic For more information.)

There are buttons at the bottom of the window:

• Script Info: Opens the Script Information window giving details about script usage on the region and your avatar.
• Buy Land: If the parcel is for sale, this will open the Buy Land window, giving details so you can decide whether you wish to purchase it.
• Buy Pass: If the parcel requires paid access, you can click this to purchase an access pass.
• Abandon Land: If you own or rent the parcel, you can click this to return it to Linden control. You receive no payment for this.
• Buy for Group: Similar to Buy (above) except that you are purchasing the land for a specific group. See this SL Wiki page for more information.

The General Tab shows basic information about the current parcel. It can be accessed by first clicking the parcel's name in the top-bar of the client. The general tab also allows parcel owners to customize various essential aspects of their land.

• Name: The name of the parcel which will show on the top of the viewer when you are on the parcel, and in search if the parcel is set to show in search.
• Description: An additional description of the parcel which is visible in this window and in search results if the parcel is set to show in search. This also can be used to place keywords about the land to increase search results.
• Type: The type of region the parcel is located on (types being: Mainland or Estate/Full Region, Homestead, or Openspace).
• Rating: The maturity rating of the region, which can be: General, Moderate, or Adult. Depending on the rating, certain ages or those that are not age verified will not be permitted to enter.
• Owner: Indicates who “owns” the parcel, usually a specific resident, or group. Normal users do not actually have ownership rights like in real life. They have control over the parcel as long as they pay monthly maintenance fees directly or indirectly to Linden Lab (usually a premium and tier), who actually own the servers the region is hosted on. In this sense it is more like a lease in real life. The info (the “I” icon”) button will open the 'Profile' floating window for the listed owner.
• Group: In some cases it may become necessary to have a parcel set to a group (for instance, to grant access to a club based on who is in the VIP group). The Set button will open the Groups tab of the Communicate or Contacts window in order to set or change the group assignment.
• Allow Deed to Group: Allows the landowner to sell the parcel to the assigned group. The owners of the group become the new owners of the land. The Deed button opens the 'Deed to Group' window in order to transfer ownership. (See Group Land Ownership.)
• Owner Makes Contribution With Deed: When transferring ownership to a group, this check box also assigns land area from the owner's land allowance to the group at the same time. (See Tier for more information).
• For Sale: This shows for sale or not for sale status. If for sale, it shows price and whether for sale to anyone, or a specific person. If you own the land, buttons to set for sale, not for sale, or abandon the land will appear.
• Claimed: The date and time the current owner became the owner of the parcel.
• Area: The horizontal area of the parcel. Sloped land is measured in the XY horizontal plane, not along the slope. Land is divisible into units of 4×4 meters in size, so the minimum parcel area is 16 sq.m., and can be any multiple of 16 up to the full area of a region (256x256m or 65,536 sq.m.). A single parcel must be entirely within the boundaries of one region, but may consist of discontinuous pieces.
• Traffic: The number of avatar-minutes present on the parcel over the last measurement interval. Thus one avatar present for one hour = 60 traffic. The normal measurement interval is over the previous 24 hours, and is updated 2 times a day. (See Land Traffic For more information.)

There are buttons at the bottom of the window:

• Script Info: Opens the Script Information window giving details about script usage on the region and your avatar.
• Buy Land: If the parcel is for sale, this will open the Buy Land window, giving details so you can decide whether you wish to purchase it.
• Buy Pass: If the parcel requires paid access, you can click this to purchase an access pass.
• Abandon Land: If you own or rent the parcel, you can click this to return it to Linden control. You receive no payment for this.
• Buy for Group: Similar to Buy (above) except that you are purchasing the land for a specific group. See this SL Wiki page for more information.

The General Tab shows basic information about the current parcel. It can be accessed by first clicking the parcel's name in the top-bar of the client. The general tab also allows parcel owners to customize various essential aspects of their land.

• Name: The name of the parcel which will show on the top of the viewer when you are on the parcel, and in search if the parcel is set to show in search.
• Description: An additional description of the parcel which is visible in this window and in search results if the parcel is set to show in search. This also can be used to place keywords about the land to increase search results.
• Type: The type of region the parcel is located on (types being: Mainland or Estate/Full Region, Homestead, or Openspace).
• Rating: The maturity rating of the region, which can be: General, Moderate, or Adult. Depending on the rating, certain ages or those that are not age verified will not be permitted to enter.
• Owner: Indicates who “owns” the parcel, usually a specific resident, or group. Normal users do not actually have ownership rights like in real life. They have control over the parcel as long as they pay monthly maintenance fees directly or indirectly to Linden Lab (usually a premium and tier), who actually own the servers the region is hosted on. In this sense it is more like a lease in real life. The info (the “I” icon”) button will open the 'Profile' floating window for the listed owner.
• Group: In some cases it may become necessary to have a parcel set to a group (for instance, to grant access to a club based on who is in the VIP group). The Set button will open the Groups tab of the Communicate or Contacts window in order to set or change the group assignment.
• Allow Deed to Group: Allows the landowner to sell the parcel to the assigned group. The owners of the group become the new owners of the land. The Deed button opens the 'Deed to Group' window in order to transfer ownership. (See Group Land Ownership.)
• Owner Makes Contribution With Deed: When transferring ownership to a group, this check box also assigns land area from the owner's land allowance to the group at the same time. (See Tier for more information).
• For Sale: This shows for sale or not for sale status. If for sale, it shows price and whether for sale to anyone, or a specific person. If you own the land, buttons to set for sale, not for sale, or abandon the land will appear.
• Claimed: The date and time the current owner became the owner of the parcel.
• Area: The horizontal area of the parcel. Sloped land is measured in the XY horizontal plane, not along the slope. Land is divisible into units of 4×4 meters in size, so the minimum parcel area is 16 sq.m., and can be any multiple of 16 up to the full area of a region (256x256m or 65,536 sq.m.). A single parcel must be entirely within the boundaries of one region, but may consist of discontinuous pieces.
• Traffic: The number of avatar-minutes present on the parcel over the last measurement interval. Thus one avatar present for one hour = 60 traffic. The normal measurement interval is over the previous 24 hours, and is updated 2 times a day. (See Land Traffic For more information.)

There are buttons at the bottom of the window:

• Script Info: Opens the Script Information window giving details about script usage on the region and your avatar.
• Buy Land: If the parcel is for sale, this will open the Buy Land window, giving details so you can decide whether you wish to purchase it.
• Buy Pass: If the parcel requires paid access, you can click this to purchase an access pass.
• Abandon Land: If you own or rent the parcel, you can click this to return it to Linden control. You receive no payment for this.
• Buy for Group: Similar to Buy (above) except that you are purchasing the land for a specific group. See this SL Wiki page for more information.

Select Environment

• Use Region Settings
• Use Inventory
• Customize

Day Settings

• Day Length (hours)
• Day Offset (hours)
• Apparent Time of Day

Sky Altitudes

• Sky 4 3000m
• Sky 3 2000m
• Sky 2 1000m
• Ground
• Water

The Firestorm inventory window is accessed by clicking the inventory icon on the bottom button bar.

This will open the inventory window, which is initially docked, but as with all other such windows, may be undocked. A typical inventory window looks like the one below.

These are special Firestorm Viewer folders which are “protected” by default to prevent inadvertent mishaps.

For more information, see Animation Overrider

For more information, see Firestorm LSL Bridge

Restrained Love. For basic setup, see RLVa Quick Setup

The Wearable Favorites window allows you to list frequently used items, HUDs as an example, in an easily accessible location so that you can quickly attach and detach them as needed. See Wearable Favorites

• Help: Click the question mark to get help - this page.
• Minimize: The horizontal line will minimize the window on your screen.
• Close: To the right of the redock arrow is an X; clicking this will close the inventory window. To reopen, click the inventory button again, as described above.

• Filter: If you wish to search for items with specific names, type part of the name here. Partial matches work; for example, if you type in hair it will match chair as well as hair. The inventory folders will open and all matching items will be shown, but not others. To remove the filter, click the X that appears at the end of that edit box.

• Collapse: Clicking this will close all open inventory folders.
• Expand: To open all inventory folders, click this button.
• Filter Types Dropdown: You can narrow your inventory search by a single type of content with the dropdown menu. For more detailed filtering, click Custom at the bottom of this menu.

There are three views available in the inventory window; you can toggle between them by clicking the tabs described below:

• INVENTORY: This tab displays your entire inventory in the window.
• RECENT: Clicking this tab will reduce the inventory to showing only recent items. By default, this means all items acquired since last login. This default can be changed - see below.
• WORN: This tab shows only those items in your inventory which are currently worn.

Below these three tabs is your inventory proper. Inventory is organized into a hierarchical tree. By default, the main inventory consists of two folders, which you cannot rename: Inventory and Library. Within Inventory are more folders. Some of these are system folders, meaning they have default and standard uses and cannot be removed or renamed or moved; all other folders here can be manipulated at will. For the most part, this main folder will contain items you accumulate in SL, things you purchase, or make.

The Library folder, on the other hand, is supplied by SL. It contains all manner of things which might be of use. You are free to use items in this folder as you wish, but you may not delete or otherwise manipulate the contents.

If a folder icon has a small arrow to the left, then it contains items; click that arrow to expand the folder. Folders may contain single items or other folders, or a mix of both. Items may be objects, textures, animations, and so on.

If you click on any folder, to the left of the name you will see the number of elements in the folder, that is, actual items, and subfolders. Referencing the image above, the Objects folder shown contains 28 items, and 6 subfolders.

Note that the total displayed (6616 in the image) includes items and folders.

Below the inventory view are more icons:

• Gear: Clicking this icon pops open a menu, shown to the right. The entries in the menu are as follows:
  • New Inventory Window: Open a new inventory window. Note that if you have a lot of items this may take a moment to open.
  • Sort by Name/Most Recent: Sets how you wish folders and items to be sorted in the inventory display.
  • Sort Folders Always by Name: This forces folders to sort alphabetically, regardless of the setting above.
  • Sort System Folders to Top: This places the system folders at the top of the list of folders, with all the others below. System folders include: Animations, Body Parts, Calling Cards, and so on, down to Trash.
  • Search By: Allows you to search inventory according to different fields:
    • Name
    • Creator
    • Description
    • UUID
    • All
  • Add objects on double click: If enabled, double click on an attachment will cause it to be added to its attachment spot; if disabled, it will be worn (meaning any currently worn attachments on that sport will be removed).
  • Add clothes on double click: As above, but for layered clothing, as opposed to attachments.
  • Show Filters: Opens the Inventory Finder, which enables you to limit which items are visible in your inventory, according to item type.
  • Reset Filters: Clears all filters set with Show Filters.
  • Close All Folders: Same as the Collapse button.
  • Empty Lost and Found: Deletes the contents of the Lost and Found folder without moving them to the trash. Use with caution!
  • Save Textures As: Disabled unless a texture is selected in the inventory list. Then it will allow a texture to be saved to your hard drive.
  • Share: Click this to give the selected inventory item(s) or folder(s) to another avatar. A window will open, from which you may select who to give it to. This method is an alternative to dragging the item(s) onto an avatar's profile.
  • Find Original: Disabled unless the currently selected item in your inventory is an inventory link. ¹⁾
  • Find All Links: If clicked when an item is selected, this will show all links to it - if any exist.
  • Replace Links: Used to repair broken inventory links. Refer to this page for more information.
  • Show Links: When enabled, this will display links in inventory.
  • Show Only Links: Filters the list to show links only, hiding all other items.
  • Hide Links: Prevents links from being shown.
  • Empty Trash: Removes the contents of the Trash folder. Use with caution - this cannot be undone! (Same as right clicking the trash folder and selecting Empty trash.)

• +: Creates a new item in the currently active folder. The same options are available by right clicking a folder name.
• Suitcase Icon: This opens a new inventory window, and is thus the same as selecting “New Inventory Window” from the gear menu.
• Total: This shows the total count of elements (items and folders) in your inventory.

The bottom of the inventory window has 3 buttons:

• Profile: This will be disabled unless an item is selected - then, when clicked, it will display the item's properties.
• Share: Allows you to give the selected item(s) to another avatar. Same as dragging the item onto the avatar's profile.
• Marketplace/Wear/Teleport/Play: The third button will change depending on what you currently have highlighted in inventory:
  • Marketplace: If you have a folder, texture or a script highlighted, then it will read Marketplace; clicking it will open the SL Marketplace in your web browser.
  • Wear: The button will show Wear if you have an wearable item, or any object, highlighted.
  • Teleport: Shown if you have a landmark highlighted.
  • Play: This shows on highlighting a gesture or animation.

Inventory can be searched by typing into the white space at the top. As you type, inventory is filtered to show only items that match what has been typed. As described above, you can search by name, creator, description or UUID.

If you want to search on multiple words, separate them with a '+', but without spaces. For example, if you are looking for a landmark that you think contains Firestorm Marina, type in: Firestorm+Marina. This will match (assuming you actually have such a landmark, of course), Firestorm Gateway Marina.

To clear the search field, click the 'x' at the end of the search bar.

Normally, search operates across all tabs in the Inventory window. If you want to use separate searchs on Inventory tabs, then go to Preferences → User Interface → Interface Windows → Allow separate search terms on each tab in inventory.

If you right click any inventory item or folder, you get a menu. This menu will vary depending on context; for example, right clicking a menu will give a different menu that right clicking an item.

• Share: Selecting this allows you to give the selected item to someone else. The avatar selector window opens, allowing you to select the person you want to give it to.
• Open: Certain types of items may be opened or previewed: scripts, notecards, textures, sounds, gestures.
• Properties: This opens the item properties window, where you may view and change select item properties.
• Rename: Allows you to rename the object; only available if the object is modifyable for you. (You can also press F2 to edit an item's name.)
• Copy Asset UUID: Copies the UUID of the object to the clipboard, for some types of item.
• Restore to Last Position: if the item is an object, this will cause it to be rezzed out to its last position in the region. Use with caution! The function doesn't take into account the region name, only coordinates within a region. So do not use it if the object was never rezzed out in the region you are in, unless you are prepared to go hunting for it.

• Copy: Select this to make a copy of an object. You can then use one or both of the following two to paste copies.
• Paste: Paste a previously copied item into the folder which is currently selected. (You cannot make a copy if the item is no copy for you.)
• Paste as Link: Pastes a link to a previously copied item, into the folder which is currently selected.
• Replace Links: Used to repair broken inventory links. Refer to this page for more information.

• Delete: As the name suggests, this deletes the selected item, moving it to your Trash folder.

• Wear: Wears the item on your avatar, replacing any other items which might be already worn in the same spot.
• Add: Wears the item on your avatar, adding it to any other items which might already be worn in the same spot.
• Attach To: Allows you to select a body part on which to wear an object.
• Attach to HUD: Allows you to select an HUD point on which to attach the object.

For the Recent tab only:

• Show in Main View: Highlights the item in the Inventory tab.

• Share: Selecting this will allow you to give the folder (and its contents) to someone else. The avatar selector window opens, allowing you to select the person you want to give it to.
• New Folder: Creates a new folder inside the currently selected one. The name will default to New Folder, and will start off in edit mode so you can rename it.
• New Script: Creates a new, default script in the current folder.
• New Notecard: Creates a new blank notecard in the current folder.
• New Gesture: Creates a new gesture in the current folder.
• New Clothes: Creates a new clothing item in the current folder. Select the type from the sub-menu.
• New Body Parts: Creates a new body part in the current folder. Select the type from the sub-menu.
• Use as default for: Allows you to set the folder as the default folder for uploads of images, sounds, animations or (mesh) models. To view the current default folder settings, look in Preferences→ Firestorm -> Uploads.

• Replace Current Outfit: Removes all attachments and replaces them with the contents of the current folder. If the folder contains body parts *system hair, skin, shape, eyes), any worn ones will also be replaced; if any of the four required body parts are not present in the folder, the currently worn one will remain worn.
• Add to Current Outfit: Adds the items in the current folder to your avatar. Any worn attachments will not be removed. If the folder contains any system body parts, then the worn parts will be replaced (as you cannot wear more than one of each part).
• Wear items: Similar to Replace (described above), except that attachments are not removed if the folder contains no replacement. For example, if you are wearing something attached to the Chest point, and the folder has no object that would attach there, the existing attachment will not be removed.
• Remove from Current Outfit: If you are wearing any of the items in the current folder, they will be removed.

• Rename: Allows you to rename the currently folder. This can also be accomplished by pressing F2, rather than right-clicking it.

• Copy: Select this to make a copy of a folder. You can then use one or both of the following two to paste copies. (Naturally, this will not be available if the item is no copy for you.)
• Paste: Paste a previously copied folder into the folder which is currently selected.
• Paste as Link: Pastes a link to a previously copied folder, into the folder which is currently selected. As with items, this is just a reference.

• Delete: Allows you to delete the selected folder, and everything inside it. The folder is moved to your trash.

Aside from the usual Share option, there is a Cleanup Broken Links option. This will remove any broken links from the folder, without you having to unprotect it, and then manually go through and delete broken links.

With the advent of Direct Delivery, there can now be a new Received items folder or sub-panel in the inventory window. This will appear the very first time you make a purchase from the SL Marketplace, that is sent by Direct Delivery - as opposed to the previous “Magic Box” system.

If you prefer to have this sub-panel displayed as a normal inventory folder, open Preferences→ User Interface -> Interface Windows, and enable Show the Received Items folder in normal inventory.

For more information on Direct Delivery, please see the Direct Delivery FAQ.