June 2020: Refer to this SL bug report: Issues with the SL viewer in Mac OS Catalina.

There is no real fix for this crash (the fix will need to come from Apple); however, switching over to using the Nvidia web drivers will stop the crashes. There is a chance of the viewer running with poorer performance.

(This crash has continued on Sierra.)

This problem affects other games, too; for example, see constant crashes - OS X 10.11 El Capitan and OSX El Capitan 10.11 Beta (15A21). The same workaround appears to fix the problem in other games also; that is, to switch over to using the Nvidia web drivers instead of the Nvidia driver that Apple provides.

Please note that this is not a viewer-specific crash. Refer to this Firestorm Jira: [BUG-10302] [Mac El Capitan] Firestorm crash/incompatibility with Mac OS 10.11 and this SL Jira: BUG-10302 Frequent Crashes in Mac OS X 10.11 El Capitan.

• Find the list of Nvidia web drivers here, with download links directly from Nvidia: Nvidia Web Drivers.
• It is important that the drivers are matched to you OS Build number, see here for: How to determine your OS Build Number.
• You can switch between using the Apple Nvidia driver and the Nvidia web driver (needs a reboot after each change).

If some characters now display as boxes, you can edit the fonts.xml file within Firestorm to cause the characters to load properly.

• Log out of Firestorm.
• In a Finder window, go to your Applications folder.
• Right click on your Firestorm application and choose “Show Package Contents.”
• Navigate to Contents/Resources/fonts/fonts.xml.
• Open fonts.xml with Text Edit.
• From there, scroll down to the section where it shows hiragana.
• After the line <os name=“Mac”>, insert this line:
  <file>ヒラギノ角ゴシック W3.ttc</file>
  so that the page looks like this:

<os name="Mac">
<file>ヒラギノ角ゴシック W3.ttc</file> ///(only insert this line and leave everything else as is.)///
<file>ヒラギノ角ゴ Pro W3.otf</file>
<file>ヒラギノ角ゴ ProN W3.otf</file>
<file>AppleSDGothicNeo-Regular.otf</file>
<file>AppleGothic.dfont</file>
<file>AppleGothic.ttf</file>
<file>华文细黑.ttf</file>
</os>

• Be sure to save and exit.
• Open Firestorm and toggle to your Japanese keyboard or type in Japanese. It should now work as expected.

NOTE: This is only necessary for Firestorm versions 4.7.3 and older.

Mac OS apps will need to be notarized to be accepted by Apple's Gatekeeper after its Mojave 10.14.5 update.

Reference Safely open apps on your Mac
Also see BUG-227740 Mac OS 10.15 Catalina throws error on launch

To get around the lack of notarization of Firestorm, you will need to allow it to open anyway. Don't be alarmed by the dialog boxes that pop up. As long as you have downloaded the viewer from the Firestorm blog, you can rest assured that it is free from malware.

• Whether you ctrl + click > Open the application from the Applications folder or using the Dock icon, you will see this dialog appear. Be sure to click on the Cancel button (circled in green) before proceeding. If you click on “Move to Trash,” that will instantly put Firestorm into the trash can for you to delete later.

• Open System Preferences for your Mac. You can get to it from many places such as the Apple Menu in the top left corner of your screen or the grey gears icon from the Dock. You will then want to navigate to the Security & Privacy pane. In this screenshot, it is circled in green.

• After clicking to open this pane, you'll see there's a little blurb about opening the viewer anyway and a button to click that allows you to do so. Click this button to start the process.
  
  Note: You do not have to unlock the padlock to click this button.

• You will see another dialog box pop up as a final warning that this software may be harmful. Do not fear! As long as you downloaded the viewer from us (linked at the start of this tutorial), you are safe to open it without any harm. Simply click the Open button to finalize telling Gatekeeper that this program is safe. After you click Open on this last dialog box, the viewer will open as expected. This will persist for as long as the program is installed.
  
  Note: This will need to be repeated for any new installs of the viewer such as installing the OpenSim capable version of Firestorm, or updating the viewer to a new version.

This is a new security feature introduced by Apple in Catalina. See https://support.apple.com/guide/mac-help/control-access-to-input-monitoring-on-mac-mchl4cedafb6/mac for information.

• Firestorm does not need to monitor any of your input devices when you're using other apps.
• You can simply deny permission if you get this dialog from your Mac.

June 2020: Refer to this SL bug report: Issues with the SL viewer in Mac OS Catalina.

Start with this page EEP Basics

Second Life Community - Environmental Enhancement Project (aka EEP!) Feedback Thread

Second Life's Lab Gab Episode 23 - EEP Team!

Second Life Tutorial|EEP, Environmental Enhancement Project (Italian)

