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

• 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, 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 page explains some of the more common reasons for log in failure, and what you can do about it. For information on other kinds of log in problems, refer to this page and this page.

NOTE: Before doing anything else, check the Second Life Grid Status page to see if there are any known issues reported. If so, that might explain the issues you are having.

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:

First, make sure your drivers are fully updated

• Visit Intel and try to update your drivers there.
• An additional resource for certain Intel graphics is this Microsoft list of drivers for Intel(R) HD Graphics.

If this does not help, then refer to our fix for outdated Intel graphics.

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

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).
• If you found a solution or explanation, please let us know that too.

Thanks!

Index Général

• Téléchargements
• Firestorm Release Notes

• Information de base pour obtenir de l'aide
• Diagnostic et solutions rapides
• Comment déposer un JIRA
• Comment contacter le Support

• Ecran d'accueil
• Modes du viewer
• Mise en page du viewer

• Chat
• Inventaire
• Profils
• Tenues vestimentaires
• Gestures
• Mouselook
• Modifier les shapes ou autres parties du corps
• Bouton Personnes on peut accéder à “Près de Vous” (Radar), “Mes Amis” et “Mes groupes” à partir d'ici
• Utiliser la Recherche
• Managing Groups
• Diffusion Audio et Video
• Voix

• Sauvegarder ses paramètres
• Préférences
• Quick Preferences
• Le Cache - Ce que c'est
• Raccourcis clavier

• Paramètres de Complexité de l'avatar
• Préréglages graphiques personnalisés

• Effets physiques de l'avatar
• AO intégré
• Le Bridge LSL
• Windlight
• Debug Settings
• Comprendre le lag
• Phototools

• Informations de base pour obtenir de l'aide
• How to Contact Support

• Firestorm In-World Groups
• Firestorm Classes
• Phoenix Hour Archive

• Firestorm Preview Interface Customization Tutorial Vid

The following videos are about the Firestorm AO:

• Import to AO part 1
• Customize your AO part 2
• Options in AO part 3

• Firestorm Licenses
• Firestorm Privacy Policy
• Firestorm Credits
• Firestorm Source repository
• Main website

App Nap is a function introduced in Mavericks that allows a program not in focus to use fewer resources. On Yosemite, this function causes a fullscreen FS to time out, forcing a disconnect. You an solve this by disabling App Nap, as follows:

• Open the Finder (click on the blue happy face on the Dock) and navigate to your Applications folder.
• Select the Firestorm application and ctrl + click the icon and select Get Info. This brings up a separate pop up window that details everything about that particular application.
• In the General section of the window, after the details of the application itself, there are two check boxes: Prevent App Nap and Locked. Enable Prevent App Nap and close the window.

More info on what App Nap does can be found here.

If you are using Firestorm 4.7.1 on Yosemite, and have an nVidia graphics card, you are likely experiencing this issue. It appears that Apple decided to include an older version of the graphics card driver for this release.

No solution is available as of the time this was written; please refer to the JIRA linked above for the most current information.

So you find yourself suddenly missing a window, perhaps inventory, or chat, or the edit window… How to find it?

• Close all other windows, to make sure it isn't hiding under one of them.

• Hide the chat bar: Preferences→ Chat -> Typing→ Autohide main chatbar, and see if the window is under there.

• Compress all the buttons on the bottom toolbar to the right.
  Alternately, drag the toolbar buttons from their present location onto another toolbar;
  (Reminder: there are three available toolbars: bottom of the screen, right side, and left side. Buttons are dragged by left clicking, holding the left mouse button down, and dragging.)

• Go to Preferences→ User Interface → 2D Overlay, and lower the UI Scaling slider. The default setting is 1.0. You may find that setting it lower, temporarily, will reveal the missing window. If you find the missing window, move it to the center of the screen, then reset UI Scaling to 1.0 or your preferred value.

