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

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.

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

Firestorm 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/

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

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

Other things to try:

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

• make sure FS AO is off
• remove attachments (Note: animations can be in ANY attachment)
• reset skelly & anim
• stop anims & revoke perms

lag

conflicting AOs

• try turning the opposite direction to the spin
• try pressing BOTH right and left arrow keys at the same time, repeatedly
• relog

Possible bridge problem: recreate bridge

Possible bridge problem: recreate bridge

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

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

This window opens when you select, from the top menu bar, Avatar → Upload → Import Linkset, or Build → Upload → Import Linkset.

It allows you to import objects which you have previously exported. For more general information on exporting and importing, see here.

First click on the Choose File button, which opens the file picker window so you can browse to the file you wish to import.

Once the file has been selected, you can specify import options:

• Do not attach object: Enable this if you do not wish to automatically wear objects that were exported while worn.
• Restore Region Position: Create the imported object at the same region coordinates at which it was exported.
• Upload: Upload any associated content (textures, notecards, scripts…) as well; this has a L$10 cost per texture.
  Note that if you disable this, but already have the textures in your inventory, the object will have the textures correctly applied - since you own the texture referenced by the UUID.

Click the Import button to start the import. The object will be created near you - unless you are importing an attachment, in which case it will automatically attach once created.

Closing the Import window before import has completed, may crash you, so don't do that.

• Onscreen console font size: Choose Small, Medium, Large or Huge

• Play avatar animations (such as shouting): Animates your avatar for some standard actions.
• Wrap system chat messages in brackets: makes system messages distinct by enclosing them in brackets.
• Show “You” in chat transcripts instead of your name: Replace your name in transcripts.
• Emotes use italic font: Makes emotes show in italics.
• Bold Shouting, Italicize whispering: If enabled, emphasises shouting and whispering, as the option indicates.
• Mark objects with (no name) when they speak to avoid spoofing: This allows object names in chat to be clicked, so that you can get information about them (creator, owner, etc). Useful in griefing situations.
• Route llOwnerSay to script debug window:llOwnerSay script output is sent to the script debug window rather than being shown in console, on screen.
• Show chat in bubbles above avatars: puts local chat in bubbles above users heads.
  • Don't show chat in Nearby Chat console and toasts: Prevents chat from showing in console and toasts (only available if the above option is enabled; greyed out otherwise).
• Show typing indicator in bubbles above avatars: This will show something like a chat bubble but only when another avatar is typing; it gives a visual indication that someone is typing. The text itself will appear according to your settings.
• Show typing indicator in nametag above avatars: Similar to the above, but the indicator appears in the nametag instead.

• Show seconds in timestamps: adds seconds to the timestamps.
• Show timestamps in: You can select whether to show timestamps in…
  • Nearby chat
  • IMs
  • Transcript

• Use classic draw mode for console: Changes the chat console ¹⁾ background to surround all visible text instead of displaying separate backgrounds per line of chat.
• Use full screen width for console: Will allow the chat to be the full width of the screen (requires restart).
• Fade chat after _seconds __ # lines: Allows you to choose how long, and how many lines show in the chat console.

• Chat window font size: Choose Small, Medium, Large or Huge

• Show names in direct IMs: If this is disabled, user names are not shown on each line in IMs.
• Use V1 style chat headers: Makes chat look like V1 style chat. With this unchecked, chat headers will appear as horizontal bars across chat windows, with text underneath. With it checked, timestamp and name will precede text on the same line.
• When using V3 style chat headers, show mini icons: shows the icon in the IM/group chat next to the name. If Remove chat headers is enabled this will not show even if enabled.
• Show the end of the last conversation: If enabled, the last few lines of the last conversation will be shown in IM windows. This requires that chat transcripts be enabled in Preferences→ Privacy → Logs & Transcripts.
• Add additional chevron (>) as typing indicator to IM sessions: This depends on the other person having enabled Send typing notifications to other avatars during IM sessions. If they have, then you will see a chevron when they are typing.

• Show new message notification for: If you have scrolled up in a chat window, and a new message has arrived, you can be informed of this, by enabling one or both of:
  • Nearby chat
  • Instant and group messages.

• Show IMs in: (requires restart)
  • Separate windows
  • Tabs

• Chat tab orientation: (requires restart)
  • Horizontal (along the bottom of the Conversations window)
  • Vertical (down the left side of the Conversations window)

• Name format for IM tabs: If you have both display names and user names enabled in Preferences -> General, then you can select what names you want display in IM chat tabs:
  • Display name
  • Username
  • Display Name (Username)
  • Username (Display Name).

• Enable group moderator message highlighting: This option will make text posted by group moderators stand out in group chat, so you can easily tell which poster has moderator rights. Two options may be combined (you may enable either one, or both):
  • Name Style: You can opt to have moderator names highlighted in one of several text styles, such as bold, italic, etc.
  • Text Style: You can also specify a style for the etxt that apepars in chat after the moderator name.
• Disable ALL group chats: Prevents group chats from opening automatically when another user IMs the group.
  Note: The viewer will still receive group chat with this option turned on when an IM/Group Chat tab is open for the group in the Conversations window. What the option does is prevent the automatic creation of a tab when a group message is received.
• When “receive group notices” is disabled, disable group chat as well: Turns off group chat from any group from which you are not receiving group notices.
  Note: Group text chat may now be disabled independantly of group notices, in the groups profile window.
  Note: The viewer will receive group chat with this option turned on when an IM/Group Chat tab is open for the group in the Conversations window. What the option does is prevent the automatic creation of a tab when a group message is received.
• Automatically ignore and leave all conference (ad-hoc) chats: Shuts down any conference chats in which you are included.
  • Report ignored conference chats in nearby chat: Informs you that a conference chat was ignored.
    The name of the person is shown, and may be clicked in nearby chat to bring up their profile.
  • Don't ignore conference chats invitations from my friends: overrides the automatically ignore settings for conferences started by those on your friends list.

• Group Chat Snooze Duration: Length of time a group chat will be muted when clicking the Snooze button. Setting this to zero will simply close the group window until the next group message arrives.
  Note that any chat which occurs during the “snooze” period will not be logged - should you have logging enabled.
• Set group chat snooze duration individually per group: If enabled, when you snooze a group chat, a window will open asking how long to snooze the chat for.

• Auto-Replace: Opens the Auto-Replace Settings window where you can define word replacement. Useful as an auto correct feature, for example.
• Spell Checking: Opens the Spell Checker Settings window.
• Translation (button): Opens the Chat Translation Settings window, where you can specify if you want chat to be translated, and which service to use.

• Play typing animation when chatting: Your avatar will play the typing animation when chatting in local with this enabled.
  • Play typing animation also when emoting: If the above is enabled, then this option will have your avatar play a typing animation when using emotes.
• Hear typing sound when people type in local chat: If enabled, you will hear the sound of typing
• Send typing notifications to other avatars during IM sessions: If enabled, this will show “xxx is typing” in IMs. It can also trigger the other person's IM to open before you actually send the IM text. (See Announce incoming IMs as soon as the sender starts typing below.)
• Enable auto-completion of gestures in nearby chat bar: If this is enabled, then typed gestures will auto-complete as typed.
• Enable automatic name prediction in nearby chat bar: When this is enabled, the viewer will attempt to autocomplete a name based on the names of those near you.
• ”:” as a synonym for ”/me”: Used in Role Playing. Allows use of ”:” instead of ”/me” to indicate an action, instead of a statement. For example; ”:nods in agreement” appears as “John Doe nods in agreement”. (NOTE: No space after the ':'.)
• Auto-close ((OOC)) parentheses: Used in Role Playing. When entering message in RP mode, it is assumed they are speaking as their character. To communicate something outside of their character, they enclose their message with “((” and “)) ”.
  When checked, the viewer automatically appends a ”))” to a message if it isn't present. For Example ((This is OOC“ results in ”((This is OOC)) “.
• Show send chat button in the chat bar for IM sessions: Adds a “Send” button at the right end of the chat bar in IM and group chat windows.
• Add a chatbar in the Nearby Chat window: As the name implies.
  • Show channel selection in chat bar: Enables the channel selector in the nearby chat bar.
  • Show chat type / send chat button in chat bar: Adds a button to the right of the nearby chat bar; you can click this to send chat, and you can select whether to say, whisper or shout.
