• See Jira updates below.

Catznip RLVa 2.2 Release Notes

Release Notes for v6.4.6. (545962) - Second Life Viewer Released on Monday, August 10, 2020.
https://releasenotes.secondlife.com/viewer/6.4.6.545962.html

Viewer Compiler Updates

Internal build update to VS2017 and Boost.Fiber. Because we had to rebuild all the component autobuild packages for the compiler upgrade, the project also subsumed the problem of migrating all our autobuild packages to git source repositories.

No user facing changes.

Release Notes for v6.4.7. (546539) - Second Life Viewer Released on Wednesday, August 19, 2020.
https://releasenotes.secondlife.com/viewer/6.4.7.546539.html

Maintenance - Arrack

Arrack is a distilled alcoholic drink typically produced in the Indian subcontinent and Southeast Asia, made from the fermented sap of coconut flowers or sugarcane, and also with grain (e.g. red rice) or fruit depending upon the country of origin. It is sometimes spelled arak, or simply referred to as ‘rack or ‘rak. It is not to be confused with the anise-flavored distilled spirit called Arak or Araq.

There are two primary styles of Arrack that are very different from one another: Batavia Arrack is often clear in color but has a flavor profile more similar to dark rum, with a distinctive “funk” or “hogo” imparted to it from fermented red rice. Ceylon Arrack, by contrast, is a more refined and subtle spirit. It has hints of Cognac and rum character and a wealth of delicate floral notes. Both styles are also made “in house” by local citizenry and can be more akin to moonshine in their presentation.

Note: This Viewer uses Viewer Manager 2.0.538279

FMOD Studio 2.01.03 (updated Windows, Linux)
FMOD Studio 2.01.02 (Mac)

KDU v8.0.6 (Windows, Linux, Mac)

Voice Server Version: Vivox Version 4.10.0000.32327

LibVLC Version: 2.2.8

Chromium Embedded Framework (CEF) Dullahan:

• Dullahan: 1.8.0.202007201344 (Windows)
• Dullahan: 1.7.0.202005311125 (Mac)
• 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-29517 - [Mac] [Linux] Transitioning from third person view to mouselook freeze the view for a few seconds
FIRE-29536 - media icon doesn't change when media is playing (MOAP)
FIRE-29930 - Move and View Appearance Auto Pose re-enables itself
FIRE-29942 - Delete Links Only in Replace Links feature stalls stops

FIRE-3973 - Login screen a patchwork on large screens - image doesn't fill
FIRE-12802 - Vintage/Latency skins. Minimized windows can be lost under bottom chat bat, toolbar
FIRE-24171 - the “receive group IM” checkbox has no effect
FIRE-29081 - [BUG-228873] Problem with ipv6 streaming addresses
FIRE-29761 - Clear Location History does not clear Location History
FIRE-29774 - script recover message across different accounts
FIRE-29902 - Fix help links on EEP viewer
FIRE-29903 - [OpenSim] Agent appearance not sent to simulator
FIRE-29911 - Group Chat Transcripts Sometimes lack “(group)” in File Name
FIRE-29938 - [Windows] SLURL handler replaced with each client installation
FIRE-29942 - Delete Links Only in Replace Links feature stalls stops
FIRE-29943 - Chat log file created when “Sharing” an inventory item does not obey “Use Legacy File Name format”
FIRE-29950 - Camera Controls - can not toggle in and out of object view
FIRE-29977 - Inventory + Upload Displays costs currency symbol twice as $L$L
FIRE-29994 - Choosing “What's Hot” from login screen does not update the location field
FIRE-29995 - DEBUG_CHANNEL messages count as spam
FIRE-30003 - Ctrl F10 will not bind to Gestures
FIRE-30019 - [Linux] Login window doesn't take up the entire viewer window, has horizontal scrollbar
FIRE-30029 - Linux Compile Issue: SL-13634 breaks Linux opensource builds

FIRE-29926 - Add Crossfade option for EEP Settings

