There is a helpful tutorial video here.

Radar is presently sortable by name, age, seen and range. Just click on the appropriate button.

• The untitled column to the right of Name shows whether the person is speaking on voice
• The next column will display a green square if the person is in the same region as you, yellow if in the same parcel (ie, yellow and green, usually, for both same parcel and same region).
• The next shows if the person is typing.
• This column indicates is the person is sitting.
• The next column will show a $ sign if the person has payment info on file, and a $$ for payment info used.
• Then comes Avatar has notes, which will contain an N if you put notes on that person's profile.
• Age indicates the avatar's age in days.
• Seen is the length of time the person has been within radar range.
• Range shows their current distance, in meters. Use of bolding and color distinguishes chat range, shout range, and beyond.

When you right click on a person's name you get the following options:

• View Profile: Opens a window showing the person's profile.
• Add Friend: This option is only shown if the person is not already on your friends list. It will send a friendship request.
• Remove Friend: This option is only shown if the person is on your friends list. Clicking it will dissolve the friendship. Currently, the other person is not informed, but one copy of your calling card will be removed from the person's Calling Cards folder (a second copy will remain there until/unless they choose to delete it; if the person is logged in at the time, the removed copy will appear in their Trash).
• IM: Opens an IM to the person.
• VoiceCall: Initiates a private voice conversation with the other person. Naturally, both need to have voice enabled and functioning.
• Map: If your friend gave you map rights, this item will be enabled. If clicked, it will open the world map and show the person's current location.
• Track: shows a beacon allowing to you locate the person and track their movement. (Versions after 3.2.2 only.)
• Share: If you click this entry, an IM window opens; you can then drag and drop inventory items into it, to give them to the other person.
• Pay: Opens a window, which you can use to pay the other person L$. Some default values are shown, or you can type the number in manually.
• Offer Teleport: Click this if you wish to offer to teleport the person to your present location.
• Teleport To: Teleports you to the other person's location.
• Zoom In: If enabled, moves your camera to view the other person.
• Invite to group: allows you to invite the person to a group you belong to; opens the Groups selector window.
• Get Script Info: Displays the script info for the avatar; requires that the Firestorm bridge be enabled and worn.

• Block/Unblock: aka Mute/Unmute. This mutes the other person, completely blocking them from contacting you. You will not see anything they type in local chat or receive any IMs they might send, and all inventory offers made will be automatically declined. Use with caution; muting a person can also mute their objects, which means that if you make a purchase from them, you are likely to not receive what you paid for.
• Report: Allows you to file an abuse report against the selected avatar. This should not be done lightly and never be misused. Click here for more information on what an abuse report is.
• Freeze: Estate managers/owners can use this to freeze an avatar's movements. This is a tool to be used in cases of griefing and not to be used frivolously.
• Parcel Eject/Ban: If selected, this will eject and ban the avatar from the parcel you are in. You must have the appropriate rights in that parcel or this will not work.
• Estate Kick/Ban: Similar to the above, but operates at the estate level. Therefore, this is only available to estate managers or owners.
• Estate Teleport Home: Selecting this will teleport the avatar to his/her home location. This does not ban them, however, and may fail if they have no home location set or if that location is not accessible (eg, the region is down).
• Derender: Temporarily derenders the avatar.
• Derender + Blacklist: Derenders and blacklists the avatar. This derender is permanent - unless you remove the person from the blacklist; see this page.

The Sprocket/Gear icon at the top of the Nearby tab has the same functions as the right click menu for individual avatar names.

The List icon, to the right of the gear, has the following radar functions:

• Show Minimap above Radar: If enabled, the panel expands upward to show a minimap of the current area.
• Limit Results to Specific Radius: If selected, a slider will appear at the bottom of the window, to the right of the sprocket/gear. Here you may change the range at which the radar is active. This allows you to monitor smaller areas than the radar normally can report. Useful if you only are interested in a parcel rather than an entire region and those adjoining. If you wish to have radar report at max range all the time, it is more efficient to just disable this option.
• Show muted and blacklisted Avatars: If enabled, radar will list people you have muted and/or derendered.
• Radar Name Format: Allows you to select how you want names to be displayed in the radar. Available options depend on how you have preferences set for display names and user names.
• Displayed Columns: You can enable or disable specific columns in the list. Handy if you want to reduce the overall width.
• Color names based on distance: same as the option in Preferences→ Colors -> Name tags.

• Report To: allows you to select whether to show radar notifications to chat or as notification toasts.
• Local chat distance ring in Minimap: Show chat raneg on the minimap. Same as the option in Preferences → Colors -> Minimap.
• Report Entering Draw Range: If enabled, this will report to chat when someone enters your draw distance range.
• Report Leaving Draw Range: If enabled, this will report to chat when someone leaves your draw distance range.
• Report Entering Chat Range: If enabled, this reports to chat whenever someone enters chat range (20m).
• Report Leaving Chat Range: If enabled, this reports to chat whenever someone leaves chat range (20m).
• Report Entering your Region: Enable this to have the radar report people entering the region you are currently in.
• Report Leaving your Region: Enable this to have the radar report people leaving the region you are currently in.
• Report Enter Alerts to Scripts: If enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
• Report Exit Alerts to Scripts: If this is enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
• Enhance Radar with LSL Bridge: ENhance radar functionality via the Bridge. Used to improve distance calculations.

• Open Blocked Residents & Objects:

  This displays the list of people and objects you have blocked (muted).

The '+' icon, to the right of the list (radar) icon, when clicked, will give the following message: “Friends can give permissions to track each other on the map and receive online status updates.” And it will ask you if you want to offer friendship to an Avatar that you highlighted. If they are already on your friends list, the '+' sign will be greyed out.

There is a helpful tutorial video here.

This panel combines several functions into one place. It is accessed by clicking the People icon in the bottom button bar.

The panel is divided into tabs…

Radar is presently sortable by name, age, seen and range. Just click on the appropriate button.

• The untitled column to the right of Name shows whether the person is speaking on voice
• The next column will display a green dot if the person is in the same region as you.
• The next shows if the person is typing.
• This column indicates is the person is sitting.
• The next column will show a $ sign if the person has payment info on file, and a $$ for payment info used.
• Then comes Avatar has notes, which will contain an N if you put notes on that person's profile.
• Age indicates the avatar's age in days.
• Seen is the length of time the person has been within radar range.
• Range shows their current distance, in meters. Use of bolding and color distinguishes chat range, shout range, and beyond.

When you right click on a person's name you get the following options:

• View Profile: Opens a window showing the person's profile.
• Add Friend: This option is only shown if the person is not already on your friends list. It will send a friendship request.
• Remove Friend: This option is only shown if the person is on your friends list. Clicking it will dissolve the friendship. Currently, the other person is not informed, but one copy of your calling card will be removed from the person's Calling Cards folder (a second copy will remain there until/unless they choose to delete it; if the person is logged in at the time, the removed copy will appear in their Trash).
• IM: Opens an IM to the person.
• VoiceCall: Initiates a private voice conversation with the other person. Naturally, both need to have voice enabled and functioning.
• Map: If your friend gave you map rights, this item will be enabled. If clicked, it will open the world map and show the person's current location.
• Track: shows a beacon allowing to you locate the person and track their movement. (Versions after 3.2.2 only.)
• Share: If you click this entry, an IM window opens; you can then drag and drop inventory items into it, to give them to the other person.
• Pay: Opens a window, which you can use to pay the other person L$. Some default values are shown, or you can type the number in manually.
• Offer Teleport: Click this if you wish to offer to teleport the person to your present location.
• Teleport To: Teleports you to the other person's location.
• Zoom In: If enabled, moves your camera to view the other person.
• Invite to group: allows you to invite the person to a group you belong to; opens the Groups selector window.
• Get Script Info: Displays the script info for the avatar; requires that the Firestorm bridge be enabled and worn.

• Block/Unblock: aka Mute/Unmute. This mutes the other person, completely blocking them from contacting you. You will not see anything they type in local chat or receive any IMs they might send, and all inventory offers made will be automatically declined. Use with caution; muting a person can also mute their objects, which means that if you make a purchase from them, you are likely to not receive what you paid for.
• Report: Allows you to file an abuse report against the selected avatar. This should not be done lightly and never be misused. Click here for more information on what an abuse report is.
• Freeze: Estate managers/owners can use this to freeze an avatar's movements. This is a tool to be used in cases of griefing and not to be used frivolously.
• Parcel Eject/Ban: If selected, this will eject and ban the avatar from the parcel you are in. You must have the appropriate rights in that parcel or this will not work.
• Estate Kick/Ban: Similar to the above, but operates at the estate level. Therefore, this is only available to estate managers or owners.
• Estate Teleport Home: Selecting this will teleport the avatar to his/her home location. This does not ban them, however, and may fail if they have no home location set or if that location is not accessible (eg, the region is down).
• Derender: Temporarily derenders the avatar.
• Derender + Blacklist: Derenders and blacklists the avatar. This derender is permanent - unless you remove the person from the blacklist; see this page.