• Autohide Main chatbar: If this is enabled, then the chat bar at the bottom if the screen will close after you have typed something. Starting to type anything again will cause it to reopen.
  Note that if both the WASD selection in Pressing Letter Keys (above) and Autohide are enabled, you will need to hit Enter/Return before you begin typing in an autohidden chat bar.
• Deselect Chat after sending Messages: Will move the cursor out of the chatbar after you send a message.
  • De-focus chat history as well: Will also remove focus from the nearby chat history window.

Here, you can enable/disable three special shortcuts:

• Ctrl-Enter - Shout
• Shift-Enter - Whisper
• Alt-Enter - OOC

• Enable incoming chat popups: Allows Group and/or IM chats to appear onscreen, in either console or toasts, whichever is set below.
  • Group Chats
  • IM Chats

• Use console for chat popups instead of floating toasts (Viewer 1.x style): Displays chat in the onscreen left-hand console rather than in bottom-right toasts
  • Show IMs in chat console: Will show IMs in the chat console; this is on the lower left of the screen, not in the communication window.
  • Show group chat in chat console: Will show group chat in the chat console; as noted above, this is on the screen, not in the communication window.
  • Length of group name to be printed in chat transcripts:
    • Setting '0' turns it off.
    • Setting '-1' shows the full group name.
    • Setting '1 or higher' shows the group name truncated to how ever many characters are set here, the '[' and ']' aren't counted.

• Open Conversations when an offline mesage has been received: Normally, any offline messages you get will be shown as chiclets when you log in. If you enable this, the Conversations window will also open to show the text of the messages.
• Email me IMs when I'm offline: will send any offline IMs to your email that you have on file with LL
• Show IMs in nearby chat window: Shows the text of received IMs in the nearby chat window.
  • Save IMs in nearby chat: Enable logging of IMs along with local chat; requires that local chat be logged, which can be enabled in the Privacy -> Logs & Transcripts tab.
  • Fade IM text into the background of the chat transcript window: 0.25 for most faded, 1 for no fade.
• Show number of unread IMs in Firestorm's window title: Displays a count of unread messages in the window title bar.
• Announce incoming IMs as soon as the sender starts typing: If enabled, your IM window will open and beep as soon as someone starts typing a message to you, rather than after they complete and send the message.
  Note that this will not work if the person IMing you has disabled Send typing notifications to other avatars (above).
• Flash IM tabs when friends come online or go offline: visually notifies you when friends log in or out; most useful during IM conversations.
• Flash chat toolbar button if new nearby chat arrives: The nearby chat window must be docked to the conversations window, and this must be closed for the button to flash.
• Flash chat toolbar button if new IM arrives: The IM window must be docked to the conversations window, and this must be closed for the button to flash. also, this option is only available if IMs are shown in tabs, rather than separate windows; see the setting in Preferences→ Chat -> Chat Windows.
• Report muted group chat in nearby chat: If chat starts in a group which you have “muted”, a message to that effect will be displayed in nearby chat.
  Group chat can be “muted” (disabled) in the groups profile window.
• Show group notices in group chats, in addition to toasts: If enabled, the text of group notices is displayed in the group chat window.
  • Show their subjects and authors as well: Also shows the title and sender of notices in group chat.

• Radar reports when avatars enter/leave chat range: Will show in nearby chat when an avatar enters or leaves chat range.
• Radar reports when avatars enter/leave draw distance: Will show in nearby chat when an avatar enters or leaves your draw distance.
• Radar reports when avatars enter/leave the region: Will show in nearby chat when an avatar enters or leaves the region.

Each of the above can, optionally, play an alert sound, which you can change by specifying your own sound clip UUID. You an hear the sound by clicking the button labelled 'P', or revert the sound to the default by clicking the 'D'.

Note that the names shown by radar, in the nearby chat window, can be clicked to open a profile.

• Report enter/exit alters to scripts: This is the same function that is available from the People panel gear menu. It will output radar information to user scripts. For more information, refer to this page.

• Enhance radar with LSL-Client Bridge: If this is enabled, radar functions responsible for determining avatar locations at high altitudes are assisted by the LSL bridge, particularly when they are beyond draw distance.

• Age Alert: You can also be alerted to avatars who are “younger” than a certain number of days.
  • Threshold: Set the age in days.
  • Radar reports avatars younger than the specified age: Enable to be alerted.
    again, you can specify your own alert sound by giving a valid sound UUID.

• Enable Keyword Alerts: Enables using Keyword Alerts.
• Look for Keywords in Local Chat: When checked, the alert system monitors Local Chat for the presence of these keywords.
• Look for Keywords in IMs and Group Chat: When checked, the alert system monitors the IM and Group Chat areas for presence of these keywords.
• Check sender's name for keywords: Look for keywords in the names of speakers or objects as well.
• All keywords are case-sensitive: Enable this if you want (for example) Apple to be treated differently from apple.
• Only match whole words: Enabling this will prevent an alert from being generated on partial matches. For example, if you have an alert on the word frank, you will not be alerted if someone types frankly.

Note: Because Group Chats are prevented from appearing when either When Receive Group Notices is disabled, Disable Group Chat As Well or Disable All Group Chats are enabled (see above), no alerts are triggered.