Second Life Environmental Enhancement Project

Importing old settings
You can import your old Windlight settings into EEP.
Note that approximately 200 Windlight settings have already been imported and can be found in My Environments - Library - Environments folder. These can be accessed via Quick Preferences. Otherwise, right-click and copy as desired to your Inventory - Settings folder.

1. Open an environment editor (Daycycle, Sky, or Water)
   
2. Select the Import button - This will open a file picker dialog
3. Navigate to where you have stored your Windlight XML files and select the file you would like to import:
   • C:\Program Files\Firestorm_64\app_settings\windlight
   • C:\Users\User\AppData\Roaming\Firestorm_x64\user_settings\windlight (personalized custom files)

You should import Windlights of the same type as the editor you have open (Daycycle, Sky, or Water) Windlight XML files are very sensitive to the directory structure. Files should be laid out as follows: ./windlight/days ./windlight/skies ./windlight/water

Group Ability If a group member other than the owner needs to apply an environment to a parcel, assign the ability under Parcel Settings - Modify environment settings and day cycle.

Ability to create Camera Presets

CEF Viewer which supports YouTube Live streams. CEF = Wikipedia - Chromium Embedded Framework

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

• See Jira updates below.

Catznip RLVa 2.2 Release Notes

Release Notes for v6.4.0. (540188) - Second Life Viewer Released on Friday, April 17, 2020.
https://releasenotes.secondlife.com/viewer/6.4.0.540188.html

Environmental Enhancement Project - EEP

Welcome to the Environmental Enhancement Project (aka EEP!) EEP is a major enhancement to the legacy Windlight environments, introducing new inventory object for defining the environmental settings. To properly experience EEP you will need ALM (Advanced Lighting Model) enabled under your graphics settings.

Highlights Shareable environmental objects that you can keep in your inventory. Parcel level control of environments. Up to four different sky layers that may be set independently. More options for customization. And much, much more

Personal Lighting This EEP RC includes a new Personal Lighting floater. When you open this floater it will snap an image of the current shared environment wherever you are standing. You are presented with a number of controls that allow you to make quick modifications to the environment, including sun and moon position, ambient lighting, and more!

These changes will persist until you log out or select “Use Shared Environment” from the World>Environment menu, so you can close the floater to get it out of your way.

Release Notes for v6.4.1. (540593) - Second Life Viewer Released on Monday, April 27, 2020.
https://releasenotes.secondlife.com/viewer/6.4.1.540593.html

Maintenance: Zirbenz

The Zirbenz Stone Pine Liqueur is a specially crafted beverage that comes from the Alps in Austria. The key ingredient from which this liqueur draws its flavor is the Arolla Stone Pine Fruit that is native to the Alps. Exceptionally smooth, slightly sweet and with a crisp floral finish – this Pine liqueur has been made the same way since 1797. Since this is an artisanal liqueur, it is not mass produced in any factory. Usually enjoyed as an after-ski drink, the liqueur is also used in various cocktails. It is made from completely natural ingredients. This liqueur was first made by Josef Hofer. It is handcrafted and bottled in a family distillery till date.

Release Notes for v6.4.2. (541639) - Second Life Viewer Released on Monday, May 11, 2020.
https://releasenotes.secondlife.com/viewer/6.4.2.541639.html

Camera Presets

Improved camera controls, including the ability to save presets.

Release Notes for v6.4.4. (543157) - Second Life Viewer Released on Tuesday, June 23, 2020.
https://releasenotes.secondlife.com/viewer/6.4.4.543157.html

CEF Update 2020

CEF Viewer which supports YouTube Live streams.

FMOD Studio 2.01.01 (updated Windows, Linux)
FMOD Studio 2.00.08 (Mac)

KDU v7.10.7 (Windows, Linux, Mac)

Voice Server Version: Vivox Version 4.10.0000.32327

LibVLC Version: 2.2.8

Chromium Embedded Framework (CEF) Dullahan:

• Dullahan: 1.7.0.202005311828
• CEF: 81.3.10+gb223419+chromium-81.0.4044.138
• Chromium: 81.0.4044.138
• Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

FIRE-23891 - [macOS] Mouse cursor jumps around when HiDPI is enabled and when using Pie menu
FIRE-24229 - Separate SL and Opensim settings folders / mixed up folders in appdata/roaming
FIRE-24311 - [BUG-228474] [SL-13082] [macOS] Blur when HiDPI Support Option Not Used
FIRE-29517 - [Mac] [Linux] Transitioning from third person view to mouselook freeze the view for a few seconds
FIRE-29567 - Potential crash caused by AO if floater is open at login
FIRE-29536 - media icon doesn't change when media is playing (MOAP)

Linden Lab Bug Tracker - EEP Issues Filter - requires login

