To APPLY: Please send a notecard with your contact info (including login name), the position interested in and your qualifications to Teresa Firelight or Starwolff (Starwolff2000).

The Firestorm Gateway is trying to launch a 24×7 SciFi RolePlay (RP) area along with some Regularly Scheduled RP Events. We need staff* to make this happen. We currently have openings in the following areas:

• Callahan's Spiral Galaxy - a 24×7 Drop-in Roleplay SciFi Cantina/Bar. It is set on a Space Station's visitor area, where crews of docking ships can enjoy themselves. Side business of all kinds (legal and otherwise) can be conducted here.
• Space Station Crew RP - a 24×7 Roleplay area for those who would like to RP living/working on a Space Station. There are multiple decks, with the main RP deck being on Level 2 of the Tempus Space Station.
• Star Trek RP - These are “Missions” occurring at regularly scheduled times and take place on board USS Gateway, a Sovereign Class Starship. Current Scheduled times are: Fridays Noon SLT, Sundays 8 AM SLT, Sundays 6 PM SLT. We are looking for crew. Also, for those who have experience planning/running Trek-style missions, we are also looking for CO's/Mission Planners.
• LEADERSHIP Roles - We are looking for people who already have strong RP Leadership experience to take on leadership and organizational roles in each of the three areas listed above.

Please Note: These positions are RP and RP leadership, and won't automatically make you a member of Firestorm's Staff. However, those who are consistent/dependable and make significant contributions may be invited onto the Firestorm Team at a future time.

~~~~~~~~~~~~~~~~~~~ Open Positions ~~~~~~~~~~~~~~~~~~~~

Current available positions and qualifications are listed below. (However if you have an idea for something that is not listed, please feel free to contact Teresa and suggest it, as she is open to new ideas to help make the RP successful.)

Callahan's is looking for staff, such as bartenders, waitresses, the janitor, etc – these are RP positions and filling one will not automatically put you on the Firestorm Team.You will develop a character and come somewhat regularly as that character with the goal of helping to foster the RP. These positions require a commitment to frequent and hang out at the bar, and engage those who drop by in RP. You can also use the Firestorm Gateway Roleplay Group chat to invite folks to join you for RP.

Qualifications: Some experience in RP required, dependability (e.g., RP here frequently), newcomer friendly (e.g, welcoming/helpful towards new-to-SL and new-to-RP individuals).

Callahan's is looking for regular bar customers. This can include people who are stranded on the station, freighter crew looking for customers who need shipping (legal items or contraband), Captains/Crew of ships who frequent the station, etc. You will develop a character and come somewhat regularly as that character with the goal of helping to foster the RP. These positions require a commitment to frequent and hang out at the bar, and to engage those who drop by in RP. You can also use the Firestorm Gateway Roleplay Group chat to invite folks to join you for RP or for a game of Greedy or Poker, etc.

Qualifications: Some experience in RP required, dependability (e.g., RP here frequently), newcomer friendly (e.g, welcoming/helpful towards new-to-SL and new-to-RP individuals).

We are looking for people who want to be crew of the SS Tempus Space Station. This means that IC you live/work on the station. You can RP on any of the decks of the station (including Callahan's). Ideally you can also interact with the Callahan's guests: a doctor can treat injuries or give checkups, a security officer can interrogate customers of questionable character, an Engineer might assist a docked ship with repairs, etc. In addition, we hope to have regular Station RPs in addition to the DropIn RPs once we have a Station Commander.

Qualifications: Some experience in RP required, dependability (e.g., RP here frequently), newcomer friendly (e.g, welcoming/helpful towards new-to-SL and new-to-RP individuals).

This person will be responsible to assure that RP is happening somewhat regularly at Tempus Space Station. They will organize a weekly weekly RP for the crew, as well as some RP events or activities (themed RPs, training sessions, combat drills, etc). Also the Commander will be responsible to recruit new crew for the weekly scheduled RPs.

In addition, the Manager will be the first point of contact for SS Tempus Crew, assisting them with issues/concerns, giving advice when requested, etc.)

Qualifications: Requires experience in RP leadership, preferable in a 24×7 setting, and ability to plan missions and/or RP events. Requires good interpersonal skills, commitment/dependability, newcomer friendly (e.g, welcoming/helpful towards new-to-SL and new-to-RP individuals).

We are looking for people to be crew of the USS Gateway at one (or more) of her regularly scheduled RPs. Currently, RPs are scheduled for Noon SLT Fridays, 8 AM SLT Sundays and 6 PM SLT Sundays. We hope to add more regularly scheduled RPs. In addition, crew can do drop-in RP on the ship the whenever it is not in use for a mission.

We currently have openings in Engineering, Medical, OPs, Science, and Security. Free Uniforms are available on the supply deck. Crew members commit to RPing at one (or more) of the mission times on a regular basis.

Qualifications: Some experience in RP required, dependability (e.g., RP here regularly), newcomer friendly (e.g, welcoming/helpful towards new-to-SL and new-to-RP individuals). Some knowledge of Star Trek is helpful.

We are looking for people who can plan/lead a Trek RP session. You will plan and command weekly missions, announce them to multiple groups, welcome and help out any new-to-SL residents who come, etc.

Qualifications: This is a nontrivial job. it requires that you have experience planning and running Trek missions, that you are there like clockwork for every one of your scheduled missions, that you come 1/2 hour before mission start to send out notices about the mission to multiple groups and/or group chats. In addition, we strongly prefer that you have an existing small base of crew committed to attending your missions, so you can RP even if no new residents show up at the beginning of the RP. You must have good people skills and be newcomer-friendly. And, of course, you must have a fairly extensive familiarity and/or knowledge of Trek.

This person is responsible for helping establish 24×7 RP on the Firestorm Gateway. Their Primary focus will be on creating scheduled and drop-in RP on SS Tempus. This will include overseeing 24×7 RP activity and establishing some regularly scheduled events to draw people to the RP area.

Qualifications: This person must have solid experience in a 24×7 RP environment with some leadership experience in it. They must have good people skills, be newcomer friendly (e.g, welcoming/helpful towards new-to-SL and new-to-RP individuals), be very dependable, and be willing to have a near-daily presence at the RP area.

This person is responsible for getting the word out as widely as possible about the Firestorm Gateway RolePlay – including the general RP, any activities, special events, etc. Firestorm has a large group for new-to-SL residents, where they can send notices. There are some SciFi Groups that permit this type of announcement as well. Plus they should set up and maintain a standard Internet presence for the Firestorm Gateway's RolePlay (Blog, Facebook, twitter, etc).

Qualifications: A solid knowledge of standard Internet publicity mechanisms, an enthusiasm for promoting Firestorm Gateway's RP, good writing skills, and some experience in internet publicity.

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.

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.

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

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

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

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

You can also try adjusting your bandwidth as explained here.

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

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

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

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

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

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

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

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

• Try a relog, or even 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.

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

Some have issues with voice on Firestorm - specifically, “stuttering”, or SLVoice crashing when you unplug a USB device. The only work-around currently is to swap out the voice files.

• To this end, download this file; save it to your hard drive. Make sure you do not have Firestorm running. Then extract the files to your Firestorm install folder. (For Firestorm 32-bit viewer, this is typically located at C:\Program Files\Firestorm on 32 bit Windows, and C:\Program Files (x86)\Firestorm on Windows 64-bit. For Firestorm 64-bit Viewer, this is typically located at C:\Program Files\Firestorm.) When prompted, allow the replacement of existing files.

Try disabling compatibility mode, if enabled:

• Locate your desktop shortcut for Firestorm
• Right click on the icon and select Properties
• Select the Compatibility tab
• Find “Run this program in compatibility mode for:” if it is set then disable this
• Make sure “Run as Administrator” is enabled (if this is greyed out, then you're probably already running as administrator, so you can ignore this step).
• Click Apply.
• Now log back into the viewer, and see if voice works (do you have the white dot over your head?). If not, go to Preferences→ Sound & Media -> Voice and disable voice; wait a few moments, then re-enable. ¹⁾

On Windows 7, if you find yourself being able to talk but not hear what others say, then a possible solution is to use the sound drivers from Vista. (This needs further confirmation.)

Check that slvoice.exe is not muted in the speaker/headphones icon (located in the notification area) → mixer.

Every linux distro is different; and each distro may have more than one window manager to further complicate things. So tips can't be “absolute”; you will need to experiment and see what works for you. The following have been suggested by some as effective. But first….

In the Firestorm install directory, there's a text file (originally from LL) with tips on getting voice to work in linux. If you haven't read that, then you can try to see if it helps.

• Make sure you have ALSA and/or FMODEX available. FMODEX is supplied with Firestorm, normally. If you look at Help → About Firestorm, you should see a line that resembles this:
  Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.11.753 / OpenAL Community / OpenAL Soft: PulseAudio Software
  If that says “none” then you have no audio driver available to Firestorm and need to install one.

• Edit the firestorm shell script and remove the #. That will force LL to use FMOD rather than ALSA. Some say this is how to get voice working.

#export LL_BAD_OPENAL_DRIVER=x

• Some swear that the problem is PulseAudio, so you can try to remove that from your system. Be warned, however, that this could cause more problems than it solves. Make sure you remove only Pulse and not half the OS.
• Be sure to have the correct devices select in Firestorm for voice:
  
  Preferences → Sound & Media → Voice → Audio Device Settings (button) … input and output may not work if left at default; they may need to go to a specific device like “ALSA Capture on [device name]”.

Below are results for selected linux distros, based on input from Phoenix and Firestorm users. This will be updated as more information becomes available.

• ubuntu 16.04 64 bit + FS64: The following command installs a few 32-bit libs and voice works after. Maybe you need fewer 32-bit libs but that needs further investigation.
  Apparently, arch requires these as well - or some of them - though the exact lib name may be different.

sudo apt-get install gstreamer0.10-pulseaudio:i386 libidn11:i386 libuuid1:i386 libstdc++6:i386

• A new option in Firestorm 4.7.9 is a debug setting, FSLinuxEnableWin32VoiceProxy, which when enabled will cause Firestorm to launch the Windows version of SLVoice.exe via WINE. To use this, you need to ensure that WINE is installed; install WINE with your package manager. An existing WINE profile/prefix is not needed, but will be used if present. Depending on your system, it may take several seconds before voice comes up.
  NOTES:
  * If you disable voice and then re-enable too quickly, WINE may not successfully restart and voice may fail to re-enable. If you get the warning that there was a problem connecting, you will need to relog before voice will re-enable. Thirty seconds between disable and enable should be enough.
  * There is a known related issue here
  * To speed up the initial loading of voice, use

  wine-preloader $HOME/path/to/firestorm/bin/win32/SLVoice.exe

  before launching Firestorm

If you are unable to connect to voice and you are also having problems with teleporting and/or loading your friends list, perhaps along with other things, then see the “Mac-specific” section of this page for instructions and more explanation.

Some Mountain Lion users experience a problem with voice output, while input works fine (that is, you can hear but you can't speak). To fix this, open the voice preferences for your viewer (Preferences→ Sound & Media -> Voice in Firestorm). Click the device settings button and select “built-in microph” as the audio input device and click OK. Reopen Preferences and go back to the device settings button to ensure you're getting sound in on the mic.

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

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

Locations are indicated in the far right column as follows:

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

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

*All times SLT*

For instructions for Phoenix, please refer here.

Some anti-virus programs will incorrectly flag a viewer - or necessary components of a viewer - as a virus or threat. They may remove the suspected part completely, rendering all or part of the viewer non-functional. There is nothing we can do about this. However, it should be possible for you to tell your anti-virus that the viewer is safe; you will need to whitelist the viewer program as well as some components.

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

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

1. Uninstall the viewer normally.
2. Disable the anti-virus software completely (in a few cases, this requires rebooting to make sure that the AV is not running anymore).
3. Reinstall the viewer, but make sure you do not install it back to the default folder suggested; install to a new folder. This step is vital.
4. In your anti-virus program, whitelist the following, per the instructions below (or better, consult the manual for your anti-virus software):
   • the viewer install folder
     • inside this, the viewer itself (firestorm.exe), slplugin.exe, slvoice.exe and llceflib_host.exe (for FS 4.7.7 and later).
   • the viewer cache folder
     • In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Now you need to locate the cache folder:
       • Windows XP: C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Firestorm
       • Windows Vista/7/8/10: C:\Users\[USERNAME]\AppData\Local\Firestorm
       • Mac: /Users/[USERNAME]/Library/Caches/Firestorm
5. Run the viewer to ensure that it is working correctly; do a test of search and voice to ensure that both work, checking that the respective plugins get loaded. Log out of the viewer.
6. Re-enable your anti-virus software and run the viewer again, repeating the tests above.

• Open the Avast User Interface
• Click Real-time shields
• Click File system shield
• Click Expert Settings
• Click Exclusions
• Click Add
• Click Browse and navigate to the Firestorm install folder
• Click OK
• Repeat for the Firestorm cache folder
• Click OK all the way out

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

Please refer to this page.

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

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

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

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

In order to create an exclusion rule:

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

Rules can apply to the following protection components:

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

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

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

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

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

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

• Open Settings and in the search field at the top right enter defender
• Click the Windows Defender Settings option.
• Exclude the cache
  • Click Add an Exclusion
  • Click Exclude a folder
  • Click in the address bar and type %LOCALAPPDATA% and press Enter
  • Click the Firestorm folder
  • Click the Exclude this folder button
  • Repeat this if you have more than one Firestorm folder (64-bit and 32-bit, for example)
• Exclude the viewer executables
  • Click the Exclude a .exe, .com or .scr process button
  • Navigate to C:\Program Files\Firestorm-Release64
  • Click Firestorm-bin
  • Click the Exclude This file button
  • Repeat this for SLPlugin and SLVoice - and llceflib_host (for FS 4.7.7 and later).
  • Repeat this for 32-bit Firestorm ( C:\Program Files (x86) )

Add exclusion to Auto-Protect and Risk scan

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

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

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

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

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

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

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

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

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

For additional information:

• https://community.webroot.com/t5/Webroot-for-Business/how-to-set-file-and-folder-exclusions-in-the-webroot-console/td-p/189775
• https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/How-to-exclude-a-folder-from-being-scanned-in-the-latest-WSA-AV/td-p/78063

The events we advertise for, on the viewer Message of the Day are:

• not for profit, community events organized, hosted and/or sponsored by the community;
• charity events that benefit good causes.

The idea behind what we agree to advertise for and what we don't are simple. If it's going to benefit you financially either directly or indirectly (publicity stunt), we are not going to advertise it. However if it's purely for residents, hosted by residents with no profits or financial benefits either directly or indirectly to you or those involved, we will consider it. We have always been, and will always be, about the community.

We cannot however advertise religious events or anything that may offend or exclude other races, creeds, cultures or persons. For example, we were asked to promote Memorial Day, and while we support troops all around the world 100%, it is an American event which other countries do not participate in. That makes it exclusionary and not something that qualifies for us to promote.

If you have a community event that you would like promoted on our MOTD you can send a request to jessica.lyon@phoenixviewer.com for consideration. We do not charge for advertising nor will we accept any benefits, financial or otherwise. Though you can expect we may attend your event ;). Please provide your in-world name and details to the event. All events we advertise for are required to have a website we can link to.

Note: we do not promote anything on the login page itself. Just the Message of the day.

Coming soon!
Click here to apply for a Firestorm MotD

(Extracted from this blog post.)

The Firestorm viewer has a built-in AO (Animation Overrider). This makes the use of scripted AOs unnecessary, which in turn reduces the amount of scripts you wear, and so server-side lag.

The AO is accessed via a button on the bottom button bar.

The AO is activated by clicking the button labeled AO; it will show pressed down, as in the image above. To disable it, press the button again, and it will appear released.

To the right of this is an up arrow. Clicking that pops up a small window, the mini AO view, which gives quick and easy access to a few basic functions, such as moving from one stand animation to another, toggling sit overrides and loading a new set of animations. Clicking this same button again will close the window.

This small window has a screwdriver-wrench icon; clicking that opens the AO window to its largest size, allowing full control of the AO.

A brief glossary of terms as they are used here.

• AO: Animation Override or Animation Overrider. Generally, a scripted attachment worn as an HUD, containing animations and notecards which, along with the scripts, animate the avatars while it is in certain states, such as standing, walking, flying, etc. Absent an AO, the avatar will use basic default Linden-defined animations. The Firestorm client AO replaces the usual scripted AO by duplicating its functions, without the script overhead.
• Animation Set: The collection of animations which, taken together, make up any given AO.
• Animation Group: One or more animations which serve to replace a single animation state. Examples of animation groups include stands, sits, walks, etc. All of the animation groups, together, make up an animation set.

Basic functions of the AO can be accomplished via the mini AO view shown below.

• Currently loaded animation set: Referring to the image above, the currently loaded set is named “! Default”. By clicking the small down arrow, you can easily select another set (if others are available, of course).
• Screwdriver-Wrench icon expands the mini window to full size for greater control; see below for more.
• Left/Right Arrows switch to the previous and next animation in the current group, respectively.
• “Sit” checkbox indicates whether the AO should override sits animations that are part of scripted furniture. If this is enabled, the AO will try to force the use of whatever sit animation you have in the animation set ¹⁾ ; if disabled, then the animation in the furniture will be used.

For greater control over the AO, click the Screwdriver-Wrench icon; this will open the AO window to maximum size. It looks like this.

• The Current animation set is shown in the top drop-down. Clicking the down arrow beside it allows for the selection of an alternate animation set (if you have others available, of course). You can rename your AO set right here. Just click the name and change it to what you want it to be.
• The check mark to the right of the animation set name will activate the animation set. click this if you have picked a new one.
• Default: check this if you wish to make the current animation set the default when you start Firestorm.
• Override sits: Does the same thing as the Sits checkbox described above.
• Be Smart: If this is enabled, the AO will try to determine whether the furniture being sat on has an animation; if it determines that it does, it will disable the sit in the AO, so the one in the furniture will be used instead.
• Disable Stands in Mouselook: If this is checked, the AO will disable stand animations when mouselook is entered. This is useful for combat situations, for example.
• + Button: Click this button to manually define a new animation set.
• Trash: To delete the current animation set, click this button.
• Animation Group: With this drop down you can select an animation group, such as Standing, Walking, Running, etc. Having selected one, you can then change the order in which animations are played, by using ….
• Up/Down Arrows: moves the currently selected animation up or down in the list, thus changing the order in which the animations are played in the animation group.
• Trash: Clicking this will delete the currently selected animation from the animation group. This will NOT delete the animation itself; just the reference to it, from the group.
• Cycle: Enabling this will cause a different animation to be played, from the selected group, at each “cycle time” interval (see below).
• Randomize order: Enabling this causes the animations in the selected group to be played in random order.
• Cycle time: Indicates how long an animation should play before the next one begins. Set this to zero to disable.
• Reload: Forces the AO to reload the configuration of the current animation set.
• Left/Right Arrows: skips to the previous/next animation in the current animation group. These are the same arrows seen in the mini AO view, described previously.
• Down Arrow: The arrow in the bottom right corner collapses the full AO window into the mini view, which was described above.

If you own a scripted AO, the type worn as an HUD attachment, you can transfer it to the client AO quite easily. You may follows these steps to do so. Multiple AOs can be loaded, and you can switch from one to another simply by selecting the set within the Firestorm AO.

NOTE: The notecard must be in standard ZHAO II format, or in Oracul format. Most AO creators support ZHAO II so you should not run into issues. However, it must be noted that some major vendors have extended the ZHAO II format, and thus their AO notecard will need to be edited before they can be used in the Firestorm AO. Similarly, older AOs which use the old ZHAO format will have to be converted.

NOTE: Unlike Phoenix, the animations and notecard do not need to be placed in a special predefined folder. However, they do need to be together in the same place. Once imported, the Firestorm client AO creates a new special folder: #Firestorm → #AO. This folder is protected - meaning, it cannot be deleted, nor items removed from it ²⁾ . Inside that are several more folders, containing links to the original animations. So do not delete the original animations used or the AO will “break”.

Follow these steps if you are in a location where you can build; if requires the ability to rez out.

• Rez a cube on the ground.
• If you are wearing the scripted AO, detach it.
• Cam into the cube you made, then drag the AO onto it. HUDs are normally very small when rezzed in-world, and can be hard to see if you are not cammed in.
• Right click AO you rezzed out and select Open. A window opens which will list the contents of the AO; once this has fully populated, click Ok.
  This will result in the creation of a folder in your inventory, containing everything in the AO: scripts, animations and notecards.
• If the AO is copyable, you can now delete it; otherwise, take it back into your inventory. Then delete the cube.
• Locate the folder that was created in the step above. This folder can be dragged to another folder where it is out of the way but still available, like the Animations folder, for example.
• Inside the folder, locate the notecard which defines the AO. An example is shown below.
• Open the Firestorm AO to maximum, then drag the AO notecard onto the Firestorm AO window.
• The notecard is parsed and if all goes well, you have finished transferring the AO.
• Select options to apply, like whether this will be the default animation set, whether to override sits, etc.

You can follow these steps if you are unable to rez the AO out in-world, for whatever reason.

• Location the Animations folder in your inventory - it is at the top. Right Click the folder name, and select New Folder.
• Type in a name for the folder - for example, give it the name of the AO you are transferring.
• Make sure the AO HUD is worn; right click it and select Edit.
• Click on the Content tab.
• Once the AO contents are all displayed, select all items: click on the top one, then use the scroller to scroll to the bottom, press and hold Shift, and click on the last item.
• Drag all the items into the folder you created.
• Close the edit window.
• Inside the folder, locate the notecard which defines the AO. An example is shown below.
• Open the Firestorm AO to maximum, then drag the AO notecard onto the Firestorm AO window.
• The notecard is parsed and if all goes well, you have finished transferring the AO.
• Select options to apply, like whether this will be the default animation set, whether to override sits, etc.

As noted above, the Firestorm AO supports notecards in the standard ZHAO II format. Here is an example of what such a notecard looks like:

[ Standing ]vAStand01DANGER|VAStand05_DANGER_F|VAStand02_DANGER|VAStand06_DANGERe
[ Standing ]VAStand04_DANGER|VAStand06_iDANGER|VAStand07_DANGER3|VAStand08_DANGER30
[ Standing ]VAStand09_DANGER|vAStand11_DANGER|VAStand12_DANGER|VAStand13_DANGER|VAStand14_DANGER
[ Walking ]08WALKDANGER|DANGERMIXWALK1|DANGERMIXWALK2.3
[ Sitting ]sit01DANGER|sit02DANGER|sit03DANGER|sit04DANGER|sit00DANGER
[ Sitting On Ground ]sitgDANGER01|SitGDANGER2|sitgDANGER3
[ Crouching ]crounch02DANGER|VAmocCROUNCH3
[ Crouch Walking ]vAFLIPWALK2
[ Landing ]landing2DANGER|Landing_Jump03_AN
[ Standing Up ]vA_boxerlanding1
[ Falling ]fall_VA_fly3
[ Flying Down ]vA_DangerFlyDown
[ Flying Up ]vA_DANGERflyUp
[ Flying ]vA_DangerFly|VAmocFLIGHT2
[ Flying Slow ]vAmocFSLOW
[ Hovering ]vA_DANGERhover_v02
[ Jumping ]jump02DANGER|jump_Jump03_AN
[ Pre Jumping ] v3_VA_Prejump|preJump_Jump03_SL
[ Running ]vISTARUN
[ Turning Right ]vATURNR
[ Turning Left ]vATURNL
[ Floating ]fLOAT
[ Swimming Forward ]vA.DIVE
[ Swimming Up ]
[ Swimming Down ]
[ Typing ]typex

Notice how the animation state is in brackets, followed by each name of the animation separated with a pipe character “|”. Lines should not be longer than 255 characters, and in the example above, the animations in the Standing group have been broken up into several lines so they are shorter and easier to read.

NOTE: It is best to delete any/all lines containing comments, before loading into the client AO. Comment lines usually start with a # character.

There is no need to have a prepared AO with a notecard to create an AO in Firestorm; you can “roll your own” if you have animations to use.

You should have the AO window at maximum size, as shown above.

• Click the + button near the top right corner to create a new animation set. You will be prompted to supply a name for it.
• A new, blank animation set is created; make sure it is showing in the list of animation sets. You can now begin to fill. It starts with the Standing group selected.
• In your inventory, select the animation(s) to be used as stands. Drag them from your inventory onto the AO window. (Note that it is faster to drag them all in at once rather than one by one.) The AO processes, then you can continue.
• Once you have dropped all the stands in, you can switch to another animation group, like Walking. Again, select and drag the animations from your inventory onto the AO.
• Repeat this for all groups for which you have animations.
• Select options to apply, like whether this will be the default animation set, whether to override sits, etc.
• Do not delete the original animations used or the AO will “break”.

Other options related to the Firestorm AO.

• Turn avatar around when walking backward: in Preferences→ Move & View → Firestorm. If enabled, when you press the down arrow to walk backward, your avatar will turn to face the camera. If disabled, then your avatar will walk backward.

The AO may also be controlled by scripts. This can be very handy for those who wear collars, for example. For more information on how to implement this, see this page.

Cette fenêtre est accessible à partir du menu World > Avatar Render Settings. Elle affiche une liste des avatars desquels vous avez modifié la méthode d'affichage par défaut par rapport à leur complexité.

En cliquant droit sur le nom d'un avatar dans cette lsite, vous pouvez changer comment cette personne s'affichera :

• Normally (Normalement) - Supprimera le nom de la liste
• Do not render (Ne pas afficher) - l'avatar sera toujours affiché en silhouette colorée
• Fully (Entièrement) - l'avatar s'affichera toujours entièrement, quelle que soit sa complexité.

Regarder la vidéo ci-dessous pour une information visuelle de ce qu'est cette nouvelle particularité :

• https://www.youtube.com/watch?v=PxWrqd0o3dc&feature=youtu.be

• Il déterminera quels avatars apparaîtront comme des silhouettes (“jellydolls”) dans votre viewer, sur la base de leur propre complexité.
• Allez à Preferences → Graphics → General → Maximum Complexity
• NB: baisser ce paramètre à l'aide du slider réduira le lag graphique et affichera plus d'avatars en tant que silhouettes ; augmenter le réglage est susceptible de causer plus de lag mais plus d'avatars seront entièrement visibles.
• Notez aussi : il n'est pas recommandé de régler ce slider au maximum (No Limit) car si en effet, aucun avatar ne s'affichera plus comme silhouette colorée pour vous, vous serez cependant livré au lag et et à la merci des crashers graphiques.

• Cliquer droit sur le nom de l'avatar (sur son tag) et choisir à partir du menu:
• More > More > Render > Normally– l'avatar sera affecté par votre slider de complexité (voir ci-dessus)
• More > More > Never– l'avatar restera une silhouette sur votre écran
• More > More > Fully– l'avatar s'affichera entièrement même si votre slider de complexité est bas

Dans la barre de menus en haut de votre écran allez dans le menu World > Avatar Render settings. A partir d'ici vous pourrez changer la manière dont les avatars s'affichent pour vous. Voir cette page pour plus d'infos.

• Allez à Preferences → General et cochez selon vos souhaits “Show Avatar Complexity” (Afficher la complexité de l'avatar), Only if too complex“ (seulement si trop complexe) et “Show own complexity” (afficher ma propre complexité)

• Cet avertissement apparaît dans le coin supérieur droit de votre écran.
• Allez à Preferences → Notifications → Alerts, et faites passer “Warn me if my avatar complexity may be too high” dans la liste du bas “Never show”.

• Ceci apparaît dans le coin supérieur droit de votre écran lorsque vous changez de tenue ou d'accessoires.
• Allez au menu Advanced → Show Debug Settings → ShowMyComplexityChanges, mettez la valeur sur 0 pour le masquer, ou à une valeur plus élevée pour l'afficher. Notez quelque part ce réglage au cas où vous voudriez le modifier de nouveau.

• Ceci affiche non seulement la complexité mais aussi le rang et la distance des avatars au-dessus de leur tête.
• Allez à Avatar → Avatar Health → Show Avatar Complexity Information
• Notez bien : la hauteur du texte n'est pas ajustable.

Allez dans le menu Avatar > Appearance, et regarder en bas à droite de l'écran.

Il existe 2 méthodes :

• Porter l'attachement puis l'enlever, tout en notant le changement de complexité de votre avatar en haut à droite de votre écran.
• Porter l'attachement et éditez-le. Dans la fenêtre d'édition, cliquez sur “More Info” et regardez le nombre listé sous “Display”.

Voici les paramètres par défaut qui déterminent le seuil à partir duquel vous voyez les avatars s'afficher pleinement ou en tant que silhouettes. Ils correspondent au slider de qualité et vitesse graphique (“Quality and Speed”) dans Préférences → Graphics → General. Lorsque les paramètres sont laissés par défaut, les avatars dont la complexité est au-dessous de ces seuils seront visibles, alors que ceux à complexité supérieure du seuil s'afficheront en tant que silhouettes colorées.

• Low: 35,000
• Low-Mid: 100,000
• Mid: 200,000
• Mid-High: 250,000
• High: 300,000
• High-Ultra: 350,000
• Ultra: 350,000

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

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

Locations are indicated in the far right column as follows:

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

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

*All times SLT*

Beta testing Firestorm is more properly called QA (Quality Assurance). This means using test builds of the viewers before general release, using them and actively trying to identify bugs, glitches and things that need improvement. In other words, being part of the beta (QA) team means more than just getting your hands on a “new shiny” before everyone else does. You will be asked to do specific tests for each release, the results of which are vital to helping us determine where there may be problems.

So, if you are interested in becoming an active participant in the beta team, and are willing and able to endure crashes, multiple relogs, full settings wipes (several times), and so on, then please read on.

In applying to become part of the beta testing team, you are explicitly agreeing to the non disclosure terms below.

• Create an account on our JIRA, if you have not already got one. This is required in order for you to access the beta test site.
  If you need tips on creating an account, see Creating an Account on our wiki page on filing a JIRA.
  Either way, make sure you are logged in. Please use your Second Life name, NOT your Real Life name when creating an account on our JIRA. Both Username and Full Name should be your Second Life account name (no display names).
• In the top right of the page you'll see a link that says 'Create Issue'. Click that and in the page that opens…
• For 'Project', select 'Tester Applications, BETA'.
• For 'Issue Type' select 'BTA'.
• For the 'Summary' field enter your SL username, not your display name.
  If you have more than one operating system and would like to have an alt added for testing additional operating systems, add their username here with your names separated by commas.
• Set 'Priority' to Major.
• For 'SL Avatar Name' fill in the SL username of your primary SL avatar that you would like used for beta testing correspondence.
• Leave 'Patch attached' unchecked.
• For 'Affects Version/s' select the current Firestorm release version. (For example, 4.7.5).
• For 'Environment' copy and paste the entire environment from the Help menu, About Firestorm, Info tab in Firestorm for any machines and or operating systems you will be using for testing.
• For 'Description' give us a brief explanation of why you think you would make a good member of our beta test team.
• 'Attachment' and 'Labels' should be left blank, they're not used for applications.
• Click Create.
• Be sure and keep an eye on the JIRA you created as this is where you will be initially contacted to complete your addition to our beta test program. Do not reply via email to any emails you receive from the JIRA, they will not work.

Your application will be assessed as soon as it is seen by the QA team lead to ensure it is complete and correct. If any corrections need to be made you will be notified in the comments section of your application.

There is a seven day “cool-off” period after your application is submitted until you are notified if you have been approved.

You will need to follow the instructions in your BTA once accepted, and at that time will receive an invitation to the in-world group, Firestorm Beta testers.

All information provided when applying to become a Firestorm Beta Tester on issue type BTA is strictly confidential and only accessible by you and Firestorm team members.

As part of the beta test team, you will be given access to test builds from time to time. Such builds are not to be circulated outside of the beta test team. Nor are direct or indirect web links to be shared with people who are not part of the beta test team. Doing so will result in immediate termination of beta tester status.

The reason for this is very simple: test builds are often known to have bugs, sometimes very severe ones. We test them anyway because there may be other aspects of the build on which we need to have feedback. Clearly, we do not want viewer builds which are known to have bugs - or which may potentially have severe bugs - to be circulated to the general public.

Here is an outline of the general procedure for each new test release.

• A notice is posted to the in-world beta test group, announcing the new test build. Any specific directions are given at that time, often in an attached notecard.
• Log in to the Phoenix Beta Site, then download the test release.
• Install the test viewer. Most of the time installs can be dirty and installed directly over your current Firestorm install. On occasion you will be asked to do a clean install which is a total wipe of settings, possibly including cache. A clean install is explained here. If you are not given specific instructions on this in the new test notice or on the test itself, then assume that a clean install is not required.
• In most cases, there will be a smoke test to carry out; that is, specific things that we need to have tested. This smoke test is structured as a questionnaire: a description is given of what needs to be tested, and you are asked to fill in the results. This is a sample segment of such a test:
  
• Once you have completed the test - and it cannot be stressed enough how vital it is that you do so! - continue to use the viewer as you normally would, and report any problems you find to JIRA (making sure you select the correct viewer versions for Reported in and Affects).
• You are encouraged to use the in-world group to ask questions, to see whether specific issues are known or perhaps expected behavior. But bug reporting should be done to JIRA or your bugs may go unnoticed.

form> Action mail lassie@phoenixviewer.com subject @“=Event Name”@ Thanks “Thanks for submitting your Firestorm MotD request.”

Fieldset “Website Checklist”

static “The MotD doesn't send people to your event, it is meant to encourage people to visit your website. It is up to you to sell your event with your website.”

yesno “Is your website safe for a general audience (PG/G)?” !

yesno “Is your website open to the public?” !

yesno “Does your website adequately describe and up-sell your event?” !

yesno “Does your website contain a prominently displayed SLURL to your event?” !

Fieldset “Event Checklist”

yesno “Is your event location capable of handling the potential traffic a Firestorm MotD may potentially send you?” ! static “Events located on Homestead or Open Space regions should reconsider if they truly would like to have a Firestorm MotD. Events located on small parcels (8192 sqm or less) should reconsider if they truly would like to have a Firestorm MotD.”

yesno “Is your event located on a General rated region?” ! static “Events on Mature regions are considered on a case by case basis. Events on Adult regions will not be considered.”

Fieldset “MotD Request Information”

static “Blank or missing fields in this section can delay your MotD.”

Textbox “What is your SecondLife user name, (not your display name)?” “=SL Name”

email “What is your email address (optional)?” ! static “(This email address will not be shared with anyone.)”

Textbox “Who is your point of contact for any correspondence for this events MotD?” “=Contact Name” static “This individual should be someone who can make final decisions concerning this event.”

email “What is your point of contacts email address?” @@ static “If we have questions about your event we will contact by email, if we are unable to reach anyone your MotD WILL NOT RUN. (This email address will not be shared with anyone.)”

Textbox “What is the name or title of your event?” “=Event Name”

yesno “Is your event suitable for a general audience?” ! static “We are unable to run MotD's for events containing adult content. This includes content on your website.”

Date “What is the start date of your event?”

Textbox “What is the SLT start time of your event (optional)?” “=Start Time” !

Date “What is the end date of your event?”

Textbox “What is the SLT end time of your event (optional)?” “=End Time” !

Textbox “What is the URL to the website for your event?” “=Website URL”

textarea “What would you like your MotD to say?” static “This is optional, if you don't provide something we will write one for you based on information provided on your website. If you do provide something it may be rewritten to fit in the limited space available for the MotD, for content or for readability.”

textarea “Do you have any comments or questions about your Firestorm MotD?” !

submit “Submit Request” </form>

There are a few reasons for this, none of which are related to the viewer.

1. Your email address is not correctly listed
2. Your option to send IMs while offline is not enabled
3. Your email has not been verified
4. The messages are not being delivered

If in the viewer, go to the Avatar menu and choose Account. If not in the viewer, click on this link. Then click the Contact Information link and edit your email address. Enter your password and click Save Changes.

If in the viewer, go to the Avatar menu and choose Account. If you are not in the viewer, click on this link. You should now be in your account on the Second Life web site. Then check the box for “I would like to receive offline IMs via Email” and click Save Changes.

Second Life now requires an email verification step in order to send any emails to you, including offline messages. See the official instructions for how to do this here: https://community.secondlife.com/blogs/entry/2155-making-email-from-second-life-more-reliable/.

If your email address is correct, and the option to send IMs to email is enabled, and you have verified your email address, then the problem could be spam filters or server issues. Usually server issues don't occur, but server configuration could play a part.

First check your email's spam folder to see if the email is being incorrectly flagged.

If not there, then try using a different email address at a different provider (Yahoo, Google, etc.).

If IMs are delivered to the new address, contact your regular email provider and ask them if mail coming from “im.agni.lindenlab.com” is being blocked.

If IMs are still not delivered to the new email address, ask your friends if they have the same problem, check the Grid Status page and see if there is any reported issue, and then if nothing is there contact Second Life Support and report the issue. Make sure you tell them everything you've done, in detail.

Hotmail users, try the suggestion on this page.

July 5, 2014: Offline email to one set of providers not being delivered.

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:
  • 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 sounds is going to the correct device (ie, speakers or headset), and so on;
  • 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

If using a VEA4 TV, you get a “File could not be found” error, disable the IPv6 protocol in the Windows network adapter. Note that this is not recommended, but apparently is the only way to get this brand of TV to work.

If sound eventually cuts out on your computer while using Firestorm and the only way to get it back is to log off Firestorm, disable Audio Enhancement via the steps shown here. Another possibility is Loudness equalization; reference this JIRA.

Refer to this page for all Win10 issues.

Please ensure that you have the most recent version of Flash for Safari installed. You can get this via the normal update process, or from Adobe.

For streaming music on OS X 10.9 Mavericks, please refer to this page.

For users on Sierra, there are reports of media features (such as MOAP, TVs, web search, and web profiles) working more slowly. Ref. BUG-40552.

Both the 32-bit and 64-bit versions of Firestorm for Linux require 32-bit libraries to function. See this page for a link to your Linux flavor to verify you have all the needed audio-related packages installed and to troubleshoot stream issues.

For instructions for Phoenix, please refer here.

Some anti-virus programs will incorrectly flag a viewer - or necessary components of a viewer - as a virus or threat. They may remove the suspected part completely, rendering all or part of the viewer non-functional. There is nothing we can do about this. However, it should be possible for you to tell your anti-virus that the viewer is safe; you will need to whitelist the viewer program as well as some components.

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

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

1. Uninstall the viewer normally.
2. Disable the anti-virus software completely (in a few cases, this requires rebooting to make sure that the AV is not running anymore).
3. Reinstall the viewer, but make sure you do not install it back to the default folder suggested; install to a new folder. This step is vital.
4. In your anti-virus program, whitelist the following, per the instructions below (or better, consult the manual for your anti-virus software):
   • the viewer install folder
     • inside this, the viewer itself (firestorm.exe), slplugin.exe, slvoice.exe and llceflib_host.exe (for FS 4.7.7 and later).
   • the viewer cache folder
     • In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Now you need to locate the cache folder:
       • Windows XP: C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Firestorm
       • Windows Vista/7/8/10: C:\Users\[USERNAME]\AppData\Local\Firestorm
       • Mac: /Users/[USERNAME]/Library/Caches/Firestorm
5. Run the viewer to ensure that it is working correctly; do a test of search and voice to ensure that both work, checking that the respective plugins get loaded. Log out of the viewer.
6. Re-enable your anti-virus software and run the viewer again, repeating the tests above.

• Open the Avast User Interface
• Click Settings
• Click Components
• Click File-System Shield Customize
• Click Exclusions
• Click Add
• Click Browse and navigate to the Firestorm install folder
• Click OK
• Repeat for the Firestorm cache folder
• Click OK all the way out

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

Please refer to this page.

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

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

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

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

In order to create an exclusion rule:

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

Rules can apply to the following protection components:

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

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

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

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

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

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

• Open Settings and in the search field at the top right enter defender
• Click the Windows Defender Settings option.
• Exclude the cache
  • Click Add an Exclusion
  • Click Exclude a folder
  • Click in the address bar and type %LOCALAPPDATA% and press Enter
  • Click the Firestorm folder
  • Click the Exclude this folder button
  • Repeat this if you have more than one Firestorm folder (64-bit and 32-bit, for example)
• Exclude the viewer executables
  • Click the Exclude a .exe, .com or .scr process button
  • Navigate to C:\Program Files\Firestorm-Release64
  • Click Firestorm-bin
  • Click the Exclude This file button
  • Repeat this for SLPlugin and SLVoice - and llceflib_host (for FS 4.7.7 and later).
  • Repeat this for 32-bit Firestorm ( C:\Program Files (x86) )

Add exclusion to Auto-Protect and Risk scan

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

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

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

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

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

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

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

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

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

For additional information:

• https://community.webroot.com/t5/Webroot-for-Business/how-to-set-file-and-folder-exclusions-in-the-webroot-console/td-p/189775
• https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/How-to-exclude-a-folder-from-being-scanned-in-the-latest-WSA-AV/td-p/78063

There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.

You might also have been affected by what appears to be a server-side bug: BUG-41379.

Below are things you can try to get the HUDs working again. First of all, relog then test the HUD(s) again. That may be enough. If not, read on.

Things to try:

• Check for location issues:
  • Make sure you are in a region that has scripts enabled.
  • Go to other regions and test the HUDs there. This will rule out technical problems with the original region.
  • If you have RLV enabled, disable it (Preferences → Firestorm, top option), relog, then try again.

Stay in a script-enabled region to do all of the following:

• Attempt to get scripts running:
  • Try removing and reattaching the HUDs.
  • If the HUDs are modifiable, try resetting them or setting their scripts to running: Inventory, right-click the item → Edit, and while it is in Edit, go to Build menu → Scripts → Reset Scripts, or Build menu → Scripts→ Set Scripts to Running).

• Identify broken HUDs:
  • Try removing all the HUDs and testing them one at a time: test each one, then remove it, then test another.
  • If you have original copies of the HUDs, try detaching the ones you are currently wearing and using a fresh copy from the original.
  • If a HUD is no-mod and you can't get it to start running again, and you don't have another copy, you will need to request a new copy from the creator.
  • Note: If the non-working HUDs are for your mesh body parts (or other scripted attachments), you probably will need to use fresh copies of the original HUDS and the body parts – every part, from scratch (not copies of the broken ones).

• Check for interference:
  • Look in Inventory > Current Outfit folder, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached.¹⁾
  • Check that HUDs are not overlapping each other on the screen (and so preventing you from clicking).

• Check for issues with attachment points:
  • If any HUDs are sharing the same HUD attachment point, try moving them to separate HUD attachment points:
    Inventory → Right-click → Detach from Yourself, then Inventory → Right-click → Attach to HUD, and choose an unused point.
  • Even if they are not sharing attachment points, try moving them to different attachment points.

• Test basic functionality:
  1. Rez a fresh cube
  2. Add the default script to it
  3. Take it into inventory
  4. Attach it to a HUD point
  5. Touch the HUD and see if there is script output in Local chat.

• Account: will prompt you to open your SL dashboard in a web browser
• Marketplace Listings: Manage your SL marketplace listings.
• Buy L$: opens the floater to let you buy L$
• Inventory (Ctrl-I): opens your inventory
• Picks: opens the Picks and Classifieds window for creation and editing of picks and classified ads.
• Experiences: opens the Experiences window.
• Profile: opens your profile
• Appearance: opens the appearance floater at My Outfits (will be greyed out if you are a cloud; see here if that has happened to you)
• Choose an avatar: opens the Choose an Avatar window.
• Movement: opens the movement sub menu where you can set
  • Sit down (Alt-Shift-S): will sit your avatar down (not available if already sitting)
  • Fly (Home): this toggles will turn on fly mode (not available if sitting)
  • Stop Flying (Home): this toggle will turn off fly mode.
  • Always Run (Ctrl-R): toggles run
  • Force Ground Sit (Ctrl Alt S): This forces your avatar into a ground sit regardless of where your avatar is.
  • Move Lock (Ctrl-Alt-P): When enabled, will lock your avatar in place so it cannot be pushed.
    You will not be able to move yourself either, unless you enable Preferences→ Move & View -> Movement→ Lock and unlock position after stopping or starting movement.
  • Quickjump: If enabled, the viewer suppresses any pre-jump animation.
• Move Controls: toggles the movement controls floater
• Camera Controls: toggles the camera controls floater
• Avatar Health: opens the Avatar Health sub menu
  • Stop avatar animations: used to stop animations acting on your avatar
  • Stop avatar animations & revoke permissions:
  • Undeform Avatar: Attempts to undeform your avatar, to recover its normal shape after deformation after the use of oversized avatars or griefer objects.
  • Force appearance update (Rebake)(Ctrl-Alt-R): rebakes your avatar's textures
  • Refresh Attachments: In cases where attachments are “ghosted”, it will attempt to reattach them. Ghosted attachments are those that shows attached to you but others don't see them.
  • Reset Default Male Avatar (Character Test): forces your avatar to the default male
  • Reset Default Female Avatar (Character Test): forces your avatar to the default female
  • Show Avatar Complexity Information:
  • Lag Meter: Opens the Lag Meter window.
  • Recreate LSL Bridge: creates a fresh copy of the LSL bridge
• Snapshot (Ctrl-Shift-S): opens the snapshot floater
• Money Tracker: Shows a list of who last paid you; see this page for more information.
• Pose Stand…: Open the Pose Stand window; replicates the functionality of a pose stand.
• Preferences (Ctrl-P): opens your preferences window
• Toolbar Buttons: Opens the toolbar buttons window, allowing the button layout to be customized.
• Show HUD Attachments (Alt-Shift-H): Shows all HUDs that you have attached
• Exit Firestorm (Ctrl-Q): Closes Firestorm

• Online Status: opens the Online Status sub menu where you can set yourself to:
  • Away
  • Unavailable (Busy)
  • Auto-respond: (the auto-response messages are set in Preferences→ Privacy -> Autoresponse)
  • Autorespond to non friends
  • Reject teleport offers and requests
  • Reject all group invites
  • Reject all friendship requests
• Friends (Ctrl-Shift-F): opens the Friends tab in the contacts list.
• Contacts (Ctrl-Alt-Shift-F): Opens or closes the contacts list.
• Contact Sets (Ctrl-Alt-Shift-C): opens the Contact Sets window, to manage your own groups of contacts
• Groups (Ctrl-Shift-G): opens the Groups tab in the contacts list.
• Chat (Ctrl-H): opens the nearby chat tab in the Conversations window
• People: Opens the people window.
• Conversations (Ctrl-T): opens the Conversations window
• Gestures (Ctrl-G): opens the Gestures window
• Facebook…: opens the Post to Facebook window.
• Twitter…: opens the Twitter window.
• Flickr…: opens the Upload to Flickr window.
• Voice Morphing:
  • No voice morphing: Enables/Disables voice morphing provided you are already subscribing to Linden Lab's voice morphing.
  • Preview: Opens the Voice Morphing Preview window.
  • Subscribe: Opens the Second Life Voice Morphing web page.
• Conversation Log: Opens the Conversation Log window.
• Nearby Voice: opens nearby voice, aka active speakers
• Block List: opens the people window → Block List

• Resync Animations: Restarts animations within your view; this allows couples dances to be resynchronized.
• Nearby Avatars (Ctrl-Shift-A): Opens the Nearby tab in the People window.
• Radar: Opens the Radar window.
• Teleport History (Alt-H): Opens the Places window, teleport history tab.
• Places: Opens the Places window.
• Destinations: Opens up Destination window.
• Events: Opens the SL Events web page.
• Mini-Map (Ctrl-Shift-M): Opens the Minimap
• World Map (Ctrl-M): Opens the World Map
• Region Tracker: Opens the Region Tracker window.
• Landmark This Place: Creates a landmark of your current location
• Location Profile: Opens the Places Profile window
• Parcel Details: Opens the About Land window
• Region Details: Opens the Region/Estate window
• Buy This Land: oOpens the Buy Land window (If you are on land that is not for sale, this will be greyed out)
• Show Owned Land: Opens the Owned Land window
• Show More: opens the Show More sub menu where you can chose to show
  • Ban Lines Enables or disables the ability to see ban lines around parcels to which you are not allowed access.
  • Beacons (Ctrl-Alt-shift-N) Hide/show beacons for some types of objects, like sound sources, particle sources, and so on.
  • Property Lines (Ctrl-Alt-Shift-P) Enables or disables showing lines at property boundaries.
  • Land Owners Colors land: Green is land owned by you, red is land owned by others, yellow is land for sale.
  • Coordinates: Shows your current coordinates in the menu bar
  • Parcel Permissions: Shows icons of your parcel rights
  • Advanced Menu (Ctrl-Alt-Shift-D): Hides/shows the Advanced Menu. This can also be done in Preferences→ Advanced.
• Teleport Home (Ctrl-Shift-H): teleports you home
• Set Home to Here: sets your home location to the point you are at; also saves a snapshot, which will be displayed when you log in to your home location.
• Sun Position: opens the Sun Position sub menu, where you can set the sun position to
  • Sunrise (Ctrl-Shift-U)
  • Midday (Ctrl-Shift-Y)
  • Sunset (Ctrl-Shift-N)
  • Midnight (Ctrl-Shift-X)
  • Estate Time
• Environment Editor: (Photographers might prefer that fast access available in QuickPrefs or Phototools) This has these sub-menus:
  • Environment Settings: Opens the environment settings window.
  • Water Presets: has sub-menus to allow water presets to be created, edited, deleted.
  • Sky Presets: has sub-menus to allow sky presets to be created, edited, deleted.
  • Day Presets: has sub-menus to allow day presets to be created, edited, deleted.
• Photo and Video: opens the submenu for
  • Phototools (Ctrl-Alt-P): opens the Phototools floater.
  • Cameratools (Ctrl-Alt-C): opens the Cameratools floater.
• Area Search: Opens the Area Search window
• Sound Explorer: Opens the Sound Explorer window.
• Animation Explorer: Opens the Animation Explorer window.
• Asset Blacklist: Opens the Asset Blacklist Window.
• Avatar Render Settings: Opens the Avatar Render Settings window.
• Always show Friends normally: This will show all friends as normally rendered avatar instead of a “jelly doll” image.
• Show Friends only: This will temporarily derender all avatars except those on your friends list. To re-render, you will have to teleport out of the region and then back in.

• Build (Ctrl-B): opens the Build/Edit window
• Select Build Tool: opens the Build Tool sub menu where you can select
  • Focus Tool (Ctrl-1)
  • Move Tool (Ctrl-2)
  • Edit Tool (Ctrl-3)
  • Create Tool (Ctrl-4)
  • Land Tool (Ctrl-5)
• Link (Ctrl-L): will link multiple prims
• Unlink (Ctrl-Shift-L): will unlink prims in a linkset
• Edit Linked Parts: allows you to edit individual prims in a linkset
• Select Elements: opens the Select Elements sub menu where you can choose:
  • Select Next Part (Ctrl-.)
  • Select Previous Part (Ctrl-,)
  • Include Next Part (Ctrl-Shift-.)
  • Include Previous Part (Ctrl-Shift-,)
• Focus on Selection (H): will focus your camera on an object you have selected
• Zoom to Selection (Shift-H): will zoom your camera on an object you have selected
• Object: opens the Object sub menu that allows you to:
  • Take: Takes the object back to inventory
  • Take Copy: Creates a copy of the object in inventory.
  • Duplicate (Ctrl-D): Creates a duplicate of the object next to the original object.
  • Edit Particles: Opens the Particle Editor.
  • Save Back to Object Contents If you drag the contents of an object directly onto the ground (rather than into your inventory first, then out onto the ground), and make changes to it, this function allows those changes to be saved back to the original object.
  • Return Object Returns the object to the owner.
  • Save as:
    • Backup: Opens the Backup window, allowing you to save the object to your hard drive.
    • Collada: Opens the Collada Export window, which you can use to export the object as mesh.
• Scripts: opens the Scripts sub menu where you can:
  • Show Script Warnings/Errors
  • Script Info (Counter): If the object is moddable, this will show script information for it.
  • Recompile Scripts (Mono)
  • Recompile Scripts (LSL)
  • Reset Scripts: this will only work if the object is moddable.
  • Set Scripts to Running
  • Set Scripts to Not Running
  • Remove Scripts from Selection: If the selected object is moddable, removes all scripts from it.
• Pathfinding: Options concerning Pathfinding.
  • Linksets: Opens the Pathfinding Linksets window.
  • Characters: Opens the Pathfinding characters window.
  • View / Test: Opens the Pathfinding console.
  • Rebake Region: Rebakes the region NavMesh, if there are pending changes - assuming you have rights to do so and Pathfinding is enabled for the region; will by greyed out otherwise. This can also be done by clicking the Pathfinding icon in the top menu bar.
• Options: opens the Options sub menu where you can:
  • Show Advanced Permissions: Refer to this SL Wiki page for more on Advanced (Debug) permissions.
  • Select Only My Objects
  • Select Only Movable Objects
  • Select Only Locked Objects
  • Select Only Copyable Objects
  • Select By Surrounding
  • Include Group-Owned Objects
  • Show Selection Outlines (Ctrl-Alt-H)
  • Show Hidden Selection
  • Show Light Radius for Selection
  • Show Selection Beam
  • Snap to Grid (G)
  • Snap Object XY to Grid (Shift-X)
  • Use Selection for Grid (Shift-G)
  • Grid Options (Ctrl-Shift-B)
  • Set Default Permissions: Opens the Default Creation Permissions window.
• Upload: opens the Upload sub menu which allows you to choose what to upload (Same as the Upload item in the Avatar Menu):
  • Image (L$10): Opens a file selector, then the image upload window.
  • Sound (L$10): Opens a file selector, the the sound upload window.
  • Animation (L$10): Opens a file selector, then the animation upload window
  • Mesh Model: Opens a file selector to upload a mesh model; see the SL wiki for more info.
  • Bulk (L$10 per file): Opens a file selector where you can select multiple image files for upload.
  • Import Linkset: Opens the Import window, to upload a previous exported object.
• Undo (Ctrl Z): will undo the last changes made in the edit /build window
• Redo (Ctrl Y): will redo the last changes made with the undo command

• Search (Ctrl-F): opens the Search window
• SL Marketplace: prompts you to open the Marketplace web page
• L$ Market Data: prompts you to open the L$ market Data web page
• Script Library: prompts you to open the Script Library web page
• Firestorm Blog: prompts you to open the Firestorm Viewer Home web page
• Firestorm Flickr: prompts you to open the Firestorm Viewer Flickr web page
• Firestorm YouTube: prompts you to open the Firestorm Viewer YouTube channel
• Firestorm Twitter: prompts you to open the Firestorm Viewer Twitter web page
• Firestorm Plurk: prompts you to open the Firestorm Viewer Plurk web page
• Message of the day: this will show the message of the day in local chat. This also is shown during the login phase.

• Enable Viewer UI Hints: enables the tooltips on objects; this can also be done in Preferences→ User Interface -> General→ Hover tips.
• Firestorm Wiki (F1): opens the Firestorm Wiki page
• Troubleshooting: opens the Firestorm Troubleshooting and Quick Fixes Wiki page
• Join Firestorm Support Group: opens a window listing in-world support groups you can join, to get help.
• Firestorm Classes Schedule: opens the Firestorm Class Schedule page.
• Check Grid Status: opens the Grid Status web page
• Report Abuse: opens the Abuse Report window
• Report Bug: opens the "how to file a JIRA" page on our Wiki
• Bumps, Pushes & Hits: opens the |pushes and bumps window
• Enable Sysinfo Button: enables a button in IM window that lets you send your sysinfo
• About Firestorm: opens the About Firestorm window

This menu is toggled from Advanced Menu (Ctrl-Alt-D) → RestrainedLove API (RLVa) or from Preferences → Firestorm → Extras → Allow Remote Scripted Viewer Controls (RLVa). This will require a restart of the viewer to show this menu.

• Debug: Opens the Debug sub menu where you can enable:
  • Show Top-level RLVa Menu: Enables showing the RLVa menu in to menu bar. If disabled, RLVa menu will show in Advanced Menu.
  • Show Debug Messages: Used when debugging RLV scripts and also to know when something RLV is being done to you by either a person or object.
  • Hide Unset or Duplicate Messages
  • Show Assertion Failures
  • Hide Locked Layers
  • Hide Locked Attachments
  • Enable Legacy Naming
  • Enabled Shared Wear
  • Rename Shared Items on Wear
  • Locks: Opens the Active RLV Locks window
• Allow OOC Chat: Allows Out Of Character (OOC) chat.
• Allow Temporary Attachments
• Forbid Give to #RLV
• Show Filtered Chat
• Wear Replaces Unlocked
• Console: Opens the RLVa console window
• Restrictions: Opens the Active RLV Restrictions window
• Strings: Opens the RLVa Strings window

Please use with caution

This menu is toggled via the Ctrl-Alt-D key sequence, or from Preferences→ Advanced

• Rebake Textures (Ctrl+Alt+R): (same as Avatar→ Avatar health → Force Appearance Update).
• Refresh Attachments:
• Set UI Size to Default: Reverts any changes made in Preferences→ User Interface -> General→ UI scaling.
• Set Window Size: Allows you to set the window size.
• Limit Select Distance: Limits your select distance to about 50m.
• Disable Camera Constraints: Allows camera to pass through solid objects.
• High-res Snapshot: Enables high resolution snapshots.
• Quiet Snapshots: Disables the snapshot sound and animation.
• Performance Tools: Opens the Performance Tools sub menu where you can enable:
  • Lag Meter: Opens the Lag Meter window.
  • Statistics Bar (Ctrl-Shift-1): Displays the Statistics window (often called the “stats bar”).
  • Scene Load Statistics (Ctrl-Shift-2): Displays the Scene Load Statistics window with focus on object load and cache performance.
  • Show Avatar Complexity Information: Displays an indicator of client draw “cost” above each avatar (replaces Avatar Rendering Cost).
• Highlighting and Visibility: Opens the Highlighting and Visibility sub menu where you can choose:
  • Cheesy Beacon: Animates the red world map beacon to make it look “cheesy” (enable it to see the effect).
  • Hide Particles (Ctrl Alt Shift =) : Disables rendering of particles. Another way of achieving this is to go to Preferences→ Graphics -> General and setting Max particle count to zero - or doing the same in the Quick Preferences panel.
  • Hide Selected: Makes the currently selected (edited) object invisible, until they are no longer selected.
  • Highlight Transparent (Ctrl Alt T): Makes transparent objects visible by highlighting them in red.
  • Show Mouselook Crosshairs
  • Hover Tips: Opens Hover Tips submenu
    • Show Tips (Ctrl-Shift-T): This allows you to set what hovertips, if any, you see (please check this first to enable hover tips)
    • Show Land Tooltips:
    • Show Tips On All Objects:
• Rendering Types: Opens the Rendering Types sub menu, which allows types of things to be shown or hidden. By default, these are all enabled. Disabling some can be useful if you are trying to find a lost object.
  • Simple (Ctrl-Alt-Shift-1): Textures without alpha channels.
  • Alpha (Ctrl-Alt-Shift-2): Textures with alpha channels
  • Tree (Ctrl-Alt-Shift-3): Linden plants.
  • Avatars (Ctrl-Alt-Shift-4): Bodies and attachments but not name tags.
  • Surface Patch (Ctrl-Alt-Shift-5): Terrain/ground texture.
  • Sky (Ctrl-Alt-Shift-6): Entire sky including clouds and sun/moon.
  • Water (Ctrl-Alt-Shift-7): Water surface only, view when under water is still tinted.
  • Ground (Ctrl-Alt-Shift-8)
  • Volume (Ctrl-Alt-Shift-9): All objects except Linden plants.
  • Grass (Ctrl-Alt-Shift-0): Linden plants.
  • Clouds (Ctrl-Alt-Shift- -)
  • Particles (Ctrl-Alt-Shift-= )
  • Bump (Ctrl-Alt-Shift-\): Legacy bump map and shiny effects.
• Rendering Features: Opens the Rendering Features sub menu:
  • UI (Ctrl-Alt-F1): Be VERY careful when using this, as the menu bar is hidden as well; make mental note of the key sequence so you can re-enable the UI when you need it.
  • Selected (Ctrl-Alt-F2): Display texture alignment crosshair boxes with “Select Face”.
  • Highlighted (Ctrl-Alt-F3)
  • Dynamic Textures (Ctrl-Alt-F4): Enable clothing and sculpt previews in texture upload floater.
  • Foot Shadows (Ctrl-Alt-F5)
  • Fog (Ctrl-Alt-F6)
  • Test FRInfo (Ctrl-Alt-F8)
  • Flexible Objects (Ctrl-Alt-F9): Enable/disable flexible prim effect.
• RLVa: This will menu option will show if chose not to show RLVa menu in top menu bar. This will show RLVa submenus.
• Media Streams Backup
  • Import Stream List XML: This will import the stream_list.xml file.
  • Export Stream List XML: This will export the media stream list from top menu → World Menu → Parcel Details→ Sound tab to a file called stream_list.xml to a folder of your choosing
• Use Plugin Read Thread: Uses a separate thread to read incoming messages from plugins. So in theory, this should give you a slight performance increase if you have a multicore processor and using the internal web browser or playing quicktime videos and so on.
• Clear Group Cache: Clears group cache
• Mouse Smoothing: Should help smooth mouse movement
• Release Keys: Releases permissions taken by worn attachments.
• Shortcuts: Opens the Shortcuts sub menu, showing some of the common keyboard shortcuts:
  • Search (Ctrl-F)
  • Show Advanced Menu-legacy shortcut (Ctrl-Alt-D)
  • DoubleClick Teleport (Ctrl-Shift-D)
  • Always Run (Ctrl-R)
  • Fly (Home)
  • Close Window (Ctrl-W)
  • Close All Windows (Ctrl-Shift-W)
  • Snapshot to Disk (Ctrl-`)
  • Mouselook (M)
  • Joystick Flycam (Alt-Shift-F)
  • Reset View (Esc)
  • Reset Camera Angles (Shift-Esc)
  • Look at Last Chatter (Ctrl-\)
  • Zoom In (Ctrl-0)
  • Zoom Default (Ctrl-9)
  • Zoom Out (Ctrl-8)
• Fly Override (Ctrl-Alt-V): Allows flight in no fly areas - NOT recommended
• RestrainedLove API: Enables/disables RLV (also in Preferences→ Firestorm -> Extras→ Allow scripted viewer controls)
• Show Debug Settings: Opens the debug menu window; use with caution.
• Show Develop Menu (Ctrl-Alt-Q): Shows or hides the develop menu on the menu bar.

Please use with caution

This menu is toggled via the Ctrl-Alt-Q key sequence, or from Preferences→ Advanced

• Consoles: Opens the Consoles sub menu. These should all be disabled in normal use. If you find your screen filling with “strange” graphs and data, check here to make sure all are off.
  • Texture Console (Ctrl-Shift-3):
  • Debug Console (Ctrl-Shift-4): Scroll activity log on the main viewer window.
  • Notifications Console (Ctrl-Shift-5): Trace dialogs, alerts, notifications.
  • Fast Timers (Ctrl-Shift-9): Shows tasks performed per frame.
  • Scene Statistics: Plot complexity of objects in view.
  • Scene Loading Monitor:
  • Region Debug Console Opens the Region Debug Console.
  • Region Info to Debug Console: Dumps region flags and stats to log
  • Group Info to Debug Console: Dumps summary of active group info to log.
  • Capabilities Info to Debug Console: Dumps capability names and URLs to log.
  • Camera: Camera and agent position/rotation overlaid on screen.
  • Wind: Region wind speed and heading is overlaid on screen.
  • FOV: Camera field of view angle overlaid on screen.
  • Badge (Ctrl-Alt-Shift-H) (This won't toggle off……)
• Show Info: Opens the Show Info sub menu:
  • Show Time: Shows the time spent logged on in the lower right.
  • Show Upload Transaction: Gives a notification on upload, showing how much you were charged.
  • Show Texture Info: Shows texture information for the object under the cursor.
  • VRAM usage per object:
  • Show Avatar Render Info: Show load state and attachment weights for visible avatars.
  • Show Render Info: Displays information about the scene currently being rendered.
  • Show Matrices: OpenGL matrix info overlaid on screen.
  • Show Color Under Cursor: Shows the RGBA values for the color under the cursor, in the lower right.
  • Show Memory: Shows total viewer memory use overlaid on screen.
  • Show Private Mem Info: Private pool stats overlaid on screen.
  • Show Updates to Objects (Ctrl-Alt-Shift-U): Displays “clouds” of different colors when objects update.
• Force an Error: opens the Force an Error sub menu. Using any of these will probably crash you. Aimed at viewer developers.
  • Force Breakpoint (Ctrl-Alt-Shift-B)
  • Force LLError And Crash
  • Force Bad Memory Access
  • Force Infinite Loop
  • Force Driver Crash
  • Force Software Exception
  • Force Disconnect Viewer
  • Simulate a Memory Leak
• Render Tests: opens the Render Tests sub menu:
  • Camera Offset
  • Randomize Framerate: Add a random duration sleep with each rendered frame.
  • Periodic Slow Frame: Sleep half a second every 10 frames.
  • Frame Test: Capture buffer and pause.
  • Frame Profile: Dump GL stats to log.
  • Benchmark:
• Render Metadata: Opens the Render Metadata sub menu; these are normally all disabled:
  • Bounding Boxes
  • Avatar Hitboxes
  • Normals
  • Octree
  • Shadow Frusta
  • Physics Shapes
  • Occlusion
  • Render Batches
  • Update Type
  • Texture Anim
  • Texture Priority
  • Texture Area
  • Face Area
  • LOD Info
  • Build Queue
  • Lights
  • Particles
  • Collision Skeleton
  • Joints
  • Raycast
  • Wind Vectors
  • Render Complexity
  • Attachment Bytes
  • Sculpt
  • Texture Size
  • Texture Density
    • None
    • Current
    • Desired
    • Full
• Rendering: Opens the Rendering sub menu
  • Axes: Draw XYZ axis display centered on avatar plus region origin marker.
  • Tangent Basis
  • Selected Texture Info Basis (Ctrl-Alt-Shift-T): Show size and alpha channel presence for faces selected in editor.
  • Selected Material Info (Ctrl-Alt-Shift-M):
  • Wireframe (Ctrl-Shift-R): Show object geometry.
  • Object-Object Occlusion (Ctrl-Shift-O): Optimization, skip rendering objects that are hidden behind others.
  • Advanced Lighting Model: Enable deferred rendering.
    • Shadows from Sun/Moon/Projectors
    • SSAO and Shadow Smoothing: Wikipedia:Screen space ambient occlusion
  • Debug GL: Enable extra OpenGL error checking.
  • Debug Pipeline: Subset of Debug GL.
  • Automatic Alpha Masks (deferred): Force alpha test instead of blend if texture has little transparency (when advanced lighting on).
  • Automatic Alpha Masks (non-deferred): Force alpha test instead of blend if texture has little transparency (when advanced lighting off).
  • Animation Textures: Allows texture to be animated per llSetTextureAnim.
  • Disable Textures: Stop fetching new textures from the network.
  • Full Res Textures (dangerous): Disregard LOD and display all textures at full resolution. Increases network and memory use.
  • Render Attached Lights: Render local light sources on avatar attachments.
  • Render Attached Particles: Render particle systems emitted by avatar attachments.
  • Hover Glow Objects:
• Network: Opens the Network sub menu:
  • Pause Agent: Stop avatar movement updates. Local turns and interpolated motion will still appear.
  • Enable Message Log: Dump every protocol message to log.
  • Disable Message Log: Stop protocol message dump.
  • Velocity Interpolate Objects: When enabled it allows smoothed object motion between updates and for llTargetOmega motion to work. When it's disabled, stops “rubber band” effect at cost of these features.
  • Ping Interpolate Object Positions: Factor ping time into interpolation.
  • Drop a Packet (Ctrl-Alt-L): Simulate loss of a data packet.
• Dump Scripted Camera
• Recorder: opens the Recorder sub menu. This is used to record, and then playback, a sequence of your actions. For example, you can record yourself walking round, then when you play it back, your avatar will repeat that exactly. Useful for machinima.
  • Start Playback
  • Stop Playback
  • Loop Playback
  • Start Record
  • Stop Record
• World: Opens the World sub menu:
  • Sim Sun Override
  • Fixed Weather
  • Dump Region Object Cache: Send object cache statistics to log.
  • Dump Simulator Features to Nearby Chat
• UI: Opens the UI sub menu:
  • Media Browser Test: Opens embedded browser with Viewer URI Name Space test page.
  • Region Restart Test:
  • Web Content Browser (Ctrl-Shift-Z): Opens the internal browser.
  • FB Connect Test: For checking Second Life ShareAPI.
  • Dump SelectMgr: Info about selected objects to log.
  • Dump Inventory: Inventory UUIDs and names to log.
  • Dump Timers: Function call stats to log.
  • Dump Focus Holder: What UI element has keyboard focus to log.
  • Print Selected Object Info (Ctrl-Shift-P): Object details to log.
  • Print Agent Info (Shift-P): Avatar name and camera to log.
  • Double-Click Auto-Pilot
  • Double-Click Teleport
  • Debug SelectMgr: If this and Limit Select Distance are active, dump auto deselects to log.
  • Debug Clicks: Mouse button changes with coordinates to log.
  • Debug Views: Identify UI elements on screen.
  • Debug Name Tooltips: Identify XUI source for UI element under cursor. (alias of Show XUI Names)
  • Debug Mouse Events: Info about what has mouse focus to log.
  • Debug Keys: Text entry field activity to log.
  • Debug Window Process: Low level info for main viewer window to log.
• XUI: opens the XUI sub menu:
  • Reload Color Settings: Refresh from skin's colors.xml
  • Show Font Test: Open floater with type specimen.
  • Load from XML
  • Save to XML
  • Save XUI Names: Identify XUI source for UI element under cursor.
  • Show debugging info for views
  • XUI Preview Tool
  • Send Test IMs: Send dummy messages to test accounts.
  • Flush Names Caches: Clean avatar name cache.
• Avatar: Opens the Avatar sub menu:
  • Grab Baked Textures
    • Iris
    • Head
    • Upper Body
    • Lower Body
    • Skirt
  • Character Tests
    • Appearance To XML: Saves your avatar shape to a file; opens a file picker to allow you to select the destination folder, and file name. Shapes exported this way can be re-imported in the Appearance window.
    • Toggle Character Geometry
    • Test Male: Shortcut to wear “Male Shape & Outfit” from inventory Library/Clothing.
    • Test Female: Shortcut to wear “Female Shape & Outfit” from inventory Library/Clothing.
    • Allow Select Avatar: Avatars can be selected and “moved” with object editor, local effect only, movements do not appear to others.
  • Animation Speed
    • All Animations 10% Faster
    • All Animations 10% Slower
    • Reset All Animations Speed
    • Slow Motions Animations
  • Force Params to Default: Clear and refresh tweakable appearance settings.
  • Animation Info: Text over avatars with running animations and priorities.
  • Show Look At: Shows look at crosshairs.
  • Show Point At: Show destination for selection beam as a red crosshair.
  • Debug Joint Updates: Rapid summary of updates to log.
  • Disable LOD: For avatar bodies.
  • Debug Character Vis: Dump avatar and attachment visibility to log.
  • Show Collision Skeleton: Show avatar's “collision volume” joints. Used with fitted mesh and touch/select. Not used with simulator physics.
  • Show Bones:
  • Display Agent Target: Crosshairs with avatar's actual and rendered positions.
  • Dump Attachments: Attachment points, UUIDs, positions, visibility to log.
  • Debug Avatar Textures (Ctrl-Alt-Shift-A): Shows component textures for own avatar.
  • Dump Local Textures (Alt-Shift-M): Avatar texture info to log.
  • Reload Avatar Cloud Particle:
• Compress Images: Select a file and convert to .j2c, results to log.
• Enable Visual Leak Detector:
• Output Debug Minidump
• Console Window on next Run: Opens a window on the next run of the viewer, which shows internal information as the viewer runs. Useful for developers' to debug the viewer. Otherwise, keep this disabled.
• Set Logging level: This allows the level of detail of logging to be changed from the default (Info). The support team might request that you change this if attempting to diagnose a problem; otherwise, it should always be left at default.
  • Debug
  • Info
  • Warning
  • Error
  • None
• Request Admin Status (Ctrl-Alt-G): Request privileges. Only works if you are a Linden.
• Leave Admin Status (Ctrl-Alt-Shift-G)
• Show Admin Menu

It is possible to search the menus for specific words or phrases, by typing into the search bar at the top. For example, typing in the word upload will result in matches on up to four top menu items: Avatar, Build, Advanced and Develop. In short, using search will filter out what is shown in the top menu bar, removing all items except those that contain what you searched for.

Matched items are highlighed in color (you can change the highlight color in Preferences → Colors -> Miscellaneous→ Preferences Search Highlight Color).

To clear the search, and have the Preferences window revert to its normal state, just click the 'x' at the far right end of the search field.

Menu search is enabled (or disabled) in Preferences -> Advanced→ Show Menu Search.

: When hovering your mouse over this symbol, it will open the Graphics Presets window. Please note that this symbol will only show if you have created a graphic preset in Preferences→ Graphics -> General.

With this tab, you control who has access to your parcel.

• Access To This Parcel:
  • Allow Public Access: If this is enabled, anyone will be able to enter the parcel - other than banned residents (see below). If you disable it, ban lines will be created; restrictions specified on the rest of the tab then apply.
  • Restrict Access to Residents verified by:
    • Payment Information on File: If this is enabled, only residents who have payment information on file with LL will be allowed access to the parcel.
    • Age Verification: If enabled, only residents who have verified that they are adults, on the SL website, will be allowed access. Note that this is a parcel-level setting, and is not the same as the Adult setting, which is estate-level. It is possible to have Adult access without being age verified.
• Allow Group Access: Enabling this allows you to restrict access to members of the group that the parcel is set to, on the General Tab.
• Sell Passes to: Check to charge an admittance fee to your parcel and set the time period for which those passes are valid.

• Allowed Residents: Use the Add button to open the Avatar Picker window to add Residents who will always have access to your parcel. Select a Resident name from your Allowed Residents list and click Remove to remove them from the list.

• Banned Residents: Use the Add button to open the Avatar Picker window to add Residents who will not have access to your parcel. Select a Resident name from your Banned Residents list and click Remove to remove them from the list.

NOTE: Ban lines for residents who are explicitly excluded from entry to a parcel, extend up to 768m above the ground; for residents excluded by other means (eg, not age verified, not members of the group, etc), the ban line extends to 50m above the ground. (Ref. SL Wiki on Limits.)

< Previous Tab

With this tab, you control who has access to your parcel.

• Access To This Parcel:
  • Anyone can visit: If this is enabled, anyone will be able to enter the parcel - other than banned residents (see below). If you disable it, ban lines will be created; restrictions specified on the rest of the tab then apply.
    • Must be 18+: If enabled, only residents who have verified that they are adults, on the SL website, will be allowed access. Note that this is a parcel-level setting, and is not the same as the Adult setting, which is estate-level. It is possible to have Adult access without being age verified.
    • Must have payment Info on File: If this is enabled, only residents who have payment information on file with LL will be allowed access to the parcel.
• Allow group xxx without restrictions: Enabling this allows you to restrict access to members of the group that the parcel is set to, on the General Tab.
• Sell Passes to: Check to charge an admittance fee to your parcel and set the time period for which those passes are valid.

• Always allowed: Use the Add button to open the Avatar Picker window to add Residents who will always have access to your parcel. Select a Resident name from your Allowed Residents list and click Remove to remove them from the list.

• Always banned: Use the Add button to open the Avatar Picker window to add Residents who will not have access to your parcel. Select a Resident name from your Banned Residents list and click Remove to remove them from the list.

NOTE: Ban lines for residents who are explicitly excluded from entry to a parcel, extend up to 5000m above the ground; for residents excluded by other means (eg, not age verified, not members of the group, etc), the ban line extends to 50m above the ground. (Ref. SL Wiki on Limits.)

< Previous Tab

This tab deals primarily with access control to the region/estate you own or manage. If the estate comprises several regions, changes made will optionally be applied to all regions.

The top lines are informative: the who the name of the estate and the estate owner.

The next section concerns broad access rights and options:

• Allow public access: If enabled, then any resident may access the region/estate - unless otherwise excluded (see below for ban lists). If this is unchecked, then only residents who are specifically allowed in other sections of this tab, will be allowed access. Blocking access this way overrides any parcel access controls that might be set.
• Restrict Access to accounts verified by: These settings add global restrictions:
  • Payment Information on File: If enabled, residents will have to have payment info on file with LL in order to gain access to the region/estate.
  • Age Verification: If enabled, residents will have to be age verified in order to gain access to the region/estate. This can be independently of marking a region as Adult in the Region Tab.
• Allow Voice Chat: If enabled, resident will be able to use local voice chat; otherwise this will not be available (thought private voice IM will be).
• Allow Direct Teleport: Lets Residents teleport to specific locations within your estate's regions. If you want to force visitors to arrive at a specific area in the estate, disable this and use a telehub. If this is enabled, parcels can still set landing points.

The four lists below manage specific inclusions and exclusions to estate access. Below each are two buttons:

• Add: Opens the Avatar Selector to allow you to select people to add to the list.
• Remove: Removes the currently selected avatar(s) from the list.

• Estate Managers: The estate/region owner may specify up to 10 people who can manage the estate on their behalf. Only the owner can add/remove people here. Estate rights gives a great deal of power, so be very careful before granting such rights to anyone.
• Allowed Residents: Here you can specify individuals who will have access to the estate/region. (Note that allowed avatars may be banned at parcel level.)
• Allowed groups: Clicking Add will open the Groups Selector, which you can use to add up to 63 groups. Members of these groups will be allowed access to the region/estate.
• Banned Residents: If you wish to prevent people from accessing the region/estate, they may be added here.

Finally, two buttons:

• Send Message to Estate: Allows a message to be broadcast to the entire estate.
• Kick Resident from Estate: Opens the Avatar Selector to allow you to select someone to be expelled from the region/estate. Note: This doesn't automatically add the person to the list of banned users.

^ Main Page - Next Page >