• Keywords (separated by commas): Specifies the list of words that will trigger an alert. They can be individual words or phrases and are separated by commas.
• Enable Color Alert: When checked, any messages that are to be alerted will have their color changed to what is specified in the color selector.
• Play alert sound: Enables playing a sound, identified by the UUID:
• Alert Sound UUID: Supply the alert sound UUID here. A default is given. To get a new UUID, find a sound in your inventory with full permissions (you can view the item's properties to check this), then right-click the sound and select Copy Asset UUID from the menu. Then paste the value into the text box.

See this page for a tutorial video.

• Enable usage of chat bar as a command line: If this is enabled, all the commands given below (except where noted) will be available for use.

All of the commands below can be changed from the supplied defaults.

• Calc. expressions (calc): Used to perform a calculation on the command line to figure out an answer quickly. Calculations adhere to precedence rules where multiplication/division occur before addition/subtraction. Therefore, example: “calc 1.3+2*5” results in “11.3” as the answer, because the multiply occurs before the addition.
• Change Draw Distance (dd): Changes the draw distance of the rendered view to the specified number of meters. Example: “dd 32” sets the draw distance to 32 meters.
• Max. Bandwidth (bw): Change your current maximum bandwidth. This is set in Preferences→ Network & Files -> Connection.
• Copy camera position to clipboard (cpcampos): Saves the current camea position in the clipboard, from which it can be pasted into a script, for example.
• Turn AO on/off (cao): Turns the embedded AO system on/off. Example: “cao on” turns AO on, and “cao off” turns AO off.
• Clear the chat transcript (clrchat): Clears the chat history from local chat. Example “clrchat”
• Set the media url (/media): Sets the video media for the parcel as identified by the URL. Only the land owner can set the media URL. If the URL contains a space, use to identify the space. The type is one of: Audio, Image, Movie or Web.
• Set the music stream url (/music): Sets the music stream for the parcel as identified by the URL. Only the land owner can set the music URL. Example: “/music http://scfire-dtc-aa04.stream.aol.com:80/stream/1010” sets a Smooth Jazz sound to the URL.
• Rez a platform (rezplat): Assuming the avatar has build privileges in the parcel, this command rezzes a circular platform of the given diameter beneath the avatar. Example: “rezplat 25” rezzes a 25m diameter platform below the avatar.

• Get avatar name from key (key2name): Looks up the specified avatar key and returns the name for the key. Example: “key2name” returns “Babbage Linden”.
• Roll dice (rolld): For role play. Use by typing rolld <number of dice> <number of faces> in nearby chat. Examples:
  rolld is a regular dice with 6 faces.
  rolld 1 20 is a single dice with 20 faces.
  rolld 3 10 is 3 dice, each with 10 faces.
  Bonuses, penalties, successes and explosions modifiers can also be added to the command; for more, refer to this page.
• Teleport within sim (gtp): Teleport to anywhere within the region instantly according to the position specified. Example: “gtp 45 150 400” teleports to 45, 150, 400.
• Teleport to ground (flr): Teleport to the current ground position for the avatar's current position.
• Teleport to altitude (gth): Teleport to the specified height. Example: “gth 2800” teleports to a height of 2800 meters. It is also possible to teleport higher. Example: “gth 6500” teleports to 6500m above the region.
• Teleport to cam position (tp2cam): Teleports the avatar to the position the cursor is currently looking at. This is useful when walking into a store. After looking around and finding the item to purchase, this shortcut takes you to the position immediately, without having to walk. Example: “tp2cam”.
• Offer teleport to avatar (offertp): Sends a teleport request to the avatar identified by the given key. Example: “offertp avatar-key”.
• Teleport to avatar (tp2): Finds a given avatar within the region and teleports to them. Example: “tp2 John Doe” teleports to “John Doe” if they are in the region.
• Teleport home (tph): Teleport home. Same as hitting Shift-Ctrl-H.
• Teleport to sim x (mapto): Teleports to the region you specified (defaults 128, 128, 0 if no landing point is specified on the region). Must use the full region name, with spaces and all.
  • Use same position between sims: When enabled, your entry point at the new region will be the same coordinates you left at the old region, unless a landing point is specified in the new region.

NOTE: In the commands above, the word “sim” is used in some places because the the viewer is still worded this way currently. The correct term should be “region” in all cases.

There are a few other commands which are not shown here (and therefore cannot be changed). These include:

• /zoffset_up: Offset your avatar upward by 0.05.
• /zoffset_down: Offset your avatar downward by 0.05.
  These can be used in gestures, perhaps assigned to the PgUp and PgDn keys respectively.
• zdrop, ztake, mtake: Refer to this page.

If you're looking for how to get your own event in the Firestorm Message of the Day, click here.
If you're looking for a missed MotD or more information on the current MotD rotation, keep reading!

Oh hi! I didn't see you come in! You're probably here because you missed the message of the day. It went by too fast, it was too long, or you clicked a link in a goofy motd set up to get you here!

Anyway, if you missed the message of the day and would like to see it again;
At the top of your screen find the “Content” menu and click it.
In the menu that drops down, way down at the bottom select, “Message of the Day”.

There it is, in your local chat as a system message.

[11:28:02] [Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd]

You can also scroll down this page and see ALL the current messages of the day in the “events, tips, help and gateway” message of the day rotation. (I keep this page bookmarked as a fast reference to important wiki pages.)

The Firestorm Message of the Day is currently running on a rotation of thirty eight preset tips, help, gateway and fun messages and/or a varying amount of event messages of the day. All of which are displayed at random when you log in depending on which “MotD Cartridge” is loaded. Go ahead, try it, relog, and unless the message of the day is promoting a special event¹⁾ you'll see something different.

The preset messages of the day are split between tips to make your Firestorm Viewer experience more efficient and enjoyable, help topics to help resolve common Firestorm Viewer issues, gateway to spread information about the Firestorm Gateway and fun just because.

I'll list the message of the day presets below so you can see what's in the rotation.

These are the current messages of the day for events which are currently running and have been approved for a Firestorm message of the day;

MOTD: EVENT: Forgotten Gatcha New User Pet Gifts
New to SL and feeling lonely, overwhelmed or confused with it all? Come get your personal pet for the holidays to keep you company while exploring! Get them here till they run out! https://wiki.phoenixviewer.com/pets_for_new_residents

MOTD: EVENT: RFL Home, Garden & Breedable Expo 2019
RFL Home, Garden &amp; Breedable Expo 2019 running now through April 7th! 10 regions packed with stores and mansion displays, with stores selling furniture and furnishings, building tools, plants and vegetation and so much more! https://slhomegardenexpo.com/

These are displayed randomly and are broken down into five groups;

Security: Keep your Second Life account and your computer safe!

Release: What's the current Firestorm release version and where do I get it?

Tips: Which provide tips on how to get the most out of the Firestorm Viewer and are meant to improve your Second Life experience in some way.

Help: Which provide assistance on self resolving common Firestorm problems which are seen the most in the Firestorm Viewer help groups. These may have also been requested by the Firestorm Support Team at some point.

Gateway: Coming soon! These provide information on what's going on at the Firestorm Gateway, events, event spaces, classes and more.

I'll break them into the same groups below;

MOTD: SECURITY: Firestorm Downloads
Firestorm Security! Never download Firestorm from a website that is not firestormviewer.org! Alternate download locations should not be trusted! Firestorm downloads - https://www.firestormviewer.org/downloads/

MOTD: RELEASE: Current Firestorm release version is 5.1.7.55786
Firestorm Release! The current Firestorm release version is 5.1.7.55786! Not on it? Get it here! Get it now! READ THE BLOG POST! https://www.firestormviewer.org/firestorm-release-v5-1-7-55786/

MOTD: TIP: Firestorm Classes 1Temporarily removed from the rotation.
Did you know Firestorm has classes on how to use the Firestorm viewer? We even have an open question and answer session after each class! http://wiki.phoenixviewer.com/firestorm_classes

MOTD: TIP: Firestorm Classes 2Temporarily removed from the rotation.
Did you know Firestorm offers classes on how to get the most out of the Firestorm viewer? Click to find out more about these classes and when they are! http://wiki.phoenixviewer.com/firestorm_classes

MOTD: TIP: Avatar Complexity
Firestorm tip! Why is my friend a colored shape? What is this complexity popup thingy? Click here to find out more about this lag reducing feature! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings

MOTD: TIP: Complexity and the Slideshow
Firestorm tip! Are you at a busy club or event and Firestorm is running like a slide show? Try lowering your avatar complexity setting! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings

MOTD: TIP: FS Bridge, Trolls Not Included
Firestorm Tip! The Firestorm BRIDGE is enhancing your SL experience and you may not even know it! Click here to find out how! http://wiki.phoenixviewer.com/fs_bridge

MOTD: TIP: Can Not Log in to SL
Firestorm Tip! Can't log into Second Life? STOP! DO NOT reinstall firestorm! Save yourself a lot of trouble and check here first for possible grid issues https://status.secondlifegrid.net/

MOTD: TIP: Contact Sets
Firestorm Tip! Contact Sets allow you to organize friends and non friends into manageable groups and categories! Learn more about them at http://wiki.phoenixviewer.com/fs_contact_sets

MOTD: TIP: IM Tab Sorting
Firestorm tip! Did you know you can click and drag your IM tabs in the conversations window to sort them to your liking. For more chat tricks see http://wiki.phoenixviewer.com/fs_chat

MOTD: TIP: Customizable Quickprefs
Firestorm tip! Did you know you can add your most commonly used settings to the Quick Prefs? http://wiki.phoenixviewer.com/fs_quick_preferences

MOTD: TIP: Missed the MotD
Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd

MOTD: TIP: Outfits
Firestorm tip! Did you know the Outfits feature can help you quickly change what you&apos;re wearing without digging around in your inventory? http://wiki.phoenixviewer.com/my_outfits_tab

MOTD: TIP: Camera Controls
Firestorm tip! Something catching your eye? Hold down your ALT key and click it, then roll your mouse wheel! Interested in more? See http://wiki.phoenixviewer.com/fs_movement_and_camera#view

MOTD: TIP: Toolbars
Firestorm tip! Did you know you can add many of your commonly used Firestorm windows and floaters to the toolbars? http://wiki.phoenixviewer.com/toybox

MOTD: TIP: SL World Search
Firestorm tip! Looking for something in world but, can't find it? Try a search! http://wiki.phoenixviewer.com/floater_search

MOTD: TIP: Replace Links
Firestorm tip! Gah my inventory links are borkened! Have no fear, Replace Links are here! Fix those broken links, http://wiki.phoenixviewer.com/fs_linkreplace

MOTD: TIP: Skins
Firestorm tip! Wanna change the way firestorm looks? Then change it! http://wiki.phoenixviewer.com/preferences_skins_tab

MOTD: TIP: Settings Backup
Firestorm tip! Better safe than… NOOOOOOO! You should regularly back up your Firestorm settings. You never know when…. http://wiki.phoenixviewer.com/backup_settings

MOTD: TIP: Auto Replace
Firestrom tip! Firestone? Firestorm! If only Firestorm had an auto replace… Oh wait! It does! http://wiki.phoenixviewer.com/fs_auto_correct

MOTD: TIP: Preference Search
Firestorm tip! Is a Firestorm setting playing hide and seek and causing you to pull out your hair? Find it fast with preference search! http://wiki.phoenixviewer.com/fs_preferences

MOTD: TIP: Chat Shortcuts
Firestorm tip! Did you know when chatting you can hold down your ctrl key when you press enter to shout and the shift key to whisper? http://wiki.phoenixviewer.com/keyboard_shortcuts

MOTD: TIP: Keyword Alerts
Firestorm tip! Did you miss a message in chat? Did someone say your name while you were doing something else? Check out Keyword Alerts! http://wiki.phoenixviewer.com/preferences_chat_tab#keyword_alerts_tab

MOTD: TIP: FS Wiki
Firestorm Tip! Did you know Firestorm has its own wiki? Find out how features work, how to fix common viewer issues and more! Check it out, bookmark it, study it! http://wiki.phoenixviewer.com/

MOTD: TIP: Inventory Count
Firestorm Tip! Do you have more inventory than you thought you had? Inventory count now includes folders! Click for more http://wiki.phoenixviewer.com/my_inventory_tab

MOTD: TIP: Elements
Firestorm Tip! Elements? What is this, chemistry class? No silly, Elements is the count of Items/Folders in that folder! Click for more http://wiki.phoenixviewer.com/my_inventory_tab

MOTD: HELP: Bakefail Badness
Firestorm Help! Are you feeling overly misty as an orange cloud? Are you missing your avatar? Are you thinking, clouds belong in the sky, not on me! Click here to fix the cloud http://wiki.phoenixviewer.com/fs_bake_fail

MOTD: HELP: Camera Messed Up
Firestorm Help! HALP! I know my head looks awesome but I'm stuck staring down at the top of it! Why am I staring at my butt? What is wrong with my camera?! click click clickie! http://wiki.phoenixviewer.com/fs_camera

MOTD: HELP: Teleporting Woes
Firestorm Help! What is up with these teleport fails? Disconnected?! OMG again! Click here to help prevent TP issues! http://wiki.phoenixviewer.com/fs_tp_fail

MOTD: HELP: Slow Rezzing
Firestorm Help! Did you know many common rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/slow_rez

MOTD: HELP: Slow Rezzing Mesh
Firestorm Help! Did you know many common mesh rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/mesh_issues

MOTD: HELP: Getting Help NAO
Firestorm Help! HALP! My Firestorm is broken and I need help NAO! Have no fear, click here! http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Getting Help Dont Panic
Firestorm Help! Sudden viewer problems? Not sure what to do? Don't panic! check out our wiki: http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Voice Issues
Firestorm Help! Have you lost your voice? Firestorm voice not working for you? Why not drink a tall glass of http://wiki.phoenixviewer.com/fs_voice

MOTD: HELP: Rick and Morty Lost Login Info
Oh geez, Rick, Firestorm lost my login info again! Well, Morty, try starting here to fix it, http://wiki.phoenixviewer.com/fs_stored_passwords#failed_to_decode_login_credentials

MOTD: HELP: Help Help Help You
Firestorm Help! Need help? Help us help you! Learn how to use the Firestorm support group to get the best help! http://www.firestormviewer.org/firestorm-help-groups-tips-rules-and-guidelines/

MOTD: HELP: Second Life Account Questions
Firestorm Help! Need help with your Second Life account matters? Go to Avatar Menu - Account, or login to your Dashboard at https://secondlife.com/my/account/

MOTD: HELP: Dont Clear Your Cache
Firestorm Help! Having viewer problems? Please don't clear your cache or reinstall the viewer as the first thing you try. Instead, see this page for how to get help http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Missing Inventory
Firestorm Help! Ummmm, I know I had more things in my inventory than this! Help! I'm missing inventory! what can I do? http://wiki.phoenixviewer.com/fs_missing_inventory

MOTD: GATEWAY:
Keep an eye here for upcoming information regarding the Firestorm Gateway!

MOTD: FUN: Rhubarb Pie
Firestorm fun! Feeling hungry? try a Rhubarb Pie, Firestorm style! http://wiki.phoenixviewer.com/rhubarb_pie

This section is changing as we speak!

* if a main MOTD is set, that one is always shown
* if random MOTDs are set and no main MOTD is set, they will be randomly shown at login and during TP
* if an event MOTD is set, that is always shown at login and then, during TP either the main MOTD or one of the random MOTDs

Linden Lab will soon release the Environment Enhancement Project (EEP): Please read Environmental Enhancement Project for a full description!

This project revamps the old Windlight system and among other things, includes

• support for 24-hr day cycles
• server-side support for parcel Windlight
• the ability to set custom sun, moon and cloud textures on your region or parcel that everyone using an EEP viewer can see.

As of Tuesday, March 19, server-side support for EEP was rolled to all regions on the main grid. This means that all region Windlights in use were automatically converted over to the EEP system.

Viewing the new EEP skies on a viewer that doesn't yet have EEP support (like Firestorm 6.0.2 and older) may cause the skies to look slightly different in some cases.

• If you are have a specific Windlight sky set in your viewer (i.e. one you have chosen from Quick Prefs, Phototools, or World menu → Sun Position), then the sky will look the same.
• If you are on a parcel with a Firestorm parcel Windlight set, the sky will look the same because the viewer just reads the Windlight settings in the parcel description and applies those settings locally.
• However, if you are viewing a region Windlight (World → Sun Position → Estate Time) the sky will look different from how it used to.
• If the sky has visible stars, the stars will look much larger and blotchy. If ALM is enabled, the stars will also look black instead of white.
• The sun may be bigger or smaller than it should be.
• There may be subtle lighting differences.

All these problems will be fixed once Firestorm releases with the EEP feature. That will probably be in our next release, but as usual we cannot give you a date for that.

If you want to test out EEP, you can currently do so using the Linden Lab EEP Release Candidate viewer available from Official Linden Lab Alternative Viewers.

For discussion you can follow the EEP forum.

Please don't swamp Firestorm support with questions about EEP. Read the SL page linked above, test out the project viewer if you wish, and follow the forums to stay up to date on development. Once Firestorm includes EEP, we will be able to help you with its features. Thanks!

Teleport can fail in several ways:

• you simply don't go anywhere but remain where you were
• you get disconnected
• you crash out

The first of these cases may often be due to simple things like the region you are trying to get to is full, or you have no access to it, or it has gone down. Try again after a few minutes.

Also, please note that the recent introduction of “teleport threading”, an attempt to mitigate the effects of mono memory leak, have led to an increase in TP failures, often resulting in your being logged out of SL altogether.

Things to try:

• Disable RLV if you have it enabled. Go to Preferences → Firestorm → Extras → “Enable Remote Scripted Viewer Controls (RLVa)”, disable it if it is enabled, then relog. See if you can now teleport. If you can, you may have had an RLV restriction in place.

• If you aren't crashing or disconnecting but aren't getting anywhere, try TPing to different locations. It may just be one region giving you trouble. “Puddle jumping” by going to a different one first might help you get around sim issues.

• Try opening the landmark you are trying to TP to and let the information in the LM load fully before clicking Teleport.

• Having your bandwidth set too high is a frequent cause of TP failure. Go to Preferences→ Network & Files -> Connection and set bandwidth to 300, and see if that improves things. If it does, you can increase gradually, up to a maximum of 1500. Please refer to this page for information on determining your optimum bandwidth setting.

• There may be a problem with your connection. Log off and try resetting your router/modem. Unplug it for a minimum of two minutes. If it has a battery backup, remove the battery as well. It does not hurt to reboot your computer at this time. After at least two minutes have passed, plug the router/modem back in and/or replace the battery and log back in.

• If you crash or get logged out on all or most TPs, then you may need to add new DNS numbers in your system's networking settings. Mac users may also be experiencing other issues like an empty friends list or trouble viewing rigged mesh. Please see this page for instructions.

• 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 you are using a firewall, try disabling it temporarily and seeing if that improves things. Norton products in particular have been known to severely impair various SL functions, including teleports and texture rezzing, but the same issues may appear with other firewalls as well. If this solves the problem, re-enable the firewall, and then configure it to allow Firestorm access to the 'net; for more on that, see here.

• Right-click your tag or a non-prim part of your avatar and select Script Info. If the number of scripts reported is in the triple digits, then it might be causing the TP fail. Try removing scripted prims. To determine which attachments contain the most scripts, go to World → Parcel Details, click Script Info at the bottom and then Avatar at the top. This will list your scripted attachments with their size in memory (not number of scripts) to help you know what to try removing first.¹⁾ Note that UNscripted prims have no effect on TP failing.²⁾

• If you have teleport screens disabled, try turning them back on: Preferences → Move & View -> Teleports→ Disable Teleport Screens … make sure it is NOT checked.

¹⁾ Often, scripts in worn attachments are old-style resizers, which use one script per prim. In 200-prim hair, that is 200+ scripts! Click on the hair, jewelry, shoes, or other attachment, and if there is a menu option to delete resize scripts, then make a copy of the item in your inventory and delete the scripts out of one copy. Wear the now-unscripted copy and save the scripted one in your inventory in case you need to resize it again in the future.

Naturally, you do NOT want to stop or remove scripts from HUDs or other items that perform useful functions, like AOs, Mystitool, combat HUDs, etc., though you can reduce your scripts further by setting up and using the built-in client-side Firestorm AO instead of an AOHUD.

²⁾IMPORTANT: Avatar Complexity (formerly Avatar Render Draw Weight, also formerly Avatar Rendering Cost, which were calculated differently) is totally unrelated to script count. Low complexity does not mean your script count is low. Complexity is an indication of how much work your computer has to do to draw an avatar, no more. The association between Avatar Complexity (draw weight/ARC) and scripts is a myth, and totally false. Also, high complexity does not interfere with TP; that too is a myth.

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]. Update to Firestorm 6.0.2 to fix this.

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.

