The pages below have been updated to reflect changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.4 goes to public release.

• Avatar Menu: Favorite Wearables. A window to hold frequently used items such as HUDs and items for quick attach/detach using double click to add. Creates a protected subfolder of links #Wearable Favorites inside #Firestorm folder. See also Toolbar Buttons.

• Avatar Menu: Toolbar Buttons. Added Beacons and Favorite Wearables

• Avatar Menu: Show User Interface. Unchecking hides the user interface. Use Alt+Shift+U to show user interface again. Chiclets and script dialogs remain visible.

• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Shows the rendering weight of each worn attachment. Avatar Complexity
• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Added the ability to use double-click to remove wearables and temporary attachments.
• Avatar Menu - Appearance (Ctrl+O) - Outfits tab: Added the ability to use double-click to add/remove.

• Firestorm - Build 1: Script Editor Font. Allows you to select the name and size of the font used in the LSL script editor.
• Firestorm - Uploads: Reset default folders button resets all upload folders to default destinations.
• User Interface - 2D Overlay: Prevent statistics window from gaining focus. If enabled, the statistics window will never receive focus when another window is closed. Actions such as changing graph layout for items are still possible when enabled.

• Nearby (Radar): Render Settings. Right-click any avatar gives fly-out menu and offers options to Render Normally (default), Do Not Render, Render Fully.

• About Land - Access: Timed ban: Added the ability to ban residents from a parcel for a specific amount of time (minimum 1 hour, maximum 8766 hours (approximately 1 year)). Select the number of hours when the window opens and press OK.

This is Firestorm team's first beta version of Alex Ivy for Linux. All this penguin goodness is brought to you by the amazing efforts of the developers, QA and support team members. Awesome job! Testers are asked to give this an extra good workout.

Merged up to Linden Lab Version 5.1.3.513644
Release Notes for v5.1.3 (513644) - Second Life Viewer March 27, 2018
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.3.513644

• This release of the Viewer pulls in a raft of updates to the built in media support that were not quite ready to be integrated when the 64 bit Viewer (Alex Ivy) was released.
  It is comprised of various fixes, updates, security patches and improvements for CEF (Chromium Embedded Framework) that is the basis for the built in web browser and VLC that provides support for video media playback.
  In addition fixes are included to Dullahan (the third party library that uses CEF) as well as all the media plugin code itself.
  As per the Alex Ivy 64 bit viewer, there is no Linux version.
• Cookies
  The option to not accept cookies has been removed due to complexities of not doing so in the in-viewer browser. For a more controlled cookie experience, an external full-featured browser may be better.

AlexIvy 64bit - Fully merged up to LL's AlexIvy viewer https://community.secondlife.com/blogs/entry/2290-64-bit-viewers-for-all/for Windows and Mac. As a result of this update, there is no Linux viewer available. The Linux community is working to resolve this and accordingly, there is no way to anticipate when a Linux viewer will be available for testing.

Chromium Embedded Framework (CEF) Dullahan updated:

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

FMOD Studio 1.10.04

KDU updated to v7.10.4.

Voice Update: Vivox Version 4.9.0002.27586 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

FIRE-6155 - Previewing an animation to upload while walking/sitting/flying results in the avatar getting stuck in that animation

FIRE-9070 - build window xyz colors not changing for rotate and size

FIRE-12249 - Develop - Render Metadata - Avatar Hitboxes makes eyes disappear

FIRE-13474 - Saving .dae with brackets in filename fails

FIRE-17518 - [CEF] Opening Preferences from the login screen breaks the login page layout.

FIRE-19704 - [Mac] Crash when upload Mesh 50499 - Calculate Weights and Fees (Mac El Capitan) - LLModelgetJointInfluences(LLVector3 const&)

FIRE-21974 - recovered script after crash is empty

FIRE-22175 - [Mac] [BUG-202965] [MAINT-8208] Firestorm crashes when I use a cube as physic when uploading a mesh model

FIRE-22179 - Preprocessor warning when last line in lsl include is a comment: generic lexer warning: Unterminated C++ style comment

FIRE-22214 - Script Editor - Missing Line numbers, Vintage Skin

FIRE-22241 - Copy paste inserting timestamps unexpectedly

FIRE-22268 - Firestorm crashing when deleting items

FIRE-22281 - [BUG-214575] [MAINT-8289] Deleting inventory directory while keeping [Delete] key preesed

FIRE-22288 - [Mac] [BUG-214585] [MAINT-8287] Creating an admin group role is back. While creating a role, in a new group, once you tick the manage ban list you crash.

FIRE-22297 - [Mac and Linux only?] FPS limiter not working (do not move to Support)

FIRE-22330 - Crash when taking photos

FIRE-22346 - [Opensim] Remove Avination from Grid Manager

FIRE-4963 - using animation upload window disables physics wearables

FIRE-5686 - undocked IM window does not stays at his place after relog and undock again

FIRE-16651 - Animation upload/preview breaks eye movement

FIRE-20866 - @stopim returns The other party is not under a @startim restriction when they are

FIRE-21719 - Copy-Paste a Folder doesnt copy the links to the new folder

FIRE-22148 - Group profile icons unload when Group Titles is opened

FIRE-22164 - Black Text against very dark background Firestorm Skin Dark Scheme Experience Edit WIndow.

FIRE-22167 - Show in Main View fail in 2nd Inventory Window

FIRE-22187 - Typo in Prefs - Chat - Visuals

FIRE-8784 - Align tool not working on some prims

FIRE-9561 - Items worn from Marketplace Tab do not show up as worn items

FIRE-21425 - [CEF] Problem with drop-down menus in internal web browser.

FIRE-21579 - [BUG-202634] [MAINT-8023] Missing support for internationalized domain names.

FIRE-22383 - Links in 1st life profile tab disappear after second save

FIRE-22438 - tp2 <own name> crashes the viewer

FIRE-18130 - Setting llSetTextureAnim to FALSE while enabling llSetPrimMediaParams causes the animation to clear improperly

FIRE-20413 - [Windows 32bit] CEF Plugin error with certain videos

FIRE-22430 - SLVoice version 4.9 will not manually recycle

FIRE-22441 - Nearby Chat icons moved, vintage skin

FIRE-22478 - Inventory Elements Tooltip missing

FIRE-22483 - [BUG-216123] [MAINT-8552] Secure map links are not parsing https://maps.secondlife.com/secondlife/

FIRE-22522 - Dirty install error on mac OSStatus error -67062

FIRE-6825 - [MAINT-1421] [VWR-29484] [MAC] [LINUX] Show info - Show memory (usage) doesn't work on mac build 28570

FIRE-22204 - Firestorm Crash when enabling Physics view via eye icon for sub-mesh in OpenSim

FIRE-22278 - [OpenSim] Changing Skew or Revolutions of a Prim causes Prim to vanish or crash

FIRE-22509 - Received items shown in lower half of inventory window is empty

FIRE-22513 - Unable to add a local texture after commit 55111 - either silently fails or viewer crashes

FIRE-22514 - Metaharper skin chiclets too high

FIRE-22530 - Copy paste chat issue

FIRE-22564 - “Route llOwnerSay to scipt debug window” shows incorrect state at login screen