• Reset the window's position via Debug Settings. To do this,
  1. Try to ensure that the missing window is closed. (You many be able to tell this if you are using a toolbar button and it is highlighted or not.) If you can't tell, proceed anyway.
  2. Then open the Advanced menu (press Ctrl-Alt-D to enable Advanced, if it isn't already), and go to Show Debug Settings.
  3. Consult the table below for the names of the two settings that match your missing window.
  4. Find the first setting in the Debug Settings window; set it to 0 (zero).
  5. Repeat for the second setting.
  6. Relog.

• If you already have created a backup of your settings, then try a restore of those settings as explained here.

Should none of these work, then you will have to wipe settings, as explained on this page.

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

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

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

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

• English file: http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/file/57e32bf64851/indra/newview/skins/default/xui/en/floater_mem_leaking.xml
• Localized file: http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/file/57e32bf64851/indra/newview/skins/default/xui/pl/floater_mem_leaking.xml

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

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

• List of Polish ones: http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/file/tip/indra/newview/skins/default/xui/pl/
• List of German ones: http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/file/tip/indra/newview/skins/default/xui/de/
• and so on.

Changes from version to version (release to release) are usually not very drastic ones (http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/log?rev=translation+update), but the initial amount of workload can take around 2-3 weeks of 6-7 hours of constant work. Maintaining already created translation is not that hard.

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

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

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

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

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

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

Modern mesh bodies and heads often use a lot of smaller pieces to make up the whole item, so parts can be hidden under clothing. Sometimes the rigging information for one or more of these pieces gets corrupted during download and stuck in the viewer's cache. Currently, the best way to fix this issue is to clear cache.

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.

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 dullahan_host.exe.
• Relog and attempt video playback again
• If it works, you will need to stop your firewall/virus protection from blocking the slplugin and/or dullahan_host.exe 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 dullahan_host.exe for each one.
• If all of the above does not resolve the issue, you can try downloading the latest SL Viewer and replacing your Firestorm slplugin file with the one from SL Viewer.

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

1) Check viewer settings

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

2) Check your audio drivers