Voice doesn't work when Skype is on, or sounds don't work while using voice:

1. In Windows Control Panel > Hardware & Sound > Manage Audio Devices
2. Select the Recording tab, select the microphone, select Properties
3. Select the Advanced tab - untick 'Allow applications to take exclusive control of this device' - click OK
4. Select the Communications tab
5. Select 'Do Nothing' - click OK

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:

• 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 reboot your router/modem, and then your 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.)

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

• Problèmes avec l'EEP (Environmental Enhancement Project)

• 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

Liden Lab a déployé, ce mardi 19 mars, l“Environmental Enhancement Project” sur toute la grille de SecondLife - Les anglophones peuvnet lire Environmental Enhancement Project pour une description complète. Cela signifie que toutes les régionsont été automatiquement converties au nouveau système EEP.

En gros, il s'agit d'une amélioration des environnements Windlight, avec l'ajout d'un nouvel objet d'inventaire pour définir les paramètres d'environnement (objets d'environnement partageables que vous pouvez conserver dansvotre inventaire, contrôle de l'environnement au niveau de la parcelle, jusqu'à quatre couches différentes de ciel pouvant être installées indépendamment les unes des autres, plus d'options de personnalisation, etc).

Ce projet rénove l'ancien système de windlights et inclut, entre autres, le support de jours SL de 24 heures, la possibilité de personnaliser les textures du soleil, de la lune et de nuages sur votre région ou sur votre parcelle, visibles pour toute personne utilisant un viewer qui supporte l'EEP.