The Sprocket/Gear icon at the top of the Nearby tab has the same functions as the right click menu for individual avatar names.

The List icon, to the right of the gear, has the following radar functions:

• Show Minimap above Radar: If enabled, the panel expands upward to show a minimap of the current area.
• Limit Results to Specific Radius: If selected, a slider will appear at the bottom of the window, to the right of the sprocket/gear. Here you may change the range at which the radar is active. This allows you to monitor smaller areas than the radar normally can report. Useful if you only are interested in a parcel rather than an entire region and those adjoining. If you wish to have radar report at max range all the time, it is more efficient to just disable this option.
• Show muted and blacklisted Avatars: If enabled, radar will list people you have muted and/or derendered.
• Radar Name Format: Allows you to select how you want names to be displayed in the radar. Available options depend on how you have preferences set for display names and user names.
• Displayed Columns: You can enable or disable specific columns in the list. Handy if you want to reduce the overall width.
• Color names based on distance: same as the option in Preferences→ Colors -> Name tags.

• Report To: allows you to select whether to show radar notifications to chat or as notification toasts.
• Local chat distance ring in Minimap: Show chat raneg on the minimap. Same as the option in Preferences → Colors -> Minimap.
• Report Entering Draw Range: If enabled, this will report to chat when someone enters your draw distance range.
• Report Leaving Draw Range: If enabled, this will report to chat when someone leaves your draw distance range.
• Report Entering Chat Range: If enabled, this reports to chat whenever someone enters chat range (20m).
• Report Leaving Chat Range: If enabled, this reports to chat whenever someone leaves chat range (20m).
• Report Entering your Region: Enable this to have the radar report people entering the region you are currently in.
• Report Leaving your Region: Enable this to have the radar report people leaving the region you are currently in.
• Report Enter Alerts to Scripts: If enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
• Report Exit Alerts to Scripts: If this is enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
• Enhance Radar with LSL Bridge: ENhance radar functionality via the Bridge. Used to improve distance calculations.

• Open Blocked Residents & Objects:

  This displays the list of people and objects you have blocked (muted).

The '+' icon, to the right of the list (radar) icon, when clicked, will give the following message: “Friends can give permissions to track each other on the map and receive online status updates.” And it will ask you if you want to offer friendship to an Avatar that you highlighted. If they are already on your friends list, the '+' sign will be greyed out.

This tab shows your friends list. It has two tabs: Online and All, which are self-explanatory. The Possible Friends tab is used if you connect your SL account to Facebook; the tab will the show people whom you may know and wish to add as friends.

The list is organized in columns. The first shows the person's name. Following this are a series of icons:

• Edit rights, their objects: highlighted when the person has given you rights to edit, move, delete their objects.
• Edit rights, your objects: highlighted when you have given the person rights to edit, move, delete your objects.
• Map rights: highlighted when you have allowed the person to locate you on the world map.
• Online status: when highlighted, the avatar will be able to see your online status.

Two of these may be toggled on/off, so you can give or revoke edit rights, for example, by clicking the appropriate icon. The same is true for map rights.

When you right click on a person's name you get the following options:

• View Profile: opens the selected person's profile.
• IM: Opens an IM to the person.
• Offer Teleport: Click this if you wish to offer to teleport the person to your present location.
• Voice Call: Initiates a private voice conversation with the other person. Naturally, both need to have voice enabled and functioning.
• View Chat Transcript: Requires that chat be logged; set in Preferences → Privacy -> Logs & Transcripts.

• Remove Friend: This option is only shown if the person is on your friends list. Clicking it will dissolve the friendship. Currently, the other person is not informed, but your calling card will be moved to the person's trash.
• Invite to group: allows you to invite the epson to a group you belong to; opens the Groups selector window.

• Map: If your friend gave you map rights, this item will be enabled. If clicked, it will open the world map and show the person's current location.
• Share: If you click this entry, an IM window opens; you can then drag and drop inventory items into it, to give them to the other person.
• Pay: Opens a window, which you can use to pay the other person L$. Some default values are shown, or you can type the number in manually.
• Block/Unblock: aka Mute/Unmute. This mutes the other person, completely blocking them from contacting you. You will not see anything they type in local chat or receive any IMs they might send, and all inventory offers made will be automatically declined. Use with caution; muting a person can also mute their objects, which means that if you make a purchase from them, you are likely to not receive what you paid for.

The Sprocket/Gear icon at the top of the Friends tab has the same functions as the right click menu.

The List icon to the right, has these functions:

• Sort by Name: Sorts the friends list alphabetically. Useful on the All view.
• Sort by username: Only useful if you also have display names enabled.
• Sort by Status: Sorts the list by online status. Useful on the All view.

• View People Icons: If enabled, displays a small icon from the avatar's profile to the left of their name.
• View Permissions Granted: If enabled, shows the permissions icons described above; otherwise, these icons are hidden.
• View Conversation Log: Shows the conversation log (if logging is enabled).

The '+' icon to the right of the gear gives access to a powerful people search/selector window.

The window is organized into tabs.

• Search: type in part or all of a person's name, then click go, and the list below will populate with all matching names. Select the person you were looking for (assuming the name is listed), then double click or click on Ok to offer that person friendship.
• Friends: This is a simple sorted list of your friends.
• Near Me: Shows a radar list of avatars near you. You can increase the range to broaden the scope, if needed. The circular arrow will refresh the list. As above, if you find the name of someone you wish to add as a friend, double-click it or click the Ok button at the bottom.

Finally, the trashcan icon can be used to unfriend the selected person.

The Groups tab shows the list of groups to which you currently belong.

When you right click on a group, you get the following options:

• Activate: Sets the selected group as your active group.
• View Info: This displays the group profile, allowing you to view information about and manage the group (if you have the ability to do so).
• Chat: Opens the chat window for the selected group.
• Voice Call: Initiates a voice conference call with the group.

• Leave: Select this if you wish to leave the selected group. You are prompted for confirmation.

If you mouse over the list of groups, you will see two icons appear to the far right. These give fast access to the group profile.

The sprocket/gear icon at the top has the same options as the right click menu.

The list iconto the right, has this option:

• Display Group Icons: If enabled, shows an icon image of the group logo.

The '+' sign gives the options to:

• Join Group: This will open the search window, where you can enter the name of the group you wish to join.
• New Group (Create): Opens a blank group profile window, with which you may create a new in-world group. Fill in at least the group name and select the group maturity rating. Creating a group costs L$100.

The Trashcan icon allows you to leave the selected group.

The next tab of the People panel is Recent. This shows a list of people with whom you have recently had IM conversations - “recent” here meaning since you last logged in. The list will show the name of the person and when you last spoke to them.

If you right click a person's name, you get the following options:

• View Profile: Opens a window showing the person's profile.
• IM: Opens an IM to the person.
• Offer Teleport: Click this if you wish to offer to teleport the person to your present location.
• Voice Call: Initiates a private voice conversation with the other person. Naturally, both need to have voice enabled and functioning.
• View Chat Transcript: Requires that chat be logged; set in Preferences → Privacy -> Logs & Transcripts.

• Add Friend: This option is only shown if the person is not already on your friends list. It will send a friendship request.
• Remove Friend: This option is only shown if the person is on your friends list. Clicking it will dissolve the friendship. Currently, the other person is not informed, but your calling card will be moved to the person's trash.
• Invite to group: allows you to invite the epson to a group you belong to; opens the Groups selector window.

• Map: If your friend gave you map rights, this item will be enabled. If clicked, it will open the world map and show the person's current location.
• Share: If you click this entry, an IM window opens; you can then drag and drop inventory items into it, to give them to the other person.
• Pay: Opens a window, which you can use to pay the other person L$. Some default values are shown, or you can type the number in manually.
• Block/Unblock: aka Mute/Unmute. This mutes the other person, completely blocking them from contacting you. You will not see anything they type in local chat or receive any IMs they might send, and all inventory offers made will be automatically declined. Use with caution; muting a person can also mute their objects, which means that if you make a purchase from them, you are likely to not receive what you paid for.

The sprocket/gear icon at the top has the same options as the right click menu.

The List icon has the following functions:

• Sort by Most Recent: Sorts the list by when you last spoke with each person.
• Sort by Name: Sorts the friends list alphabetically by name.

• View People Icons: If enabled, displays a small icon from the avatar's profile to the left of their name.

The '+' gives quick access to offering friendship to the selected person.

The trashcan icon will allow you to unfriend the eprson - if he/she is a friend.

This tab shows the list of avatars, objects and groups which you have blocked (muted).

Right clicking any name gives the following options:

