Quantcast
Viewing all 5258 articles
Browse latest View live

preferences_skins_tab - ↷ Links adapted because of a move operation

Preferences - Skins

In this preferences panel you can choose the viewer skin and viewer color theme for Firestorm. The viewer skin determines the overall shape, layout, and graphics of Firestorm's controls. The theme determines what colors are used to draw these viewer controls. The viewer skin and viewer colors are only for Firestorm itself - these do not affect your avatar or anything else in-world.

The following skins ship with firestorm:

  • Firestorm
  • Metaharper
  • Starlight
  • Starlight CUI
  • Vintage
  • AnsaStorm
  • Latency

These come with different color schemes, which may be selected from the drop down menu below. The top of the panel gives a handy preview of the skin.

There are three other options on this page:

  • Reset Toolbars to the skin's preferred layout when changing skins: If this is enabled, when you change skins and relog, the predefined toolbar buttons layouts will be applied; disable this to maintain your customised layout, if any.
  • Reset toolbars to the login mode's preferred layout when changing login modes: When enabled, this option keeps the login mode's designed toolbar button layout, overriding your chosen toolbar customizations, when you change login mode.
  • Use Viewer 1 style cursors: Changes the cursors to the “old style” ones used in Phoenix. You will need to relog if you change this option.

Details

AnsaStorm

Author     : Ansariel Hiller
Themes     : Bright Blue, Classic Brown

Firestorm Skin

Author     : Jessica Lyon, Wolfspirit Magic, Ansariel Hiller
Themes     : Grey, Dark, High Contrast

The Firestorm skin is the default skin for most installs. It was created to resemble a V1-style viewer with its inventory, profiles, friends, blue dialogs, and other nuances. The grey theme provides medium contrast that is not as harsh as darker backgrounds, while still not taking away from the in-world colors. This skin uses solid backgrounds on the bottom buttons and select other controls for maximum control clarity.

Metaharper Modern Skin

Author     : Arrehn Oberlander
Themes     : Appalachian Sky, CoolOcean, BlackGlass

The Metaharper modern skin is an avant-gard blend of the V1 and V2 styles. It features darker backgrounds to emphasize in-world colors, and makes frequent use of transparency in its controls, most noticeably in the bottom buttons and top toolbars. Icons in Metaharper modern are ghostly white. The Appalachian Sky color scheme uses natural mossy green and forest browns for accents. Metaharper modern is occasionally used for experimental UI changes: At the moment it features an experimental quick preferences button variation that prefers avatar physics control in place of older sliders. It also features an experimental camera floater with all modes exposed, similar to the Kokua viewer.

Starlight Skin

Author     : Hitomi Tiponi & Starlight Contributors
Themes     : Original Orange, Original Teal, Mono Teal, Nostalgia Blue, Silver Pink, Silver Blue

Starlight is a skin with a large number of usability and presentation improvements, many contributed by residents. In addition Starlight has brought its own subtle redesign to give the interface a lighter feel, several colour variants (called 'Themes'). The color themes of the starlight skin are diverse: “Nostalgia Blue” pays homage to early official viewer colors, while “Original Teal” may be most like stock V2 of all the skins included in Firestorm. The “Silver” pair of color variations bring a rare dark text on light backgrounds look to the viewer.

Starlight CUI Skin

Author     : Hitomi Tiponi & Starlight Contributors
Themes     : Custom Dark, Custom Light

Starlight CUI - Colourable User Interface. This is a highly customizable skin; information on how to customize is give on this SL wiki page. See also the Custom Colors Tab in Preferences.

Vintage

Author     : Zi Ree
Themes     : Classic

Vintage is designed to look and feel as close as possible to the original Phoenix skin.

Screenshots


archive:preferences_opensim_tab_fs624 - created

Preferences - OpenSim

Grid Manager

This tab allows you to edit, delete or add grids that the viewer will recognize, and make available at the log in screen.

In order to be able to login to grid other than Second Life, you need to enable PreferencesAdvanced→ Allow login to other grids.

Secondly, you need the grid selector on the log in screen. If you do not see it, press Shift-Ctrl-G to activate it.

  • Add new grid: Here you can type in the login URI of a grid you wish to add to the existing list. You should consult with the specs of the grid in question to obtain the correct URI to place here. Click on Apply to save the URI; click on Clear if you change your mind.
  • Manage Grids: This shows the list of currently defined grids. Many are already present, by default.
    • Refresh: Reloads the default definitions.
    • Remove: Deletes the currently selected grid from the list.

The fields below this are auto-populated and cannot be edited:

  • Grid name
  • Grid URI
  • Login page
  • Helper URI
  • Grid Website
  • Grid Support
  • Grid Registration
  • Grid Password URI
  • Grid Search
  • Grid Message URI

Miscellaneous

  • Enable region Lightshare settings: Use OSGrid Lightshare.
  • Debug Search:
    • Override current search url: replace the default search URL (SecondLife) with a different one. The default will be used if this is left empty.

preferences_opensim_tab

Preferences - OpenSim

Grid Manager

This tab allows you to edit, delete or add grids that the viewer will recognize, and make available at the log in screen.

Secondly, you need the grid selector on the log in screen. If you do not see it, press Shift-Ctrl-G to activate it.

  • Add new grid: Here you can type in the login URI of a grid you wish to add to the existing list. You should consult with the specs of the grid in question to obtain the correct URI to place here. Click on Apply to save the URI; click on Clear if you change your mind.
  • Manage Grids: This shows the list of currently defined grids. Many are already present, by default.
    • Refresh: Reloads the default definitions.
    • Remove: Deletes the currently selected grid from the list.

The fields below this are auto-populated and cannot be edited:

  • Grid name
  • Grid URI
  • Login page
  • Helper URI
  • Grid Website
  • Grid Support
  • Grid Registration
  • Grid Password URI
  • Grid Search
  • Grid Message URI

Miscellaneous

  • Enable region Lightshare settings: Use OSGrid Lightshare.
  • Debug Search:
    • Override current search url: replace the default search URL (SecondLife) with a different one. The default will be used if this is left empty.


See this page for documentation on Firestorm 6.2.4 (57588) and earlier.

fs_controlling_ao_w_scripts - [OpenCollar]

Controlling the Firestorm AO from a Script

Firestorm has the ability to have its built-in animation overrider controlled by a script inworld. There are two interfaces, one compatible with the OpenCollar attachment protocol, the other compatible with the LockMeister restraints interface.

This can be disabled in PreferencesFirestorm -> Avatar - bottom two options.

LockMeister

The LockMeister interface is simple to use. Any item wishing to control the AO needs to send a message on the LockMeister channel, -8888. The message consists of the key of the targeted avatar followed immediately by the word “booton” to turn on the AO or “bootoff” to turn it off. For example, “12345678-1234-1234-1234-abc123456789booton” would enable the AO of the avatar whose key was 12345678-1234-1234-1234-abc123456789.

The full protocol is described on this page.

Click here for a test script.

OpenCollar

The OpenCollar interface is more complex to use. Its main advantage is that it was designed to be compatible with the protocol used by the OpenCollar Sub AO. The full protocol is described on this site.

OpenCollar software is now being developed by two different organizations, and the protocols for each can be found at the OpenCollar group at Github and the OpenCollar group at www.opencollar.cc/. The protocol is the same for both.

It is also less resource-intensive, as the protocol was designed to be controlled by only one device, which relieves it from hearing large numbers of messages not intended for it.

To begin, the controlling device announces its presence on the command channel by saying “OpenCollar=Yes”, either when it is attached or rezzed, or when requested by the bridge, which will send a message “OpenCollar?” when it is rezzed. Once it has done so, it may then send a message to enable the AO, or disable it: “499|ZHAO_AOON” to enable it, or “499|ZHAO_AOOFF” to disable it. The controlling device should send the message “OpenCollar=No” when it is shut down or derezzed, or no longer desires to control the AO.

It's important to note that the OpenCollar interface assumes there is only one controlling device. A second device will not be able to gain control of the AO, since the bridge will only listen to the sender of an OpenCollar=Yes message it receives until it is rerezzed or reset; other senders simply will not be heard.

Click here for a test script.