Le fait d'utiliser un viewer ne supportant pas encore l'EEP (comme Firestorm actuellement) a pour inconvénient de rendre l'aspect du ciel un peu différent danscertains cas.

• Si vous avez choisi un ciel Windlight dans votre viewer (soit dans les Quick Preferences, Phototools,ou à partir du menu World > Sun position), vous ne verrez pas de différence.
• Si vous avez mis un ciel Windlight sur votre parcelle de terrain, l'aspect du ciel devrait être le même car le viewer ne fait que lire les paramètres WIndlight dans la description de la parcelle, puis applique ces paramètres au niveau local.
• Cependant, si vous voyez un Windlight de région (World > Sun position > Estate time) le ciel paraîtra différent.
• Si le ciel comporte des étoiles, celles-ci sembleront beaucoup plus grosses. Si Advanced Lighting Model est activé dans Preferences > Grahics > General

• If the sky has visible stars, the stars will look much larger and blotchy. If ALM is enabled, the stars will also look black instead of white.
• The sun may be bigger or smaller than it should be.
• There may be subtle lighting differences.

All these problems will be fixed once Firestorm releases with the EEP feature. That will probably be in our next release, but as usual we cannot give you a date for that.

If you want to test out EEP, you can currently do so using the Linden Lab EEP Release Candidate viewer available from Official Linden Lab Alternative Viewers.

For discussion you can follow the EEP forum.

Please don't swamp Firestorm support with questions about EEP. Read the SL page linked above, test out the project viewer if you wish, and follow the forums to stay up to date on development. Once Firestorm includes EEP, we will be able to help you with its features. Thanks!

Le partage de Windlight de parcelle est une focntionnalité de Firestorm qui permet aux propriétaires de terrains de spécifier un préréglage Windlight que le viewer utilise lorsqu'ils sont sur leur parcelle de terrain.

5 secondes après être entré sur le terrain où un WL est installé, le viewer demandera la permission de changer de paramètres ou de l'ignorer. Toutes les permissions sont réinitialisées après une reconnexion.

Supprimer les paramètres Windlight après qu'il saient été appliqués est très simple : changez-les juste avec les moyens habituels. Les paramètres WL de parcelle ne seront alors ré-appliqués après avoir quitté la parcelle et y être revenu. On peut révoquer la permission et revenir à l'environnement de la région en cliquant l'icone WL dans la abrre de statut en haut du viewer à gauche de l'info du lieu.

C'est vous qui décidez si vous souhaitez voir les paramétrages Windlight que le autres ont installé sur leur terrain, ou non. Pour cela, utilisez Preferences → Firestorm → Windlight - décocher la case du haut vous laisera seul maître de ce que vous voyez comme réglage d'environnement.

• Use Firstorm Parcel Windlight Sharing: Si ceci est activé, tout paramétrage Windlight de n'importe quelle parcelle sera décrypté lorsque vous entrez sur une parcelle, et le viewer vous demandera si vou souhaitez l'appliquer ou non. D'autre aprt, le paramétrage de votre propre parcelle sera toujours automatiquement appliqué.
• Auto apply WL settings from friend's land: Si cette case est cochée, tous les paramétrages Windlight des parcelles de vos amis seront automatiquement appliqués lorsque vous y entrez.
• Auto apply WL settings from my group's land: Si c'est activé, tous les paramétrages Windlight des parcelles de votre groupe actuellement actif seront automatiquement appliqués.
• Auto apply WL settings from any parcel: Si cette case est cochée, tout paramétrage Windlight sera automatiquement appliqué, quels que soient les réglages ci-dessus.

Pour paramétrer un préréglage Windligth sur sa parcelle, le propriétaire doit ajouter une chaîne de caractères à la fin de la description de sa parcelle. La descriptiond e la parcelle set rouve dans le menu World → Parcel details → General → champ “Description”:

/*Windlight Sky: "[nom du Windlight de ciel]"*/

Il peut également utiliser les préréglages Windlight de l'eau :

/*Windlight Sky: "[nom du Windlight de ciel]" Water: "[nom du Windlight d'eau]"*/

Exemple: SI le préréglage du ciel est [TOR] BIG SUN - Awwyeah et le préréglage d'eau [TOR] Watermelon juice et que la description de la parcelle est “Home Sweet Home” alors la description de la parcelle sera la suivante :

Home Sweet Home

/*Windlight Sky: "[TOR] BIG SUN - Awwyeah" Water: "[TOR] Watermelon juice"*/