• Look in Help menu → About Firestorm for the line that begins with “Audio Driver Version.” If that line says “Undefined,” reboot your computer and see if the Audio Driver Version appears.
• If this doesn't help:
  • Go into Windows device manager (https://support.microsoft.com/en-us/instantanswers/005a1acb-776e-4320-b9f2-3a2302a320da/open-device-manager) & see if there is a yellow triangle warning symbol against your Sound devices (or your display adapters).
  • Also make sure your sound card driver is up to date.
  • Reinstall your graphics driver; the drivers also include audio components.

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.

Terraforming allows you to edit the terrain of a parcel or region, assuming you have the rights to do so. You will have rights if you own the region; you may have rights if you own or rent a parcel.

When in this mode, your pointer turns into a bulldozer, over a grid. The grid size indicates how much of an area will be affected by your terraforming. You can change the size and the strength of the bulldozer tool by using the sliders under Bulldozer on the window.

There are several terraforming modes available:

• Select Land: If you click this, you can then drag a selection on the land, and then apply terrain changes within the selection.
  to do that, after having selected the land to modify, click on one of the effects below, then on the Apply button. You can click this repeatedly.
  If you do not use a selection, then the effects below will be applied dynamically as you move the tool over the land.
• Flatten: Flattens the area of land. If you are editing manually, the starting point will be used, and all land you pass the tool over will be brought to that height.
• Raise: Raises the land under the bulldozer tool grid.
• Lower: Lowers the land under the tool.
• Smooth: Smooths elevation changes to make the land more even.
• Roughen: Creates uneven bumps in the land.
• Revert: Undoes terraforming based on the last terrain bake.
• Apply: Use this button to apply your edit option to the whole selected area.

This section gives information about the current parcel.

• Area: Displays the area of the current parcel, in sqm.
• Price: Shows the currently selected parcel's price - if it is for sale.
• About Land (button): Opens a window showing information about the current parcel.
• ShowOwners: Highlights land parcels in different colors depending on who owns them:
  • Green - Your land.
  • Aqua - Land owned by a group you're a member of.
  • Purple - Land in the auction system.
  • Red - Owned by others.

The operations here require the use of the Select land function described above. You will need to select an area of land before using either of them.

• Subdivide: Splits off the currently selected area of land into a new parcel.
• Join: Joins two parcels into a single parcel. To select more than one parcel, drag the selection box until it partially overlaps both (it's not necessary to completely select both parcels). The resultant parcel will acquire the properties (name, description, etc) from the last parcel selected during dragging.

Functions concerning the purchase and sale of land:

• Buy Land: Click this to buy the current parcel - if it is for sale.
• Abandon land: Abandon the currently selected parcel if you don't want it anymore and don't wish to sell it. Most people would rather not do this.

The mini-map gives you an overview of the region in which you are located. It shows the region and people and objects in it.

You can use your mouse scroll wheel to zoom in and out. Press and hold shift, then left click to pan the view around. If you click and drag the lower right corner, you can resize it.

The mouse cursor is a small cross hair, superimposed on a circle. The color, opacity and size of this circle can be changed, in Preference→ Colors -> Minimap→ Pick Radius.

The mini map contains color coded symbols, as follows:

• Yellow dot in the center: That's you!
• Cone of light: This comes from the yellow dot; it shows which direction you're facing and your field of vision.
• Yellow dots: Yellow dots represent nearby friends.
• Grey dots: Grey dots represents residents that you have blocked/muted.
• Blue dots: Blue dots represents Linden residents.
• Green dots: Green dots represent other Residents of Second Life

NOTE: the colors of these dots may be changed in Preferences → Colors -> Minimap.

Avatar dots change shape depending on their height relative to yours:

• Round dot: An avatar at about the same height as your camera viewpoint; for example, if you're standing next to them.
• ^ - An avatar above your camera position. They may be flying, or in a very high building.
• v - An avatar below your camera position. This may also show if the avatar is over 1,000m.
• ǂ - Height over 1020m and that does not have a viewer object representation, usually meaning out of draw distance.

• Dark gray blocks: These are objects owned by others.
• Cyan blocks: These are objects you own in the area.
• Fuchsia blocks: These are objects deeded to (owned by) a group you're in.
• Pale Orange blocks: Scripted objects.
• Dark orange: Temp on rez objects.
• Red blocks: Physical objects.
• Tiled dark blue: These are areas beyond your vision. You can see them by moving closer, or increase your draw distance in the Graphics tab of the Preferences window.
• Red areas: The Mini-Map turns red if the Region is offline or your viewer has lost its connection.

Some of the above are not enabled by default. Right click the mini map, and enable as desired in the Show sub-menu.

If you mouse over an avatar symbol, you will get a hover tip showing the avatar's name and distance from you. Clicking the orange (i) allows you to view their profile.

Right clicking on the map opens a menu:

• Zoom Close/Medium/Far/Default: A quick way to change the map zoom level.
• Show: Shows a list of what you want to show on the minimap.
• Rotate Map: Enabling this makes the map rotate, keeping your field of view directed upward. Otherwise, the map will be oriented North, and your field of view will change on the map as you move and turn.
• Auto Center: If enabled, the minimap will keep your avatar at the cenetr of the window.
• Chat Distance Ring: If enabled, draws rings showing your change range limit (20m) and shout range limit (100m).
• Place Profile: Opens the place profile window, showing infomation about the parcel.
• World Map: Opens the world map for the region.

If you right click on an avatar, the menu will have more options:

• Profile: Opens the person's profile. (Versions after 3.2.2 only.)
• Cam: Allows you to cam on the avatar - assuming parcel privacy allows it. (Parcel privacy is set in About Land→ Options)
• Mark: Allows you to color the specific avatar's dot differently.
• More options:
  • Add Friend: Offers friendship.
  • Add to Set: adds the person to a contact set.
  • Remove Friend: Remove the person from your friends list (if they are a friend).
  • IM: Start an IM conversation
  • Call: Initiates a voice call
  • Map: Shows the eprson on the world map, if they have granted you map rights.
  • Share: Allows you to share inventory items with the person.
  • Pay: Opens a pay window, so you can pay L$.
  • Offer teleport: Sends a teleport invite.
  • Request teleport: Sends a message asking that the person send you a teleport.
  • Teleport To: Directly teleport to the person.
  • Invite to Group: Allows you to send a group invitation.
  • Get Script Info: Gets information on the running scripts the person is wearing.
  • Block/Unblock: Blocks (mutes) the person - or reverses this.
  • Report: Opens the Abuse Report window.
  • Derender: Temporarily Derenders the person.
  • Derender + Blacklist: Permanent derender.
• Start Tracking: Enables tracking avatars by drawing a beacon.
• Stop Tracking: If you have a red beacon active, this will clear it.

Second Life Release Viewer version 6.0.0.518949
Release Notes for v6.0.0 (518949) - Second Life Viewer Released on August 24, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/6.0.0.518949

Animesh is a new feature under development by Linden Lab that allows non-avatar objects to play animations like avatars do today.
Blog Posting

See the Animesh User Guide for details on how to get started with animesh.

You can discuss it with other interested residents at the Animesh Forum.

You can also join the Content Creation User Group most Thursdays for public meetings.

Animesh Test Item Vendor 1.0 available for free on Aditi
secondlife://util.aditi.lindenlab.com/secondlife/Animesh4/128/128/23

This page covers the Features tab of the toolbox window in Edit and Build modes. This tab is shown in the image to the right. The upper section of this window is described here.

In Edit mode, some fields will be unavailable if the object is not modifyable.

NOTE: The term “Object” is used to refer to a single unlinked prim, or to a linked set of prims.
Most of the settings below can only be applied to individual prims; they will be disabled if you are editing a linked set.
Note that the overall properties of a linked set are the same as the properties of the root prim.

There are several groups of settings here, mostly unrelated to one another.

Applicable to boxes, cylinders and prism types, this makes the prim flexible (usually known as a flexi prim). Such prims are usually path cut and hollowed. Flexible prims are commonly used in clothing attachments like capes, for flags and other wavy things. Flexible prims are automatically made phantom.

Flexible prim characteristics are as follows:

• Softness: Controls the stiffness of the prim on a scale of 0 to 3, where 0 is the most stiff and 3 is the most soft.
• Gravity: Controls how hard gravity pulls down on the prim. If you enter a negative value, gravity pulls the object upward instead.
• Drag: Controls how much drag the atmosphere appears to exert on the prim when it's moved.
• Wind: Controls how much this prim bends in response to the current region's wind.
• Tension: Controls how much force is pulling the top of the prim away from its base.
• Force X/Y/Z: Controls how much artificial force is applied on the prim, from different directions.

• Physics Shape Type: Physics Shape type selects between different “physical” representations of the object. The physical representation is different to the visual representation. The latter is (perhaps obviously) what you see, whereas the physics shape is what you collide with. It is important in determining whether you walk through, around or over an item, and importantly, it pays a very key role in determining where an item drop/dragged into the viewer will actually be placed.
  There are 3 possible options, but not all are available to all objects and in some cases cannot be used in certain circumstances.
  • None: Physics type None is only available for child prims of a linkset. It disables the physics processing for these prims and crucially, removes their physics cost (see later) from the LI calculation.
  • Convex hull: A convex hull is a mathematical term, stop wait…come back…., seriously, it's ok. It just means “the shape I get if I cover this object in plastic wrap”. The convex hull is, therefore, an approximation of the shape of an object. It does not support holes on objects and a wall containing a doorway with a convex hull physics shape will not let you pass through. The plastic wrap analogy holds good for pretty much all such examples. Convex hull is available for all objects but can force a prim to cost more than 1LI. This is the default for Mesh.
  • Prim: This is without the doubt the most confusing name in the list. The “prim” physics shape is generally only seen on Meshes. It actually tells the region to use the objects custom physics shape, a dedicated shape that the creator of the object decided was a good and appropriate shape for the object. A “prim physics” shape allows the creator to specify exactly which parts of an object you can collide with and which parts you walk through, allowing them, for example, to open up doorways but keep windows impassable, if they so choose. Unfortunately, many creators are neglectful in this selection and the prim physics shape is often not very useful. The reason for the name is clearer when considering that this is the default mode for traditional prims and reflects a physical shape that matches the visible shape of the prim closely.
• Material: (Only applies when the object is physical.) The notional real-life material that behaves most like this object. It affects the friction and bounce of an object in collisions, as well as the default sounds made. *Important: This has nothing whatsoever to do with the texturing “materials”.
• Gravity: (Only applies when the object is physical.) Affects the way that an object interacts, 1.0 is earth standard gravity (i.e. 1g) a negative value will cause a physical object to rise.
• Friction:
• Density:
• Bounciness: (Only applies when the object is physical.) These three override the defaults implied by the “Material”.

To the right of Physics Shape Type is an eye icon. Clicking this switches in and out of physics view. Physics view will show the object's physics shape in a colour that reflects the physics cost.
The physics cost is not normally used for prims, but becomes important if a prim is linked to a mesh, or has any modern feature such as a bump map applied to it. A low physics cost will be a passive blue, moving through a worrying orange to an angry red. If you plan to link a prim to a mesh or use any other modern feature it is worth checking this quickly to avoid your Land Impact (LI) from sky rocketing. See this blog post for more details.

Cause the prim to emit light. In order to be able to see the light, you need to have Preferences→ Graphics → General→ Local Lights enabled.

• Color: Click this to open a color picker, from which you can select the light color.
• Intensity: Sets the initial brightness of the prim; the possible values are between 0 and 1.
• Radius: Specifies how far the light travels, in meters. The maximum is 20m.
• Falloff: Sets how quickly the light's Intensity fades as it travels to its outer Radius. Lower values are more gradual.

For general information on projectors, please refer to this SL page.

When you have Advanced Lighting Model enabled (in Preferences→ Graphics, then you can make use of projectors. In the Features tab of the edit window, you will see additional fields in the lower right.

• Texture: This is the texture to project. Clicking it will open the Texture Picker.
• FOV: The FOV setting defines the field of view of the projector, in radians. The field of view is the angular width of the cone of light projected. The possible range of values from 0.0 to 3.0 correspond to widths from 0 degrees to approx 172 degrees (almost a hemisphere of influence). Fidelity of shadows caused by a projector may degrade as the FOV becomes larger.
• Focus: A projected texture appears blurrier the further the projection point is from the projector. The Focus value controls how attenuated this effect is. Positive values keep the projection sharper for farther distances, negative values make the projection start to blur at a closer range.
• Ambiance: Ambiance adds a very blurred version of the projected image to all faces within the cone of influence, regardless of whether they are in shadow or facing away from the projector. The goal is to roughly simulate light influence being diffused in all directions by surfaces receiving a projected image. Thus it is acceptable that this be even brighter on faces facing away from the projector. The brightness of this effect is proportional to the Ambiance value.

This tab controls permissions and restrictions on the parcel for users other than the owner. Generally the parcel owner keeps full abilities on the parcel.

• Edit Terrain: If enabled, this grants the ability to any other resident to edit the terrain in the parcel. Do not grant lightly!

• Fly: Allow residents on the land to fly, if unchecked residents will notice their “fly” button has been disabled.

• Create Objects, Object Entry, Run Scripts: These permissions are divided into “All Residents”, and “Group”, which refers to the group set on the General tab. Object Entry refers to objects not attached to an avatar, such as a bullet fired from a gun. Run Scripts refers to all scripts, whether in attached or detached objects.

• Safe (no damage): If checked, disables combat ¹⁾.

• No Pushing: If checked, then pushes from objects is disabled. Pushing another avatar is often used to annoy them, and most regions have turned on this item to prevent it.

• Show Place in Search: If checked, the parcel will be listed in the Search window with the name and description from the General tab, and the snapshot below from this tab. A fee of L$30 per week is charged for listing in search, and optionally a category can be chosen from the dropdown menu on this item.

• Allow Residents on other parcels to - See and chat with residents on this parcel: If enabled, people outside the parcel will be able to see and chat with those inside the parcel; if disabled, anyone in the parcel will be invisible to those outside, no matter how close they may be.

• Moderate Content: This is the parcel rating.

• Category: Select the category of parcel from the drop-down.

• Snapshot: This image will be displayed in the “Search” results and landmarks created for the parcel. Clicking the image area will open the “Pick: Texture” floating window so that you can choose the image to display. Alternately, your chosen image can be dragged from your inventory to the image area.

• Landing Point: Lists the coordinates of the landing point if set, or (none) if not set. The set button will set the landing point to your current avatar position, and the clear button will unset it.

• Teleport Routing: Determines where teleport landings are allowed for other users. Blocked means that teleports into the parcel are not allowed, and avatars will land outside the parcel; Landing point indicates that teleports are limited to the landing point set above; Anywhere means that teleports may arrive at any location on the parcel.

• 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

• AliciaFlanagan1
• annailisa (German)
• Ardwenia (French, Portuguese)
• Avalon Bouvier
• ChuckPC
• Cypherofme
• ErikLuc
• Fayleen Bellios
• FrankASinatra
• Ganaelle Aabye (French)
• Gokyu Ugajin
• ImaLuckygirl
• JadeWindsong
• Jolie Serendipity
• kobayashiMaroo
• Liliana Darwinian (Portuguese)
• LosAngelesGraff
• MacMaccee (German, English)
• MarcSeven Lubitsch
• Mari Teardrop
• SayreAvondale
• Scarlet Vavoom
• Scuzzy Usbourne
• Sedona Bluemood
• Silver Frakture (German)
• Sniper Siemens
• Sparkle Weatherwax
• Talula Shippe
• 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

Submitted: %G-%m-%d

User name: @@User name@@
URI: @@Your account URI@@
Skype: @@Skype handle@@
Email: @@Email@@

Give an example of a problem where you might suggest that the user clear cache.
@@Give an example of a problem where you might suggest that the user clear cache.@@

Give an example of a problem where a cache wipe would not help solve the problem.
@@Give an example of a problem where a cache wipe would not help solve the problem.@@

Give an example of a problem where you might suggest that the user reinstall the viewer.
@@Give an example of a problem where you might suggest that the user reinstall the viewer.@@

Give an example of a problem where a reinstall would not help solve the problem.
@@Give an example of a problem where a reinstall would not help solve the problem.@@

If a user finds him/herself unable to walk or move, what would be the first thing you would suggest be checked?
@@If a user finds him/herself unable to walk or move, what would be the first thing you would suggest be checked?@@

How do you change your display name?
@@How do you change your display name?@@

Does high complexity cause region lag?
@@Does high complexity cause region lag?@@

What is the highest value LOD you should use in normal situations?
@@What is the highest value LOD you should use in normal situations?@@

What is the range of normal chat?
@@What is the range of normal chat?@@

If you cannot see an item you have rezzed out, how would you go about finding it?
@@If you cannot see an item you have rezzed out, how would you go about finding it?@@

What do you feel is the best way to handle each of the following types of challenging group members? * Someone who spams the group with an ad?
@@Someone who spams the group with an ad?@@ * Someone (not a support team member) who answers a support question with bad advice or wrong information?
@@Someone (not a support team member) who answers a support question with bad advice or wrong information?@@ * Someone who pastes a malicious link into group chat?
@@Someone who pastes a malicious link into group chat?@@ * Someone seeking help who responds to your followup questions and suggestions in an aggressive and defensive manner?
@@Someone seeking help who responds to your followup questions and suggestions in an aggressive and defensive manner?@@ * Someone seeking help who is polite but doesn't understand your suggestions?
@@Someone seeking help who is polite but doesn't understand your suggestions?@@ Describe some things about Firestorm support group chats that work well or don't work well – either things personally involving you or things you have observed.
@@Describe some things about Firestorm support group chats that work well or don't work well – either things personally involving you or things you have observed.@@ Have you helped out in a Firestorm support group? What kinds of questions have you answered, or what kind of help have you given?
@@Have you helped out in a Firestorm support group? What kinds of questions have you answered, or what kind of help have you given?@@ How well do you respond to criticism?
@@How well do you respond to criticism?@@ Describe a time when you had to admit to one or more people that you were wrong about something. How did you feeling while doing it? How did it work out? Would you be comfortable doing that in a public context?
@@Describe a time when you had to admit to one or more people that you were wrong about something. How did you feeling while doing it? How did it work out? Would you be comfortable doing that in a public context?@@ ==== About You ==== Why do you want to be on the support team?
@@Why do you want to be on the support team?@@ Name three places in SL that 'wow' you.
@@Name three places in SL that 'wow' you.@@ What special interests do you have in SL (ie: building, designing clothes, photography,etc)?
@@What special interests do you have in SL (ie: building, designing clothes, photography,etc)?@@ What frustrates you most about Second Life?
@@What frustrates you most about Second Life?@@ What do you like most about Second Life?
@@What do you like most about Second Life?@@ What is your timezone?
@@What is your timezone?@@ What languages do you speak/write?
@@What languages do you speak/write?@@ How long have you been in SL (on any account)?
@@How long have you been in SL (on any account)?@@ How long have you been using Firestorm?**
@@How long have you been using Firestorm?@@

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.

Version 5.1.7., voice crashes when turning on microphone. See BUG-225293 and FIRE-22940
Fixed on LL Viewer. Fix pending on FS viewer.
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.

• 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, 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.)

Firestorm 5.1.7 (55786) Release Notes

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

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

• SLURLs not working in your browser, or choose to open with a different viewer (Windows)
  • SLURL Proxy.zip
  • Instructions are included, but can also be seen on the Wiki at slurl_proxy

Firestorm 5.1.7, 5.0.11, 5.0.7, 5.0.1 Release

• Windows - Download in Firefox or Chrome to play Flash media inside Second Life.
  Choose the correct operating system under Step 1.
  Choose FP 30 for Opera & Chromium - PPAPI under Step 2.
  Install Flash.

• Mac - Ensure that you have the most recent version of Flash for Safari installed. You an get this via the normal update process, or from Adobe.
  Choose the correct operating system under Step 1.
  Choose FP 30 for Safari and Firefox – NPAPI under Step 2.
  Install Flash.

• Linux - You need to have the pepperflash plugin installed, which can be satisfied by installing Google Chrome.

Firestorm 5.1.7, 5.0.11, 5.0.7, 5.0.1

• Windows - Quicktime does not need to be installed to play media on Firestorm 5.0.1 or later.

• Mac - Quicktime to play streaming videos. (iTunes is not needed)

for Linux only

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

Linux has this already

• Windows Download To get external notices about events when the viewer is minimized.
• Mac Download To get external notices about events when the viewer is minimized.

Windows only

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

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

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

• Latest driverLast checked 21/07/2018 - Windows: 398.36 (2018.6.26) - Linux: 390.77 (2018.7.16)

• Latest driverLast checked 21/07/2018 - Windows: Adrenalin Edition 18.5.1 (5/23/2018) - Linux: Linux Download Center
  

• Intel driver download page Intel does not have a universal driver set. Please go to Intel's site and use the auto detect feature.

https://hg.phoenixviewer.com/