fs_bake_fail

Dealing with Avatar Bake Fail

For bake fail issues on grids which do not have Server Side Appearance, please refer to this page.

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

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

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

First Steps

  • In your inventory, find a different shape from the one you normally use, and wear it, replacing the one you have on. If that doesn't fix the issue, then do the same thing for your
    • system skin
    • system eyes
    • system hair base
    • If that doesn't work, read on.
  • If you have RLV enabled, in Preferences → Firestorm → Extras (top option), disable it and relog, then try the above step again.
  • Your inventory needs to be fully loaded before you will bake. Click on the Recent tab of the Inventory window. Make sure that the inventory count doesn't say “Fetched” or “Fetching”; if it does, your inventory is still loading. Let it finish. If it isn't moving, try typing random characters into the inventory search box.
    Should your inventory not fully load, please refer to this page for help on getting it to load.
    Once you have done that, try the first bullet point again.
  • Select a different outfit in your Outfits folder and select Replace Outfit.
  • Make sure that all of the 4 required system parts are worn:
    • Method 1: In your Inventory window, Inventory tab, Current Outfit folder, make sure the four required system parts all show as worn: shape, skin, eyes, hair base. If not, right-click them and wear them.
    • Method 2: Open the Appearance window (Avatar menu → Appearance), go to the Wearing tab, scroll to the bottom, and make sure that the last four items listed are your shape, skin, hair and eyes. If one of those items is missing, find it in inventory and wear it.
    • If you are unable to wear all 4 items, create a new folder in your inventory with the 4 basic items, plus system clothing if you wish (no attachments). Then right click the folder and select Replace Outfit.
  • If you are connected via cellphone, you will most likely see yourself and everyone grey. You need to have a decent internet connection. So if possible, switch to that, then see if you rez in normally.
  • Reboot your router/modem.
  • If none of the above helps, then continue reading.

Avatar Is Invisible

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

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

Avatar Textures Remain Blurry

This also applies if you are a cloud.

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

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

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

For more info, you can refer to this JIRA.

Avatar Textures Remain Grey

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

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

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

For more info, see this LL JIRA.

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

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

Persistent Bakefail Not Fixed by Anything Above

Changed Clothing Doesn't Update for Others

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

firestorm_change_log_6.3.2.58052

Firestorm Release Notes 6.3.2.58052 Bakes On Mesh


Firestorm 6.3.2.58052 Downloads can be found HERE


New Features And Improvements In This Release

This page shows all changes since the Firestorm 6.2.4.57588 Release.
If you are updating from an earlier version than 6.2.4, see HERE for previous release notes.

For a summary of all the major new features and improvements in this release, please
see Inara Pey's Firestorm 6.3.2.58052 blog post.



Linden Lab New Features and Improvements


BOM - Bakes On Mesh

Bakes on Mesh is a new feature to allow system avatar baked textures to be shown on mesh attachments.

Basic features
  • Any face of a mesh object can be textured using one of the server baked textures.
  • The corresponding region of the system avatar is hidden if an attached mesh is using a baked texture.
  • 5 new bake channels - leftarm, leftleg, aux1, aux2, aux3. You can use the new bake channels on the face of a mesh.
  • A universal wearable type.
  • New tattoos for universal wearable type -
    • HEAD_TATTOO, → baked to head
    • UPPER_TATTOO → baked to upper
    • LOWER_TATTOO, → baked to lower
    • SKIRT_TATTOO, → baked to skirt
    • HAIR_TATTOO, → baked to hair
    • EYES_TATTOO, → baked to eyes
    • LEFT_ARM_TATTOO, → baked to left arm
    • LEFT_LEG_TATTOO, → baked to left leg
    • AUX1_TATTOO, → baked to aux1
    • AUX2_TATTOO, → baked to aux2
    • AUX3_TATTOO, → baked to aux3
Benefits
  • Avoid the need for texture appliers → easier customization workflow.
  • Avoid the need for onion avatars → fewer meshes, fewer textures at display time.
  • Avoid the need to sell full-perm meshes. You can customize any mesh you have modify permissions for simply by setting the flags and equipping the appropriate wearables.

Avatar wearables are baked into eleven different textures (BAKE_HEAD, BAKE_UPPER, BAKE_LOWER, BAKE_EYES, BAKE_SKIRT, BAKE_HAIR, BAKE_LEFTARM, BAKE_LEFTLEG, BAKE_AUX1, BAKE_AUX2, BAKE_AUX3) by the baking service.
You can now apply these textures to your avatar’s object attachments’ diffuse texture slot.
Right-click on the attachment, click edit and from the edit face menu select textures.
Click the diffuse texture icon to open up the texture picker.
The texture picker has an extra radio button mode called ‘bake’ for selecting server bakes.
The ‘bake’ radio button mode has a dropdown for selecting BAKE_HEAD, BAKE_UPPER, BAKE_LOWER, BAKE_EYES, BAKE_SKIRT, BAKE_HAIR, BAKE_LEFTARM, BAKE_LEFTLEG, BAKE_AUX1, BAKE_AUX2, BAKE_AUX3 server bake textures.
When an attachment is using a baked texture, the corresponding base mesh region of the system avatar is hidden.

If a mesh face is set to show a baked texture but is not attached to an avatar, you will see a default baked texture.
If you are using an older viewer without bakes on mesh support, then faces set to show baked textures will also display as the default baked texture, and base mesh regions will not be hidden.

For more detailed documentation, please see:



Love Me Render 3

A variety of graphics/rendering related fixes from Linden Lab.
Linden Lab Love Me Render 3 Release Notes
Ruslan ProductEngine, AndreyK ProductEngine, AndreyL ProductEngine, Maxim ProductEngine, Mnikolenko ProductEngine


Lots and lots of Maintenance fixes

Too many to list them all here.
See the full change log for details.
Highlighted fixes are listed below.

Nat Linden, Anchor Linden, Vir Linden, Brad Linden, Callum Linden, Eli Linden, Ruslan ProductEngine, AndreyK ProductEngine, AndreyL ProductEngine, Maxim ProductEngine


  • NEWAdded the ability to edit notecards in an external editor
    For Firestorm, to set the external notecard editor, go to Preferences → Firestorm → Build 1 → External Editor → Browse to the program or application and select then press OK.
    When a notecard is open, you will see a new “Edit” button bottom left.
    Clicking the Edit button opens the Notecard in the external editor.
    Making changes in the external editor & then saving the file in the external editor will upload the changes into the notecard in Second Life.
    If no external editor is selected in Preferences, the viewer will try to use the external editor that you have set to open txt files.
    NOTE: There is a known bug with this feature that causes the order of embedded content to break - see BUG-227626 for details
    Maxim ProductEngine
  • NEWAdded the ability to duplicate a group role
    The feature allows you to duplicate a group role so that the copied role has the same permissions and you can just give the copied role a different title.
    This feature was requested in BUG-226986
    Open the group profile → Members & Roles → Roles → Left click on a role to select it → Click the “Copy Role” button.
    AndreyK ProductEngine
  • NEWIncreased the allowed sound clip length from 10s to 30s
    This adds support to the viewer to upload & play sound clips up to 30 seconds in length.
    Currently, sound uploads over 10 seconds are not possible, but will be soon when the server-side support is added by Linden Lab.
    Firestorm 6.3.2 is ready to support this feature as soon as the required server-side changes are made
    AndreyL ProductEngine
  • Improved the performance impact of selection outlines
    Ruslan ProductEngine
  • Implemented separate texture layers alignment for diffuse, normal & specular textures
    Ruslan ProductEngine
  • Fixed “Align planar faces” not working on normal or specular maps
    This fixes BUG-6489
    Ruslan ProductEngine
  • Fixed Animesh objects not being highlighted when viewing objects owned by users in 'About Land'
    This fixes BUG-227240
    Maxim ProductEngine
  • Fixed Object Profile > Details not showing magenta highlight for mesh objects
    This fixes BUG-227252
    Maxim ProductEngine
  • Fixed depth mode snapshots broken when snapshot size is set to anything above current window size
    This fixes BUG-227191
    Ruslan ProductEngine
  • Fixed Animesh objects being difficult to select
    This fixes BUG-226860
    AndreyK ProductEngine
  • Fixed the last CEF update breaking many visitor trackers & scoreboards
    This fixes BUG-226704
    AndreyK ProductEngine
  • Fixed proxy port number is limited to 12K instead of 65K
    This fixes BUG-226789
    AndreyK ProductEngine
  • Renamed the abuse category for Skill gaming
    Under Help → Report Abuse, “Gaming Policy Violation” has been changed to “Skill Gaming Policy Violation”
    AndreyL ProductEngine
  • Fixed Experiences search resetting the “Max Content Rating” back to general each session
    This fixes /BUG-226900
    Maxim ProductEngine
  • Fixed the broken “Cache Hit Rate” in Statistics
    This fixes BUG-226855
    Maxim ProductEngine
  • REMOVEDRemoved Facebook In-world Sharing
    Removed the ability to share photos & post to Facebook, as this was broken at the Facebook end
    Ref: BUG-225205
    AndreyL ProductEngine