Les paramètres Windlight supportent également des réglages basés sur l'atitude. Cela permet aux skyboxes d'avoir des réglages différents de ceux du niveau du sol :

/*Windlight Sky @ [niveau bas]m to [niveau haut]m: "[nom du Windlight de ciel]"*/

Exemple : Si les préréglages de la parcelle sont [TOR] MIDDAY - Cheery cyan pour le ciel, et [TOR] Ice-like pour l'eau, avec une skybox entre 500 et 600 mètres d'altitude utilisant [TOR] NIGHT - Moony pour son ciel, la chaîne de configuration sera la suivante :

/*Windlight Sky: "[TOR] MIDDAY - Cheery cyan" Water: "[TOR] Ice-like" Sky @ 500m to 600m: "[TOR] NIGHT - Moony"*/

Les paramètres Windlight de la parcelle pour le ciel et l'eau sont optionnels. Il est possible de n'utiliser des zones d'altitude tout en laissant le reste de la parcelle sur les réglages par défaut de la région.

NB: Il y a un minimum de 3 mètres de distance entre les zones d'altitude, les zones doivent être laissées à 10 mètres de chacune d'entre elles pour déborder de 5 mètres et laisser les 5 secondes de délai permettant la détection des changements.

S'il n'y a pas suffisamment d'espace dans la decription de la parcelle pour la chaîne de caractères, il existe des options de formatage et de “blancs”.

Est équivalent à :

Les zones d'altitude peuvent aussi être raccourcies:

Beta testing Firestorm is more properly called QA (Quality Assurance). This means using test builds of the viewers before general release, using them and actively trying to identify bugs, glitches and things that need improvement. In other words, being part of the beta (QA) team means more than just getting your hands on a “new shiny” before everyone else does. You will be asked to do specific tests for each release, the results of which are vital to helping us determine where there may be problems.

So, if you are interested in becoming an active participant in the beta team, and are willing and able to endure crashes, multiple relogs, full settings wipes (several times), and so on, then please read on.

In applying to become part of the beta testing team, you are explicitly agreeing to the non disclosure terms below.

• Create an account on our JIRA, if you have not already got one. This is required in order for you to access the beta test site.
  If you need tips on creating an account, see Creating an Account on our wiki page on filing a JIRA.
  Either way, make sure you are logged in. Please use your Second Life name, NOT your Real Life name when creating an account on our JIRA. Both Username and Full Name should be your Second Life account name (no display names).
• In the top right of the page you'll see a link that says 'Create Issue'. Click that and in the page that opens…
• For 'Project', select 'Tester Applications, BETA'.
• For 'Issue Type' select 'BTA'.
• For the 'Summary' field enter your SL username, not your display name.
  If you have more than one operating system and would like to have an alt added for testing additional operating systems, add their username here with your names separated by commas.
• Set 'Priority' to Major.
• For 'SL Avatar Name' fill in the SL username of your primary SL avatar that you would like used for beta testing correspondence.
• Leave 'Patch attached' unchecked.
• For 'Affects Version/s' select the current Firestorm release version. (For example, 5.0.11.).
• For 'Environment' copy and paste the entire environment from the Help menu, About Firestorm, Info tab in Firestorm for any machines and or operating systems you will be using for testing.
• For 'Description' give us a brief explanation of why you think you would make a good member of our beta test team.
• 'Attachment' and 'Labels' should be left blank, they're not used for applications.
• Click Create.
• Be sure and keep an eye on the JIRA you created as this is where you will be initially contacted to complete your addition to our beta test program. Do not reply via email to any emails you receive from the JIRA, they will not work.

Your application will be assessed as soon as it is seen by the QA team lead to ensure it is complete and correct. If any corrections need to be made you will be notified in the comments section of your application.

There is a seven day “cool-off” period after your application is submitted until you are notified if you have been approved.

You will need to follow the instructions in your BTA once accepted, and at that time will receive an invitation to the inworld group, Firestorm Beta testers.

All information provided when applying to become a Firestorm Beta Tester on issue type BTA is strictly confidential and only accessible by you and Firestorm team members.

As part of the beta test team, you will be given access to test builds from time to time. Such builds are not to be circulated outside of the beta test team. Nor are direct or indirect web links to be shared with people who are not part of the beta test team. Doing so will result in immediate termination of beta tester status.

The reason for this is very simple: test builds are often known to have bugs, sometimes very severe ones. We test them anyway because there may be other aspects of the build on which we need to have feedback. Clearly, we do not want viewer builds which are known to have bugs - or which may potentially have severe bugs - to be circulated to the general public.

Here is an outline of the general procedure for each new test release.

• A notice is posted to the inworld beta test group, announcing the new test build. Any specific directions are given at that time, often in an attached notecard.
• Log in to the Phoenix-Firestorm Beta Site, then download the test release.
• Install the test viewer. Most of the time installs can be dirty and installed directly over your current Firestorm install. On occasion you will be asked to do a clean install which is a total wipe of settings, possibly including cache. A clean install is explained here. If you are not given specific instructions on this in the new test notice or on the test itself, then assume that a clean install is not required.
• In some cases, there will be a smoke test to carry out; that is, specific things that we need to have tested. This smoke test is structured as a questionnaire: a description is given of what needs to be tested, and you are asked to fill in the results. This is a sample segment of such a test:
  
• Once you have completed the test - and it cannot be stressed enough how vital it is that you do so! - continue to use the viewer as you normally would, and report any problems you find to JIRA (making sure you select the correct viewer versions for Reported in and Affects).
• You are encouraged to use the inworld group to ask questions, to see whether specific issues are known or perhaps expected behavior. But bug reporting should be done to JIRA or your bugs may go unnoticed.

• Onscreen console font size: Choose Small, Medium, Large or Huge

• Play avatar animations (such as shouting): Animates your avatar for some standard actions.
• Wrap system chat messages in brackets: makes system messages distinct by enclosing them in brackets.
• Show “You” in chat transcripts instead of your name: Replace your name in transcripts.
• Emotes use italic font: Makes emotes show in italics.
• Bold Shouting, Italicize whispering: If enabled, emphasises shouting and whispering, as the option indicates.
• Mark objects with (no name) when they speak to avoid spoofing: This allows object names in chat to be clicked, so that you can get information about them (creator, owner, etc). Useful in griefing situations.
• Route llOwnerSay to script debug window:llOwnerSay script output is sent to the script debug window rather than being shown in console, on screen.
• Show chat in bubbles above avatars: puts local chat in bubbles above users heads.
  • Don't show chat in Nearby Chat console and toasts: Prevents chat from showing in console and toasts (only available if the above option is enabled; greyed out otherwise).
• Show typing indicator in bubbles above avatars: This will show something like a chat bubble but only when another avatar is typing; it gives a visual indication that someone is typing. The text itself will appear according to your settings.
• Show typing indicator in nametag above avatars: Similar to the above, but the indicator appears in the nametag instead.

• Show seconds in timestamps: adds seconds to the timestamps.
• Show timestamps in: You can select whether to show timestamps in…
  • Nearby chat
  • IMs
  • Transcript

• Use classic draw mode for console: Changes the chat console ¹⁾ background to surround all visible text instead of displaying separate backgrounds per line of chat.
• Use full screen width for console: Will allow the chat to be the full width of the screen (requires restart).
• Fade chat after _seconds __ # lines: Allows you to choose how long, and how many lines show in the chat console.

• Chat window font size: Choose Small, Medium, Large or Huge

• Show names in direct IMs: If this is disabled, user names are not shown on each line in IMs.
• Use V1 style chat headers: Makes chat look like V1 style chat. With this unchecked, chat headers will appear as horizontal bars across chat windows, with text underneath. With it checked, timestamp and name will precede text on the same line.
• When using V3 style chat headers, show mini icons: shows the icon in the IM/group chat next to the name. If Remove chat headers is enabled this will not show even if enabled.
• Show the end of the last conversation: If enabled, the last few lines of the last conversation will be shown in IM windows. This requires that chat transcripts be enabled in Preferences→ Privacy → Logs & Transcripts.
• Add additional chevron (>) as typing indicator to IM sessions: This depends on the other person having enabled Send typing notifications to other avatars during IM sessions. If they have, then you will see a chevron when they are typing.