• Unblock: Allows you to remove the person, object or group from the block list.
• Profile: For avatars, opens the person's profile.

The gear icon on the top has the same fucntions as the right click menu.

The List icon has these otpions:

• Sort by Name: Sorts the friends list alphabetically by name.
• Sort by Type: Sorts the list by type (ie, Group, avatar, object)

The '+' icon allows you to add a person or object to your block list:

• Block Resident by name: Opens a person selector window, so you can pick who you wish to mute.
• Block object by name: Opens a window into which you should type the name of the object to block.

The trascan icon can be used to remove the selected entry from the block list.

This panel replicates many of the features of Contact Sets in the Conversations window.

Across the top, there are:

• Current set name: This drop down allows you to select a contact set.
• Gear Icon: Functions and Settings.
• + Icon: Add person or set.
• Trash Icon: Remove set or person.

Since these functions are all essentially the same as on the main Contact Sets window, please refer here for details.

The mini-map gives you an overview of the region in which you are located. It shows the region and people and objects in it.

You can use your mouse scroll wheel to zoom in and out. Press and hold shift, then left click to pan the view around. If you click and drag the lower right corner, you can resize it.

The mouse cursor is a small cross hair, superimposed on a circle. The color, opacity and size of this circle can be changed, in Preference→ Colors -> Minimap→ Pick Radius.

The mini map contains color coded symbols, as follows:

• Yellow dot in the center: That's you!
• Cone of light: This comes from the yellow dot; it shows which direction you're facing and your field of vision.
• Yellow dots: Yellow dots represent nearby friends.
• Grey dots: Grey dots represents residents that you have blocked/muted.
• Blue dots: Blue dots represents Linden residents.
• Green dots: Green dots represent other Residents of Second Life

NOTE: the colors of these dots may be changed in Preferences → Colors -> Minimap.

Avatar dots change shape depending on their height relative to yours:

• Round dot: An avatar at about the same height as your camera viewpoint; for example, if you're standing next to them.
• ^ - An avatar above your camera position. They may be flying, or in a very high building.
• v - An avatar below your camera position. This may also show if the avatar is over 1,000m.
• ǂ - Height over 1020m and that does not have a viewer object representation, usually meaning out of draw distance.

• Dark gray blocks: These are objects owned by others.
• Cyan blocks: These are objects you own in the area.
• Fuchsia blocks: These are objects deeded to (owned by) a group you're in.
• Pale Orange blocks: Scripted objects.
• Dark orange: Temp on rez objects.
• Red blocks: Physical objects.
• Tiled dark blue: These are areas beyond your vision. You can see them by moving closer, or increase your draw distance in the Graphics tab of the Preferences window.
• Red areas: The Mini-Map turns red if the Region is offline or your viewer has lost its connection.

Some of the above are not enabled by default. Right click the mini map, and enable as desired in the Show sub-menu.

If you mouse over an avatar symbol, you will get a hover tip showing the avatar's name and distance from you. Clicking the orange (i) allows you to view their profile.

Right clicking on the map opens a menu:

• Zoom Close/Medium/Far/Default: A quick way to change the map zoom level.
• Show: Shows a list of what you want to show on the minimap.
• Rotate Map: Enabling this makes the map rotate, keeping your field of view directed upward. Otherwise, the map will be oriented North, and your field of view will change on the map as you move and turn.
• Auto Center: If enabled, the minimap will keep your avatar at the cenetr of the window.
• Chat Distance Ring: If enabled, draws rings showing your change range limit (20m) and shout range limit (100m).
• Place Profile: Opens the place profile window, showing infomation about the parcel.
• World Map: Opens the world map for the region.

If you right click on an avatar, the menu will have more options:

• Profile: Opens the person's profile. (Versions after 3.2.2 only.)
• Cam: Allows you to cam on the avatar - assuming parcel privacy allows it. (Parcel privacy is set in About Land→ Options)
• Mark: Allows you to color the specific avatar's dot differently.
• More options:
  • Add Friend: Offers friendship.
  • Add to Set: adds the person to a contact set.
  • Remove Friend: Remove the person from your friends list (if they are a friend).
  • IM: Start an IM conversation
  • Call: Initiates a voice call
  • Map: Shows the eprson on the world map, if they have granted you map rights.
  • Share: Allows you to share inventory items with the person.
  • Pay: Opens a pay window, so you can pay L$.
  • Offer teleport: Sends a teleport invite.
  • Request teleport: Sends a message asking that the person send you a teleport.
  • Teleport To: Directly teleport to the person.
  • Invite to Group: Allows you to send a group invitation.
  • Get Script Info: Gets information on the running scripts the person is wearing.
  • Block/Unblock: Blocks (mutes) the person - or reverses this.
  • Report: Opens the Abuse Report window.
  • Derender: Temporarily Derenders the person.
  • Derender + Blacklist: Permanent derender.
• Start Tracking: Enables tracking avatars by drawing a beacon.
• Stop Tracking: If you have a red beacon active, this will clear it.

Version 5.x and later of Firestorm are built with the latest Xcode toolchain and macOS release.

You will need to install the following tools:

• Xcode. It's a free download from Apple.
  • You will need to install the command line tools. To do this, after you've copied the Xcode application to your Applications folder, open a command line (Terminal, or equivalent) window, and issue the command

    xcode-select --install

• CMake version 3.
  • Again, you will need to install the command line links. The menu option to do this from within CMake is broken, and has been for several versions. From your command line prompt, issue the following command:

    sudo /Applications/CMake.app/Contents/MacOS/CMake

  • This will launch the CMake application with root permissions. Once you've done that, select Tools→Install for Command Line Use from the CMake menu. When that completes, exit CMake.
• The latest version of the Mercurial source code management system.
• The pip Python package installation tool, which is required for the next step. Issue this command:

  sudo easy_install pip

• The pyparsing Python package. This package is installed by default, but in a way that keeps pip from upgrading it. Force the current version to be installed by issuing this command:

  sudo pip -H install --ignore-installed pyparsing

• The autobuild Python package. Issue this command:

  sudo pip -H install autobuild

If you want to use licensed FMOD Studio or KDU build libraries (they are optional) you have to provide these yourself. If you're building Firestorm as part of the project team, ask for the libraries for fmodstudio and kdu. Put them into /opt/firestorm .

If you're a community builder, you'll need to build these libraries yourself, then change your autobuild.xml file to point to your own versions, or create a different autobuild.xml with your customizations, and use this with autobuild instead of our default autobuild.xml There are some examples of how to build FMOD Studio on the LL Wiki and opensource-dev mailing list.

We've created a non-KDU build target to make this easier. Everywhere you see “ReleaseFS” below, use “ReleaseFS_open” instead. This will perform the same build, using openjpeg instead of KDU and omitting FMOD Studio.

Available premade firestorm-specific build targets:

ReleaseFS		(includes KDU, FMOD)
ReleaseFS_open		(no KDU, no FMOD)
RelWithDebInfo_open	(no KDU, no FMOD)

To build firestorm:

      autobuild build -c ReleaseFS                        

Other examples:

      autobuild configure -c ReleaseFS                    # basic configuration step, don't build, just configure
      autobuild configure -c ReleaseFS -- --clean         # clean the output area first, then configure
      autobuild configure -c ReleaseFS -- --chan Private-Yourname   # configure with a custom channel

      autobuild build -c ReleaseFS --no-configure               # default quick rebuild
      autobuild build -c ReleaseFS --no-configure -- --clean    # Clean rebuild

      autobuild configure -c ReleaseFS_open --            # configure with no third-party libraries
      autobuild configure -c ReleaseFS_open -- --fmodex   # configure with FMOD Ex but no KDU

Any of the configure options can also be used (and do the same thing) with the build options. Typical LL autobuild configure options should also work, as long as they don't duplicate configuration we are already doing.

Logs: Look for logs in build-darwin-i386/logs.

Output: Look for output in build-darwin-i386/newview/Release

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

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

This can take a while. It's a rather large download.

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

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

• Enter these commands into the command prompt:

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

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

wrote /Users/tonya/3p-fmodex/fmodex-44453-darwin-201505171651-r21.tar.bz2
md5 3b0d38f2a17ff1b73c8ab6dffbd661eb

Next, update Firestorms autobuild.xml file to use your FMOD Ex.

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

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

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

For example:

autobuild installables edit fmodex platform=darwin hash=3b0d38f2a17ff1b73c8ab6dffbd661eb url=file:///Users/tonya/3p-fmodex/fmodex-44453-darwin-201505171651-r21.tar.bz2

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

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

export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

cd ~/firestorm/phoenix-firestorm-lgpl

 autobuild configure -c ReleaseFS_open

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

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

• FMODSTUDIO (bool) controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps in Fmod_using_autobuild for this to work. This is the switch the –fmodstudio build argument sets.
• LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.

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

Example:

autobuild configure -c ReleaseFS_open -- -DLL_TESTS:BOOL=FALSE -DFMODSTUDIO:BOOL=TRUE

There is one other switch you need to set. The -A 64 switch tells autobuild to build a 64-bit version of the viewer. This switch goes immediately after the build or configure argument, as in

autobuild configure -A 64 -c ReleaseFS_open

It must be specified on both the configure and build commands. If you want to build a 64-bit viewer after building for 32 bits, or vice versa, you must do the first build when you change the architecture with –clean; otherwise, the viewer may build, but will almost certainly refuse to run.

Note that, for OS X, 32-bit builds are deprecated and will likely run into problems. There is no longer any reason to build a 32-bit macOS viewer.

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

export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

cd ~/firestorm/phoenix-firestorm-lgpl
autobuild build -c ReleaseFS_open --no-configure

Now, sit back, read War and Peace, calculate π to 50 places, tour the country, whatever you desire. Compiling may take quite a bit of time, depending on how fast your machine is and how much else you're doing.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -c ReleaseFS [– config options] .) Some find it is clearer if these steps are done separately, but can save a bit of time if done together.

• Kittin Ninetails
• Cinder Biscuits
• Reworked for v5 by Tonya Souther

Please note: Viewers play a minor part in voice functionality. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons:

• Your ISP is throttling or blocking the voice service;
• failure of the Vivox service;
• voice issues on the region you are on;
• voice being throttled by bandwidth set incorrectly - please check it by following the instructions here;
• voice hardware (mic, headset) not configured correctly in your operating system settings;
• voice hardware not configured correctly in the viewer;
• another application has your voice hardware in use (example, Skype);

• your anti virus software has “mangled” the voice application; see steps on this page: here.

• your firewall is blocking slvoice. Add slvoice to your firewall's exclusion/allow list.

macOS 10.14 Mojave: No voice input using Firestorm-Beta 6.0.1. See [Mac Mojave] SL Voice No Input on 6.0.1. You may add a comment on that JIRA ticket requesting a test viewer to use until next release which contains a fix for this issue.

The IP address of the server 'www.bhr.vivox.com' recently changed to 74.201.103.238 so anyone having a problem can check to see what address their system sees for that name - if it's not that address, it's probably wrong. A simple reboot may resolve this issue. If not, see DNS Fail - General steps for help fixing this.

nslookup command how-to: WindowsMacLinux

Since 4.7.9, voice has not always connected to the voice servers. This is due to some coding issues that we inherited from the official SL viewer and that code's interaction with the latest voice files. The issue is documented on LL's Jira. A workaround is to disable and then re-enable voice. But if you're presented with the voice connection failure message that tells you “Voice communications will not be available”, you may need to disable voice and then relog before voice will try to reconnect.

Steps:

• Go to Preferences → Sound & Media → Voice, and untick “Enable Voice.”
• Relog.
• Wait 10-20 seconds, or until the viewer has finished rezzing the scene.
• Re-enable voice.

Version 5.1.7., voice crashes when turning on microphone. See BUG-225293 and FIRE-22940
Fixed Firestorm-Beta 6.0.1.
Note that the SLVoice executable in this viewer is not compatible with most older viewers; do not copy it into other viewers.http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.8.518593

Most voice connection issues happen when the viewer tries to connect to voice during the login process. The workaround is to disable voice before you log out, and then only enable it after logging in when you need it. You can toggle Voice from the Media Controls at the top of the viewer (not enabled by default for Vintage or Latency skins) by hovering over the speaker icon and then checking or unchecking the last checkbox, or by going to Preferences ⇒ Sound & Media ⇒ Voice and checking or unchecking the top option.

If you have issues hearing but not being heard, or vice versa, then make sure that your headset is properly connected to your computer. Unplug it, then plug it back in, making sure it is fully inserted.

And on a related note, if you plug your headset in while logged into SL, you will very likely have to relog to get it to be recognised.