Firestorm New Features and Improvements


  • Merge up to Linden Lab viewer 6.3.1 code-base Image may be NSFW.
    Clik here to view.
    FIXME

    Firestorm 6.3.2.58052 is fully merged up to the 6.3.1 Linden code-base Image may be NSFW.
    Clik here to view.
    FIXME
    , plus some cherry picked fixes from upstream.
    Ansariel Hiller
  • Updated FMOD Studio to 2.00.03
    Full FMOD Studio release notes
    Ansariel Hiller - Windows
    Nicky Dasmijn - Mac & Linux


RLVa Fixes and Improvements


Firestorm 6.3.2 is using the RestrainedLove API: RLV v3.2.1 / RLVa v2.2.0.57583
Image may be NSFW.
Clik here to view.
FIXME

Here are the full RLVa 2.2 Release Notes



Skinning And Translations


  • FIXEDFixed a typo in German translation for Exporting Collada Confirmation
    This fixes FIRE-24253
    Ansariel Hiller
Translation updates and improvements
  • German - Ansariel Hiller
  • Polish - PanteraPolnocy Resident




For Builders And Scripters



Communications


  • NEWAdded Discord rich presence support
    This feature allows you to connect your SL account with your Discord account.
    Once connected, Discord will show your SL online status & session length, and optionally, your username and location in SL.
    For further details, see the Firestom Discord wiki page.
    Comm → Discord
    Liny Odell, Ansariel Hiller, Nicky Dasmijn



  • FIXEDMovement at region crossing - Fixed Predict behaving like Stop
    This fixes FIRE-24184
    Preferences → Move & View → Movement at region crossing
    Ansariel Hiller


Inventory, Appearance, Avatar


  • NEWAttachments now auto-refresh if they are ghosted on teleport
    Added timer for refreshing attachments if attachments were attempted to get killed after the actual teleport finished
    This feature should mostly solve the problem where attachments are invisible to observers after a teleport or region change
    It provides the same function as “Refresh Attachments” under Avatar → Avatar Health, but the refresh is triggered automatically when needed
    This feature is enabled by default
    Optionally, if the debug setting FSExperimentalLostAttachmentsFixReport is set to TRUE, Firestorm reports attachments that were attempted to get detached during a teleport or region crossing to nearby chat, followed by reporting “Refreshing attachments…” to nearby chat when the auto-refresh starts
    This should hopefully workaround FIRE-12004 and BUG-7761 until there is a server-side fix from Linden Lab.
    Ansariel Hiller
  • FIXEDFixed being unable to add multiple copies of identical system layers
    Removed the restriction on adding system layers with identical asset UUIDs at the same time since at some point LL fixed it server-side and creating a new asset UUID
    The fixes FIRE-24334
    Ansariel Hiller
  • FIXEDFixed LookAt target clamping sometimes causing avatar eyes to cross
    This fixes FIRE-24175
    Chaser Zaks
  • FIXED Broke “wear_folder” links from working in legacy profiles
    Previously it was possible to put obfuscated links in your legacy profile that, when clicked by another user, would replace outfit with one of the default outfits from the inventory library.
    For example [secondlife:///app/wear_folder/?folder_id=bedd047e-a3d7-23e6-57bc-1ef367d848e7 See me nude!] would just display as a “See Me Nude” link.
    This will now no longer work & The link text will now display as “Wear Inventory Folder”.
    Also marked user-editable fields in legacy profiles as untrusted content
    This fixes FIRE-24262
    Ansariel Hiller


User Interface


  • REMOVEDRemoved the setting “Use HTTP for receiving textures” from SL-only viewer preferences
    Fetching textures over UDP on Second Life grids is no longer supported.
    This fixes FIRE-24256
    Liny Odell


General


  • IMPROVEMENTPayment confirmation is now skipped if paying yourself
    Also fixed a case where the payment confirmation notification would not be shown if the amount would be exactly the remaining L$ balance
    This improvement was requested in FIRE-24208
    Ansariel Hiller
  • IMPROVEMENTThe Sanity Checker warning icon now calls up the sanity checker dialog with a “fix it” option.
    Zi Ree
  • FIXEDPartially fixed alpha triangles showing on certain mesh hairs on Linux
    This fixes the majority of the affected hairs but not all of them.
    This “fixes” FIRE-23370 and BUG-8801
    Nicky Dasmijn
  • FIXEDFixed compiler warnings when building the viewer with GCC 8.3.0+
    This fixes FIRE-24294 and BUG-227485
    Chaser Zaks


Performance and Stability Improvements


  • CRASH FIXFixed crash in legacy search on Latency skin
    Ansariel Hiller


Known Issues

Firestorm JIRA Link Details Official viewer bug? 1) New on 6.3.2?
FIRE-22968Sim surrounds no longer showing with new update to firestorm BUG-225295 No
FIRE-22746 Alpha masking with mask cutoff of 1 shows white lines in it BUG-225039 No
FIRE-22776 Web-page does not scroll using mousescroll in internal viewer browser BUG-216094 No
FIRE-22212 Dragging a folder of no copy items into object contents does not remove the no copy items from inventory view till relog BUG-203011 No
FIRE-22230 Gestures containing the “BigSmile” or “Open Mouth” built-in animation take way too long to load BUG-139305 No
FIRE-19333 Legacy Profile 2nd Life Pic sometimes blurry and opens at 32×32 instead of full size N/A No
FIRE-18160 [CEF] Media volume control has no effect on media volume. Mac & Linux onlyBUG-11821 No
FIRE-17392 Counts of individual Roles are reported wrong in the Group info BUG-10804 No
FIRE-17101 Unable to see group members belonging to any group role in the Roles tab until you switch to the Members tab and back to Roles tab. BUG-10447 No
FIRE-16745 Standing up from Groundsit triggers walk/run BUG-10122 No
FIRE-15967 Avatar moved underground when adding accessories to worn items while in edit mode. While wearing deformer skeleton. BUG-8616 No
FIRE-15852 Some rigged mesh avatars are deformed on post-attachment fix viewers for self and all observers BUG-9010 No
FIRE-12520 Highlight transparent no longer highlights particles that use a texture containing alpha BUG-4731 No
FIRE-12496 On Materials enabled viewers, textures containing alpha display as full bright if basic shaders are disabled BUG-4709 No
FIRE-12213 Enabling Advanced Lighting Model in graphics preferences causes horizon to invert BUG-4430 No
FIRE-12072 Alpha masking is broken again on avatar clothing when ALM is enabled BUG-4357 No
FIRE-11929 Some prims have black moire-like patterns when ALM is enabled MAINT-3302 No
FIRE-11740 Mesh clothing with solid/sheer clothing combo pixelated
Mac only
MAINT-3238 No
FIRE-10883 Context Menu - The top of the right click menus are hidden No No
FIRE-10041 Rotating Objects flicker from a distance MAINT-2648 No
FIRE-7979 Changing from Ultra to Low with basic shaders disabled breaks much of the UI MAINT-3363 No

Change Log Since 6.2.4.57588 Release

1)
Only publicly viewable issues are given as links

fs_index

General Index

X

fs_search_issues - [Firestorm Web Feed Issues]

Firestorm Web Feed Issues