• Show new message notification for: If you have scrolled up in a chat window, and a new message has arrived, you can be informed of this, by enabling one or both of:
  • Nearby chat
  • Instant and group messages.

• Show IMs in: (requires restart)
  • Separate windows
  • Tabs

• Chat tab orientation: (requires restart)
  • Horizontal (along the bottom of the Conversations window)
  • Vertical (down the left side of the Conversations window)

• Name format for IM tabs: If you have both display names and user names enabled in Preferences -> General, then you can select what names you want display in IM chat tabs:
  • Display name
  • Username
  • Display Name (Username)
  • Username (Display Name).

• Enable group moderator message highlighting: This option will make text posted by group moderators stand out in group chat, so you can easily tell which poster has moderator rights.²⁾ Two options may be combined (you may enable either one, or both):
  • Name Style: You can opt to have moderator names highlighted in one of several text styles, such as bold, italic, etc.
  • Text Style: You can also specify a style for the etxt that apepars in chat after the moderator name.
• Disable ALL group chats: Prevents group chats from opening automatically when another user IMs the group.
  Note: The viewer will still receive group chat with this option turned on when an IM/Group Chat tab is open for the group in the Conversations window. What the option does is prevent the automatic creation of a tab when a group message is received.
• When “receive group notices” is disabled, disable group chat as well: Turns off group chat from any group from which you are not receiving group notices.
  Note: Group text chat may now be disabled independantly of group notices, in the groups profile window.
  Note: The viewer will receive group chat with this option turned on when an IM/Group Chat tab is open for the group in the Conversations window. What the option does is prevent the automatic creation of a tab when a group message is received.
• Automatically ignore and leave all conference (ad-hoc) chats: Shuts down any conference chats in which you are included.
  • Report ignored conference chats in nearby chat: Informs you that a conference chat was ignored.
    The name of the person is shown, and may be clicked in nearby chat to bring up their profile.
  • Don't ignore conference chats invitations from my friends: overrides the automatically ignore settings for conferences started by those on your friends list.

• Group Chat Snooze Duration: Length of time a group chat will be muted when clicking the Snooze button. Setting this to zero will simply close the group window until the next group message arrives.
  Note that any chat which occurs during the “snooze” period will not be logged - should you have logging enabled.
• Set group chat snooze duration individually per group: If enabled, when you snooze a group chat, a window will open asking how long to snooze the chat for.

• Auto-Replace: Opens the Auto-Replace Settings window where you can define word replacement. Useful as an auto correct feature, for example.
• Spell Checking: Opens the Spell Checker Settings window.
• Translation (button): Opens the Chat Translation Settings window, where you can specify if you want chat to be translated, and which service to use.

• Play typing animation when chatting: Your avatar will play the typing animation when chatting in local with this enabled.
  • Play typing animation also when emoting: If the above is enabled, then this option will have your avatar play a typing animation when using emotes.
• Hear typing sound when people type in local chat: If enabled, you will hear the sound of typing
• Send typing notifications to other avatars during IM sessions: If enabled, this will show “xxx is typing” in IMs. It can also trigger the other person's IM to open before you actually send the IM text. (See Announce incoming IMs as soon as the sender starts typing below.)
• Enable auto-completion of gestures in nearby chat bar: If this is enabled, then typed gestures will auto-complete as typed.
• Enable automatic name prediction in nearby chat bar: When this is enabled, the viewer will attempt to autocomplete a name based on the names of those near you.
• ”:” as a synonym for ”/me”: Used in Role Playing. Allows use of ”:” instead of ”/me” to indicate an action, instead of a statement. For example; ”:nods in agreement” appears as “John Doe nods in agreement”. (NOTE: No space after the ':'.)
• Auto-close ((OOC)) parentheses: Used in Role Playing. When entering message in RP mode, it is assumed they are speaking as their character. To communicate something outside of their character, they enclose their message with “((” and “)) ”.
  When checked, the viewer automatically appends a ”))” to a message if it isn't present. For Example ((This is OOC“ results in ”((This is OOC)) “.
• Show send chat button in the chat bar for IM sessions: Adds a “Send” button at the right end of the chat bar in IM and group chat windows.
• Add a chatbar in the Nearby Chat window: As the name implies.
  • Show channel selection in chat bar: Enables the channel selector in the nearby chat bar.
  • Show chat type / send chat button in chat bar: Adds a button to the right of the nearby chat bar; you can click this to send chat, and you can select whether to say, whisper or shout.
• Autohide Main chatbar: If this is enabled, then the chat bar at the bottom if the screen will close after you have typed something. Starting to type anything again will cause it to reopen.
  Note that if both the WASD selection in Pressing Letter Keys (above) and Autohide are enabled, you will need to hit Enter/Return before you begin typing in an autohidden chat bar.
• Deselect Chat after sending Messages: Will move the cursor out of the chatbar after you send a message.
  • De-focus chat history as well: Will also remove focus from the nearby chat history window.

Here, you can enable/disable three special shortcuts:

• Ctrl-Enter - Shout
• Shift-Enter - Whisper
• Alt-Enter - OOC

• Enable incoming chat popups: Allows Group and/or IM chats to appear onscreen, in either console or toasts, whichever is set below.
  • Group Chats
  • IM Chats

• Use console for chat popups instead of floating toasts (Viewer 1.x style): Displays chat in the onscreen left-hand console rather than in bottom-right toasts
  • Show IMs in chat console: Will show IMs in the chat console; this is on the lower left of the screen, not in the communication window.
  • Show group chat in chat console: Will show group chat in the chat console; as noted above, this is on the screen, not in the communication window.
  • Length of group name to be printed in chat transcripts:
    • Setting '0' turns it off.
    • Setting '-1' shows the full group name.
    • Setting '1 or higher' shows the group name truncated to how ever many characters are set here, the '[' and ']' aren't counted.

• Open Conversations when an offline mesage has been received: Normally, any offline messages you get will be shown as chiclets when you log in. If you enable this, the Conversations window will also open to show the text of the messages.
• Email me IMs when I'm offline: will send any offline IMs to your email that you have on file with LL
• Show IMs in nearby chat window: Shows the text of received IMs in the nearby chat window.
  • Save IMs in nearby chat: Enable logging of IMs along with local chat; requires that local chat be logged, which can be enabled in the Privacy -> Logs & Transcripts tab.
  • Fade IM text into the background of the chat transcript window: 0.25 for most faded, 1 for no fade.
• Show number of unread IMs in Firestorm's window title: Displays a count of unread messages in the window title bar.
• Announce incoming IMs as soon as the sender starts typing: If enabled, your IM window will open and beep as soon as someone starts typing a message to you, rather than after they complete and send the message.
  Note that this will not work if the person IMing you has disabled Send typing notifications to other avatars (above).
• Flash IM tabs when friends come online or go offline: visually notifies you when friends log in or out; most useful during IM conversations.
• Flash chat toolbar button if new nearby chat arrives: The nearby chat window must be docked to the conversations window, and this must be closed for the button to flash.
• Flash chat toolbar button if new IM arrives: The IM window must be docked to the conversations window, and this must be closed for the button to flash. also, this option is only available if IMs are shown in tabs, rather than separate windows; see the setting in Preferences→ Chat -> Chat Windows.
• Report muted group chat in nearby chat: If chat starts in a group which you have “muted”, a message to that effect will be displayed in nearby chat.
  Group chat can be “muted” (disabled) in the groups profile window.
• Show group notices in group chats, in addition to toasts: If enabled, the text of group notices is displayed in the group chat window.
  • Show their subjects and authors as well: Also shows the title and sender of notices in group chat.

• Radar reports when avatars enter/leave chat range: Will show in nearby chat when an avatar enters or leaves chat range.
• Radar reports when avatars enter/leave draw distance: Will show in nearby chat when an avatar enters or leaves your draw distance.
• Radar reports when avatars enter/leave the region: Will show in nearby chat when an avatar enters or leaves the region.

Each of the above can, optionally, play an alert sound, which you can change by specifying your own sound clip UUID. You an hear the sound by clicking the button labelled 'P', or revert the sound to the default by clicking the 'D'.