FIRE-24306 - Make It So Saving a Notecard Does Not Return You to the Top of the Notecard
FIRE-29880 - Provide feedback to user when user tries to move with movelock or other locks engaged
FIRE-29893 - Remove the terms “WL” and “Windlight” from EEP viewer
FIRE-29935 - Add option to deactivate the confirmation for bulk uploads

FIRE-29918 - French translation update
FIRE-29953 - French translation update
FIRE-29956 - French translation update
FIRE-29957 - French translation update
FIRE-30025 - French translation update
FIRE-30030 - French translation update

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.

See the SL page Environment Editor: Personal Lighting for full details.

The Personal Lighting Floater is used to make temporary adjustments to the environment where you are. This is useful for photography or simply for changing something to suit your own preference. It is NOT for creating your own settings assets, and changes cannot be saved.

When you open this floater it will “grab” the current shared environment wherever you are standing. That lighting will be retained as your personal lighting until you reset it or log out. You are also 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. The lighting, and any changes you made, will persist (across TPs), until you log out or reset it, so you can close the floater to get it out of your way.

There are two ways to reset. Both do the same thing—return you to the Shared Environment:

• Select “Use Shared Environment” from the World → Environment menu
• Click the “X” button in the lower right of Quick Prefs.

Alternatively, you can choose a different EEP setting from Quick Prefs or Inventory, and that will supersede the Personal Lighting.

If you find that you are crashing frequently, then perhaps the suggestions here will be helpful. Please don't skim the page - read it carefully.

It is important to distinguish between two things: being logged out (disconnected), and crashing.

If a small window appears, saying that you have been logged out of SL, this isn't a crash. Rather, SL is disconnecting you, for one of a number of reasons, including:

• The region you are in is going down.
• During teleport, the SL servers may fail to hand you over to your destination and so log you out; help on that is given here.
• Your network connection has gone down.
• Your network connection has become poor or unreliable and SL has lost contact with your avatar.

Things to try - in order:

• Reboot your router/modem, then your computer;
• Make sure your bandwidth is set correctly - follow the instructions hereexactly as given;
• Shut down any other programs that are making heavy use of your network connection, such as torrents;
• If using wifi, move closer to your router, if possible, or change to a wired connection;
• If you use Mac with Yosemite, see if this might be your case.
• If the problems persist still, try changing your DNS to Google, as explained here.

If you are being logged out when you edit appearance, or edit shape, or use the Appearance toolbar button, did you drop items into the Outfits folder that were not created via the Outfits/Appearance window? If so, remove those items.

Firestorm itself has crashed. The remainder of this page offers possible solutions.

• New using Version 6.3.9 only. If you crash within a few seconds of logging in, it may be related to a crash in the client AO. See FS AO Crash with Firestorm 6.3.9 for methods to resolve this.

• Update your Operating System. See the advice from LL, and the reasons behind it, here.

• (Windows-only)
  • If you are using an ATI (AMD) graphics card, then please refer here for known problems with these cards.
  • For nVidia users, please refer to this page.
  • Also for nVidia: if you recently updated your drivers and are experiencing crashes, try reverting to an older driver that worked for you.

• (Mac-only)
  • If you have Sierra plus Nvidia graphics, see Mac Sierra.
  • If you have El Capitan plus Nvidia graphics, see Mac El Capitan.
  • If you crash when uploading images to SL or when saving snapshots to your hard drive, see Mac File Picker Crash.

• In Preferences → Graphics → General:
  • Reduce Draw Distance by half (or more).
  • Reduce Max # non-impostor avatars.
  • Reduce Maximum Complexity by half (or more).

• Disable VBO: Run Firestorm and before logging in, press Ctrl-P to bring up the Preferences window. Then click on Graphics → Hardware Settings tab. Make sure that “Enable OpenGL Vertex Buffer Objects” is not checked. NOTE: This will result in a significant drop in FPS.

• Several creators recommend specific debug 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:
  • RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
  • TextureLoadFullRes should never be enabled.

• (Grids other than SL only!) Disable HTTP Get Textures: Open the preferences window, then click on Graphics → Rendering tab. Make sure “Use HTTP Textures” is not checked. Please clear your cache if you change this setting.