If you get a black screen when opening Search, Web Profiles, or Destinations, then try the following:

  • Sometimes the window opens minimized at the top left; check to see if this is the case.
  • Go to PreferencesNetwork & Files -> Connection and ensure that the following are all enabled:
    • Enable Plugins
    • Enable Javascript
  • If this is not enough to get search working then go to PreferencesPrivacy -> General and click on Clear History (top of the window). Then relog.
  • If this still doesn't help, then make sure that your anti-virus software hasn't flagged, and possibly deleted, SLPlugin.exe, which is required for search to work. Try disabling your anti-virus completely, then reinstalling Firestorm to a different folder. Once done, re-enable your anti-virus and make sure you set it to exclude SLPlugin.exe from being scanned.

Some other issues affecting search are covered here.


downloads - [Current Release for Second Life]

Firestorm Viewer Downloads For Second Life

IMPORTANT:
How to update Firestorm:
Firestorm Viewer is certified to be free of viruses and malware.

Current Release for Second Life

Firestorm 6.3.2 (58052) Bakes On Mesh Release

Firestorm 6.3.2 (58052) Release Notes

“n/a” in the table below means “not available”; see the boxed note above.

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit
64-bit only SL only X Full Release Firestorm Release 6.3.2.58052 64 bit Windows Setup.exe
MD5 Checksum: 22D4173CD14803AE99F0592D1813171A
Windows
32-bit
32 and 64 SL only X Full Release Firestorm Release 6.3.2.58052 32 bit Windows setup.exe
MD5 Checksum: AD980B6F8297E182F82740B3DAAC28EA

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit
64-bit only SL only X Full Release Firestorm Release 6.3.2.58052 64 bit Intel Mac.dmg
MD5 Checksum: DC8CA6ADBE9862ECD2BD5A1A18DC4BB7
Mac
32-bit
32 and 64 SL only X n/a n/a

linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit
64-bit only SL only Full Release Firestorm Release 6.3.2.58052 64 bit Linux.tar.bz2
MD5 Checksum: CF3B34B07C50AD43D9952117F1FB60CF
Linux
32-bit
32 and 64 SL only n/a n/a

More information about the 64-bit builds can be found here.

Current Release for OpenSim

OpenSIM versions of FS do not have Havok. That only matters if you're uploading mesh objects and need to specify the mesh physics properties, or if you need to manipulate the region navmesh for pathfinding. The terms of the Havok license prohibit its use anywhere but Second Life, so it's not present in OpenSim versions.

Firestorm 6.0.2 (56680) Animesh Release

Firestorm 6.0.2 (56680) Animesh Release Notes

“n/a” in the table below means “not available”; see the boxed note above.

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.0.2.56680OS 64 bit Windows Setup.exe
MD5 Checksum: 08a67070083a1399997db2aaa102d8df
Windows
32-bit OpenSim
32 and 64 OpenSim only Full Release Firestorm Release 6.0.2.56680OS 32 bit Windows setup.exe
MD5 Checksum: 9ddaac654820a5168c1f4bed4603fc6b

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.0.2.56680OS 64 bit Intel Mac.dmg
MD5 Checksum: 5c152ac11982c01b25edcadef26e9366
Mac
32-bit OpenSim
32 and 64 OpenSim only n/a n/a

linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit OpenSim
64-bit only OpenSim Only Full Release Firestorm Release 6.0.2.56680OS 64 bit Linux.tar.bz2
MD5 Checksum: c11857b11dbb4a4accfc785529d63451
Linux
32-bit OpenSim
32 and 64 OpenSim Only Full Release Firestorm Release 6.0.2.56680OS 32 bit Linux.tar.bz2
MD5 Checksum: 9e20172f32789f68671c0be8bcdd8315

Supported Operating Systems

Windows

  • Windows 7 SP1, 8.1 and 10 32bit and 64bit are supported.
    Earlier versions of Windows are not supported.
  • Firestorm 5.1.7, 6.0.2, 6.2.4 & 6.3.2 will NOT even install on Windows XP.
  • Firestorm 5.1.7, 6.0.2, 6.2.4 & 6.3.2 may install on Windows Vista but is likely to be very unstable.
  • Windows 10 - Firestorm 5.1.7, 6.0.2, 6.2.4 & 6.3.2 are compatible with Windows 10.
    However, if you are running Windows 10 on a system with an older Intel graphics card which does not support Windows 10 - Intel HD 2000, Intel HD 3000 or anything marked as “No” for Windows 10 on this list,
    you will only be able to run the 32bit versions of Firestorm 5.1.7, 6.0.2, 6.2.4 & 6.3.2 even if you have a 64bit version of Windows 10.
    Please see this page for detailed instructions if you are running Windows 10 on an older unsupported Intel card and have problems running Firestorm 5.1.7, 6.0.2, 6.2.4 or 6.3.2.

Mac

  • Mac 10.9 or later OS X versions are supported.
  • MacOS Mojave 10.14 will run Firestorm 5.1.7. viewer and newer.
  • Mac PPC is not supported.
  • Firestorm 5.1.7 & later viewers will NOT run on PPC Mac 10.6, 10.7, 10.8, 10.9, or 10.10.

Linux

  • We use Debian to build our Linux viewer. Any actively maintained, up-to-date Debian-based distribution should be able to run Firestorm. However, due to the variety of distributions and SL's small Linux user-base, we cannot provide testing and support beyond those systems that our own team use. Feel free to submit details of your success and/or failure to any Firestorm team member or to the Firestorm Jira.
  • Some additional libraries and/or packages may be needed; they are listed on this page.
  • Certain older unsupported hardware may not be able to support Firestorm.

Additional Downloads to Fix Problems

Windows

  • SLURLs not working in your browser, or choose to open with a different viewer (Windows)

Additional Downloads to Enhance User Experience

Flash

Firestorm 6.3.2, 6.2.4, 6.0.2, 5.1.7 Release

  • Windows - Download in Firefox or Chrome to play Flash media inside Second Life.
    Choose the correct operating system under Step 1.
    Choose FP 32 for Opera & Chromium - PPAPI under Step 2.
    Install Flash.
  • Mac - Ensure that you have the most recent version of Flash for Safari installed. You an get this via the normal update process, or from Adobe.
    Choose the correct operating system under Step 1.
    Choose FP 32 for Safari and Firefox – NPAPI under Step 2.
    Install Flash.
  • Linux - You need to have the pepperflash plugin installed, which can be satisfied by installing Google Chrome.

Quicktime

Firestorm 6.3.2, 6.2.4, 6.0.2, 5.1.7

  • Windows - Quicktime does not need to be installed to play media on Firestorm 5.0.1 or later.
  • Mac - Quicktime to play streaming videos. (iTunes is not needed)

GStreamer

for Linux only

  • Info for download to play streaming videos. (Please read page for info on installing GStreamer for your particular distribution.)

Growl

  • Growl for Windows– As of November 2018 this site is dead. Users who already have Growl installed can continue to use it for the time being. Windows users may be able to download a copy from its github release page.
  • Mac– This site will lead you to the Mac App Store for downloading. Please note the reviews and the update status of Growl before purchasing; Firestorm cannot guarantee its functionality.
  • Linux: Growl is implicit in libnotify, which should come already installed in most distros. However, if you are on a 64-bit linux, you may need to install the 32-bit version of libnotify. For ubuntu and similar (like mint), run the following command:
    sudo apt-get install libnotify4:i386

DirectX Runtime

Windows only

  • DX runtime April 2011 to help increase performance and stability. For all versions of Windows. Please refer to this page.

Video Drivers

Mac drivers are included with OS upgrades. However, to determine what card you have, select “About this Mac” from the Apple menu, then click “More Info”. Under Hardware select Graphics/Displays.

If you are not sure what type of video card you have, use GPU-Z found (Windows only) here. For linux, in a console use:
lspci | grep VGA

Nvidia Video Driver

  • Latest driverLast checked 29/09/2019 - Windows: 436.30 (2019.9.10) - Linux: 430.50 (2019.9.11)

ATI Video Driver

  • Latest driverLast checked 29/09/2019 - Windows: Adrenalin 2019 Edition 19.9.2 (9/23/2019 ) - Linux: 19.30 (8/13/2019)