Due to the many different versions of each operating system (Windows, linux distros, Mac OSx's), it is very difficult to give specifics for each one. Nonetheless, make sure that your operating system is correctly configured for voice: that voice is going to your headset (or speakers, as you prefer), and that your mic is enabled and configured.

If you can hear people but cannot be heard, or vice versa, it is most likely a problem in this area.

A bit more specifically, for Windows and linux, check in Mixer that SLvoice is listed, and not muted. Check that input and output devices are correct. For Mac, look in the Sound Preference pane.

Some details provided below.

• Go to Preferences→ Sound & Media -> Sounds. Find the Voice Chat slider and make sure it is not all to the left. Try increasing the volume.
• Make sure that Voice chat is enabled on that preferences tab.
• go to Preferences→ Sound & Media -> Voice. Click on Audio Device Settings. For Input and Output, use the dropdowns to select your voice devices (headset, microphone, whatever you use). It is best not to leave these at Default.
• Close Preferences and locate the Mic button on the button bar. Click the Lock checkbox then the actual button, and try speaking (hopefully, you went to Voice Echo Canyon so you can test).

Try reinstalling the drivers for your sound card, if you have one. Sometimes, these drivers conflict with the sound component of graphics card drivers. Similarly, you may have success by reinstalling your graphics card driver.

If voice still does not work, then continue working through this page.

If you find that voice cuts in and out, particularly right after a TP, and at the same time, you notice that things are not rezzing in for you very well (avatars, objects, etc), then the likely cause is that your router is being “overwhelmed” with texture transfers. So reboot your router/modem, and then your computer, and see if the problem is solved.

You can also try adjusting your bandwidth as explained here.

If that does not help, then proceed with the section below.

Chances are good that the problem lies with the SL servers or the voice provider, Vivox. Still, there are things you can try:

• May 2018: If you had a recent Windows update, see this page.

• Open Preferences, and go to Sound & Media → Voice, and click Reset (circular arrow).

• Shut down all applications that use, or can use, voice - like Skype, etc. Then relog.

• What sometimes helps to get voice working is disabling voice in Preferences→ Sound & Media -> Voice, hitting Ok, waiting a minute and then enabling voice and click Ok. When these methods fail (assuming voice usually works for you) it is usually the Vivox voice servers that are the problem.

• If this does not work at your current location, go to a region where other people are able to use voice at this time. One possibility is Firestorm Social, but any region where voice is known to be functioning is fine. Disable voice in Preferences→ Sound & Media -> Voice. Relog, using the last location selection on your login screen. Wait a couple of minutes. Reenable voice. Wait another couple of minutes (in other words, give the connection time to be established). If voice comes on, then the problem may have been the region you were in before. Was voice disabled there? If not, a region restart might solve the problem.

• Go to Preferences → Network & Files -> Connection and reduce your bandwidth setting to 500 (if it is not already set there). Repeat the above step to toggle voice off and back on. See here for more information on setting your bandwidth properly, but bear in mind that lower levels than those calculated there may be necessary for troubleshooting purposes.

• Log out of the viewer, then check Task Manager (or equivalent) and see if SLVoice is still running. If so, kill the process, restart the viewer and see if voice connects.

• Try a relog, or even a reboot of the computer.

• Sometimes device settings can reset, so check in Preferences→ Sound & Media -> Voice→ Audio Device Settings, to be sure that the input and output are set correctly.

• HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

• Does your headset/microphone work outside of SL? ie when using Skype, Yahoo or MSN

• Does your headset/microphone work in Preferences→ Sound & Media -> Voice→ Audio Device Settings?

• Is your voice chat volume turned up and not muted?

• Is the SLVoice.exe (simply SLVoice on Mac) that is in the Firestorm folder in the exceptions/allowed list for your firewall? If your firewall is turned off, turn it on and add the SLVoice.exe (or SLVoice) anyway.
  If your Firewall has SLVoice listed twice, then remove both instances, and allow it again. For Win10, make sure that SLVoice has Private unchecked, and Public checked. If you had these set differently, change them, then close the window, log out of SL, reboot.

• Check the bandwidth you are actually getting and what you have set in Preferences → Network & Files → Connection. Please refer to this page for specifics.

• Go to top menu, Advanced → Debug Settings, and in the window that opens, type: Cmdlinedisablevoice - then ensure this is set to FALSE. (Use Crtl-Alt-D to enable the Advanced menu, if it isn't.)

• 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

• akafox
• Alexegram
• Angela Kwak
• Avalon Bouvier
• ChuckPC
• ErikLuc
• Fayleen Bellios
• FrankASinatra
• ImaLuckygirl
• Jolie Serendipity
• Kitty Beery (Dutch)
• LegitBonzai
• Liliana Darwinian (Portuguese)
• LosAngelesGraff
• MacMaccee (German, English)
• MarcSeven Lubitsch
• PassionateAviator
• Pim Peccable
• Skyspinner Soulstar
• Sparkle Weatherwax
• Talula Shippe
• Tracy Argus
• Webbi Jonson

• 0079Galadriel
• MarcSeven Lubitsch
• 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

Donc vous avez la dernière version du viewer mais vous ne voyez pas les mesh - Que se passe-t-il ?

Eh bien ça ne fonctionne pas nécessairement automatiquement. Cela dépend de votre matériel informatique, de certains paramètres qui ont besoin d'être activés et qui sont peut-être désactivés par défaut.

Allez à Préférences→ Graphiques -> Général;. activez les Basic Shaders.

Si l'option est grisée, augmentez le niveau de Performance dans le même onglet jusqu'à ce que les Basic Shaders soient activés et cochables.

Vérifiez que votre Distance d'Affichage est raisonnable. Si vous avez des difficultés à voir les mesh, réduisez-la; si votre Distance d'Affichage est au-dessus de 128, réglez-la sur 128 ou moins. (La valeur optimale dépend totalement de votre matériel; il vous faudra expérimenter ce qui focntionne le mieux pour vous).

Dans certains cas, les attachements en mesh ne s'afficheront toujours pas correctement. Allez dans Préférences→ Graphiques -> Rendering et désactivez les deux options Alpha Mask Rendering.

Quelquefois aussi un bug où le mesh que vous portez semble porté par un autre avatar. Dans ce cas, allez dans Préférences → Graphiques → Général, et activez Hardware Skinning.

Il est possible que le protocole HTTP soir en train de surcharger votre box/router; essayez les suggestions données ici; si ça ne vous aide pas, défaites les changements effectués et continuez à lire.

Si rien n'a résolu le problème - et assurez-vous que vous avez bien tout essayé d'abord ! - alors dans la barre de manus du haut, ouvrez Avancé → Paramètres de Débogage, tapez MeshMaxConcurrentRequests et réduisez progressivement la valeur. (Si le menu Avancé n'est pas visible, pressez Ctrl-Alt-D).

Si cela ne vous aide pas, revenez à la valeur par défaut (Pressez le bouton “Reset to Default”) et essayez d'augmenter la valeur progressivement. Ne la réglez en aucun cas au-dessus de 64. Les anglophiles peuvent lire ce commentaire pour une explication sur les inconvénients possibles de l'augmentation de cette valeur. De plus, nous conseillons de remettre la valeur sur défaut une fois que le mesh aura visible.

• Utilisateurs Mac : Le problème peut être en rapport avec le DNS, particulièrement s'il est associé à des crashes ou des déconnexions pendant toutes les téléportations ou presque et/ou une liste d'amis vide. Voyez la partie spécifique aux MACs cette page pour plus d'explications.

Si vous voyez les mesh correctement mais qu'un mesh en particulier n'arrive pas à s'afficher et/ou affiche une pyramide, un triangle ou un canard après qu'il soit porté ou posé, voir ci-dessous.

Avant d'essayer quoi que ce soit d'autre, reconnectez-vous. Le problème se résout souvent de cette façon. Sinon …

• Assurez-vous que les dossiers et fichiers cachés sont affichés; voir ici. Puis naviguez jusqu'à cet emplacement :
  • Sur XP: C:\Documents and Settings[VOTRE NOM D'UTILISATEUR]\Application Data\Firestorm
  • Sur Windows Vista et 7: C:\Users[VOTRE NOM D'UTILISATEUR]\AppData\Roaming\Firestorm
  • Sur un Mac: /Users/[VOTRE NOM D'UTILISATEUR]/Bibliothèque/Application Support/Firestorm
  • Sur Linux: ~/.firestorm
• Dans ce dossier Firestorm, ouvrez le dossier qui porte le nom de l'avatar qui a le problème.
• Supprimez le fichier texture_list_last.xml
• Connectez-vous et voyez si le mesh coupable charge.

• Sauvegardez vos paramètres - voir ici
• Effacez vos paramètres manuellement, comme expliqué ici
• Reconnectez-vous et voyez si le mesh s'affiche correctement?. Si oui …
• Restaurez vos paramètres - voir voir ici - et vérifiez le mesh de nouveau.

Ceci paraît être spécifique àà ceux qui ont une carte graphique ATI/AMD. Voir ici.

So you have the latest viewer and still can't see mesh - what's the deal?

Well, it isn't necessarily automatic. Depending on your specific hardware, certain settings that need to be enabled for mesh, may be set off by default.

Go to Preferences→ Graphics -> General; then enable Basic Shaders.

If this remains greyed out, then increase the level of Render Quality until Basic Shaders becomes enabled and can be checked.

Make sure you have a reasonable draw distance. If you have difficulty rendering mesh, lower it; if your draw distance is over 128, set it to 128, or less. (The optimal value for draw distance is entirely dependent on your own hardware; you will need to experiment to find what works best for you.)

In some cases, worn mesh attachments will not render properly still. Go to Preferences→ Graphics -> Rendering and disable both of the Alpha Mask Rendering options.

There are also rare instances of glitches where mesh that you are wearing appears worn by another avatar (yes, it is bizarre!). In that case, try going to Preferences → Graphics → General, and enable Hardware Skinning.

In some cases, low-end graphics cards or very old graphics drivers may require you to turn hardware skinning off rather than on. Before doing this, please try updating your graphics drivers and review the other options on this page, as turning hardware skinning off may reduce your performance.

If you have Webroot SecureAnywhere Antivirus, see Webroot Issues. For other antivirus apps, see our Whitelisting Guide, and be sure to whitelist all parts of the viewer. This may need to be done from scratch each time you upgrade to a new version.

If mesh is simply slow to appear, but does appear eventually, that is not necessarily a problem with mesh itself; please work through this page: Slow Rezzing.

HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

If none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, type in Mesh2MaxConcurrentRequests and gradually decrease (not increase) the value. (If Advanced is not visible on the top menu bar, press Ctrl-Alt-D.) If it does not help, try increasing the value from the default. Under no circumstances should you increase this beyond 64. Please see this comment on a related JIRA ticket for an explanation of the possible drawbacks of increasing this setting. Additionally, we recommend returning it to default once the mesh you're trying to see is visible.

In most cases, this is due to the mesh item being made low LOD so as to reduce its land impact. You should never try to resolve this by increasing LOD above the maximum allowed in Preferences → Graphics → General (4), as that would result in greatly increased memory use, usually leading to a significantly increased rate of crashing. Rather, the issue is inherent in how the mesh item was made. So you either live with it, or replace the item.

This happens more frequently for those using ATI/AMD graphics and drivers, but has been seen occasionally with Nvidia graphics and drivers as well. Visit Graphics Glitches for ways to address this.

If you can see most mesh fine but a specific mesh item fails to render and/or displays a pyramid, triangle, or ducky when it's first worn or rezzed, then read on. This is caused by mesh that fails to load, and in many cases is a result of having too high a draw distance in the presence of a lot of complex mesh.

• Reduce draw distance significantly, then relog. That often clears the problem.
• If that doesn't help, reboot all your network hardware and then your computer.
• (If the problem occurs only on selected regions, it could simply be a symptom of region lag–see this page for information. In this case, there may be nothing you can do about it.)

If this still doesn't help, then:

• Back up your settings - see this page
• Wipe your settings manually, as explained in this page
• Log back in and see if the mesh renders correctly. If it does…
• Restore your settings (see the backup page above), then check the mesh again.

In Preferences → Graphics → General, make sure Basic Shaders and Hardware Skinning are enabled.

Modern mesh bodies and heads often use a lot of smaller pieces to make up the whole item, so parts can be hidden under clothing. Sometimes the rigging information for one or more of these pieces gets corrupted during download and stuck in the viewer's cache. Currently, the best way to fix this issue is to clear cache.

If certain mesh objects are invisible on Firestorm 5.0.11 on OpenSim grids, set the debug setting FSEnforceStrictObjectCheck to False. To change that setting, go to top menu, Advanced (Ctrl-Alt-D to enable Advanced, if it isn't), Show Debug Settings. Type in FSEnforceStrictObjectCheck, set to False, then close the DebugSettings window.
On OpenSim grids, mesh should never be uploaded using “Analyze”. Analyze should only be used on grids that support Havok.
On Firestorm 5.0.11, mesh uploaded with Analyze is likely to render invisible when FSEnforceStrictObjectCheck is set to true.
An in-depth discussion about this problem can be found here.

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*

On nous rapporte parfois que les attachements en “rigged mesh” deviennent soudain invisibles pour les autres avatars après une téléportation. Ce problème peut généralement être résolu en cliquant dans le menu Avatar > Avatar Health > Refresh Attachments. Si cela ne fonctionne pas, vous devrez vous déco/reco.

Pour réduire ce genre d'incident, assurez-vous que tous les articles en “rigged mesh” que vous portez sont attachés sur des points différents (attention à ne PAS attacher à un point réservé aux HUDs, ou bien vous serez le ou la seul(e) à voir cet article sur votre avatar). De nombreux créateurs ne modifient pas le point d'attachement par défaut qui est la main droite. Cela a pour effet de voir tous les articles en “rigged mesh” s'attacher sur le même point d'attachement, avec donc le risque aggravé de rencontrer ce problème. Donc lorsque vous portez une tenue, vérifiez chaque article en “rigged mesh” et s'ils sont attachés à la main droite, rattachez-les sur un autre point de préférence libre de tout attachement; après quoi détachez l'article pour que le point d'attachement soit sauvegardé.

Ceci est une conséquence du bug décrit ci-dessus. Lorsque vous traversez un grand nombre de régions ou que vous vous téléportez, certains de vos attachements deviennent “fantômes” de telle sorte que le viewer “croit” encore qu'ils sont attachés (donc vous les voyez sur vous dans le viewer), mais pour ce qui est de la région, les attachements en question sont détachés. Personne d'autre que vous ne les voit, et aucun de leurs scripts ne peuvent fonctionner.

Par la suite si vous ajoutez ou enlevez quelque chose que vous portez, il est possible que cela “rafaraîchisse” en quelque sorte le statut de vos attachements tel qu'il est pour la région. Lorsque ceci se produit, certains de ces attachements - voire tous - vous apparaîtront comme étant détachés.

Poru ceux qui comprennent l'anglais, voir : FIRE-22970 etFIRE-17998.

Il s'agit d'un incident assez courant : les modifications que vous avez effectuées sur un attachement, que ce soit en mode édition ou par le biais d'un “applier”, se trouvent annulées si vous crashez.

La cause en est la façon dont SL fonctionne. Les modifications faites sur les attachements ne sont enregistrées qu'après avoir détaché l'article, ou lorsque vous vous déconnectez. Afin d'éviter que cela ne se produise, détachez l'article et comptez jusqu'à 10 à chaque modification, puis rattachez l'article (ceci est également valable pour les modifications sur les parties masquées/visibles d'un corps en mesh).

Il est possible que les attachements que vous voyez portés par votre avatar ne s'affichent pas dans votre inventaire comme étant portés. Vous ne pouvez donc pas les détacher par un clic droit dans votre inventaire.

Nous suggérons plusieurs solutions. Essayez-les l'une après l'autre et dans l'ordre, jusqu'à ce que l'une d'entre elles fonctionne.

1. Cliquez droit l'attachement sur votre avatar > Detach.
2. Si cela ne fonctionne pas, allez dans une région low lag comme celle-ci, puis déco/reco au même endroit. Essayez ensuite de détacher soit de la manière habituelle, soit de la manière décrite ci-dessus.
3. En cas d'échec, essayez de remplacer votre tenue selon la procédure décrite plus loin.

Le problème est plus compliqué lorsqu'il s'agit du bridge. Si pour une raison quelconque vous vous apercevez que vous devez recréer le bridge mais que dans votre inventaire il ne semble pas être porté, vous devrez le forcer à se détacher comme ceci :

• Allez dans vos Préférences → Firestorm → Extras→ Enable LSL-Client Bridge et désactivez le paramètre.
• Allez dans l'onglet “Worn Items” de votre inventaire, et détachez - si possible - tout bridge apparaissant comme étant porté (“Worn”).
• Dans votre inventaire cherchez “LSL bridge, puis supprimez-les tous de votre inventaire et videz votre corbeille.
• Déconnectez-vous.
• Relancez le viewer mais ne vous reconnectez pas.
• Ouvrez les Préférences (Ctrl P) > Firestorm > General et réactivez le bridge.
• Reconnectez-vous à Hippo Hollow (ou à un endroit les scripts sont autorisés à s'exécuter).
• Votre bridge devrait se recréer automatiquement à la reconnexion.

Si par contre vous constatez qu'à la connexion les attachements se détachent puis se rattachent, parfois plusieurs au même point d'attachement, essayez la procédure suivante :

• Créez un dossier temporaire à un endroit de votre inventaire que vous retrouverez facilement
• Dans ce dossier placez une copie de votre skin, shape, de vos yeux système et et votre “baldbase” système - ajoutez un pantalon et un haut (pas de mesh, de scuplty ou de prims, utilisez les vieux articles !)
• Cliquez droit sur le dossier et sélectionnez “Replace Current Outfit” (pas “Wear”, pas “Add”), ou encore, faites glisser le dossier sur votre avatar.
• Reconnnectez-vous.
• Une fois connecté, vous pouvez porter vos tenues habituelles

Si vous constatez que des attachements disparaissent après une téléportation, (entièrement ou partiellement), mais uniquement pour vous (les autres continuent de les voir normalement), activez les écrans de TP s'ils sont désactivés : Preferences → Move & View → Teleports → Disable teleport screens : décochez cette case.

Si un attachement scripté (comme un HUD par exemple) ne fonctionne plus après une téléportation; il est possible qu'il se soit détaché pendant la téléportation. Vous le voyez sur votre écran, mais le serveur “pense” qu'il est détaché et donc les scripts ne s'exécutant plus. Essayez ceci :

• Détachez/rattachez l'article. Vous devrez peut-être vous déco/reco avant et/ou après.
• De plus, si le HUD s'attache au point “Center 2”, assignez-lui un autre point d'attachement HUD.Les attachements ontmoins de risque d'être détachés sur les autres points.

NB: Ceci s'apparente à ce bug (en anglais).

Voir ici pour voir ce qu'est le cache et comment il fonctionne.

Vider le cache de la façon suivante règlera certain types de problèmes de textures ou d'inventaire et est la procédure conseillée avant de se résoudre à des solutions plus rdicales comme la réinstallation du viewer.

• Aller dans les Préférences → Configuration → Dossiers
• Cliquez le bouton “Ouvrir” juste à côté du chemin “Emplacement du cache” . Une fenêtre d'exploration s'ouvrira, affichant le contenu de votre cache.
• Gardez cette fenêtre ouverte et déconnectez-vous, puis supprimez tout le contenu de ce dossier.
• Si vous n'arrivez pas à lancer le viewer pour ouvrir les Préférences, trouvez le dossier manuellement. Son emplacement par défaut est caché dans la plupart des systèmes d'exploitation. Pour le trouver vous devrez afficher les dossiers et fichiers cachés.
  Maintenant vous devez trouver le dossier du cache :

Continuez comme ceci :

• Reconnectez-vous avec Firestorm dans une région low lag (essayez Phoenix Support parcel ou une SIM d'eau Linden comme aich ou hatton).Dans votre fenêtre d'inventaire cliquez “Récent”.
• Attendez que votre inventaire aie entièrement chargé. On peut accélérer le processus, si nécessaire, en tapant des lettres au hasard dans la barre de recherche de l'inventaire ou en cliquant alternativement sur les boutons “Developper” et “Réduire”.
• Pendant que l'inventaire charge, ne vous téléportez nulle part, et n'essayez pas d'accéder quoi que ce soit dans votre inventaire, pas d'IMs, et ne naviguez pas sur internet.
• Reagrdez-le charger, tant que vous voyez “… articles récupérés” il est encore en train de charger.
• Une fois qu'il a terminé de charger, déconnectez-vous de SL et reconnectez-vous.
  

Nous ne donnons le conseil “videz le cache” que si le problème semble directement lié à une corruption de texture ou d'inventaire. Un cache plein est pratiquement toujours mieux qu'un cache vide. Videz le cache d'inventaire peut-être utile lorsque vous n'arrivez pas à faire charger votre inventaire, si les moyens habituels de le faire charger ne fonctionnent pas (voir Mon inventaire est incomplet).

A certaines occasions vous n'aurez besoin de vider que le cache de textures et non pas le cache entier (avec celui d'inventaire). Actuellement ceci ne peut être réalisé que manuellement. Si vous devez vider le cache de textures, déconnectez-vous puis supprimez entièrement le dossier texturecache. Si vous voulez vider tout le cache excepté le cache d'inventaire, ne supprimez pas les fichiers portant votre UUID ayant pour suffixe.inv.gz (il y en a un par avatar si vous avez plusieurs comptes SL).

Si vous voulez ne vider que votre cache d'inventaire, supprimez uniquement les fichiers portant votre UUID ayant pour suffixe.inv.gz** (il y en a un par avatar si vous avez plusieurs comptes SL).

A d'autres occasions vous aurez besoin de vider le cache entièrement, faites-le manuellement en ouvrant le dossier du cache à partir de Préférences > Configuration > Dossiers > Emplacement du Cache > Pressez le bouton Ouvrir juste après. Déconnectez-vous et supprimez totu le contenu du dossier de cache.

Normalement, tout devrait être maintenant revenu à la normale.

Windows 10 updates since March 2017 have resulted in users experiencing stalling or crashing at “initializing VFS”.

Firestorm Release 5.0.7.52912 addresses this issue, but you must do this additional step once you have installed the 64bit version:

1. While logged out of Firestorm.
2. Right click the desktop shortcut for the 64bit Firestorm → Properties → Shortcut tab.
3. In the “Target” text box, go to the end of the text, *add a space* and then add this exact text to the end: --noprobe.

"C:\Program Files\FirestormOS-Releasex64\FirestormOS-Releasex64.exe" --set InstallLanguage en --noprobe 

4. Click “OK” to apply to save changes and launch Firestorm using the Desktop shortcut. (Note that if you use the pinned application on your task bar, make sure you pin the shortcut, not the running viewer.)

For reference, see: https://jira.phoenixviewer.com/browse/FIRE-21109
[Windows 64bit] Windows 10 - Stuck on “Initializing VFS” after KB4015217 on Intel HD, Intel HD 2500 & Intel HD 4000 cards on 64bit viewers only.

Reminder to check directly with the Intel website for the most up to date drivers. https://downloadcenter.intel.com/

EN COURS DE TRADUCTION, MERCI DE VOTRE COMPREHENSION !

Windows 10 updates since March 2017 have resulted in users experiencing stalling or crashing at “initializing VFS”.

Firestorm Release 5.0.7.52912 addresses this issue, but you must do this additional step once you have installed the 64bit version:

1. While logged out of Firestorm.
2. Right click the desktop shortcut for the 64bit Firestorm → Properties → Shortcut tab.
3. In the “Target” text box, go to the end of the text, *add a space* and then add this exact text to the end: --noprobe.

"C:\Program Files\FirestormOS-Releasex64\FirestormOS-Releasex64.exe" --set InstallLanguage en --noprobe 

4. Click “OK” to apply to save changes and launch Firestorm using the Desktop shortcut. (Note that if you use the pinned application on your task bar, make sure you pin the shortcut, not the running viewer.)

For reference, see: https://jira.phoenixviewer.com/browse/FIRE-21109
[Windows 64bit] Windows 10 - Stuck on “Initializing VFS” after KB4015217 on Intel HD, Intel HD 2500 & Intel HD 4000 cards on 64bit viewers only.

Reminder to check directly with the Intel website for the most up to date drivers. https://downloadcenter.intel.com/

This window is used in contexts where you need to select a resident, for example:

• to send an invitation to join a group.
• to add someone to your parcel access list.

The Avatar Picker window has four tabs, which allow you to search for people in different ways.

Type the partial or full name of the Resident you wish to choose (a search query must be at least three characters), then click Go to search. A list of top possible matches appears below the search field.

You can enter a partial match for first or last name. For example, if you enter “J Lin”, all results include a first name beginning with “J” and a last name beginning with “Lin”, such as “Jeremy Linden” and “Jon Linden”.

Use this if the Resident you wish to choose is already on your Friends list.

If you've recently added a friend but they aren't showing up here, click the refresh button.

Use this if the Resident you wish to choose is nearby.

• Range: Drag this slider to the left to decrease the range of Residents in proximity, and drag it to the right to increase the range. Goes from 5 to 130 meters.

Click the refresh button if Residents who have just entered your chosen range aren't showing up as expected. Changing the range also refreshes the list.

Handy if you have an avatar UUID but not the name. Put the UUID into the text field, click Go. If the UUID is valid, you will get an avatar name in the list below. If you're happy with that, click Select at the bottom.

Pour une introduction au diagnostic des pannes de base, référez-vous à cette page.

Il existe des vidéos-tutoriels sur YouTube; visitez et ajoutez à vos favoris : Phoenix Viewer channel.

• Firestorm 64-bit

• Crash pendant l'Installation ou au démarrage

• Crash pendant l'Exécution de Firestorm

• Impossible de se Connecter

• Message d'erreur "Texture Discarded Due to Insufficent Memory"

• Problèmes graphiques et crashes - Versions plus anciennes de Firestorm

• Faire une installation propre

• Comment vider le cache manuellement

• Effacer ses paramètres manuellement

• Problèmes de Media / vidéo

• La Recherche ne fonctionne pas, la Fenêtre Reste Noire

• Problèmes de Voice

• Problèmes de Bridge

• La camera pointe n'importe-où

• Amis/Groupes Détachés des Conversations

• Firestorm "verrouille" sur "Initializing VFS"

• Main qui Clignote

• Problèmes avec les Mesh

• Je ne peux me connecter que si je vide d'abord mon cache

• Cliquer sur une SLURL N'ouvre Pas Firestorm

• J'ai Fait Glisser Quelque Chose Dans le Dossier de l'AO et Je ne Peux Pas l'Enlever !

• My Friends List is Empty!

• The Viewer Seems to Freeze Every So Often

• How do I Get Rid of all this Debug Stuff?

• Trouver une fenêtre manquante

• Issues Related to Shadows

• Large Flexi Prims, Like Tree Fronds, Vanish

• Objects Vanish

• Small Prims Vanish Even when Quite Close

• Making WindLight Setting Persist after Teleport

• How do I Derender/Re-render things?

• When I log in, I see a Blue Screen - I am at 10, 10, 10

• Les Attachements de Détachent Puis Se Rattachent A La Reconnexion

• Mes pieds s'enfoncent dans le sol ou je flotte

• Mon inventaire est incomplet

• Help! I'm Wearing my Entire Inventory!

• Résoudre les problèmes d'apparence - Nuage, Ruth, Vêtements qui ne chargent pas

• I Can't Log In Because It Says I am Already Logged In

• Persistent Typing Animation

• Stuck Inventory Folders Work-Around

• Pourquoi les téléportations ne fonctionnent-elles pas?

• Problèmes de HUDs qui ne fonctionnent plus

• Problèmes d'attachements liés aux serveurs

• Script trying to trigger animation but PERMISSION_TRIGGER_ANIMATION permission not set

• Régler votre Bande Passante Correctement

• Problème de protocole HTTP (HTTP Fetching)

• I See Everything Grey

• Pourquoi tant de lag ?

• Tout est noir

• Intel Graphics Issues

• I See Things Like Stars in the sky

• My CPU is Always at 100%

• Problèmes cartes ATI

• Laptop Optimus Issues

• Problèmes spécifiques à Windows 10

• Viewer Not Responding - Vista/Win7 64-Bit

• "Display driver stopped responding and has recovered" error in Windows

• I Get a User Account Control (Security) Pop-up

• Frame Load Interrupted by Policy Change

• Copy/Paste No Longer Works

• Clicking on a Link in Firestorm Causes a Crash

• Error Importing itdownload.dll

• Firestorm Flagged as a Virus or Malware

• Mac OS X 10.5 Leopard Problems

• Problème sur Mac OS X 10.9 Mavericks

• Linux: Left Mouse Button Stops Working

• Alt-Click Not Working on Ubuntu

• Firestorm on Ubuntu 13.10 64-bit

• DNS Fail when Trying to Log in

• I Can't Sit on Things

• How to Get Inventory Back

• Gesture Issues

Si vous avez certaines puces Intel HD, et que vous êtes passé à Windows 10, votre dispositif graphique ne sera pas entièrement supporté par Intel. Si vous rencontrez ce problème, vous n'arriverez pas à vous connecter. Vous obtiendrez le message d'erreur suivant :

Firestorm is unable to run because your video card drivers did not install properly or are out of date, or are for unsupported hardware.  Please make sure you have the latest video card drivers, and even if you do have the latest, try reinstalling them.  If you continue to receive this message, contact the Second Life Support Portal

Il ne s'agit pas d'une fonction du viewer, mais plutôt une fonction des pilotes fournis par Intel pour votre ordinateur. Cependant, nous avons trouvé une parade qui devrait aider la plupart des utilisateurs à continuer d'utiliser le viewer Firestorm.

1. Vérifiez que votre carte graphique est l'une des versions affectées. Vous en trouverez un tableau ici :Graphics Drivers Supported Operating Systems, sachant que le plus souvent ce sont les puces Intel HD 2000 et Intel HD 3000 que nous avons vues affectées par ce souci. Les infos système de votre ordinateur vous indiquent votre périphérique graphique.
2. Ci-dessous,sélectionner le fichier zip correspondant à votre version téléchargée - soit la Havok 32-bit , soit la OpenSim 32-bit - et téléchargez-la. Vous devrez dézipper le fichier et l'enregistrer sur votre ordinateur à un endroit dont vous vous souviendrez.
3. Sur votre ordinateur, ouvrez votre Explorateur de Fichiers. (S'il n'apparaît pas dans votre barre des tâches vous devrez utilser la recherche Windows pour le trouver). Sélectionnez l'onglet “Affichage” en haut de la page et dans “Afficher/masquer” cochez la case “Extensions de noms de fichiers”.
4. Dans l'Explorateur de Fichiers, naviguez jusqu'à “Cet Ordinateur”vpuis séléctionnez votre Disque (C:) (ou l'endroit dans lequel vous installez habituellement Firestorm s'il est différent) puis naviguez jusqu'à Program Files (x86). Ouvrez Program Files (x86), localisez le répertoire Firestorm et ouvez-le. Dans lce répertoire Firestorm, trouvez le fichier Firestorm-Release.exe et supprimez-le.
5. remplacez-le par le fichier Firestorm.exe qui set rouvait dans le fichier zippé que vosu avez téléchargé sur le site web.

Vous devriez maintenant pouvoir utiliser Firestorm sur votre PC.

• Havok SL
  SHA-1: 035B4C3B6896CDB5CEEB2B688207EC45E1B46152
• 32-bit non-Havok OS
  SHA-1: CC5EE45EF344E4CED98E683BD5BC86F45767AAE3

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

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

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

If you 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 are on Windows 10, and get an error such as this:

First, make sure your drivers are fully updated

• Visit Intel and try to update your drivers there.
• An additional resource for certain Intel graphics is this Microsoft list of drivers for Intel(R) HD Graphics.

If this does not help, then refer to our fix for outdated Intel graphics.

If you are on Windows 10, and get this error:

This is a known issue with recent Intel graphics drivers, affecting other graphics applications besides SL viewers.

• Many people have received this graphics driver update without realizing it.
• The problem sometimes appears after a crash.
• Many users on HP laptops with OEM drivers are having this problem, although it is also affecting others.

What to do:

• Try rolling back to a previous driver that worked for you.

1. Method 1 https://www.intel.com/content/www/us/en/support/graphics-drivers/000008628.html for instructions. If the Roll Back Driver button is grayed out; see
2. Method 2 FIRE-21264 Roll Back Driver Steps

• If you are unable to rollback to older drivers, contact your laptop manufacturer for support. Here's a list of sites if you need it https://www.intel.com/content/www/us/en/support/topics/oems.html?wapkw=manufacturer+support Explain the issue, and tell them you need Windows Graphics Driver Version: 21.20.0016.4627, OpenGL Version: 4.2.0 - Build 21.20.16.4627 which is the last known non-buggy driver.

• Some users have reported that the following newer driver fixes the problem: Intel® Graphics Driver for Windows* [15.46] Version: 15.46.05.4771 (Latest) Date: 8/23/2017. Download from https://downloadcenter.intel.com. This driver may or may not be available to you depending on your computer.

• Workaround: Run the viewer in Full Screen Mode. Preferences → Graphics → General → Fullscreen Mode, then relog.

More information: Please refer to FIRE-21264 for more information and to report any additional details about the issue.

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 2000 or 3000 graphics, refer to this page.

If your laptop has an Intel CPU and also has either an AMD or Nvidia graphics system, it may have the ability to switch between the Integrated Intel graphics (for power savings) and the AMD/Nvidia (for performance). But sometimes Firestorm isn't automatically configured to use the high-performance graphics.

You can confirm this issue by looking at Help → About Firestorm and checking the name of the graphics card listed. If it says Intel, please follow the steps on this page.

This mysterious flashing problem has been reported numerous times now and after some investigation we believe we finally have a repro for what's causing the issue. We do not yet know the specifics of exactly which systems are affected.

Typically the issue arises when Worn Rigged Mesh is in view and has at least one texture containing alpha and set to alpha blend mode. Alpha masking and emissive mask do not reproduce the problem.

We have also verified that this reproduces using the Official LL Viewer.

The Following Table shows which systems and drivers we have tested and whether they reproduce the Flashing Issue.

The Driver Version linked in the above table (DRIVER VERSION: 15.40.14.64.4352 & 15.40.14.32.4352) Has not reproduced the issue for us and is the Driver we recommend that you download direct from Intel.

If you receive the following Message when installing the Intel Driver:

• Check the website (or contact support) of your specific PC manufacturer and check for updates.
• Uninstall the OEM Driver and install the Intel Driver direct from Intel. This method is carried out At Your Own Risk

If decide to wait for an update from your computer manufacturer, or are simply uncertain about removing an installed driver, the following steps may help to make things more tolerable for you until your drivers are updated.

• If ALM is disabled the flashing will always reproduce unless Hardware skinning is disabled.
• If ALM is enabled the flashing will only reproduce when the avatar wearing the alpha blended rigged mesh is standing in Linden water.
  • If Hardware Skinning is disabled, the flashing stops in this case too.

Note: If you install the recommended driver above and still experience issues please read the related jira FIRE-17290 and add your details to the comments. Instructions for using the Jira can be found HERE

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 “Configurer les graphiques commutables”
• 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 :
  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
• Faites un double clic sur l’application
• Si vous avez à la fois une version 32 et 64 bits de Firestorm, recommencez la procédure pour la 2ème version.
• Une fois Firestorm affiché dans le panneau de contrôle AMD, le bouton à droite sur la ligne permet de sélectionner le mode haute performance.
• 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.

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

If you 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 are on Windows 10, and get an error such as this:

First, make sure your drivers are fully updated

• Visit Intel and try to update your drivers there.
• An additional resource for certain Intel graphics is this Microsoft list of drivers for Intel(R) HD Graphics.

If this does not help, then refer to our fix for outdated Intel graphics.

If you are on Windows 10, and get this error:

This is a known issue with recent Intel graphics drivers, affecting other graphics applications besides SL viewers.

• Many people have received this graphics driver update without realizing it.
• The problem sometimes appears after a crash.
• Many users on HP laptops with OEM drivers are having this problem, although it is also affecting others.

What to do:

• Try rolling back to a previous driver that worked for you.

1. Method 1 See How to Roll Back Your Driver to a Previous Version for instructions. If the Roll Back Driver button is grayed out; see
2. Method 2 FIRE-21264 Roll Back Driver Steps

• If you are unable to rollback to older drivers, contact your laptop manufacturer for support. Here's a list of sites if you need it Computer Manufacturer Support Websites Explain the issue, and tell them you need Windows Graphics Driver Version: 21.20.0016.4627, OpenGL Version: 4.2.0 - Build 21.20.16.4627 which is the last known non-buggy driver.

• Some users have reported that the following newer driver fixes the problem: Intel® Graphics Driver for Windows* [15.46] Version: 15.46.05.4771 (Latest) Date: 8/23/2017. Download from https://downloadcenter.intel.com. This driver may or may not be available to you depending on your computer.

• Workaround: Run the viewer in Full Screen Mode. Preferences → Graphics → General → Fullscreen Mode, then relog.

More information: Please refer to FIRE-21264 for more information and to report any additional details about the issue.

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 2000 or 3000 graphics, refer to this page.

If your laptop has an Intel CPU and also has either an AMD or Nvidia graphics system, it may have the ability to switch between the Integrated Intel graphics (for power savings) and the AMD/Nvidia (for performance). But sometimes Firestorm isn't automatically configured to use the high-performance graphics.

You can confirm this issue by looking at Help → About Firestorm and checking the name of the graphics card listed. If it says Intel, please follow the steps on this page.

This mysterious flashing problem has been reported numerous times now and after some investigation we believe we finally have a repro for what's causing the issue. We do not yet know the specifics of exactly which systems are affected.

Typically the issue arises when Worn Rigged Mesh is in view and has at least one texture containing alpha and set to alpha blend mode. Alpha masking and emissive mask do not reproduce the problem.

We have also verified that this reproduces using the Official LL Viewer.

The Following Table shows which systems and drivers we have tested and whether they reproduce the Flashing Issue.

The Driver Version linked in the above table (DRIVER VERSION: 15.40.14.64.4352 & 15.40.14.32.4352) Has not reproduced the issue for us and is the Driver we recommend that you download direct from Intel.

If you receive the following Message when installing the Intel Driver:

• Check the website (or contact support) of your specific PC manufacturer and check for updates.
• Uninstall the OEM Driver and install the Intel Driver direct from Intel. This method is carried out At Your Own Risk

If decide to wait for an update from your computer manufacturer, or are simply uncertain about removing an installed driver, the following steps may help to make things more tolerable for you until your drivers are updated.

• If ALM is disabled the flashing will always reproduce unless Hardware skinning is disabled.
• If ALM is enabled the flashing will only reproduce when the avatar wearing the alpha blended rigged mesh is standing in Linden water.
  • If Hardware Skinning is disabled, the flashing stops in this case too.

Note: If you install the recommended driver above and still experience issues please read the related jira FIRE-17290 and add your details to the comments. Instructions for using the Jira can be found HERE

Il vous sera parfois utile d'accéder à vos fichiers cachés. Voici des liens à des articles sur la manière de procéder.

• Windows XP
• Windows Vista
• Windows 7
• Windows 10

• Mac OSX Lion& Mountain Lion
• Mac OSX Mavericks
• Mac OSX Yosemite
• Mac OSX Sierra

• linux