FIRE-15266 - Toolbar Button for Beacons

FIRE-20959 - Update in-world browser cipher suites

FIRE-22331 - [Opensim] Mesh uploaded with Analyze likely to render invisible

FIRE-22334 - Reset All Settings button misleading

FIRE-4595 - Paste as Link - in system generated folders like outfits

FIRE-16207 - [Starlight CUI] Contact Sets Panel text

FIRE-22116 - Pennys Windlight Presets

FIRE-5974 - Allow SEARCH to include Received Items Folder

FIRE-22354 - Beyond chat range diminish factor slider is confusing

FIRE-22484 - Appearance - Outfits - possible to add/remove attachments with double click?

FIRE-22507 - Windlight Submission - Water - Lassies Clearwater

FIRE-22521 - Offer the complexity render options (always/normal/never) in the nearby people/radar right click menu

FIRE-22538 - Add function to reset the upload folder to default

FIRE-19520 - Add per-item render-weight display to Appearance window

FIRE-20809 - HUD Management, Favorite Wearables Folder (protected) and Toolbar Button

FIRE-20818 - Option to adjust font size in script editor

FIRE-21078 - Show Rendering Cost per attachment

FIRE-22115 - Jeans Windlight Presets

FIRE-5993 - timed land ban

The pages below have been updated to reflect changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.6 goes to public release.

• Avatar Menu: Favorite Wearables. A window to hold frequently used items such as HUDs and items for quick attach/detach using double click to add. Creates a protected subfolder of links #Wearable Favorites inside #Firestorm folder. See also Toolbar Buttons.

• Avatar Menu: Toolbar Buttons. Added Beacons and Favorite Wearables

• Avatar Menu: Show User Interface. Unchecking hides the user interface. Use Alt+Shift+U to show user interface again. Chiclets and script dialogs remain visible.

• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Shows the rendering weight of each worn attachment. Avatar Complexity
• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Added the ability to use double-click to remove wearables and temporary attachments.
• Avatar Menu - Appearance (Ctrl+O) - Outfits tab: Added the ability to use double-click to add/remove.

• Firestorm - Build 1: Script Editor Font. Allows you to select the name and size of the font used in the LSL script editor.
• Firestorm - Uploads: Reset default folders button resets all upload folders to default destinations.
• User Interface - 2D Overlay: Prevent statistics window from gaining focus. If enabled, the statistics window will never receive focus when another window is closed. Actions such as changing graph layout for items are still possible when enabled.

• Nearby (Radar): Render Settings. Right-click any avatar gives fly-out menu and offers options to Render Normally (default), Do Not Render, Render Fully.

• About Land - Access: Timed ban: Added the ability to ban residents from a parcel for a specific amount of time (minimum 1 hour, maximum 8766 hours (approximately 1 year)). Select the number of hours when the window opens and press OK.

Firestorm Team is pleased to be able to offer beta versions of Alex Ivy for Linux. All this penguin goodness is brought to you by the amazing efforts of the developers, QA and support team members. Awesome job! Testers are asked to give this an extra good workout. (see Other changes and updates below for backstory)

[KB]

Merged up to Linden Lab Version 5.1.5.515811
Release Notes for v5.1.5 (515811) - Second Life Viewer Released on May 31, 2018.

The Love Me Render Viewer Release represents a collection of work on the rendering pipeline, many in response to bugs and feature requests filed over the years. We always appreciate the diligent help of our residents in finding, filing, and sometimes fixing these - and following along with the development efforts.