Intel Video Driver

Source code

firestorm_classes

Firestorm Classes

These classes are based on our official Firestorm release and are conducted in text except when otherwise noted. There's no need to talk, but you may want to be able to hear. We also usually have help available to answer questions in text. This schedule is subject to change.

Note that it is best if you are on Firestorm for the classes.

Locations are indicated in the far right column as follows:

Class times and days change regularly. Classes may be held any day of the week, with start times from 8 am to 7 pm SLT. Nonetheless, if the class times are still inconvenient you may prefer to watch recorded versions of some of these classes on YouTube.

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

*All times SLT*

Tue 1 Oct 2 Pm – QuickPrefs Customization + Lag (TEXT ONLY)
Two mini-classes in one. One discusses the causes of lag in SL. The other explains how to customize your Quick Preferences.
FS
Wed 2 Oct 2 Pm – Preferences Set 4 (TEXT ONLY)
We will cover some of the Firestorm preferences (Colors, Skins, Notifications, User Interface, Sounds and Media).
FS
Thur 3 Oct 12 Pm – Reporting Bugs, Requesting Features (TEXT ONLY)
Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need.
FS
Fri 4 Oct 2 Pm – Avatar Complexity and Graphics Presets (TEXT ONLY)
Learn how to boost performance with av complexity and improve usability with the presets.
FS
Sat 5 Oct 2 Pm – Firestorm Skins (TEXT ONLY)
This class covers the differences among Firestorm's many skin options, including the Vintage Classic and Colorable User Interface skins.
FS
Sun 6 Oct 3 Pm – Animation Overrider (TEXT ONLY)
On Firestorm, you can save scripts and HUD space by running your AO animations through the viewer. Learn how to set up and get the most out of this feature.
FS
Mon 7 Oct 12 Pm – Basic Troubleshooting (TEXT ONLY)
An introduction to basic methods to start locating problems. Focused on Firestorm but some parts are non-viewer-specific.
FS
Tue 8 Oct 2 Pm – Backing up Settings and Logs (TEXT ONLY)
This class covers how to save your settings and chat logs on your computer. Recommended to take this before the Clean Install class.
FS
Wed 9 Oct 3 Pm – Contact Sets (TEXT ONLY)
There is a cool feature called Contact Sets that lets you organize your Contact List. We'll cover how to set them up and use this epic feature.
FS
Thur 10 Oct 2 Pm – Introduction to Firestorm and the Wiki (TEXT ONLY)
This class gives you an overview of the Firestorm Viewer and of our greatest informational resource, our Wiki, including search tips.
FS
Fri 11 Oct 2 Pm – Clean Install (TEXT ONLY)
Learn how to correctly and quickly perform this most fundamental and important of tasks. Recommended taking Settings Backup class first.
FS
Sat 12 Oct 2 Pm – Menus 1 (TEXT ONLY)
We will be covering the menus on the top bar, from Avatar through Help.
FS
Sun 13 Oct 3 Pm – Menus 2 (TEXT ONLY)
We will cover the Advanced and Developer menus in the top bar.
FS
Mon 14 Oct 12 Pm – Odds & Ends 1 (TEXT ONLY)
This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.
FS
Tue 15 Oct 2 Pm – Odds & Ends 2(TEXT ONLY)
Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more.
FS
Wed 16 Oct 3 Pm – Preferences Set 1 (TEXT ONLY)
We will cover some of the Firestorm preferences (General, Chat, Privacy), based on our current release.
FS
Thur 17 Oct 12 Pm – Preferences Set 2 (TEXT ONLY)
We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release.
FS
Fri 18 Oct 2 Pm Preferences Set 3 (TEXT ONLY)
We will cover some of the Firestorm preferences (Move & View, Advanced, Firestorm), based on our current release.
FS

fs_632_prerelease - [JIRA Known Issues]

Firestorm Beta 6.3.2. Prerelease

BoM - Bakes on Mesh: LL Bakes on Mesh Viewer is Live
LMR - Love Me Render: Graphics/rendering related fixes. See release notes below for more details.
Maintenance - Umeshu: Assorted crash fixes, improvements and new features from LL.

Bakes on Mesh Resources

User Interface Changes

  • The Texture Picker window in Edit now displays a new option called “Bake”. This option is only available when the object is being worn and is required when setting your mesh to allow baking. Please see the KB for more information on how to use KB - Bakes on Mesh
  • There is a new inventory asset that can be found in the options to create New Clothing. The Asset is called “Universal” and the purpose of it is explained in the KB KB - Bakes on Mesh
  • For those who have not used system layers for some time, this is a reminder that you can sort the order of your layers. Do this via “Edit Outfit”, select the layer and then click the arrow up or down to move it. You can only re-order them by asset type, for example, you cannot move a tattoo above a shirt.
  • Facebook removed from inworld sharing menus.
  • Comm Menu - Discord. Toolbar Button. Adds the ability to connect to your Discord account. See Discord
  • Sound File upload limit increased from 10s to 30s. Awaiting server side support.
  • Group Roles. Added the ability to duplicate a role with a copy button.
  • Notecards. Added option to edit in external editor. Go to Preferences - Firestorm - Build 1 - External Editor - Browse to program or application and select, press OK. (see Known Issues below)

RestrainedLove API: RLV v3.2.1 / RLVa v2.2.0

Other changes and updates

Second Life Release Viewer version 6.3.1.530559 - Maintenance

Release Notes for v6.3.1. (530559) - Second Life Viewer Released on September 5, 2019.
https://releasenotes.secondlife.com/viewer/6.3.1.530559.html

Maintenance - Umeshu

Second Life Release Viewer version 6.3.0.530115

Release Notes for v6.3.0. (530115) - Second Life Viewer Released on August 26, 2019.
https://releasenotes.secondlife.com/viewer/6.3.0.530115.html

Bakes on Mesh

Bakes on Mesh is a new feature to allow system avatar baked textures to be shown on mesh attachments.

Second Life Release Viewer version 6.2.4.529638

Release Notes for v6.2.4. (529638) - Second Life Viewer Released on August 5, 2019.
https://releasenotes.secondlife.com/viewer/6.2.4.529638.html

Love Me Render

This viewer adds a variety of graphics/rendering related fixes.

Other

FMOD Studio 2.00.03 (updated Windows, Linux, Mac)

KDU v7.10.7 (Windows, Linux, Mac)

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

LibVLC Version: 2.2.8

Chromium Embedded Framework (CEF) Dullahan:

  • Dullahan: 1.1.1320
  • CEF: 3.3626.1895.g7001d56
  • Chromium: 72.0.3626.121
  • Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

JIRA Known Issues

JIRA Bug Fixes

  • FIRE-24033 - [BUG-40745] [SL-3242] When ALM is enabled, Depth dropdown in snapshot fails on higher-than-screen resolution
  • FIRE-24112 - Purple highlight doesn't show when selecting mesh links in the inspection floater
  • FIRE-23074 - [BUG-226953] [SL-11139] LLFontGL::getStringFromStyle() never return “NORMAL”
  • FIRE-23080 - [BUG-226952] [SL-11138] Not all bitmaps formats are supported by LLImageBMP
  • FIRE-24013 - [MAC] [HiDPI] [BUG-226660] [SL10898] HiDPI when enabled, unable to zoom using Alt and the mouse without getting a blackscreen
  • FIRE-24175 - LookAt distance limit causes undesired eye bone behaviour - crossed eyes
  • FIRE-24184 - REGRESSION preference/Move&View/ Movement - Movement at Region crossing - PREDICT
  • FIRE-24334 - Cannot add multiple copies of system layers
  • FIRE-24202 - [BUG-227559] [SL-11848] Crash - Face with no texture index references indexed texture draw info
  • FIRE-28972 - Crash - Face with no texture index references indexed texture draw info

JIRA Improvements

  • FIRE-24208 - Skip Payment Confirmation Dialog When Paying Self
  • FIRE-24262 - [SL-11721] Warn on secondlife: command link to replace outfits

JIRA New Features

JIRA Translations

  • FIRE-24253 - Exporting Collada Confirmation has missing translation/typo in german

JIRA Tasks