• It is possible that your graphics settings are set higher than your computer can handle. To see if this is the case, go to Preferences → Graphics, and click on Reset (the circular arrow to the right of the quality slider). After doing this, you may still need to reduce Draw Distance and Max # non-impostor avatars, as mentioned above.

• If you have Shadows turned on, try turning them off. See this page for more side effects of shadows.

• Another thing you can try is: Develop → World → Dump Region Object Cache, then relog. (The Develop menu is revealed with Ctrl-Alt-Q, if you cannot see it.) This sometimes also helps deal with odd texture issues; it may need to be done several times.

• If clicking on a link or SLURL in Firestorm causes an instant crash: do you have AVG 2011 installed? If so, it probably flagged SLPlugin as malware. See here for more on this.

• If you have Webroot SecureAnywhere Antivirus, see Webroot Issues.

• If you are crashing when you try to upload a texture, please try disabling VBO, as described above. If you are on a Mac, this workaround may fix the problem.

• If the above tips do not help, you might benefit from a cache clear or viewer clean reinstall.

• If you find that a full manual cache clear allows you to log in, and you crash unless you do this, or if one of your accounts in particular tends to crash after logging in, then there is a good chance that you have one or more problems with certain inventory items; please see this page for how to deal with this.

If you have eliminated all the possible causes for the crash and you are still crashing, it's time to submit a Support Request on our jira. In that request, you can include screenshots or videos, if they will help clarify your description, as well as your sysinfo and viewer event logs. Follow the steps in this link to create the request and add your logs.

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.

A Windows 10 update in mid May 2018 (and reported as recently as May 2019) has resulted in many having audio problems with the viewer. This is actually a problem with the update, and needs to be fixed externally to the viewer.

• If your mic seems to have stopped working, try this: In your operating system, go to Settings → Privacy → Microphone and make sure “Allow apps to access my microphone” is ON.
• In addition: A user has kindly provided this link to help you check your settings in the new Windows software and resolve the issue.
• Further to this, you should also check Windows Mixer settings, since audio devices may have been reset.

If you're on an ASUS laptop and Sonic 3 is running, this is preventing FS from finding your driver. The solution is to disable Sonic 3.

If you suddenly sound like a man (and you aren't), or your friend suddenly sounds like a demon (and isn't), or you are hearing other forms of distorted voice, try this:

1. Right click the Speakers icon on your system tray and select Open Sound Settings.
2. Go to Input section and click on Device Properties.
3. Switch to the Advanced tab.
4. Under Default Format drop down menu, select: 2 channel, 16 bit, 44100 Hz (CD quality).
5. Switch to Enhancements tab.
6. Check “Disable All Sound Effects”
7. Press OK
8. Close the Setting window
9. Relog if needed.

If you suddenly find that sounds do not play, things like button sounds or in-world object sounds, the possible cause is your default output format. Try this:

1. Right click the Speakers icon on your Windows PC system tray and select Open Sound Settings.
2. Click on Device Properties in the Output section.
3. Click on Additional device properties under Related Settings.
4. Switch to the Advanced tab.
5. Under Default Format drop down menu, select: 16 bit, 44100 Hz (CD quality).
6. Click Apply and OK.
7. Relog if needed.

If some characters now display as boxes, you will need to reinstall Windows font packs. Some of the more common font packs are Chinese, Japanese and Korean, though if you installed those and still see boxes, you will want to ask the person using those characters to tell you what language (or symbol set) they are so that you can install the appropriate font pack.

1. Log out of Firestorm.
2. Go to the Windows Start menu and choose Settings.
3. In the window that opens, click in the search field at the top right and type in “language”
4. Select Add a language from the search results.
5. Click the + Add a language option and select the language from the list. The contents of the window scrolls left and right.
6. Back in the Add a language section, click the newly added language and choose Options.
7. Click the top Download button. The language will download and install, and it may take some time.
8. Repeat this for each language pack you wish to install.
9. Now log into Firestorm; you should see the missing characters correctly rendered.

Error 0xc000007b when launching 64 bit Firestorm:

Try following these steps to get the Firestorm installer to reinstall the Visual C++ redistributables that come packaged with it:

1. First make sure you have the Firestorm installer handy in a place where you can easily access it when you get to the step where it's needed below. (You can download it from here, or from here if you need an older version than the current release.)
2. Go to the Windows Start Menu and choose Settings.
3. In the window that opens, click on “System Display, notifications, apps, power.”
4. In the next window go down to “Apps & features.”
5. Scroll down to the entry for “Microsoft Visual C++ 2010 x86 Redistributable.” Click on it and choose “Uninstall” (the list won't necessarily update to show that it is uninstalled, but it is).
6. Click on “Microsoft Visual C++ 2010 x64 Redistributable” and once again choose “Uninstall.”
7. Close that window.
8. Re-run the Firstorm installer. The installer window will now say “Modify Setup” (since FS is already installed) and will give you 3 options: “Repair”, “Uninstall” and “Close.” Click on “Repair.” Firestorm will reinstall the Microsoft Visual C++ 2010 Redistributables that it ships with.
9. Restart your computer. You should be able to launch Firestorm without getting the error message now.

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 graphics, install the 32bit version of the viewer.

The most common cause for this is a non-default DPI value, or screen scaling. Refer to this page for tips on setting DPI/scaling to default.

First try increasing Preferences → User Interface → 2D Overlay → UI Scaling. Another possibility is Preferencess → User Interface → Font → Font size adjustment.

This is most often caused by a high DPI scaling setting, usually 125% on most 2k displays. A viewer set to the same width as the display resolution (1920, for example), would extend beyond the display border. To correct this:

• Log out of Firestorm
• Right click the Firestorm shortcut and choose Properties
• In Properties, click the Compatibility tab
• Near the bottom, find and check “Disable display scaling on high DPI settings”
• Click OK and Apply

When you launch Firestorm, it should display at the default DPI scale, 100%

Some Windows 10 updates change the machine ID used to create login credentials, resulting in Firestorm reporting “Failed to Decode Login Credentials”. The best way to deal with this is to wipe the stored credentials file, as explained here. Naturally, you will then have to retype the user name and password for all your accounts, when first logging in after deleting the credentials file.

Reported on Linden Lab's bug tracker BUG-139291

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

• Open Windows settings (left side, above Power)
• Select Language
• Set Display language to your local one
• Select Administrative language settings
• in Language for non-unicode programs select UTF-8 for English United States

Ref. here.

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 and 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*

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

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

However, there are a few other things to try:

• Go to a different region and see if you are able to move there. If so, something at your original location is causing the problem.
• If you are using a LAQ mesh head, make sure you don't have the Pose feature turned on.
• Make sure you don't have some other HUD with a pose feature. (For instance, one user has reported this problem with the Lelutka Axis face HUD.)
• If you can't find what attachment is causing the problem, try going to Advanced menu (Ctrl-Alt-D ) → Release Keys.
  • Note: Release Keys will be greyed out if RLV has locked any of your attachments. To disable RLV, go to Prefs → Firestorm → Extras, untick the top item, and then relog.
• Make sure you don't have the Firestorm pose stand active.
  • If you have the Pose Stand button on your toolbar, make sure it's not “on.”
  • If you don't have the button, go to Avatar menu → Toolbar Buttons, drag the Pose Stand button out to your toolbar, and make sure it's not “on.”

You can control the MoveLock behavior in Firestorm 4.6.5 and newer via Preferences→ Move & View→ Movement:

• Always re-lock position after region changes > When enabled, MoveLock is disabled during teleport, then re-enabled it after you arrive. When disabled, MoveLock is not re-enabled after a teleport
• Lock and unlock position after stopping or starting movement > When enabled, MoveLock is temporarily disabled when you manually move your avatar, and re-enabled when you stop moving. When disabled, you will be unable to move your avatar while MoveLock is enabled.

Also in Preferences→ Firestorm→ Extras, at the bottom, is Enable LSL-Client Bridge. This must be enabled in order to use MoveLock.

If, after a failed region crossing on a vehicle, you find yourself unsat from the vehicle, and able to walk forward/backward, but unable to turn left or right after stopping animations then recreate the bridge: top menu, Avatar → Avatar health → Recreate LSL Bridge.

• Tap your PageDn key and see if the animation stops. If it does, you were in crouch.
• Try Avatar menu → Avatar Health → Stop Animations & Revoke Permissions.
• Try right clicking your avatar → Reset Skeleton & Animations.
• If the above items did not work, go to a different region and try them again.
• If you have the animation in your inventory, play it from inventory, then click Stop.
• Remove attachments one by one until the animation stops. (This will eliminate worn items as a cause.)
  • Note: Animations can be in ANY attachment. Please don't assume that any particular attachment is not the problem. Take them all off.
  • Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Make sure the Firestorm AO is off:
  • On the AO button on your toolbar, untick the checkbox.
  • Note: The Firestorm AO can be active even if the button is not on your toolbar. If it is not on your toolbar, go to Avatar menu → Toolbar Buttons, drag the AO button out onto your toolbar, and make sure it is not ticked.

• If you know that a “sittable” item gave you the animation:
  1. Go to Preferences → Firestorm → Protection → Revoke Permissions.
  2. Temporarily set this to “Revoke on Sit and Stand.”
  3. Sit on the item, then stand. This should stop the animation.
  4. Change Preferences → Firestorm → Protection → Revoke Permissions back to either “Never” or “Revoke on Stand.”

• Try Advanced menu → Release keys. (After doing this, you will need to recreate the FS bridge: Avatar → Avatar health → Recreate LSL Bridge.)

• You may simply be experiencing lag: See Troubleshooting Lag for tips to reduce this.
• Many pose balls will request permission to animate you. If you did not see the animation request, look in your Notifications window for the message. Click “Accept.”
• Make sure you have not blocked the item or its owner: Look in Comm menu → Block List, see if the item or the item's owner is there, and remove the item/person from the block list.
• Go to Preferences → Firestorm → Protection → Revoke Permissions. For normal use, this should be set to either “Normal” (no protection) or “Revoke on Stand.” It should normally NOT be set to “Revoke on Sit” or “Revoke on Sit and Stand,” as both of these will prevent items from animating you when you are sitting.

Remove all attachments, then add one by one, testing in between to see if one causes the problem.

The TMP “Legacy” body HUD is known to cause this problem. Turn off the cam control located on the HUD.

“Rubber-banding” is when you try to walk forward and then suddenly snap back to a previous position. Sometimes you will seem unable to stop walking. This is caused by region lag, when the server can't keep up with processing avatar movement (collisions).

• For info about region lag see here: Region Lag
• For some things that region or parcel owners can do to reduce region lag see here: Reducing Server Lag.

This typically happens when you have two or more conflicting AOs (animation overriders) on.

• Start by removing known AOs until you are wearing only one known AO.
• If that doesn't help, start by removing other HUDs, then all other attachments, one by one, until it stops. Any worn item can contain an animation, so don't assume that some items are “ok.”
• Note: Attachments are anything with a box icon. Look in Inventory → Current Outfit folder to see all your attachments.

• Try turning the opposite direction to the spin.
• Try pressing BOTH right and left arrow keys at the same time, repeatedly.
• Relog.

• Remove other attachments that contain animations.
• Remove or turn off ankle-locks.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

This is a possible bridge problem: recreate bridge by going to Avatar menu → Avatar Health → Recreate LSL Bridge.

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

Go to Preferences → Privacy → Lookat, and tick “Don't send any look at targets at all, even to myself”

• In most cases, pressing Ctrl-R to toggle run mode will get you back into walk (though it may in some cases be necessary to hit Ctrl-R more than once).
• If you are wearing a scripted AO (animation overrider), turn off any “running” features it has.
• If you are using the Firestorm built-in AO (animation overrider), make sure there are no running animations in the “Walking” or “Standing” categories.

Ref. BUG-6825

In one specific case, the above will not work. Specifically:

• You have Preferences → Move & View → Movement → Tap-tap-hold to run enabled.
• Press shift, then tap-tap-hold the left or right arrow key

That gets you running sideways. If you release shift before the arrow key, you will be stuck running.

To stop running, you have to repeat the sequence: press shift, then tap-tap-hold left or right arrow.

• Go to Preferences → Sound & Media → Voice, and deselect “Move Avatar Lips When Speaking.” Note: This is the only viewer feature that affects lip movement.
• If you are wearing a mesh head, turn off any animations in the head. For more help, ask the support group for that head.
• Go to Comm menu → Gestures. Tick “Active only” at the bottom of the window. Review the list for any gestures that might contain a face animation. If in doubt, turn them all off, one at a time, to find the one responsible for the lip movement.

This is a known SL bug also affecting the SL viewer. Refer to this SL bug report for more information.

This happens if you turn off this setting: Preferences → Chat → Typing → “Play typing animation when chatting.”

* To stop the head-bobbing, go to Preferences → Chat → Visuals, and disable “Play avatar animations (such as shouting).”

Note: If you can't get your avatar to stop typing, see Turning Off Typing.

There are some known issues with the Firestorm bridge:

• If you log in and find yourself wearing a rock, detach it from yourself. To do this:
  • Go to Preferences→ Firestorm → Extras and disable the bridge
  • open top menu → Advanced → Debug Settings, and type in: ProtectBridgeFolder; set to FALSE, close the Debug Settings window.
  • open the #Firestorm folder in your inventory, and in that, the #LSL Bridge folder
  • detach the #Firestorm LSL Bridge, then delete it
  • search your inventory for any other copies of the bridge and delete them all, including any links to bridges
  • empty your trash
  • relog
  • re-enable ProtectBridgeFolder
  • re-enable the bridge
  • generate a new one bridge: use the top menu bar, go to Avatar → Avatar Health → Recreate LSL Bridge.

• If you have the bridge recreating on each log in or each TP, this is likely related to your connection. So, please make sure your bandwidth is set correctly, per this page - and please follow the steps exactly.
  If you need to get rid of excess bridges that may have accumulated due to this frequent recreation, proceed as above.

• If the bridge won't create, check to make sure that your inventory is fully loaded–specifically, the Library folder. The bridge uses an item from the Library, so if the Library is not loaded, bridge creation could fail.
  • If the Library will not load, and you cannot find the item “Rock - medium, round” in the Landscaping folder, clear your Library cache file per this page: how to clear cache.

• If you find that your hair suddenly appears to be attached to a place other than your head, even after a relog, then proceed as described above.

• Attempting to wear the bridge manually while it is being created can “break” it. When bridge creation begins, you will see a message in local chat; when creation is complete, you will see another message. During this period, do not attempt to do anything with the bridge; allow it to finish.

• If you use another viewer after Firestorm, the Firestorm bridge will display a message to local chat. It should, however, recognize that a different viewer is being used, and not repeat this message again. Should it happen that the message repeats, simply detach the bridge while in the other viewer.

• If you are wearing a bridge from an older version of Firestorm, the bridge will (correctly) detach but a new one will not be made. To have a new one generated, use the top menu bar, go to Avatar → Avatar Health → Recreate LSL Bridge. This will “clean up” any old bridges and make a new one.

• If the bridge is persistently unable to finish recreating itself, even on script-enabled land, and you have already relogged and tried Avatar → Avatar Health → Recreate LSL Bridge several times, try clearing your inventory cache in Avatar → Preferences → Network & Files → Directories; click the “Clear Inventory Cache” button there and relog.

• If you see a message such as #Firestorm LSL Bridge v2.24 whispers: OpenCollar in local chat, then the bridge script was reset while it was worn. Make sure you are on script-enabled land, then on the top menu bar, go to Avatar → Avatar Health → Recreate LSL Bridge.

Note: this is a list of standard keyboard shortcuts for these menu functions. Your keyboard may differ.

Note: The Developer menu must be enabled for these key combos to work: use CTRL-Alt-Q to enable it.

Key = Key Sequence

This page refers to Day Cycles in the new Environmental Enhancement system, and does not apply to viewers 6.3.9 or older.

Currently, see SL Wiki: Day Cycles for all available information about creating day cycles.

Day cycles are composed of one or more sky settings, and a water setting.

The long key frame slider at the tops is used to split the day length into times of day, each of which would have its own sky. Thus for a “real” day cycle, you would have the sun low in the east at sunrise, at the zenith at noon, and low in the west at sunset. Further, it is possible to have different day cycles at different heights.

• Clone From: Copy a day cycle from one sky to another. Typically used to replicate, for example, the ground level settings to higher skies.
• Load from: Load a definition from an existing day cycle.
• Clear: Clear all the settings for the height/water you have selected.

Click on one of the buttons on the left to work with that specific sky or water.

To add or edit a time of day key frame, left click on the horizontal bar, either on an existing key frame, which is indicated with a small block, or in a new position.

• Add Sky: Creates a blank sky definition which you can edit.
• Load Sky: Loads a sky from a sky asset.
• Delete Sky: Removes the currently selected keyframe.

When working with water, the 3 buttons above change accordingly.

Rather than using existing sky or water definitions, you can also input the data directly into the day cycle windows. See the following sections for specifics:

• Sky Tabs
• Water Tab

To add a day cycle to your parcel, see here; to add it to a region, see here.

This refers to day cycles which have day and night of equal length (eg, 2hrs day, 2hrs night, or for those wanting RL day length, 12hrs day, 12hrs night).

If you wish to create a day cycle that is equivalent to the “legacy” day cycle, of 4 hours, divided as 3 hours of day, 1 hour of night, then see below.

For day cycles where day and night are of equal length, the default day cycle, pictured above, is already set up correctly, and nothing needs to be changed. The percentages are:

This is a special section for those who would like to create the old style of SL day cycle, meaning 3 hrs day, 1 hr night.

All of the day cycles supplied as assets in the SL Library are linear. That is, the days and nights are equal in length, 2hrs and 2hrs respectively. If you wish to replicate the “legacy” day/night cycle of 3 hrs day, 1 hr night, you will need to adjust as follows.

• Copy the default day cycle into your Settings folder, then edit it.
• The midnight and noon keyframes are correct at 0 and 50%, but all the rest have to be changed.
• Make a keyframe half-way between 0 and 25%; this will be your sunrise, 06:00/6AM. Delete the 25% keyframe.
• Make a keyframe half-way between 75% and 100%; this will be your sunset, 18:00/6PM. Delete the 75% keyframe.
• Make a keyframe half-way between 0%, midnight, and your sunrise; this will be 03:00/3AM.
• Make a keyframe half-way between your 06:00/6AM and your noon; this will be your 09:00/9AM.
• Make a keyframe half-way between your noon and your 18:00/6PM; this will be your 15:00/3PM.
• Make a keyframe half-way between your sunset and the end midnight; this will be 21:00/9PM.

Consult the table below for exact values. Sadly, there is currently no way to insert keyframes at exact value; you will have to eyeball it.

Many explanations taken from this SL wiki page.

This version of Firestorm has a bug in the AO code which will result in a crash in either of these situations:

• logging out with the AO floater (window) open.
• creating an AO set for the first time with this version of the viewer - if you already have one or more sets defined before updating, then you're fine.

There are two workarounds:

If you still have Firestorm 6.3.2 (or earlier) available:

1. Log in with Firestorm 6.3.2 (or earlier) which is available here
2. Open the Firestorm AO interface (the AO Toolbar button, at the bottom of your Firestorm window)
3. If you don't normally use the Firestorm AO, delete all AO sets that are defined
4. Otherwise, make sure that exactly one of your AO sets is marked as “Default”
5. Close the AO window before logging out.

1. Log in with the Linden Lab Second Life viewer (other viewers may also work for this)
2. Open your Inventory
3. Navigate to your #Firestorm folder
4. Open the #AO folder inside there
5. If there are any empty folders under #AO, delete them
6. If there are no folders left under #AO, you can stop here
7. Otherwise, check if there is exactly one folder under #AO that ends in :** (for example, Female AO:**). This sets that folder as your default AO set.
8. If not, add the :** to the AO set that you normally use
9. Close the AO window before logging out.

After this, you should be able to log in with 6.3.9 once again.