Note: On Macs, we recommend deleting any existing Dock icon you have for the viewer, and recreating it by dragging the icon from the Applications folder to the Dock. *Do not* create a Dock icon by pinning one of the icons that appear when the viewer is running; those may cause signature verification errors when you try to use them to launch a new viewer. This will be fixed (and we'll be back to only one icon showing on the Dock) in a future fix release. Sorry for the inconvenience.

Merged up to Linden Lab Version 5.1.4.515016
Release Notes for v5.1.4 (515016) - Second Life Viewer Released on May 07, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.4.515016

Maintenance: Ouzo is here to quench your thirst.

• Ouzo is a dry anise-flavoured aperitif that is widely consumed in Greece, Cyprus and Lebanon. Its taste is similar to other anise liquors like pastis and sambuca. Other spirits of the region may or may not include anise: arak, rakı, and mastika.

• This bottle of Maintenance fixes brings you a large helping of crash fixes, a serious side of bug fixes, and a splash of improvements. Bottoms up!

Merged up to Linden Lab Version 5.1.3.513644
Release Notes for v5.1.3 (513644) - Second Life Viewer March 27, 2018
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.3.513644

• This release of the Viewer pulls in a raft of updates to the built in media support that were not quite ready to be integrated when the 64 bit Viewer (Alex Ivy) was released.
  It is comprised of various fixes, updates, security patches and improvements for CEF (Chromium Embedded Framework) that is the basis for the built in web browser and VLC that provides support for video media playback.
  In addition fixes are included to Dullahan (the third party library that uses CEF) as well as all the media plugin code itself.
  As per the Alex Ivy 64 bit viewer, there is no Linux version.
• Cookies
  The option to not accept cookies has been removed due to complexities of not doing so in the in-viewer browser. For a more controlled cookie experience, an external full-featured browser may be better.

AlexIvy 64bit - Fully merged up to LL's AlexIvy viewer https://community.secondlife.com/blogs/entry/2290-64-bit-viewers-for-all/for Windows and Mac. As a result of this update, there is no Linux viewer available. The Linux community is working to resolve this and accordingly, there is no way to anticipate when a Linux viewer will be available for testing.

Chromium Embedded Framework (CEF) Dullahan updated:

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

FMOD Studio 1.10.04

KDU updated to v7.10.4.

Voice Update: Vivox Version 4.9.0002.27586 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

FIRE-6155 - Previewing an animation to upload while walking/sitting/flying results in the avatar getting stuck in that animation

FIRE-9070 - build window xyz colors not changing for rotate and size

FIRE-12249 - Develop - Render Metadata - Avatar Hitboxes makes eyes disappear

FIRE-13474 - Saving .dae with brackets in filename fails

FIRE-17518 - [CEF] Opening Preferences from the login screen breaks the login page layout.

FIRE-19704 - [Mac] Crash when upload Mesh 50499 - Calculate Weights and Fees (Mac El Capitan) - LLModelgetJointInfluences(LLVector3 const&)

FIRE-21974 - recovered script after crash is empty

FIRE-22175 - [Mac] [BUG-202965] [MAINT-8208] Firestorm crashes when I use a cube as physic when uploading a mesh model

FIRE-22179 - Preprocessor warning when last line in lsl include is a comment: generic lexer warning: Unterminated C++ style comment

FIRE-22214 - Script Editor - Missing Line numbers, Vintage Skin

FIRE-22241 - Copy paste inserting timestamps unexpectedly

FIRE-22268 - Firestorm crashing when deleting items

FIRE-22281 - [BUG-214575] [MAINT-8289] Deleting inventory directory while keeping [Delete] key preesed

FIRE-22288 - [Mac] [BUG-214585] [MAINT-8287] Creating an admin group role is back. While creating a role, in a new group, once you tick the manage ban list you crash.

FIRE-22297 - [Mac and Linux only?] FPS limiter not working (do not move to Support)

FIRE-22330 - Crash when taking photos

FIRE-22346 - [Opensim] Remove Avination from Grid Manager

FIRE-4963 - using animation upload window disables physics wearables

FIRE-5686 - undocked IM window does not stays at his place after relog and undock again

FIRE-16651 - Animation upload/preview breaks eye movement

FIRE-20866 - @stopim returns The other party is not under a @startim restriction when they are

FIRE-21719 - Copy-Paste a Folder doesnt copy the links to the new folder

FIRE-22148 - Group profile icons unload when Group Titles is opened

FIRE-22164 - Black Text against very dark background Firestorm Skin Dark Scheme Experience Edit WIndow.

FIRE-22167 - Show in Main View fail in 2nd Inventory Window

FIRE-22187 - Typo in Prefs - Chat - Visuals

FIRE-8784 - Align tool not working on some prims

FIRE-9561 - Items worn from Marketplace Tab do not show up as worn items

FIRE-21425 - [CEF] Problem with drop-down menus in internal web browser.

FIRE-21579 - [BUG-202634] [MAINT-8023] Missing support for internationalized domain names.

FIRE-22383 - Links in 1st life profile tab disappear after second save

FIRE-22438 - tp2 <own name> crashes the viewer

FIRE-18130 - Setting llSetTextureAnim to FALSE while enabling llSetPrimMediaParams causes the animation to clear improperly

FIRE-20413 - [Windows 32bit] CEF Plugin error with certain videos

FIRE-22430 - SLVoice version 4.9 will not manually recycle

FIRE-22441 - Nearby Chat icons moved, vintage skin

FIRE-22478 - Inventory Elements Tooltip missing

FIRE-22483 - [BUG-216123] [MAINT-8552] Secure map links are not parsing https://maps.secondlife.com/secondlife/

FIRE-22522 - Dirty install error on mac OSStatus error -67062

FIRE-6825 - [MAINT-1421] [VWR-29484] [MAC] [LINUX] Show info - Show memory (usage) doesn't work on mac build 28570

FIRE-22204 - Firestorm Crash when enabling Physics view via eye icon for sub-mesh in OpenSim

FIRE-22278 - [OpenSim] Changing Skew or Revolutions of a Prim causes Prim to vanish or crash

FIRE-22509 - Received items shown in lower half of inventory window is empty

FIRE-22513 - Unable to add a local texture after commit 55111 - either silently fails or viewer crashes

FIRE-22514 - Metaharper skin chiclets too high

FIRE-22530 - Copy paste chat issue

FIRE-22564 - “Route llOwnerSay to scipt debug window” shows incorrect state at login screen

FIRE-22568 - Group Experiences tab seems to lack a correct help ID

FIRE-22578 - Italian System Info does not include viewer settings

FIRE-22579 - [Linux] Viewer window resizing failure

FIRE-20948 - [BUG-139124] [MAINT-7847] The presence of certain Avatars stops local specular textures from “sticking”. Yes really.

FIRE-22573 - No automatically Refreshing of the Windlight settings when someone else on the same Regions is changing them.

FIRE-22618 - Spanish System Info does not include RLVa setting

FIRE-15266 - Toolbar Button for Beacons

FIRE-20959 - Update in-world browser cipher suites

FIRE-22331 - [Opensim] Mesh uploaded with Analyze likely to render invisible

FIRE-22334 - Reset All Settings button misleading

FIRE-4595 - Paste as Link - in system generated folders like outfits

FIRE-16207 - [Starlight CUI] Contact Sets Panel text

FIRE-22116 - Pennys Windlight Presets

FIRE-5974 - Allow SEARCH to include Received Items Folder

FIRE-22354 - Beyond chat range diminish factor slider is confusing

FIRE-22484 - Appearance - Outfits - possible to add/remove attachments with double click?

FIRE-22507 - Windlight Submission - Water - Lassies Clearwater

FIRE-22521 - Offer the complexity render options (always/normal/never) in the nearby people/radar right click menu

FIRE-22538 - Add function to reset the upload folder to default

FIRE-22571 - Add chat feedback to Always Run shortcut

FIRE-19520 - Add per-item render-weight display to Appearance window

FIRE-20809 - HUD Management, Favorite Wearables Folder (protected) and Toolbar Button

FIRE-20818 - Option to adjust font size in script editor

FIRE-21078 - Show Rendering Cost per attachment

FIRE-22115 - Jeans Windlight Presets

FIRE-5993 - timed land ban

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

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

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

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

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

What to do:

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

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

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

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

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

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

If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.

If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.

If you have Intel HD 2000 or 3000 graphics, refer to this page.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If this still doesn't help, then:

• Back up your settings - see http://wiki.phoenixviewer.com/backup_settings
• Wipe your settings manually, as explained in http://wiki.phoenixviewer.com/fs_clearing_settings
• Log back in and see if the mesh renders correctly. If it does…
• Restore your settings (see the backup page above), then check the mesh again.

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

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

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

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

Locations are indicated in the far right column as follows:

• FS: Firestorm Support region classroom, http://maps.secondlife.com/secondlife/Firestorm%20Ghost%20Town/24/11/4000
• JU: Junkyard University, http://maps.secondlife.com/secondlife/Junkyard%20Blues%20South/112/204/22

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

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

*All times SLT*

• Firestorm Support - There may be support team members available here to help.

• Firestorm Parcel at Hippo Hollow - recommended to fix issues such as bake fail, among others.

• Firestorm Classroom - classes are held regularly here. See the schedule for details.
• Junkyard University - alternate class location.

Symptom: You receive a message that the system has “Failed to find [name of any item] in the database” every time you try to wear or remove something.

Please note: This is not a viewer issue, but we have written this page to help users with a common problem.

We have identified three causes of this.

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

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

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

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

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

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

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

(Windows only)

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

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

For more information and additional symptoms, see here.

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

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

• Alexegram
• Amaya Summers
• Bluezy Bleac (French, German, Dutch)
• Cleopatra Antiesse (French)
• Eternal Mode
• Kitty Beery (Dutch)
• Pim Peccable
• Skyspinner Soulstar
• Tracy Argus

• akafox
• AliciaFlanagan1
• annailisa (German)
• Ardwenia (French, Portuguese)
• Arenae Rosewood (French)
• Avalon Bouvier
• ChasDouglas92
• ChuckPC
• Cypherofme
• Fayleen Bellios
• FrankASinatra
• Ganaelle Aabye (French)
• Gokyu Ugajin
• hausss
• ImaLuckygirl
• JadeWindsong
• Jolie Serendipity
• kobayashiMaroo
• Liliana Darwinian (Portuguese)
• LosAngelesGraff
• MacMaccee (German, English)
• MaeveStorm
• MarcSeven Lubitsch
• Mari Teardrop
• PurrBlaize
• SayreAvondale
• Scarlet Vavoom
• Scuzzy Usbourne
• Sedona Bluemood
• Silver Frakture (German)
• Sniper Siemens
• Sparkle Weatherwax
• xAngelBaby

• Roleplay Leaders:MarcSeven Lubitsch, panterapolnocy, Starwolff2000, Teresa Firelight

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

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

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

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

• Déconnectez-vous de Firestorm

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

• Faites un clic droit sur votre bureau et sélectionnez “Configurer les graphiques commutables”
• Si vous avez utilisé Firestorm au moins une fois, il apparaîtra dans la liste des dernières applications
• Si ce n'est pas le cas, cliquez sur “Ajouter une application”
• Cherchez le dossier d'installation de Firestorm :
  C:\Program Files (x86)\Firestorm-Release\Firestorm-Release.exe for the 32-bit Havok
  C:\Program Files (x86)\FirestormOS-Release\FirestormOS-Release.exe for the 32-bit OpenSim
  C:\Program Files\Firestorm_Releasex64\Firestorm-bin.exe for the 64-bit
• Faites un double clic sur l’application
• Si vous avez à la fois une version 32 et 64 bits de Firestorm, recommencez la procédure pour la 2ème version.
• Une fois Firestorm affiché dans le panneau de contrôle AMD, le bouton à droite sur la ligne permet de sélectionner le mode haute performance.
• Cliquez sur “Appliquer” au bas de la fenêtre et fermez le panneau à l’écran.
• Ouvrez Firestorm et allez dans Help → About Firestorm. Vérifiez que la carte vidéo AMD soit affichée dans la liste du matériel.

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

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

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

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

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

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

Note: This is not the same as rainbow colors in-world.

If you see rainbow colors after logout and you have MSI True Color or f.lux installed on your system, do the following steps in order:

1. Uninstall MSI True Color if installed.
2. Install f.lux from https://justgetflux.com/ if not installed.
3. Uninstall f.lux using the f.lux uninstaller, not the Windows uninstaller from Windows programs & features / add/remove programs.
4. When running the uninstaller it will give you the option to reset to the windows default color profile; say Yes. (Running this uninstaller is the only way we have found to get rid of the MSI True Color profile.)

Refer to http://jira.phoenixviewer.com/browse/FIRE-12561. Also see the alternate workaround at the comment dated 13/Apr/17

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

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

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

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

Note also the (apparent) interaction with Chrome.

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

Please try the following - but NOT while logged in.

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

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

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

• If you have chat saving enabled, and have a large number of chat transcript files, these could be causing the freezes. (Ref. FIRE-11322.) Try moving your chat transcripts elsewhere and see if the freezing stops.
  You can find your chat transcripts by going to Preferences→ Network & Files -> Directories→ Conversation logs and transcripts location; click the Open button.
• Set Preferences → Network & Files → Directories → Cache Size to maximum (9984MB or the maximum space available, whichever is less)
• Ensure that your antivirus software is not scanning the viewer cache folder. See Whitelisting the Viewer in Anti Virus Software for more information.
• If you have ever enabled “Full Res Textures”, disable this setting. Top menu bar, Develop→ Rendering → Full Res Textures (dangerous). Ensure that this is NOT checked. (Ctrl-Alt-Q to enable Develop, if it isn't.)
• Advanced → Debug Settings → Set FastCacheFetchEnabled to FALSE - then relog.
  Ctrl-Alt-D to enable Advanced, if it isn't.
• Preferences → Graphics → Hardware Settings → Viewer Texture Memory Buffer - raise this as high as it will go. Then relog. (64-bit version only)
• Tip from a user: Windows users: If you're running CrashPlan, open the “Advanced” section of “Backup” settings and uncheck “Back up open files.

For additional suggestions, see the page on Severe Lag.

The pages below have been updated to reflect changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.6 goes to public release.

• Avatar Menu: Favorite Wearables. A window to hold frequently used items such as HUDs and items for quick attach/detach using double click to add. Creates a protected subfolder of links #Wearable Favorites inside #Firestorm folder. See also Toolbar Buttons.

• Avatar Menu: Toolbar Buttons. Added Beacons and Favorite Wearables

• Avatar Menu: Show User Interface. Unchecking hides the user interface. Use Alt+Shift+U to show user interface again. Chiclets and script dialogs remain visible.

• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Shows the rendering weight of each worn attachment. Avatar Complexity
• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Added the ability to use double-click to remove wearables and temporary attachments.
• Avatar Menu - Appearance (Ctrl+O) - Outfits tab: Added the ability to use double-click to add/remove.

• Firestorm - Build 1: Script Editor Font. Allows you to select the name and size of the font used in the LSL script editor.
• Firestorm - Uploads: Reset default folders button resets all upload folders to default destinations.
• User Interface - 2D Overlay: Prevent statistics window from gaining focus. If enabled, the statistics window will never receive focus when another window is closed. Actions such as changing graph layout for items are still possible when enabled.

• Nearby (Radar): Render Settings. Right-click any avatar gives fly-out menu and offers options to Render Normally (default), Do Not Render, Render Fully.

• About Land - Access: Timed ban: Added the ability to ban residents from a parcel for a specific amount of time (minimum 1 hour, maximum 8766 hours (approximately 1 year)). Select the number of hours when the window opens and press OK.

Firestorm Team is pleased to be able to offer beta versions of Alex Ivy for Linux. All this penguin goodness is brought to you by the amazing efforts of the developers, QA and support team members. Awesome job! Testers are asked to give this an extra good workout. (see Other changes and updates below for backstory)

[to be provided by KB]

Merged up to Linden Lab Version 5.1.5.515811
Release Notes for v5.1.5 (515811) - Second Life Viewer Released on May 31, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.5.515811

The Love Me Render Viewer Release represents a collection of work on the rendering pipeline, many in response to bugs and feature requests filed over the years. We always appreciate the diligent help of our residents in finding, filing, and sometimes fixing these - and following along with the development efforts.

Merged up to Linden Lab Version 5.1.4.515016
Release Notes for v5.1.4 (515016) - Second Life Viewer Released on May 07, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.4.515016

Maintenance: Ouzo is here to quench your thirst.

• Ouzo is a dry anise-flavoured aperitif that is widely consumed in Greece, Cyprus and Lebanon. Its taste is similar to other anise liquors like pastis and sambuca. Other spirits of the region may or may not include anise: arak, rakı, and mastika.

• This bottle of Maintenance fixes brings you a large helping of crash fixes, a serious side of bug fixes, and a splash of improvements. Bottoms up!

Merged up to Linden Lab Version 5.1.3.513644
Release Notes for v5.1.3 (513644) - Second Life Viewer March 27, 2018
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.3.513644

• This release of the Viewer pulls in a raft of updates to the built in media support that were not quite ready to be integrated when the 64 bit Viewer (Alex Ivy) was released.
  It is comprised of various fixes, updates, security patches and improvements for CEF (Chromium Embedded Framework) that is the basis for the built in web browser and VLC that provides support for video media playback.
  In addition fixes are included to Dullahan (the third party library that uses CEF) as well as all the media plugin code itself.
  As per the Alex Ivy 64 bit viewer, there is no Linux version.
• Cookies
  The option to not accept cookies has been removed due to complexities of not doing so in the in-viewer browser. For a more controlled cookie experience, an external full-featured browser may be better.

AlexIvy 64bit - Fully merged up to LL's AlexIvy viewer https://community.secondlife.com/blogs/entry/2290-64-bit-viewers-for-all/for Windows and Mac. As a result of this update, there is no Linux viewer available. The Linux community is working to resolve this and accordingly, there is no way to anticipate when a Linux viewer will be available for testing.

Chromium Embedded Framework (CEF) Dullahan updated:

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

FMOD Studio 1.10.04

KDU updated to v7.10.4.

Voice Update: Vivox Version 4.9.0002.27586 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

FIRE-6155 - Previewing an animation to upload while walking/sitting/flying results in the avatar getting stuck in that animation

FIRE-9070 - build window xyz colors not changing for rotate and size

FIRE-12249 - Develop - Render Metadata - Avatar Hitboxes makes eyes disappear

FIRE-13474 - Saving .dae with brackets in filename fails

FIRE-17518 - [CEF] Opening Preferences from the login screen breaks the login page layout.

FIRE-19704 - [Mac] Crash when upload Mesh 50499 - Calculate Weights and Fees (Mac El Capitan) - LLModelgetJointInfluences(LLVector3 const&)

FIRE-21974 - recovered script after crash is empty

FIRE-22175 - [Mac] [BUG-202965] [MAINT-8208] Firestorm crashes when I use a cube as physic when uploading a mesh model

FIRE-22179 - Preprocessor warning when last line in lsl include is a comment: generic lexer warning: Unterminated C++ style comment

FIRE-22214 - Script Editor - Missing Line numbers, Vintage Skin

FIRE-22241 - Copy paste inserting timestamps unexpectedly

FIRE-22268 - Firestorm crashing when deleting items

FIRE-22281 - [BUG-214575] [MAINT-8289] Deleting inventory directory while keeping [Delete] key preesed

FIRE-22288 - [Mac] [BUG-214585] [MAINT-8287] Creating an admin group role is back. While creating a role, in a new group, once you tick the manage ban list you crash.

FIRE-22297 - [Mac and Linux only?] FPS limiter not working (do not move to Support)

FIRE-22330 - Crash when taking photos

FIRE-22346 - [Opensim] Remove Avination from Grid Manager

FIRE-4963 - using animation upload window disables physics wearables

FIRE-5686 - undocked IM window does not stays at his place after relog and undock again

FIRE-16651 - Animation upload/preview breaks eye movement

FIRE-20866 - @stopim returns The other party is not under a @startim restriction when they are

FIRE-21719 - Copy-Paste a Folder doesnt copy the links to the new folder

FIRE-22148 - Group profile icons unload when Group Titles is opened

FIRE-22164 - Black Text against very dark background Firestorm Skin Dark Scheme Experience Edit WIndow.

FIRE-22167 - Show in Main View fail in 2nd Inventory Window

FIRE-22187 - Typo in Prefs - Chat - Visuals

FIRE-8784 - Align tool not working on some prims

FIRE-9561 - Items worn from Marketplace Tab do not show up as worn items

FIRE-21425 - [CEF] Problem with drop-down menus in internal web browser.

FIRE-21579 - [BUG-202634] [MAINT-8023] Missing support for internationalized domain names.

FIRE-22383 - Links in 1st life profile tab disappear after second save

FIRE-22438 - tp2 <own name> crashes the viewer

FIRE-18130 - Setting llSetTextureAnim to FALSE while enabling llSetPrimMediaParams causes the animation to clear improperly

FIRE-20413 - [Windows 32bit] CEF Plugin error with certain videos

FIRE-22430 - SLVoice version 4.9 will not manually recycle

FIRE-22441 - Nearby Chat icons moved, vintage skin

FIRE-22478 - Inventory Elements Tooltip missing

FIRE-22483 - [BUG-216123] [MAINT-8552] Secure map links are not parsing https://maps.secondlife.com/secondlife/

FIRE-22522 - Dirty install error on mac OSStatus error -67062

FIRE-6825 - [MAINT-1421] [VWR-29484] [MAC] [LINUX] Show info - Show memory (usage) doesn't work on mac build 28570

FIRE-22204 - Firestorm Crash when enabling Physics view via eye icon for sub-mesh in OpenSim

FIRE-22278 - [OpenSim] Changing Skew or Revolutions of a Prim causes Prim to vanish or crash

FIRE-22509 - Received items shown in lower half of inventory window is empty

FIRE-22513 - Unable to add a local texture after commit 55111 - either silently fails or viewer crashes

FIRE-22514 - Metaharper skin chiclets too high

FIRE-22530 - Copy paste chat issue

FIRE-22564 - “Route llOwnerSay to scipt debug window” shows incorrect state at login screen

FIRE-22568 - Group Experiences tab seems to lack a correct help ID

FIRE-22578 - Italian System Info does not include viewer settings

FIRE-22579 - [Linux] Viewer window resizing failure

FIRE-20948 - [BUG-139124] [MAINT-7847] The presence of certain Avatars stops local specular textures from “sticking”. Yes really.

FIRE-22573 - No automatically Refreshing of the Windlight settings when someone else on the same Regions is changing them.

FIRE-22618 - Spanish System Info does not include RLVa setting

FIRE-15266 - Toolbar Button for Beacons

FIRE-20959 - Update in-world browser cipher suites

FIRE-22331 - [Opensim] Mesh uploaded with Analyze likely to render invisible

FIRE-22334 - Reset All Settings button misleading

FIRE-4595 - Paste as Link - in system generated folders like outfits

FIRE-16207 - [Starlight CUI] Contact Sets Panel text

FIRE-22116 - Pennys Windlight Presets

FIRE-5974 - Allow SEARCH to include Received Items Folder

FIRE-22354 - Beyond chat range diminish factor slider is confusing

FIRE-22484 - Appearance - Outfits - possible to add/remove attachments with double click?

FIRE-22507 - Windlight Submission - Water - Lassies Clearwater

FIRE-22521 - Offer the complexity render options (always/normal/never) in the nearby people/radar right click menu

FIRE-22538 - Add function to reset the upload folder to default

FIRE-22571 - Add chat feedback to Always Run shortcut

FIRE-19520 - Add per-item render-weight display to Appearance window

FIRE-20809 - HUD Management, Favorite Wearables Folder (protected) and Toolbar Button

FIRE-20818 - Option to adjust font size in script editor

FIRE-21078 - Show Rendering Cost per attachment

FIRE-22115 - Jeans Windlight Presets

FIRE-5993 - timed land ban

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.

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.

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

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.

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

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

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

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

You can also try adjusting your bandwidth as explained here.

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

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

• May 2018: If you had a recent Windows update, and you are also missing all other in-world sounds, see this page.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This is a collection of error messages seen in SL. Some are system messages; some are viewer-generated. The list is by no means complete. If you get an error message that is not on this page, please report it in Firestorm Support English (in-world support group) or File a Jira alerting us to it (please provide the complete, exact wording of the message; a screenshot is also helpful).

This section covers issues related to audio, video and some aspects of search.

• For situations where you cannot hear audio, be it streaming music, or the audio from a movie/video, the first thing to do is check that:
  • May 2018: If you had a recent Windows update, see this page.
  • streaming music and/or media are enabled in Preferences→ Sound & Media -> Sounds;
  • volumes for music and media are not at minimum;
  • audio is configured correctly in your operating system (ie, Windows, linux, OSX), that sound is going to the correct device (i.e., speakers or headset), and so on (this may require you to adjust settings in your sound mixer or other similar software);
  • You have not blocked the stream/video; check Preferences → Sound & Media → Media → Manage Media Sites.
  • for streaming music, test the music URL in your external web browser, to make sure that the URL actually works.

• If you have plugged in a USB sound device, you may need to relog so that the viewer can use it.
• 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.

• Relog Firestorm and open the Search window
• Go to your computer processes and look for “slplugin.exe”
  • For Windows users, go to Task Manager → Processes Tab
  • For Mac users, go to Activity Monitor → My Processes (usually by default, but you can check top right drop down)
  • For Linux users, go to Command Terminal, and type “ps aux”
  • You may see four instances of the slplugin running (that is normal behavior)
  • If you do not see any instances of slplugin running, that is the cause of media failing
• If slplugin is not running, disable all firewall and virus protection (including anti-virus software and windows or other operating system firewalls). Do this check also for llceflib_host.
• Relog and attempt video playback again
• If it works, you will need to stop your firewall/virus protection from blocking the slplugin and/or llceflib_host files by granting appropriate permissions in your firewall/virus protection software
• NOTE: If you have several viewers installed, you will have to allow to each one access through your firewall, as well as to SLPlugin and llceflib_host for each one.
• If all of the above does not resolve the issue, you can try downloading the latest SL Viewer 2 viewer and replacing your Firestorm slplugin file with the one from Viewer 2.

• In Preferences → Sound & Media → Sounds, make sure the “Enabled” checkbox to the right of the “Media” slider is checked
  (For audio, check “Streaming Music”)
• In Preferences → Sound & Media → Media, check “Allow inworld scripts to play media”
• In Preferences → Network & Files -> Connection, make sure the Maximum Number of Web Browser Windows dropdown is set to Five, Ten or Unlimited
• Make sure the issue is not with the specific television you are using, by attempting to view videos on a television that plays video normally for other Firestorm users.
• Make sure that “Enable plugins” is ticked in Preferences → Network & Files -> Connection, else the external media plugin can not be executed, and you may see a message saying: Adobe Flash Player or an HTML5 supported browser is required for video playback.

• Windows users:
  • In order to play Flash format videos (e.g., YouTube videos), you must have the Opera & Chromium version of the Adobe Flash plugin installed. Unless you already have this specific version of Flash installed already, you will need to get the Opera & Chromium Flash plugin from Adobe.

• Linux users
  • You need to have the pepperflash plugin installed, which can be satisfied by installing pepperflashplugin-nonfree for Chromium

• Mac users
  • Mac users currently need the Safari & Firefox version of Adobe Flash plugin installed. Download it from Adobe.

• All users: Test your Flash
  • To make sure you have successfully installed the correct version of Flash and that it is working, use the in-world Flash game to test it.
    • Open the Developer menu: CTRL-Alt-Q. (Close this after testing; it's best not to leave this menu open.)
    • Then type CTRL-SHIFT-Z to open the internal browser.
    • Once the browser loads, click the Home icon in the upper left of the browser window.
    • Click “Flash game” (3rd column, 4th row).
    • A bubble-shooter game should load.

• NOTE: If you experience graphics driver crashes on nVidia cards when viewing Flash media (for example Youtube) both in-world and on a website and/or severe drops in your GPU clock mhz on any card then you will need to disable hardware acceleration on Flash Player. To do this, go to Youtube and Pick any video. Right click the video play area to bring up the options and follow the instructions here.

QuickTime is no longer needed for Windows users (and never was for linux users). Mac users, however, still need to have it.

• If YouTube videos suddenly will not play, and you just get a white screen, go to Preferences→ Privacy -> General, and click on Clear History, then try again.
• See also the Flash section, above.

Go to Preferences→ Sound & Media -> Sounds and make sure the volume sliders for streaming music and media are not all to the left and that there is no mute symbol (red no entry sign) on the speaker icon next to those. Make sure the Master Volume is not all to the left.

Check that Sound Source rolloff distance (Media tab) is correct; set back to default, if you changed it (5m and 30 respectively for min and max).

Go to Preferences→ Sound & Media -> Sounds and check that you have the Sounds and UI sliders up high enough and that there is no mute symbol (red no entry sign) on the speaker icon next to those.

Go to the top menu bar→ Advanced → Use Plugin Read Thread, and disable it, if it is enabled - or vice versa. (If you cannot see Advanced on the top menu, press Ctrl-Alt-D.)

If that doesn't help, first ensure that you have your bandwidth set correctly. Also, test the audio stream in your regular media player, and/or try a different audio stream in-world.

If the music volume fades as you cam around or edit objects, check the sound equalization settings in your operating system. For example, this may be caused by “Loudness equalization” being enabled in your speaker properties on Windows 7. (Refer to http://jira.phoenixviewer.com/browse/FIRE-19885.)

This error is due to Flash not being installed, or not installed correctly. See above.

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

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

Locations are indicated in the far right column as follows:

• FS: Firestorm Support region classroom, * Firestorm Classroom
• JU: Junkyard University, * Junkyard University Classroom

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

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

*All times SLT*

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

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

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

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

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

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

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

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

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

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

• Reboot your router/modem.

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

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

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

This also applies if you are a cloud.

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

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

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

For more info, you can refer to this JIRA.

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

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

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

For more info, see this LL JIRA.

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

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

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

For a general introduction on how to move your avatar and control your view, refer to this page.

• View angle: Affects the camera field of view.
• Distance: Changes the distance that camera view follows your avatar.
• Transition Time: How long it takes for the camera to adjust to quickly changed camera positions/angles.
• Smoothing: Affects how smoothly the camera moves.
• Disable camera constraints: Allows you to move your camera further away from your avatar. (Same as top menu bar→ Advanced → Disable camera constraints.)
• Don't use the mouse wheel to control zoom level of the camera: By default, scrolling the mouse wheel results in the camera zooming in or out; enabling this option will disable that feature.
• Automatically pose avatar during (select one or more):
  • Build/Edit: When selected, the camera automatically moves to center on the object you're editing.
  • Appearance: (set by default) When selected, the camera automatically zooms in on your avatar when you enter Appearance mode. It also automatically focuses as you select different Body Parts and Clothes tabs. Deselect this to leave the camera where it is.
    • Add Additional Lighting: If enabled, when you go into Appearance, you will have extra lighting to iluminate your avatar. (This option is not available if the one above is disabled.)
    • Show Visual Hints: Option to disable preview thumbnails (visual hints) when editing shape.
• Clicking your avatar keeps camera position: When enabled, clicking on your avatar will focus the camera at the point that you click on your avatar.
• Reset camera position after teleport (within a region): If enabled, the camera will revert to the default position after a TP within the region; when disabled, it will remain where it is, relative to your avatar.
• Reset camera position on avatar movement: If you enable this, the camera will revert to its default position whenever you move your avatar; disable this to inhibit the camera reset. Useful when taking photos, if you need to move your avatar a bit without the camera moving from where you are pointing it.
• Disable minimum camera zoom distance: Allows the camera to zoom as far in as you want, allowing you to see inside prims.
• Turn avatar towards camera direction on reset view: If this is enabled (old default behavior), then when you hit Esc to reset your camera, the avatar will turn to face whatever direction your camera was pointing at when you pressed Esc; with this disabled, your avatar will not move, but instead the camera will rotate round behind it.
• Allow the camera to move without constraints through prims: If enabled will not keep your camera view on the same side of a prim as your avatar. For example put your back against a wall, and you see the other side of the wall. When disabled, your point of view would be over your head, and you see inside.
• Show the default camera controls minifloater always as opaque: If enabled, the camera conrols window will always be opaque.

Render blocked (muted) avatars as particle cloud: Will render muted avatars as clouds.

• Re-render temporary derendered objects after teleport: If enabled, temporarily derendered objects will remain derendered until you teleport; otherwise, they stay derendered until your relog, or a manually re-rendered via the asset blacklist window.

• Enable Mouselook functionality: Enable this if you wish to use Mouselook.
  Mouselook can be entered either by scrolling forward with your mousewheel, or by using the 'M' key on your keyboard (which first equires enabling WASD for movement, in Preferences->General), or from top menu, Advanced → Shortcuts.
  • Show avatar in Mouselook: Will allow you to see yourself when in mouselook. Does not show the entire avatar, but looking down you would see your feet.
  • Show user interface in mouselook: Normally, in mouselook, user interface elements such as the inventory window, IM windows, etc, are hidden. If you enable this, they will remain on screen.
  • Don't close Conversations and Radar window when changing into Mouselook: By default, these windows close when you go into mouselook; enabel this if you prefer that they stay open.
  • Enable context menus in Mouselook: If you enable this, you will be able to open the pie/context menu using Alt Right click.
  • Leave Mouselook using the scroll wheel: If enabled, then you can exit mouselook by scrolling back with your mouse scrollwheel.
  • Show Mouselook Instructions: Will show the “press esc to exit mouselook” message while in mouselook.
  • Show Mouselook Crosshairs: when enabled, crosshairs are displayed in mouselook mode.
  • Enable combat features: Enables IFF (Identification Friend or Foe).
    • Draw target markers: Draws arrows pointing to friend/foe avatars.
    • Range: Max range for the above.
  • Mouselook mouse sensitivity slider: This affects how far your avatar turns in mouselook. Moving the slider to the right causes your avatar to turn farther When you move the mouse, with the same amount of mouse movement.

• Arrow keys always move me: The arrow keys move your avatar around if you hit them while chatting in the main chatbar. Disable this if you prefer to use arrows keys to move back/foward in text you have typed, so you can edit it.
• Pressing letter keys affects movement (i.e. WASD) instead of starting local chat: Enabel this if you wish to have the WAD keys move your avatar.
• Use AZERTY keyboard layout: Enable this if you have an AZERTY keyboard; if your keyboard has a QWERTY layout, leave it disabled.
• Tap-tap-hold to run: Allows you to double-tap and hold the up arrow key to run.
• Fly/Land on holding up/down: Allows holding the PgUp or PgDown button to fly/land, respectively.
• Enable crouch toggle mode: If this is enabled, pressing PgDown will put you into a crouch; you will remain that way till you press it again. Otherwise, you need to press and hold PgDown to stay in a crouch.
• Disable waiting for pre-jump and landing animations: In effect, a fast jump. Same as the option in the top menu, Avatar→ Movement → Quickjump.
• Allow avatars to walk backwards on your screen: If this is left off, your avatar will turn around to face the camera when you walk backward. This option affects only what you see, and does not work with scripted AOs, only the client AO (or no AO).
• Turn avatar towards a selected object: Disable this option if you do not wish your avatar to turn to an object when you select or edit it.
• If built in LSL Bridge movelock is active…
  • Always re-lock position after region change: If you enabled the movelock function in top menu, Avatar → Movement → Move Lock (Ctrl-Alt-P), then this keeps the lock enabled if you teleport.
  • Lock and unlock position after stopping or starting movement: With this setting enabled, you will be able to move even if movelock is enabled; movelock will still prevent being pushed.
• Single click on land: Clicking a spot on the ground can either do nothing, or cause you to walk to that spot.
• Double click on land:

  Double clicking a spot on the ground can:

  • Do nothing
  • Cause you to walk to that spot
  • Teleport you to that spot. (See also the Firestorm Bridge.)

• Joystick Configuration: Opens a window where you can change settings for other input devices.

• *

  Play sound effect when teleporting: Allows you to hear the teleport sound effect. * Always fly after teleporting: If enabled, your avatar will automatically fly when arriving at a new destination, after a teleport. * Always show the Teleport cancel button: This allows teleports to be cancelled once started. Note that cancelling a TP in progress may log you out. * Disable Teleport Beacons: Disables the red indicator arrows and the vertical beacons that sometimes are shown after a teleport. Thus if you do not land at the exact location you wanted to (due to teleport routing), you will not have the beacon to guide you to your intended destination. * Disable Teleport Screens: Disables the black teleport screen during all teleports. * Do not close the map when teleporting: Enable this is you want the map to stay open after a TP. * Keep 'Show Friends Only' enabled after teleporting: If this is off, then the Show Friends Only option (top menu, World→ Show Friends Only) will automatically disable after teleport. Handy in case you forgot that you enabled it, and then wonder why you can't see anyone. ==== Map & Minimap ==== === Minimap Options === * Enable Minimap Rotation: When enabled the minimap will rotate when your avatar turns. * Double click on Minimap: Select an action when you double click a point on the Minimap: * No Action * Open World Map * Teleport * Pick Scale: Controls the radius of the pick range on the minimap. Note: Other options concerning minimap are found under Preferences→ Colors -> Minimap. === World Map Options === * Filter duplicate landmarks on world map: If enabled, duplicate landmarks are filtered out of the Landmarks drop down menu on the world map. * Show additional region information on World Map: Displays avatar count and maturity level on the world map. * Show grid coordinates on the world map: Display regions' grid coordinates on the world map. * Enable double click teleports on the World map:** Allow teleport to a location on the world map by double clicking.

For a general introduction on how to move your avatar and control your view, refer to this page.

• View angle: Affects the camera field of view.
• Distance: Changes the distance that camera view follows your avatar.
• Transition Time: How long it takes for the camera to adjust to quickly changed camera positions/angles.
• Smoothing: Affects how smoothly the camera moves.
• Disable camera constraints: Allows you to move your camera further away from your avatar. (Same as top menu bar→ Advanced → Disable camera constraints.)
• Don't use the mouse wheel to control zoom level of the camera: By default, scrolling the mouse wheel results in the camera zooming in or out; enabling this option will disable that feature.
• Automatically pose avatar during (select one or more):
  • Build/Edit: When selected, the camera automatically moves to center on the object you're editing.
  • Appearance: (set by default) When selected, the camera automatically zooms in on your avatar when you enter Appearance mode. It also automatically focuses as you select different Body Parts and Clothes tabs. Deselect this to leave the camera where it is.
    • Add Additional Lighting: If enabled, when you go into Appearance, you will have extra lighting to iluminate your avatar. (This option is not available if the one above is disabled.)
    • Show Visual Hints: Option to disable preview thumbnails (visual hints) when editing shape.
• Clicking your avatar keeps camera position: When enabled, clicking on your avatar will focus the camera at the point that you click on your avatar.
• Reset camera position after teleport (within a region): If enabled, the camera will revert to the default position after a TP within the region; when disabled, it will remain where it is, relative to your avatar.
• Reset camera position on avatar movement: If you enable this, the camera will revert to its default position whenever you move your avatar; disable this to inhibit the camera reset. Useful when taking photos, if you need to move your avatar a bit without the camera moving from where you are pointing it.
• Disable minimum camera zoom distance: Allows the camera to zoom as far in as you want, allowing you to see inside prims.
• Turn avatar towards camera direction on reset view: If this is enabled (old default behavior), then when you hit Esc to reset your camera, the avatar will turn to face whatever direction your camera was pointing at when you pressed Esc; with this disabled, your avatar will not move, but instead the camera will rotate round behind it.
• Allow the camera to move without constraints through prims: If enabled will not keep your camera view on the same side of a prim as your avatar. For example put your back against a wall, and you see the other side of the wall. When disabled, your point of view would be over your head, and you see inside.
• Show the default camera controls minifloater always as opaque: If enabled, the camera conrols window will always be opaque.

Render blocked (muted) avatars as particle cloud: Will render muted avatars as clouds.

• Re-render temporary derendered objects after teleport: If enabled, temporarily derendered objects will remain derendered until you teleport; otherwise, they stay derendered until your relog, or a manually re-rendered via the asset blacklist window.

• Enable Mouselook functionality: Enable this if you wish to use Mouselook.
  Mouselook can be entered either by scrolling forward with your mousewheel, or by using the 'M' key on your keyboard (which first equires enabling WASD for movement, in Preferences->General), or from top menu, Advanced → Shortcuts.
  • Show avatar in Mouselook: Will allow you to see yourself when in mouselook. Does not show the entire avatar, but looking down you would see your feet.
  • Show user interface in mouselook: Normally, in mouselook, user interface elements such as the inventory window, IM windows, etc, are hidden. If you enable this, they will remain on screen.
  • Don't close Conversations and Radar window when changing into Mouselook: By default, these windows close when you go into mouselook; enabel this if you prefer that they stay open.
  • Enable context menus in Mouselook: If you enable this, you will be able to open the pie/context menu using Alt Right click.
  • Leave Mouselook using the scroll wheel: If enabled, then you can exit mouselook by scrolling back with your mouse scrollwheel.
  • Show Mouselook Instructions: Will show the “press esc to exit mouselook” message while in mouselook.
  • Show Mouselook Crosshairs: when enabled, crosshairs are displayed in mouselook mode.
  • Enable combat features: Enables IFF (Identification Friend or Foe).
    • Draw target markers: Draws arrows pointing to friend/foe avatars.
    • Range: Max range for the above.
  • Mouselook mouse sensitivity slider: This affects how far your avatar turns in mouselook. Moving the slider to the right causes your avatar to turn farther When you move the mouse, with the same amount of mouse movement.

• Arrow keys always move me: The arrow keys move your avatar around if you hit them while chatting in the main chatbar. Disable this if you prefer to use arrows keys to move back/foward in text you have typed, so you can edit it.
• Pressing letter keys affects movement (i.e. WASD) instead of starting local chat: Enabel this if you wish to have the WAD keys move your avatar.
• Use AZERTY keyboard layout: Enable this if you have an AZERTY keyboard; if your keyboard has a QWERTY layout, leave it disabled.
• Tap-tap-hold to run: Allows you to double-tap and hold the up arrow key to run.
• Fly/Land on holding up/down: Allows holding the PgUp or PgDown button to fly/land, respectively.
• Enable crouch toggle mode: If this is enabled, pressing PgDown will put you into a crouch; you will remain that way till you press it again. Otherwise, you need to press and hold PgDown to stay in a crouch.
• Disable waiting for pre-jump and landing animations: In effect, a fast jump. Same as the option in the top menu, Avatar→ Movement → Quickjump.
• Allow avatars to walk backwards on your screen: If this is left off, your avatar will turn around to face the camera when you walk backward. This option affects only what you see, and does not work with scripted AOs, only the client AO (or no AO).
• Turn avatar towards a selected object: Disable this option if you do not wish your avatar to turn to an object when you select or edit it.
• Movement at region crossing:
  • Predict. Original behavior will cause the viewer to try and predict movement into the region ahead whilst using bogus movement until the session with the region ahead has been setup.
  • Stop. Experimental option. Does what its name implies. Movement at the region crossing will cease until the session with the region ahead is setup and data is received (such as a position update).
• If built in LSL Bridge movelock is active…
  • Always re-lock position after region change: If you enabled the movelock function in top menu, Avatar → Movement → Move Lock (Ctrl-Alt-P), then this keeps the lock enabled if you teleport.
  • Lock and unlock position after stopping or starting movement: With this setting enabled, you will be able to move even if movelock is enabled; movelock will still prevent being pushed.
• Single click on land: Clicking a spot on the ground can either do nothing, or cause you to walk to that spot.
• Double click on land:

  Double clicking a spot on the ground can:

  • Do nothing
  • Cause you to walk to that spot
  • Teleport you to that spot. (See also the Firestorm Bridge.)

• Joystick Configuration: Opens a window where you can change settings for other input devices.

• *

  Play sound effect when teleporting: Allows you to hear the teleport sound effect. * Always fly after teleporting: If enabled, your avatar will automatically fly when arriving at a new destination, after a teleport. * Always show the Teleport cancel button: This allows teleports to be cancelled once started. Note that cancelling a TP in progress may log you out. * Disable Teleport Beacons: Disables the red indicator arrows and the vertical beacons that sometimes are shown after a teleport. Thus if you do not land at the exact location you wanted to (due to teleport routing), you will not have the beacon to guide you to your intended destination. * Disable Teleport Screens: Disables the black teleport screen during all teleports. * Do not close the map when teleporting: Enable this is you want the map to stay open after a TP. * Keep 'Show Friends Only' enabled after teleporting: If this is off, then the Show Friends Only option (top menu, World→ Show Friends Only) will automatically disable after teleport. Handy in case you forgot that you enabled it, and then wonder why you can't see anyone. ==== Map & Minimap ==== === Minimap Options === * Enable Minimap Rotation: When enabled the minimap will rotate when your avatar turns. * Double click on Minimap: Select an action when you double click a point on the Minimap: * No Action * Open World Map * Teleport * Pick Scale: Controls the radius of the pick range on the minimap. Note: Other options concerning minimap are found under Preferences→ Colors -> Minimap. === World Map Options === * Filter duplicate landmarks on world map: If enabled, duplicate landmarks are filtered out of the Landmarks drop down menu on the world map. * Show additional region information on World Map: Displays avatar count and maturity level on the world map. * Show grid coordinates on the world map: Display regions' grid coordinates on the world map. * Enable double click teleports on the World map:** Allow teleport to a location on the world map by double clicking.