Aditi / Beta Grid

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

fs_translation - All right...

Translating Firestorm

Image may be NSFW.
Clik here to view.

This page gives an outline of how to go about translating Firestorm into another language. This applies to the viewer itself, not the help files (wiki).

For simplicity it focuses only on the 'Firestorm' skin (theme is irrevelant).

When the viewer starts, it loads to memory all XML files from the default, English folder: https://hg.firestormviewer.org/phoenix-firestorm-lgpl/files/tip/indra/newview/skins/default/xui/en - interface layout and all neccessary strings.

If the language selected by user is something other than English, let's say Polish, the viewer tries to find a file in skins/default/xui/pl with the same name as English one, and replace found attributes and values in memory, on the fly, with the ones in the localization folder. Note “attributes and values” - the viewer is not replacing whole files. Quick example:

Basic English localization has a lot of tags, which are not needed in the localization itself. In fact, the most often used in non-English ones are only “label”, “tool_tip” and “name” (the latter to assign elements properly).

The viewer doesn't have “a list of strings”, but around 400 files in XML language, which need to be created and translated.

Changes from version to version (release to release) are usually not very drastic ones (https://hg.firestormviewer.org/_admin/search?q=translation+update%2A&type=commit&max_lines=10), but the initial amount of workload can take around 2-3 weeks of 6-7 hours of constant work. Maintaining already created translation is not that hard.

At the beginning there is no direct repository access. You must to know how to create a patch in diff format, preferably using TortoiseHG (Mercurial system client), and attach it to our JIRA bug reporting system: https://jira.firestormviewer.org/browse/FIRE-21006?jql=issuetype%20%3D%20Translation%20AND%20text%20~%20%22translation%20update%22

The biggest issue is to be able to fit all these strings into size-limited fields in UI. You can't say “hey, I'd like to make this space bigger” - you must fit there with your strings. For example, open Phototools floater, both in English and a different language, and you'll see a lot of shortened strings everywhere.

The recommended editor for this work is Notepad++, with unix line endings, in UTF-8 format without BOM.

IMPORTANT: In some places, you will find placeholder templates; for example: [SECONDS] These will always be enclosed in square brackets and in upper case. These should be left alone, as the viewer will replace the text at run-time. Some placeholders are visibile in the image below.

Image may be NSFW.
Clik here to view.

The “XUI preview tool”, available on the login screen after pressing CTRL + T, can be helpful in quick changes, without the need to shutdown and start the viewer again: Login screen → Debug menu at the top → XUI Preview Tool (Ctrl-Alt-D to enable the Debug menu, if it is not visible). In the image, the arrow is showing which language is the chosen one, with English as the default one.

Bonus note: If you'd like to see how does the process of translation review looks like, and get few tips about translating / formatting as well, then please read comments on this JIRA: FIRE-21006

fs_missing_inventory - [Checking Your Connection]

Missing Inventory

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

  • If items that you rezzed out in-world are missing, then refer to this page instead.
  • If you cannot receive FOLDERS shared to you by another avatar, contact SL support, as this is a database problem that can only be fixed by them.

Part 1 - Basic Steps

  • First and very important: TP to a known low lag region to do any of the things listed below. Once there, reduce draw distance significantly, to reduce the load on your network connection. Stay there while working through this page. These locations are recommended:
  • If the number of items appears correct, but not everything is showing, reset your inventory filters. On most viewer skins, this means clicking the Gear menu at the bottom of your inventory and selecting “Reset Filters.” On Vintage skin (this is what you're using if you logged in with Phoenix Mode) or Ansastorm skin, click Inventory → Reset Filters in the inventory menu.
  • If you are looking for Marketplace items using Inventory search, and they are not showing, ensure that you have the Received items folder shown in inventory, rather than as a button: Preferences → User Interface → Interface Windows → Show the Received Items folder in normal inventory. Or, click the Received button to see what items are in there.
  • If a system folder is missing, you may have opted to hide empty system folders: Preferences → User Interface → Interface Windows → Hide empty system folders from inventory.
  • In your inventory, type letters into the search filter. It doesn't matter what letters; the purpose is to prod the search into finding more items. If the fetch stalls again, pick a different letter.
  • For any/all folders that appear to be missing inventory, try creating a new item, of the appropriate type, in the folder. So for example, if you appear to be missing things in the Clothing folder, right-click the folder name → New Clothes → New Shirt. Then relog.
  • Try clearing your inventory cache.
    • Method 1: Open Preferences -> Network & Files -> Directories, then click the Clear Inventory Cache button, then relog to Hippo Hollow or whichever low-lag location you chose.
    • Method 2: If Method 1 did not work, clear the inventory cache manually:
      • Click the Open button to the right of cache location. This should open a file picker window.
      • Locate the .gz file with YOUR avatar key. Your key can be found in your profile, under your name. (Depending on your OS settings, you may not see the .gz at the end of the filename, but the file type should show as GZ, gzip, WinZip, or WinRAR, depending on what utilities you have installed on your computer.)
      • ESSENTIAL: Log out of Firestorm.
      • Delete the .gz file located above.
      • Log back in to Hippo Hollow.
      • Allow your inventory to fetch.
    • Note: If clearing inventory cache manually does not fix the problem the first time you try it, then it probably won't work on additional attempts, so don't keep doing it, unless you didn't delete the correct file the first time (though multiple relogs without cache clears may help).

Checking Your Connection

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

  • If you are on a wireless connection and are able to wire it in, do so.
  • Reboot your router/modem, leaving it unplugged and unpowered for a minimum of two minutes before powering it back up again.
    • If you have access to a different connection, try connecting your computer to it temporarily.
  • If the inventory is still not fetching all the way, view our page on bandwidth and speedtests to make sure your bandwidth is set optimally in the viewer. Although it may seem counter-intuitive, we have found that lower bandwidth settings usually allow for more reliable inventory loading than higher settings.
  • HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.
  • Please download the official SL viewer, install it, log in on it and see if the items show up there. If they do, then to make sure that you aren't being misled by cached inventory on SL viewer, wipe inventory cache there as well, and then see if your inventory fully fetches. If it does, then the problem is probably either loading or caching in Firestorm, and you can follow the set of suggestions below under “Method 2: Inventory Copy from SL Viewer.”

    If the missing items do not show up on SL viewer either, then file a support ticket with SL for assistance, making sure to specify that you have the problem with SL viewer.

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

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

Part 2 - Inventory Copy from SL Viewer

Image may be NSFW.
Clik here to view.
Your UUID

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

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

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

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

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

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

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

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

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

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

antivirus_whitelisting - [Whitelisting Steps for Specific AV Software]

Whitelisting the Viewer in Anti-Virus Software (plus Firewalls and Anti-Malware Sofware)

Introduction

Some anti-virus programs (and firewalls and anti-malware programs) will incorrectly flag a viewer - or necessary components of a viewer - as a virus or threat. They may remove the suspected part completely, rendering all or part of the viewer slow or non-functional. There is at least one anti-virus program which will scan every file placed on your computer, even if created by an authorized program. This can affect Firestorm (or any viewer) in that it will scan each and every texture placed in cache, slowing down performance of the viewer significantly, keeping objects and/or textures from rezzing, and keeping CPU usage high.

There is nothing we can do about this. However, it should be possible for you to tell your anti-virus (firewalls/anti-malware) that the viewer is safe; you will need to whitelist the viewer program as well as some components.

The following is a list of some protection software and how to whitelist. Naturally we cannot provide instructions for all existing programs, and the information here may be outdated. Therefore, it is strongly recommended that you consult the software manual for the specific program you use, for accurate and up to date information.

In the instructions below, substitute “firewall” or “anti-malware program” for “anti-virus” as needed.

Reinstalling and Whitelisting

Here are the steps to follow to reinstall and whitelist a viewer in such as way that the anti-virus program doesn't “mangle” the viewer yet again:

  1. Uninstall the viewer normally.
  2. Disable the anti-virus software completely
  3. REBOOT your computer to make sure that the AV is not running anymore.
  4. Reinstall the viewer.
    • On Windows, make sure you do not install it back to the default folder suggested; INSTALL TO A NEW FOLDER. This step is vital.
    • On Mac, simply reinstall to your Application folder as usual.
  5. In your anti-virus program, whitelist the following, per the instructions below (or better, consult the manual for your anti-virus software):
    • Windows: the viewer install folder
      • inside this, the viewer itself (firestorm.exe), slplugin.exe, slvoice.exe and
      • dullahan_host.exe (inside llplugin folder)
    • Mac: the Firestorm application (normally in your Applications folder)
    • the viewer cache folder
      • In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Now you need to locate the cache folder:
        • Windows Vista/7/8/10: C:\Users\[USERNAME]\AppData\Local\Firestorm
        • Windows Vista/7/8/10: C:\Users\[USERNAME]\AppData\Local\Firestorm_x64
        • Mac: /Users/[USERNAME]/Library/Caches/Firestorm
  6. REBOOT your computer at this time.
  7. Run the viewer to ensure that it is working correctly; do a test of search and voice to ensure that both work, checking that the respective plugins get loaded. LOG OUT of the viewer.
  8. Re-enable your anti-virus software and run the viewer again, repeating the tests above.

Whitelisting Steps for Specific AV Software

If you don't find your antivirus program listed, or the instructions are out
of date, check the help files or support site for your antivirus program.

Adaware free

  • Open the Adaware user interface
  • Click Scan Computer (second icon from top)
  • Go to Manage Exclusions and click View
  • Click Add
  • Navigate to main Firestorm application folder
  • Click OK
  • Repeat for Firestorm folders in User/Local

Advanced System Care

If you run the “junk files cleanup” function, then Advanced System Care is liable to trash your settings. Further to this, this program can also severely interfere with viewer connection to SL servers, as documented here.

Avast

2019-09-18 Update

it seems that in the early hours of 2019-09-18, an update was issues for Avast, and that update began “mangling” Firestorm. One user 1) provided the following:

I went into my Avast Virus Chest and scrolled to the bottom of the list where the Firestorm file to see if there was still a way to make an exception there….on the far right, after highlighting it, I saw 3 dots and there is an option there to Restore and Add Exception. I clicked it and it said The File was Happily Restored!

So what this is about is just to let you know that I didn't have to go through the procedure to Whitelist, in case you want to let others know who may have put it in the chest.

I reinstalled Firestorm over my present one just so I could get the shortcut (icon) again…logged on and all is well.

Basic Whitelisting

Refer to this page for how to whitelist. Please ensure that you whitelist both the viewer and the viewer cache folder.

If you cannot save snapshots to your hard drive
  1. Go to Settings → General tab
  2. Go to 'Blocked and allowed apps'
  3. Click 'Allow App' and scroll the list of programs to find Firestorm and select it (see picture below)

Image may be NSFW.
Clik here to view.

AVG

  • Open the AVG user interface.
  • Click Tools→Advance Settings.
  • Resident Shield→Exceptions.
  • The Add the program (or file, directory) you wish to be excluded from scans.
2019-09-18 Update

it seems that in the early hours of 2019-09-18, an update was issues for AVG, and that update began “mangling” Firestorm.

Bullguard

  1. Open Bullguard as normal
  2. Click on “Settings”
  3. Click on “Advanced”
  4. Go to “Antivirus” in the lefthand column
  5. Open the menu (down arrow)
  6. Select “Tuning”
  7. In the selection of tick boxes on the righthand panel, select Skip File/Folders
  8. Click on Files/Folders
  9. This will bring up a probably empty set of lines, so click on the “+” sign
  10. This should allow you to navigate to the particular folder, in this case the Firestorm Cache folder
  11. Select that and it will appear in the first line of the box
  12. To add other Firestorm folders listed at the top of this wiki page, repeat as needed
  13. Here is also a check box to allow you to skip processes. The procedure is the same: Click on “process”
  14. Click “+” and navigate to the .exe you wish to whitelist
  15. Close Bullguard.

Credits: Thanks to user Aishagain for this information.

F-Secure

(derrived from https://community.f-secure.com/t5/Security-for-PC/How-do-I-exclude-a-file-or/ta-p/15398)

  • Open Computer Security.
  • On the main page of Computer Security, click Settings.
  • Select Computer Security > Virus and spyware scanning.
  • Select Other settings > Manual scanning.
  • Click the Exclude files from the scan link. The Exclude from scanning dialog is displayed.
  • Select the Objects tab.
  • Select the Exclude objects (files, folders…) check box.
  • Click Add.
  • Navigate to and select the Firestorm install folder
  • Click Add again
  • Navigate to and select the Firestorm cache folder
  • Click OK to close the Exclude from scanning dialog.

Gatekeeper (Mac OS X)

If Gatekeeper prevents you from opening Firestorm, there is a simple workaround: See “How to open an app from a unidentified developer and exempt it from Gatekeeper” on this page. Once you have allowed Firestorm to open via this method, Gatekeeper will not flag it on subsequent launches (until you reinstall Firestorm again).

For a longer-term method, please visit here for a tutorial on whitelisting using the Gatekeeper software.

Kaspersky

In order to create an exclusion rule:

  • Open application settings window.
  • Select Protection on the left.
  • Click the Trusted Zone button in the Exclusions block.
  • Go to the tab Exclusion rules and click Add.
  • Select an exclusion type in the Properties field: Object and/or Threat type.
    • Object
      Click select object and choose a file, folder or a mask to exclude.
    • Select a Component in the corresponding field. The rule will apply to the selected component.
    • Threat type. Click enter threat type to select a file, folder or a mask to exclude.

Rules can apply to the following protection components:

  • Virus scan,
  • File Anti-Virus,
  • Mail Anti-Virus (Kaspersky Anti-Virus 6.0 for Windows Workstations 6.0.4.x only),
  • Proactive Defense (Kaspersky Anti-Virus 6.0 for Windows Workstations 6.0.4.x only),
  • Web Anti-Virus (Kaspersky Anti-Virus 6.0 for Windows Workstations 6.0.4.x only).

A scan if a disk or folder containing excluded objects scans the entire disk/folder except the excluded objects. Yet you can force scan excluded objects from the contextual menu (by right-clicking).

Also you can create an exclusion rule from within a report window:

  • Right-click the report object you want excluded.
  • Choose the option Add to Trusted Zone.

An Exclusion rule window will open. Make sure that you are satisfied with the new exclusion rule settings. Object name and threat type fields are assigned automatically on the basis of the report data. Click OK to create the rule.

Malwarebytes

For general whitelisting steps, visit Exclude detections in Malwarebytes on Windows devices

McAfee

We do not have specific details for McAfee. Check the McAfee control panel, or visit McAfee Consumer Support

Microsoft Security Essentials/Windows Defender

Basic Exclusions

https://support.microsoft.com/en-us/help/4028485/windows-add-an-exclusion-to-windows-defender-antivirus

For Win 10 (possibly also Windows 8.x):

  • Open Settings and in the search field at the top right enter defender
  • In Windows Defender click Virus & Threat Protection → Virus & Threat Protection Settings → Exclusions → Add or remove exclusions
  • Exclude the cache:
    • Click Add an Exclusion
    • Click Exclude a folder
    • Click in the address bar and type %LOCALAPPDATA% and press Enter
    • Click the Firestorm folder
    • Click the Exclude this folder button
    • Repeat this if you have more than one Firestorm folder (64-bit and 32-bit, for example)
  • Exclude the viewer executables
    • Click the Exclude a .exe, .com or .scr process button
    • Navigate to C:\Program Files\Firestorm-Release64
    • Click Firestorm-Releasex64.exe
    • Click the Exclude This file button
    • Repeat this for SLPlugin and SLVoice - and dullahan_host.exe (for FS 5.1.7 and later).
    • Repeat this for 32-bit Firestorm ( C:\Program Files (x86) )
Can't Save Files to Hard Drive (Snapshots, Chat Files, Backups, etc.)

Additionally, if you're on Windows 10 and you can't save snapshots to your hard drive (https://jira.phoenixviewer.com/browse/FIRE-23347), adding the viewer folders to the exclusion list may not be enough if you have 'Controlled Folder Access' enabled; you will need to add Firestorm to the allowed apps.

Try following these steps:

  1. Right click your Windows Defender icon on your system tray > View Security Dashboard > Virus and threat Protection > Virus & Threat Protection Settings > Controlled Folder Access
  2. Click the 'Manage Controlled Folder Access' link
  3. Under 'Controlled Folder Access' click the 'Allow an App through Controlled Folder Access' link
  4. Click '+ Add an allowed app'
  5. Browse to the viewer executable in the installation folder, left click to select , click Open at the bottom of the files explorer.

Alternatively, you can also simply disable the Controlled Folder Access feature by clicking the on/off button after Step #2.

Can't run Firestorm installer

See this page https://wiki.phoenixviewer.com/fs_install_crash#windows.

Norton

Add exclusion to Auto-Protect and Risk scan

  • Start Norton 360.
  • Click Settings.
  • Click Antivirus Protection.
  • On the Scans and Risks tab, under Exclusion/Low Risks, click Configure next to Scan Exclusions.
  • Under Scan Exclusions, click Add.
  • Browse and select the disk drive or folder or file you would like to exclude and click OK. If you want to include subfolders within the folder, check Include Subfolders.
  • Under Auto-Protect Exclusions, click Add.
  • Browse and select the disk drive or folder or file you would like to exclude and click OK. If you want to include subfolders within the folder, check Include Subfolders.
  • Click Apply > OK.
  • Click Apply > Close
Download Intelligence

Norton Internet Security includes a feature called Download Intelligence. This works such that the user community reports downloads as good or bad. While this may be very helpful, it can also be unfairly detrimental to programs, especially when they are updated as they are then treated as totally new.

Therefore, if you use Download Intelligence, you are urged to disable it before attempting to download any of our viewers, in order to avoid them being incorrectly reported as infected with a virus. Refer to this page for instructions.

Panda Cloud Antivirus Free (version 2.1.1)

  • Click on the “Antivirus” section of the UI.
  • Click on “Advanced Settings” (bottom of the panel current version)
  • Click on “Exclusions” tab
  • Choose “Add”, then navigate to your Firestorm installation folder and put a check in the box to the left of slplugin.exe (and llceflib_host.exe for FS 4.7.7 and later), and everything else you want to exclude. Once you've checked something, the “exclude” button at the bottom of the panel is enabled. Click it when you've finished checking off everything you want to exclude.
  • Click “OK” at the bottom of the “Exclusions” tab.

See this page for additional Panda tips for whitelisting files and folders: http://www.pandasecurity.com/homeusers/downloads/docs/product/help/is/2012/en/709.htm The page is out of date but the methods may still work.

PC Tools Spyware Doctor

  • Right click PC Tools icon in taskbar → Open
  • Go to Settings → Global action list
  • Click “Add”, choose “File” & browse to your Firestorm installation folder & choose slplugin.exe - and llceflib_host.exe (for FS 4.7.9 and later).
  • This will add the plugin(s) to the global whitelist.

Webroot

To date (August 2015), there is no way to whitelist the entire cache folder in WebRoot. Therefore WebRoot may continue to cause severe problems including slow rezzing and viewer freezing.

If you test with WebRoot off and find your SL experience greatly improved, the only suggestion we have is to choose another antivirus program.

Some more more info on Webroot and the problems it has been known to cause, see this page.

For additional information:


See this page for documentation on Firestorm 5.0.11 (53634) and earlier.
1)
Thank you, Sophie Katsu!

inventory_corruption - ↷ Page name changed from current_outfit_folder_corruption to ...

Inventory Corruption

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

  • only one account is affected;
  • you get an error saying that “You cannot remove protected categories”;
  • you will not receive folders given to you by others (however, single items will be received);
  • you will crash or timeout disconnect at login, usually around “Downloading clothing…”;
  • you will likely crash/disconnect on any V3 based viewer or a viewer that uses COF;
  • Reinstalling the viewer, clearing cache, replacing outfit on a non-COF viewer will not fix you.

These issues seem to occur immediately after grid problems affecting inventory. So if you start having problems immediately after a grid outage, then you problem fall into one of the cases above.

In these cases, you will need to contact SL Support in order to have your inventory repaired. However, before doing so, please be sure to verify that you have the same problem with the official SL Viewer. SL Support may not be willing to assist if you do not state that you have the problem with that viewer.

Duplicate COF Causing Bakefail

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

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

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

To test for this, please do the following:

  • Remove all animesh attachments as they will confuse the readings we are about to look at.
  • Open Advanced menu (Ctrl-Alt-D) → Debug Settings.
  • Find DebugAvatarAppearanceMessage.
  • Set that to TRUE.
  • Examine the text floating above your head.
  • In the middle of the text, you will see “cof” followed by three numbers. Example: “cof: 76,345 req: 76,345 rcv: 76,345”
  • These numbers should match each other.
  • If they do not match each other, you have duplicate Current Outfit folders.

current_outfit_folder_corruption - created

firestorm_troubleshooting

Troubleshooting Problems

For basic information on how to get help, click here.
For an introduction to the basics of troubleshooting, please refer to this page.
This page covers issues and problems which you might encounter with Firestorm; for topics concerning how to use the viewer, you are instead directed to the main Firestorm documentation page.
The topics here are divided into issues which are directly related to the viewer, and those which are really SL issues or bugs.
Should this not be helpful, then please contact support. The best place to get fast help is in one of the in-world groups. Otherwise, you may contact any of our support team. We will do our best to assist you.
If you believe you have found a genuine bug - or have a feature request, then you can file a JIRA.

Crash/Login/Launch Issues

Web Feed, Audio, Video and Voice

Viewer Interface (Viewer Windows, Information Displays)

Visual Problems with Items In-World

Behavior of Items In-World

Avatar Movement

Other

firestorm_troubleshooting_ru - ↷ Links adapted because of a move operation

Поиск и устранение неисправностей - Firestorm Viewer

Основная информация о получении помощи находится тут.
Эта страница помогает решить вопросы и проблемы, которые могут возникнуть при работе с Firestorm
Для удобства, темы разделены на вопросы, которые имеют непосредственное отношение к Firestorm, и те, которые имеют отношение к SLв целом.
Если вы не нашли ответ, то, пожалуйста свяжитесь с нами. Лучшее место, чтобы получить быструю помощь, написать нам в группу поддержки в-мире. Вы так же можете обратиться к любому из сотрудников группы поддержки или задать свой вопрос в ВК. Мы сделаем все от нас зависящее, чтобы помочь вам.
Если вы считаете, что нашли ошибку, то вы можете создать запрос в JIRA.

Введение

Для получения информации по общим неисправностям, перейдите на эту страницу.

Обучающий материал

У нас существует свой канал на YouTube; вы можете посетить его и ознакомиться с материалами. Наш канал Phoenix Viewer channel.

Относящиеся к Firestorm

Трудности со входом и сбои

Поиск, Аудио, Видео и голос

Другое

Относящиеся к SL

Общие

Лаги и сеть

Аппаратные средства

Операционная Система / Программное обеспечение

Windows
Mac
Linux

Другое

firestorm_troubleshooting_es - ↷ Links adapted because of a move operation

Troubleshooting and Quick Fixes - Firestorm Viewer

For basic information on how to get help, click here.
This page covers issues and problems which you might encounter with Firestorm; for topics concerning how to use the viewer, you are instead directed to the main Firestorm documentaion page.
The topics here are divided into issues which are directly related to the viewer, and those which are really SL issues or bugs.
Should this not be helpful, then please contact support. The best place to get fast help is in one of the in-world groups. Otherwise, you may contact any of our support team. We will do our best to assist you.
If you believe you have found a genuine bug - or have a feature request, then you can file a JIRA.

Introduction

For an introduction to the basics of troubleshooting, please refer to this page.

Tutorials

Phoenix has some video tutorials on YouTube; you may want to visit and bookmark the Phoenix Viewer channel.

Crash/Login Issues

Search, Audio, Video and Voice

Other

General

Lag and Network

Hardware

Operating System / Software

Windows
Mac
linux

Other

fs_snapshot_profile_6.3.2.png - created

Image may be NSFW.
Clik here to view.
fs_snapshot_profile_6.3.2.png
Viewing all 5258 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>