BUG-228882 - [EEP] Disabling glow rendering while ALM is off results in massive rendering flicker
BUG-228781 - [EEP] Specular color interpreted wrong (too bright) from point lights.
BUG-228581 - [EEP] Specular map reflections are way too weak.
BUG-228752 - [EEP] Sky turns black when render quality is lowered to Low-Mid
(Affects Windows and Mac. Unsure about Linux)
BUG-228586 - [EEP] Jumping glowing effect depending on the camera distance
(Really weird bug but on objects it repros on it's very jarring to see. Disabling glow with result in bug above)
BUG-228431 - [EEP] Water lighting is wrong at certain camera angles
BUG-226381 - [EEP] Low FPS on the Test DRTVWR-440 EEP project viewer
(How badly you are affected by this bug may depend if your system is CPU or GPU bound.)
BUG-228821 - Viewer stalls for a second or more 1 minute after teleporting to a different region.
BUG-228910 - Viewer freeze for several seconds after receiving a message from a large group.

No Jira issue filed. The default region environment on mainland looks dark & dingy and this is what any user on EEP will see by default on mainland.
It still looks fine on pre-EEP viewers.
See this forum post for an image: https://community.secondlife.com/forums/topic/453117-eep-finally-out/?do=findComment&comment=2129751
See Vir's explanation of the problem here: https://community.secondlife.com/forums/topic/453117-eep-finally-out/?do=findComment&comment=2130951

FIRE-5482 - [FS] Some panel opening resets the windlight function to region default.
FIRE-22897 - Using double click to teleport a short distance defeats RLV no TP
FIRE-22952 - Water rendering issues using advanced lighting with Firestorm 5.1.7 (55786)
FIRE-24072 - [Windlight bug] - changing it from like midnight to estate time causing tinting (same with sunset,sunrise,midday)
FIRE-24215 - @sittp:2=n can be defeated by double click
FIRE-29035 - [BUG-227534] [SL-11625] Skin won't load for Bakes on Mesh while editing shape
FIRE-29362 - Hover Tips on objects setting not honored.
FIRE-29477 - Error message when pasting in Outfits folder
FIRE-29603 - Crash when adding first AO set
FIRE-29605 - [BUG-228838] Unable to Save Outfits
FIRE-29608 - Disabling “Turn avatar towards camera direction on view reset” is ignored
FIRE-29614 - Console Fade Chat Cuts off at blank lines
FIRE-29623 - Crash - Unable to create error report - Please verify there is enough space in your TEMP folder
FIRE-29634 - [Starlight skin] Places Floater - Crash when trying to save a landmark
FIRE-29637 - [OpenSim][EEP] Cannot load settings for [NAME[ when entering OpenSim
FIRE-29638 - [OpenSim][EEP] No valid environment setting selected
FIRE-29642 - Area Search, Distance to HUD = Distance to <0, 0, 0>
FIRE-29649 - [BUG-228852] FS crash when trying to open Spell Check floater when “SpellCheck” is FALSE
FIRE-29661 - Compile Error Linux 6.4.4 OpenAL
FIRE-29672 - FPS are not visible in tool bar with italian language
FIRE-29678 - Unable to use Notecard Editor
FIRE-29679 - OPENSIM: 6.3.9.58205 crashes when rezzing a mesh with edit floater open
FIRE-29684 - EEP - Missing string “New Day”

FIRE-2099 - Better Camera Control - Expose Debug Settings via Preferences Panel

FIRE-29641 - Russian translation update
FIRE-29669 - Russian translation update
FIRE-29703 - French translation update
FIRE-29713 - Japanese translation update
FIRE-29745 - Russian translation small update (correction)

FIRE-29611 - [RLVa] @setcam_eyeoffset command needs to be adapted for camera presets

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

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

If you have Intel HD 530, Intel HD 620 or Intel HD 630, and Windows 10 – This is an Intel driver issue.
The fix is to roll back to driver 24.20.100.6025.
Direct download Legacy Intel® Graphics Driver for Windows® 10 Version: 24.20.100.6025 - Unofficial download; Intel has removed the driver, it seems
Manual update How to manually update Intel Drivers
(Ref. BUG-225655.)

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

First, make sure your drivers are fully updated

• Visit Intel and try to update your drivers there.

Next, verify that your graphics card is one of the affected versions. You can find a table of affected versions here: Graphics Drivers Supported Operating Systems, but most frequently we have seen Intel HD 2000 and Intel HD 3000. You should be able to verify your graphics in the system info of your computer.

If this does not help, then download and install and 32bit version of the viewer. Firestorm Viewer Downloads

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

If this does not help, then download and install and 32bit version of the viewer. Firestorm Viewer Downloads

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.

If you have certain Intel HD graphics, and have upgraded your PC to Windows 10, your graphics card will not be fully supported by Intel. If you have this issue, you will be unable to log in. You will get one of the following error dialog boxes:

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

Load Library failed with error 1114, Dynamic Link Library (DLL) initiation routine failed

This is not a function of the viewer, but instead is a function of the drivers provided by Intel for your computer.

Verify that your graphics card is one of the affected versions. You can find a table of affected versions here: Graphics Drivers Supported Operating Systems. Most frequently we have seen Intel HD 2000 and Intel HD 3000. You should be able to verify your graphics in the system info of your computer.

You should now be able to run Firestorm on your PC.

These classes are based on our current Firestorm release and are conducted in text and/or voice as noted. There's no need to talk in a voice class, but you may want to be able to hear the instructor. We also usually have help available to answer questions in text.

Note that it is not mandatory that you use Firestorm to attend our classes, but it is best if you do.

Classes are held at the Firestorm Classroom unless otherwise noted.

Classes normally held daily between 8 am to 7 pm SLT. The schedule may change without notice. if the class times are inconvenient some classes have been recorded and are available 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*

Start with this page EEP Basics

Second Life Community - Environmental Enhancement Project (aka EEP!) Feedback Thread

Second Life's Lab Gab Episode 23 - EEP Team!

Second Life Tutorial|EEP, Environmental Enhancement Project (Italian)

Second Life Environmental Enhancement Project

Importing old settings
You can import your old Windlight settings into EEP.
Note that approximately 200 Windlight settings have already been imported and can be found in My Environments - Library - Environments folder. These can be accessed via Quick Preferences. Otherwise, right-click and copy as desired to your Inventory - Settings folder.

1. Open an environment editor (Daycycle, Sky, or Water)
   
2. Select the Import button - This will open a file picker dialog
3. Navigate to where you have stored your Windlight XML files and select the file you would like to import:
   • C:\Program Files\Firestorm_64\app_settings\windlight
   • C:\Users\User\AppData\Roaming\Firestorm_x64\user_settings\windlight (personalized custom files)

You should import Windlights of the same type as the editor you have open (Daycycle, Sky, or Water) Windlight XML files are very sensitive to the directory structure. Files should be laid out as follows: ./windlight/days ./windlight/skies ./windlight/water

Group Ability If a group member other than the owner needs to apply an environment to a parcel, assign the ability under Parcel Settings - Modify environment settings and day cycle.

Ability to create Camera Presets

CEF Viewer which supports YouTube Live streams. CEF = Wikipedia - Chromium Embedded Framework

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

• See Jira updates below.

Catznip RLVa 2.2 Release Notes

Release Notes for v6.4.0. (540188) - Second Life Viewer Released on Friday, April 17, 2020.
https://releasenotes.secondlife.com/viewer/6.4.0.540188.html

Environmental Enhancement Project - EEP

Welcome to the Environmental Enhancement Project (aka EEP!) EEP is a major enhancement to the legacy Windlight environments, introducing new inventory object for defining the environmental settings. To properly experience EEP you will need ALM (Advanced Lighting Model) enabled under your graphics settings.

Highlights Shareable environmental objects that you can keep in your inventory. Parcel level control of environments. Up to four different sky layers that may be set independently. More options for customization. And much, much more

Personal Lighting This EEP RC includes a new Personal Lighting floater. When you open this floater it will snap an image of the current shared environment wherever you are standing. You are presented with a number of controls that allow you to make quick modifications to the environment, including sun and moon position, ambient lighting, and more!

These changes will persist until you log out or select “Use Shared Environment” from the World>Environment menu, so you can close the floater to get it out of your way.

Release Notes for v6.4.1. (540593) - Second Life Viewer Released on Monday, April 27, 2020.
https://releasenotes.secondlife.com/viewer/6.4.1.540593.html

Maintenance: Zirbenz

The Zirbenz Stone Pine Liqueur is a specially crafted beverage that comes from the Alps in Austria. The key ingredient from which this liqueur draws its flavor is the Arolla Stone Pine Fruit that is native to the Alps. Exceptionally smooth, slightly sweet and with a crisp floral finish – this Pine liqueur has been made the same way since 1797. Since this is an artisanal liqueur, it is not mass produced in any factory. Usually enjoyed as an after-ski drink, the liqueur is also used in various cocktails. It is made from completely natural ingredients. This liqueur was first made by Josef Hofer. It is handcrafted and bottled in a family distillery till date.

Release Notes for v6.4.2. (541639) - Second Life Viewer Released on Monday, May 11, 2020.
https://releasenotes.secondlife.com/viewer/6.4.2.541639.html

Camera Presets

Improved camera controls, including the ability to save presets.

Release Notes for v6.4.4. (543157) - Second Life Viewer Released on Tuesday, June 23, 2020.
https://releasenotes.secondlife.com/viewer/6.4.4.543157.html

CEF Update 2020

CEF Viewer which supports YouTube Live streams.

FMOD Studio 2.01.01 (updated Windows, Linux)
FMOD Studio 2.00.08 (Mac)

KDU v7.10.7 (Windows, Linux, Mac)

Voice Server Version: Vivox Version 4.10.0000.32327

LibVLC Version: 2.2.8

Chromium Embedded Framework (CEF) Dullahan:

• Dullahan: 1.7.0.202005311828
• CEF: 81.3.10+gb223419+chromium-81.0.4044.138
• Chromium: 81.0.4044.138
• Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

FIRE-23891 - [macOS] Mouse cursor jumps around when HiDPI is enabled and when using Pie menu
FIRE-24229 - Separate SL and Opensim settings folders / mixed up folders in appdata/roaming
FIRE-24311 - [BUG-228474] [SL-13082] [macOS] Blur when HiDPI Support Option Not Used
FIRE-29517 - [Mac] [Linux] Transitioning from third person view to mouselook freeze the view for a few seconds
FIRE-29567 - Potential crash caused by AO if floater is open at login
FIRE-29536 - media icon doesn't change when media is playing (MOAP)

Linden Lab Bug Tracker - EEP Issues Filter - requires login

BUG-228882 - [EEP] Disabling glow rendering while ALM is off results in massive rendering flicker
BUG-228781 - [EEP] Specular color interpreted wrong (too bright) from point lights.
BUG-228581 - [EEP] Specular map reflections are way too weak.
BUG-228752 - [EEP] Sky turns black when render quality is lowered to Low-Mid
(Affects Windows and Mac. Unsure about Linux)
BUG-228586 - [EEP] Jumping glowing effect depending on the camera distance
(Really weird bug but on objects it repros on it's very jarring to see. Disabling glow with result in bug above)
BUG-228431 - [EEP] Water lighting is wrong at certain camera angles
BUG-226381 - [EEP] Low FPS on the Test DRTVWR-440 EEP project viewer
(How badly you are affected by this bug may depend if your system is CPU or GPU bound.)
BUG-228821 - Viewer stalls for a second or more 1 minute after teleporting to a different region.
BUG-228910 - Viewer freeze for several seconds after receiving a message from a large group.

No Jira issue filed. The default region environment on mainland looks dark & dingy and this is what any user on EEP will see by default on mainland.
It still looks fine on pre-EEP viewers.
See this forum post for an image: https://community.secondlife.com/forums/topic/453117-eep-finally-out/?do=findComment&comment=2129751
See Vir's explanation of the problem here: https://community.secondlife.com/forums/topic/453117-eep-finally-out/?do=findComment&comment=2130951

FIRE-5482 - [FS] Some panel opening resets the windlight function to region default.
FIRE-22897 - Using double click to teleport a short distance defeats RLV no TP
FIRE-22952 - Water rendering issues using advanced lighting with Firestorm 5.1.7 (55786)
FIRE-24072 - [Windlight bug] - changing it from like midnight to estate time causing tinting (same with sunset,sunrise,midday)
FIRE-24215 - @sittp:2=n can be defeated by double click
FIRE-29035 - [BUG-227534] [SL-11625] Skin won't load for Bakes on Mesh while editing shape
FIRE-29362 - Hover Tips on objects setting not honored.
FIRE-29477 - Error message when pasting in Outfits folder
FIRE-29603 - Crash when adding first AO set
FIRE-29605 - [BUG-228838] Unable to Save Outfits
FIRE-29608 - Disabling “Turn avatar towards camera direction on view reset” is ignored
FIRE-29614 - Console Fade Chat Cuts off at blank lines
FIRE-29623 - Crash - Unable to create error report - Please verify there is enough space in your TEMP folder
FIRE-29634 - [Starlight skin] Places Floater - Crash when trying to save a landmark
FIRE-29637 - [OpenSim][EEP] Cannot load settings for [NAME[ when entering OpenSim
FIRE-29638 - [OpenSim][EEP] No valid environment setting selected
FIRE-29642 - Area Search, Distance to HUD = Distance to <0, 0, 0>
FIRE-29649 - [BUG-228852] FS crash when trying to open Spell Check floater when “SpellCheck” is FALSE
FIRE-29661 - Compile Error Linux 6.4.4 OpenAL
FIRE-29672 - FPS are not visible in tool bar with italian language
FIRE-29678 - Unable to use Notecard Editor
FIRE-29679 - OPENSIM: 6.3.9.58205 crashes when rezzing a mesh with edit floater open
FIRE-29684 - EEP - Missing string “New Day”

FIRE-2099 - Better Camera Control - Expose Debug Settings via Preferences Panel

FIRE-29641 - Russian translation update
FIRE-29669 - Russian translation update
FIRE-29703 - French translation update
FIRE-29713 - Japanese translation update
FIRE-29745 - Russian translation small update (correction)

FIRE-29611 - [RLVa] @setcam_eyeoffset command needs to be adapted for camera presets

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

Note that many libraries cannot be installed using Synaptic or the Software Center; use apt in a terminal instead.

The Firestorm core binary has no unmet dependencies. However, SLVoice, SLPlugin and dullahan_host require additional libraries to do their work.

Install the additional libraries

NOTE: The libraries cannot be installed using Synaptic or the Software Center. They must be installed via apt or aptitude.

sudo apt install libidn11:i386 libstdc++6:i386 libuuid1:i386 zlib1g:i386

These two packages provide support for voice and media services.

sudo apt install gstreamer1.0-pulseaudio:i386 pepperflashplugin-nonfree

If you run across the media_plugin_cef failure message, installing these packages may help:

sudo apt install libnss3:i386 libnspr4:i386 libxtst6:i386 libgconf-2-4:i386 libxss1:i386

Regardless of the method you choose, rebooting at this point can ensure that the OS is properly updated, though it should inform you if a reboot is required.

http://www.firestormviewer.org/linux/

In a terminal, type:

cd # Your home directory by default
mkdir Firestorm
tar xf Phoenix_Fire{tab to expand} -C Firestorm --strip-components=1

At this point, you can launch Firestorm from a terminal:

cd ~/Firestorm
./firestorm

And watch the output, optionally copy it for analysis since not all of it made its way to the viewer log.

You can also create a desktop shortcut, either manually or by running this script in a terminal:

~/Firestorm/etc/refresh_desktop_app_entry.sh

If you crash continually, it will be helpful to get a backtrace, like so:

cd ~/Firestorm
sed -i "/^#export .*gdb/ s/^#//" ./firestorm # This enables gnu debug
./firestorm

At the (gdb) prompt, type r to launch Firestorm. When Firestorm crashes, you should be back at a (gdb) prompt.
Type bt to get a backtrace (there may be several pages, press Enter until you get the gdb prompt again). Copy everything from the terminal screen to a text file.
Type q to exit gdb.
Create a Support Request on our Jira and attach the backtrace as well as crash logs. JIRA can guide you through the process.

NOTE: You can turn off debugging with:

sed -i "/^export .*gdb/ s/^export/#export/" ./firestorm

Default Linux voice files function, but may not on your particular system. As a workaround, install wine and use the Windows 32-bit voice files:

sudo apt install wine-stable
winecfg

Once WINE is configured to your satisfaction, launch Firestorm and log in, disable voice, then press Ctrl+Alt+Shift+S to open Debug Settings. Search for FSLinuxEnableWin32VoiceProxy, set that to TRUE, then close Debug Settings. For good measure, relog, then enable and test voice.

Note that using WINE means there is a slight delay connecting to voice as the WINE system starts up. As well, WINE needs a little time to shut down when you disconnect voice. This may cause a race condition if you toggle voice, where a new connection tries to start before the previous one shuts down. This can affect both instances of WINE, and a relog may be required to restore voice functions.

Note that many libraries cannot be installed using the Software Center; use apt in a terminal instead.

The Firestorm core binary has no unmet dependencies. However, SLVoice, SLPlugin and dullahan_host require additional libraries to do their work.

Install the additional libraries

sudo apt install libidn11:i386 libstdc++6:i386

These two packages provide support for voice and media services.

sudo apt install gstreamer1.0-pulseaudio:i386 pepperflashplugin-nonfree

If you run across the media_plugin_cef failure message, installing these packages may help:

sudo apt install libnss3:i386 libnspr4:i386 libxtst6:i386 libgconf-2-4:i386 libxss1:i386

Regardless of the method you choose, rebooting at this point can ensure that the OS is properly updated, though it should inform you if a reboot is required.

http://www.firestormviewer.org/linux/

In a terminal, type:

cd # Your home directory by default
mkdir Firestorm
tar xf Phoenix_Fire{tab to expand} -C Firestorm --strip-components=1

At this point, you can launch Firestorm from a terminal:

cd ~/Firestorm
./firestorm

And watch the output, optionally copy it for analysis since not all of it made its way to the viewer log.

You can also create a desktop shortcut, either manually or by running this script in a terminal:

~/Firestorm/etc/refresh_desktop_app_entry.sh

If you crash continually, it will be helpful to get a backtrace, like so:

cd ~/Firestorm
sed -i "/^#export .*gdb/ s/^#//" ./firestorm # This enables gnu debug
./firestorm

At the (gdb) prompt, type r to launch Firestorm. When Firestorm crashes, you should be back at a (gdb) prompt.
Type bt to get a backtrace (there may be several pages, press Enter until you get the gdb prompt again). Copy everything from the terminal screen to a text file.
Type q to exit gdb.
Create a Support Request on our Jira and attach the backtrace as well as crash logs. JIRA can guide you through the process.

NOTE: You can turn off debugging with:

sed -i "/^export .*gdb/ s/^export/#export/" ./firestorm

Default Linux voice files function, but may not on your particular system. As a workaround, install wine and use the Windows 32-bit voice files:

sudo apt install wine-stable
winecfg

Once WINE is configured to your satisfaction, launch Firestorm and log in, disable voice if necessary, then press Ctrl+Alt+Shift+S to open Debug Settings. Search for FSLinuxEnableWin32VoiceProxy, set that to TRUE, then close Debug Settings. For good measure, relog, then enable and test voice.

Note that using WINE means there is a slight delay connecting to voice as the WINE system starts up. As well, WINE needs a little time to shut down when you disconnect voice. This may cause a race condition if you toggle voice, where a new connection tries to start before the previous one shuts down. This can affect both instances of WINE, and a relog may be required to restore voice functions.

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.

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

nslookup command how-to: WindowsMacLinux

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

Steps:

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

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

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

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

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

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

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

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

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

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

Some details provided below.

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

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

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

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

You can also try adjusting your bandwidth as explained here.

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

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

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

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

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

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

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

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

• Try a relog, or even reboot your router/modem, and then your computer. ¹⁾

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

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

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

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

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

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

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

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

There are several reasons why you would want to file a JIRA:

• To request a new feature
• To request an improvement
• To report a bug
• To request support

Note: We occasionally have to disable new registrations on the Jira. If the signup page is disabled, contact one of our support team for assistance.

In order to do anything except view Firestorm issues, you will need an account on JIRA. Creating an account is very easy. Start by going to the Sign Up page and enter the following information:

• Username - This can be anything, but we prefer that it be your SL username. Don't use spaces, but you can use a period to separate words, such as beta.tester. This is what you will use to log into JIRA.
• Password - This needs to be at least 8 characters in length, and shouldn't be the same as any other password you use.
• Confirm Password - Type in your password again
• Full Name - This should be your full SL name. If your username was beta.tester, your full name would be Beta Tester. This is what everyone will see when you create a JIRA or comment on one, so do not use your real name.
• Email - Enter a valid email address. JIRA can send you emails when someone comments on your JIRA or on issues you've “watched”.

Click Sign up and you're all set. If JIRA complains, fix the entries it complains about and then click Sign up again.

No matter what kind of issue you want to create, the process is nearly identical and starts with going to the JIRA Dashboard and clicking the Create Issue link near the top of the page (every page), on the right side of the red menu line. If you don't see that there, you need to log in - click Log In at the top right, enter your username and password and then click Log In.

Clicking Create Issue opens a small box with Project and Issue Type selections. There are a lot of choices, here's a list of the most common:

• Requesting a new feature
  • Set the Project to Firestorm ¹⁾ and the Issue Type to New Feature.
• Requesting an improvement to existing code
  • Set the Project to Firestorm ²⁾ and the Issue Type to Improvement.
• Reporting a bug
  • Set the Project to Firestorm and the Issue Type to Bug.
• Requesting Support
  • Set the Project to Support and the Issue Type to Support Request.

Then click Create. This will bring up the Create Issue page. From here the fields and the information that goes in them are the same regardless of what type of issue you want to create.

• Summary - Enter a brief overview of the problem. You don't have to put everything here, just a few words to summarize the issue.
• Priority - By default this is set to Major, and it can remain that way. If you are reporting an issue that is preventing you from logging on at all with any of our viewers, you can choose Blocker. But if you spotted a typographical error, that's probably something minor or even trivial. If you put in the wrong priority, don't worry, we'll work with you as needed to set it correctly.
• SL Avatar Name - Set this to the name of the avatar that is affected.
• Patch Attached - If you're submitting a patch that would add a new feature, improve on an existing one or correct a bug of some kind, check this box. Otherwise, leave it unchecked.
• Reported In - Select the viewer that you're using. This can either be the one with the problem or some other version.
• Affects Versions - Here you would want to identify all the versions that you know are affected. For example, if you have a problem that shows up in every one of our Release versions of Firestorm, you would want to list them all. If you don't know, then list only the version you're using.
• Environment - This is very important for Support requests and bug reports. We need to know what your system looks like to the viewer. To get this information, open the viewer, click on the Help menu and select About, and then click Copy to Clipboard. Then click into the Environment field in the JIRA page, right-click and choose Paste (or press Ctrl-V).
  Note here that if you're creating anything other than a Support request, this information is visible to everyone. You can delete your location details if you wish.
• Description - Here is where you want to put as many details as you can about the issue. If you're reporting a bug, or if you have a problem that you can reproduce consistently, you want to include the steps you take to reproduce that. Also include details such as whether this affects only one avatar, whether it happens on more than one computer (we'd like system information for each computer in that case) and so on. If you get error messages, be sure to write the exact message (as closely as possible).
• Attachment - Add files that you have that can help further explain the issue, such as images or videos, use the Browse button to add them. Remember that the maximum file size is 10MB, and images must be either JPG or PNG.

Another very useful bit of information is your viewer logs. These can sometimes be very helpful in finding the root cause of a problem and crafting a solution. Logs should be collected after having logged out - or after a crash if that is your issue - and before restarting the viewer. If you log in again then the logs won't have any of the clues needed.

In its default location, the logs folder is hidden on most systems. To find it, you will need to show hidden folders. The logs folder is in:

Compress all the files in the folder named “logs”:

• Windows: Right-click on the folder and choose Send To > Compressed zip file
• Linux Gnome: Right-click on the folder and choose Compress
• Linux shell: tar -cjvf “Viewer_logs.tar.bz2” ./logs/
• Mac: Hold Shift while highlighting the contents of the folder and then Ctrl-click and choose Compress Items

You may want to move this compressed file to your Desktop.

NOTE 1: If you have a large number of accumulated files in your Logs folder, the compressed file may be too large to attach to the Jira ticket. If this happens, delete most of the subfolders starting with “dump,” keeping only the latest one.
NOTE 2: Alternatively, delete the entire Logs folder, log back in on Firestorm and reproduce your problem, log out, then compress the new Logs folder that has now been created.

To attach logs to an issue filed earlier, go to More Actions → Attach Files. Then click Select Files button, locate your compressed file (on your Desktop if you moved it there) and then click Open or OK. You may optionally add a comment at the same time. Finally, click Attach

Now that you have all fields filled, out go back and check to make sure you haven't left anything out and made all the selections needed. Once you are done checking it over click the Create button. If after double checking your ticket you decide not to file the ticket just click the Cancel button.

Once the JIRA has been created you'll be shown the issue number. It will be in the form of the project abbreviation, like SUP or FIRE, and a number (example: FIRE-1234). Only you and team members can view your own SUP issues.

You'll also get an email when someone comments, when something is attached or when some other action takes place. Click the link in the email (it looks just like the issue number you got initially) and comment in the issue itself. Do not reply to the email, it will not work.

If you don't get any emails, they could be filtered as spam or the email address you supplied is incorrect. You can confirm your email by going to your profile and then clicking the little edit pencil along the Details line.

Further reading: How to Report Bugs Effectively

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

• 0079Galadriel
• Aby Kiyori (German)
• akafox
• Alexegram
• Angel Bellisserian (French)
• Angela Kwak (Dutch)
• Arabella Luminos
• Ayah Whimsy (French)
• Banshee Heartsong
• Cheyenne Palisades
• Christa March (dutch, German)
• ChuckPC
• CountryCat Furse
• CWEarp
• Danielle Gilman (Spanish)
• djhotrod19
• Fayleen Bellios
• FrankASinatra
• fringeelement2
• Ilia Shim (Russian)
• ImaLuckygirl
• Isalia Michalak (Dutch, French)
• jackstir
• JadeTyler
• Jolie Serendipity
• Jules1979 (Hungarian)
• Kitty Beery (Dutch)
• Laurelrose Anthony
• Liliana Darwinian (Portuguese)
• Maddie Margulis
• MarcSeven Lubitsch
• meady212
• Melodia McDonnagh
• Mermaid Stormcrow
• mmimmi79 (Serbian, Bosnian and Croatian)
• Monyka Mai (Portuguese)
• NavanaxSacratus
• Olivia Halster
• opperheks Enzo (Dutch, German)
• PassionateAviator
• Pim Peccable
• Raine Kiyori
• Refyls
• Sonricita Belfire (Spanish, some Arabic, French)
• Sparkle Weatherwax
• Synthetic Mode
• Thomnus Magic (Danish)
• Tracy Argus
• Upton0Goode
• Webbi Jonson (German)

• 0079Galadriel
• briannainchains
• Forsaken Later
• Hilary Querrien
• MarcSeven Lubitsch
• nuttidoxieg4 merryman
• panterapolnocy
• Sirus Plunkett
• Starwolff2000
• Varahi Lusch

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