Note that the names shown by radar, in the nearby chat window, can be clicked to open a profile.

• Report enter/exit alters to scripts: This is the same function that is available from the People panel gear menu. It will output radar information to user scripts. For more information, refer to this page.

• Enhance radar with LSL-Client Bridge: If this is enabled, radar functions responsible for determining avatar locations at high altitudes are assisted by the LSL bridge, particularly when they are beyond draw distance.

• Age Alert: You can also be alerted to avatars who are “younger” than a certain number of days.
  • Threshold: Set the age in days.
  • Radar reports avatars younger than the specified age: Enable to be alerted.
    again, you can specify your own alert sound by giving a valid sound UUID.

• Enable Keyword Alerts: Enables using Keyword Alerts.
• Look for Keywords in Local Chat: When checked, the alert system monitors Local Chat for the presence of these keywords.
• Look for Keywords in IMs and Group Chat: When checked, the alert system monitors the IM and Group Chat areas for presence of these keywords.
• Check sender's name for keywords: Look for keywords in the names of speakers or objects as well.
• All keywords are case-sensitive: Enable this if you want (for example) Apple to be treated differently from apple.
• Only match whole words: Enabling this will prevent an alert from being generated on partial matches. For example, if you have an alert on the word frank, you will not be alerted if someone types frankly.

Note: Because Group Chats are prevented from appearing when either When Receive Group Notices is disabled, Disable Group Chat As Well or Disable All Group Chats are enabled (see above), no alerts are triggered.

• Keywords (separated by commas): Specifies the list of words that will trigger an alert. They can be individual words or phrases and are separated by commas.
• Enable Color Alert: When checked, any messages that are to be alerted will have their color changed to what is specified in the color selector.
• Play alert sound: Enables playing a sound, identified by the UUID:
• Alert Sound UUID: Supply the alert sound UUID here. A default is given. To get a new UUID, find a sound in your inventory with full permissions (you can view the item's properties to check this), then right-click the sound and select Copy Asset UUID from the menu. Then paste the value into the text box.

See this page for a tutorial video.

• Enable usage of chat bar as a command line: If this is enabled, all the commands given below (except where noted) will be available for use.

All of the commands below can be changed from the supplied defaults.

• Calc. expressions (calc): Used to perform a calculation on the command line to figure out an answer quickly. Calculations adhere to precedence rules where multiplication/division occur before addition/subtraction. Therefore, example: “calc 1.3+2*5” results in “11.3” as the answer, because the multiply occurs before the addition.
• Change Draw Distance (dd): Changes the draw distance of the rendered view to the specified number of meters. Example: “dd 32” sets the draw distance to 32 meters.
• Max. Bandwidth (bw): Change your current maximum bandwidth. This is set in Preferences→ Network & Files -> Connection.
• Copy camera position to clipboard (cpcampos): Saves the current camea position in the clipboard, from which it can be pasted into a script, for example.
• Turn AO on/off (cao): Turns the embedded AO system on/off. Example: “cao on” turns AO on, and “cao off” turns AO off.
• Clear the chat transcript (clrchat): Clears the chat history from local chat. Example “clrchat”
• Set the media url (/media): Sets the video media for the parcel as identified by the URL. Only the land owner can set the media URL. If the URL contains a space, use to identify the space. The type is one of: Audio, Image, Movie or Web.
• Set the music stream url (/music): Sets the music stream for the parcel as identified by the URL. Only the land owner can set the music URL. Example: “/music http://scfire-dtc-aa04.stream.aol.com:80/stream/1010” sets a Smooth Jazz sound to the URL.
• Rez a platform (rezplat): Assuming the avatar has build privileges in the parcel, this command rezzes a circular platform of the given diameter beneath the avatar. Example: “rezplat 25” rezzes a 25m diameter platform below the avatar.

• Get avatar name from key (key2name): Looks up the specified avatar key and returns the name for the key. Example: “key2name” returns “Babbage Linden”.
• Roll dice (rolld): For role play. Use by typing rolld <number of dice> <number of faces> in nearby chat. Examples:
  rolld is a regular dice with 6 faces.
  rolld 1 20 is a single dice with 20 faces.
  rolld 3 10 is 3 dice, each with 10 faces.
  Bonuses, penalties, successes and explosions modifiers can also be added to the command; for more, refer to this page.
• Teleport within sim (gtp): Teleport to anywhere within the region instantly according to the position specified. Example: “gtp 45 150 400” teleports to 45, 150, 400.
• Teleport to ground (flr): Teleport to the current ground position for the avatar's current position.
• Teleport to altitude (gth): Teleport to the specified height. Example: “gth 2800” teleports to a height of 2800 meters. It is also possible to teleport higher. Example: “gth 6500” teleports to 6500m above the region.
• Teleport to cam position (tp2cam): Teleports the avatar to the position the cursor is currently looking at. This is useful when walking into a store. After looking around and finding the item to purchase, this shortcut takes you to the position immediately, without having to walk. Example: “tp2cam”.
• Offer teleport to avatar (offertp): Sends a teleport request to the avatar identified by the given key. Example: “offertp avatar-key”.
• Teleport to avatar (tp2): Finds a given avatar within the region and teleports to them. Example: “tp2 John Doe” teleports to “John Doe” if they are in the region.
• Teleport home (tph): Teleport home. Same as hitting Shift-Ctrl-H.
• Teleport to sim x (mapto): Teleports to the region you specified (defaults 128, 128, 0 if no landing point is specified on the region). Must use the full region name, with spaces and all.
  • Use same position between sims: When enabled, your entry point at the new region will be the same coordinates you left at the old region, unless a landing point is specified in the new region.

NOTE: In the commands above, the word “sim” is used in some places because the the viewer is still worded this way currently. The correct term should be “region” in all cases.

There are a few other commands which are not shown here (and therefore cannot be changed). These include:

• /zoffset_up: Offset your avatar upward by 0.05.
• /zoffset_down: Offset your avatar downward by 0.05.
  These can be used in gestures, perhaps assigned to the PgUp and PgDn keys respectively.
• zdrop, ztake, mtake: Refer to this page.

This window is opened from the main inventory window, when clicking the bottom gear icon and selecting Show filters.

It has check boxes which, when enabled, will included that type of item in the inventory display. To hide (for example) notecards from being shown, uncheck the Notecards checkbox.

To select all types of items, click the All button; to deselect all types, click the None button.

• Transfer only: Check this to show only items which are transferable.
• Always show folders: Check this to show folders even if they don't contain any of the types items selected above.
• Created by me: Finds asset types created by you.
• Created by others: Finds asset types created by others.
• Since Logoff: Check this to show items new since your last logout in the Recent Tab of the Inventory window.
• -OR-
  • Newer than
  • Older than
  • Specify how many hours or days old items must be to show in the Recent tab; anything older will not show there.

Dans Firestorm, l'inventaire comporte plusieurs dossiers ayant un but particulier :

• #Firestorm, qui contient :
  • #AO
  • #LSL Bridge
  • #Wearable Favorites
• #RLV

Si vos dossiers #FS, #AO, ou #Wearable Favorites setrouvent soudain vides, ou si vous consatez que l'un d'entre eux n'est plus à sa place dans votre inventaire, faites comme ceci :

TRADUCTION EN COURS - MERCI DE VOTRE PATIENCE

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

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

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

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

Third:

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

The Favorite Wearables 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. This makes it more convenient to detach attachments you don't need or want to wear all the time due to script usage or increased texture memory usage, and saves you from digging around in your inventory when you want to add them.

To use the feature,

• drag the toolbar button to your toolbar: Avatar Menu → Toolbar Buttons → Favorite Wearables, then click the button,
• or open the window from Avatar Menu → Favorite Wearables.

Adding/deleting items from the window:

• To add items, drag them from inventory into the window. Items added to this window create a link in the #Wearable Favorites folder in inventory.
• To delete an item, select it and press the Trash icon. Note: this only deletes the link in the #Wearable Favorites folder, not the original item.

Use double-click to add or detach any item.

The window includes a search bar.

The menu options include:

• Sort by name
• Sort by date
• Sort by type name (asset type)