Please note: Viewers play a minor part in voice functionality. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons:

• Your ISP is throttling or blocking the voice service;
• failure of the Vivox service;
• voice issues on the region you are on;
• voice being throttled by bandwidth set incorrectly - please check it by following the instructions here;
• voice hardware (mic, headset) not configured correctly in your operating system settings;
• voice hardware not configured correctly in the viewer;
• another application has your voice hardware in use (example, Skype);

• your anti virus software has “mangled” the voice application; see steps on this page: here.

• your firewall is blocking slvoice. Add slvoice to your firewall's exclusion/allow list.

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

nslookup command how-to: WindowsMacLinux

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

Steps:

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

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

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

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

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

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

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

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

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

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

Some details provided below.

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

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

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

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

You can also try adjusting your bandwidth as explained here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Install the additional libraries

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

These two packages provide support for voice and media services.

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

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

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

If you plan to use the win32 voice files, also install and configure wine-stable

sudo apt install wine-stable
winecfg #Set the Windows version to Windows 10, then test the audio output.

In the viewer, set the debug setting FSLinuxEnableWin32VoiceProxy to true, then try enabling voice.
It may take a few seconds for voice to connect. If it does not, check your viewer log to see if anything obvious appears. If you had an existing .wine folder, you may want to try logging out, delete that folder, then run winecfg and create a new one, then test voice again.

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

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

In a terminal, type:

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

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

cd ~/Firestorm
./firestorm

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

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

~/Firestorm/etc/refresh_desktop_app_entry.sh

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

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

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

NOTE: You can turn off debugging with:

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

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

sudo apt install wine-stable
winecfg

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

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

There are many ways of getting great free stuff in SL to make your avatar look fantastic! There are many landmarks on this page; a G, or M indicates if the region is rated General or Moderate. To go to these shops, click on the landmark, a new web page will open, then click on teleport.

Free Dove has lots of quality stuff- look around carefully when you are there, because they usually have “hunts” with gifts from very good designers - these will be in small boxes or objects hidden everywhere in the shop.

The Bazaar Linden-support free stuff place, which anyone can contribute to. Mostly older things, but still much that may be helpful in getting started in SL.

The Stay at Home Club: Started during the COVID-19 crisis, this sites lists places offering free items in a number of categories. Click here to visit the site, then on Gifts at the top.

You can find a lot of free stuff on the marketplace. A good idea is to include the word “gift” in your search. Some items you might find useful:

• Female AO (to make your avi move naturally)
• Male AO
• Makeup
• Skins: type “skin gift” in the search slot and you'll get quite a lot - mostly female but some for the boys too!

Most designers have a group for their shop, which they use to send people news about new releases and events - if you join their group you will get gifts, generally on a monthly basis, but sometimes more often. Sooo… when you visit a shop, look out for group gifts - there is usually a group joiner next to them, and clicking on it you get instructions in local chat how to join the group. Some groups have a join fee, sometimes quite expensive, but many are free. Also, you'll find lucky chairs and lucky boards - if your name starts with the letter displayed on them, you win the prize.

Some stores offer free items for the Residents new to Second Life, some with an age limit to be eligible to collect these gifts - eg:- Under 30 days of age.

• Free hair pack to New Residents (2 weeks and younger) Just send a notecard with your name and hairstyle choice & color to * No Match Owner
  No Match Store location :- * No Match Hair Store

• Free clothing for men - Kauna (no age limit)

• SEmotions free AO Bento - SEmotions (90 Days and younger)

• TuTy's free AO Bento - TuTy's (no age limit)

• Firelight free male & female hair - !! Firelight !! (some 30 days and younger, many free group gifts)

• Amazing Creations free male & female clothing - AmAzInG CrEaTiOns (group gifts, free to join, no age limit)

• JStyle free male & female clothing - jStyle (group gifts, free to join, no age limit)

• WarBug HQ bizarre and questionable gadgets and accessories - WarBug HQ (no group required, no age limit)

Many others available please use your search.

Another good idea is to Join an Inworld freebie shopping group! Not only will you be kept updated with all the latest freebies, but you can also get help and support to find the shops you are looking for.

There are quite a few around, but this one is probably the most popular: (to join, right-click the “group joiner” below, select “Copy to Clipboard”, then paste it in local - then click on the link that will appear)
Group joiner

Some good blogs featuring a lot of freebies:

• Fabulously Free in SL
• The SL Fashionista
• Teleport Hub
• Go Dutch
• Scoop It

And last but not least, there are treasure hunts! These are a really fun way to find new places and shops and get awesome free stuff!

You'll find the info to get you started here:

• Seraphim Hunts & Games Register
• FabFree SL Hunt Guide

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

See http://wiki.secondlife.com/wiki/Environmental_Enhancement_Project for info.

• Load: Click this to load an existing sky into the editor.
• Import: Import an existing sky into your current sky.

This controls the color and intensity of ambient light in the atmosphere. This is used for simulating how the light from the sun is scattered by the atmosphere and other objects once it hits the Earth. You can create a very bright sun, and a relatively dark world (think of a sunset) with an Ambient setting of zero, but if you want to simulate mid-day illumination while the the sun was low in the sky, you need to increase the Ambient setting. This setting also controls how dark shadows are: darker ambient makes darker shadows.

Adjusts the color of the sky. In meteorological terms, this setting affects “atmospheric scattering”, which is the scientific answer to the age-old question, "Why is the sky blue?"

Blue Density affects the overall color saturation of your sky. Brighter colors make everything brighter and more vibrant. Darker colors make things become duller, eventually fading to black and white.

This setting affects the height of haze on the horizon. At higher settings, the haze will reach up into the sky and obscure the actual horizon. Haze on the horizon can help to accentuate the sun, and create a dusty, smoggy, or humid effect. This setting will not work if Haze Density is set to zero.

Haze density affects the amount of haze you can see in the atmosphere. At lower settings, this can make for some great outdoor views in dusty or tropical environments, and at higher levels it can create a thick, vision-obscuring fog. If you set Haze Density to zero, the Haze Horizon setting will have no effect.

Controls the level of moisture (think rain) in the atmosphere. Higher values will create a rainbow opposite the sun.

This is a physical parameter affecting the shape and distribution of the colors in the rainbow.

Higher value create a halo round the sun.

This control adjusts your screen's distribution of light and dark output. Lower settings will cause everything to appear dim, while higher settings may make the scene look gray and “washed out”. Scene Gamma is more precise than the older Gamma in that it only affects your rendered view of the SL world, not the menus and rest of your computer's screen.

The Density Multiplier can be used to affect the overall atmospheric density. At lower settings, it creates a feeling of “thin air”, and at higher settings, it creates a very heavy, smoggy effect.

This setting affects your perceived distance within the atmosphere. To make everything look hazy and distant, move the slider to the right. If you want to completely remove the Sky Settings' effects from terrain and objects, set the slider to zero.

Adjusts the altitude calculations Second Life makes when it is computing atmospheric lighting. At later times of day, it can be useful for calculating how “deep” a sunset appears, while at noon it can be used to achieve proper brightness values.

This affects the color of your clouds, if you have any. Use the individual Red/Green/Blue sliders to change the color, or the Intensity (I) slider to drag all three at once.

As the name implies, this control sets the amount of cloud coverage. At zero, there isn't a cloud in the sky, but at higher settings, you can get a completely overcast effect.

This setting affects the perceived altitude of the clouds… if you slide the control to the right, it will make the clouds appear to be higher in the sky.

These sliders affect the direction and speed at which the clouds float in the sky. You may also check the Lock checkbox to prevent clouds from moving on the selected axis.

You can replace the default cloud image. A few textures are provided in the Library, under Environments, Textures. Or you can make your own.

• Creating Clouds
• Starfields: Step by step gimp tutorial here.
  Starfields can be used as cloud textures, but in that case, they need to be grey-scale.

Use the X and Y sliders to change the horizontal position of all clouds in the sky. The D slider affects the overall density of the individual clouds; at low settings you will see thin, wispy clouds, and at higher settings you will see thicker, more solid clouds.

These settings affect the detail imagery of your clouds. The X and Y sliders shift its horizontal position, and the D slider controls how puffy and/or fractured your clouds look.

Use the orbs to drag the sun and moon around the sky. To get the sun or moon over the horizon, press and hold the Ctrl key while dragging.

You can replace the default textures for both the sun and moon. As always, the larger the image, the longer it will take to render. 512 is a good size. Scale allows you to control how large the sun or moon are. You an also change the brightness of the moon.

Several textures are provided in the Library, under Environments, Textures. Or you can make your own.

• Planets:Creating Planets and Planetary Rings in GIMP

This setting affects the color of the light your sun and moon produce. Keep in mind that the color of your sunlight/moonlight will affect the color of your sky.

There are two settings under Sun Glow: Size defines the size of the sun, and Focus adjusts how much the sun blurs over the sky. At very high settings, Focus can cause the sun to completely wash out a portion of the sky with brilliant light, and at zero, it will cause the sun (but not the light it casts) to disappear from the sky.

Star Brightness defines how visible the stars are in the sky. If you play with this slider while the sun is up, you can see stars in the middle of the day.

This draws a direction line from your avatar toward the sun or moon.

Many explanations taken from this SL wiki page.

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

See http://wiki.secondlife.com/wiki/Environmental_Enhancement_Project for info.

This changes the color of the particulate matter in your water, essentially defining the color of the water itself. If your water has no fog, it will appear crystal clear and colorless.

Controls the density of your water fog; this setting defines how far you are able to see into the water.

Controls how the fog density changes when you are underwater. Useful for creating far-seeing views when underwater while keeping the surface fairly opaque. For example, at a setting of 0.25, the water fog is 1/4 as dense while underwater as it appears from above the surface.

Determines how much light is reflected at different angles; increasing this slider reduces visual reflection effects on the water's surface.

Determines how much total light is reflected; increasing this slider increases the amount of light reflected by the water's surface.

Controls the normal map used for determining reflections and refractions. Any texture may be used for this setting- but true normal maps work best.

Controls the scale of the three wavelets that make up the surface of the water.

Controls the X and Y direction and speed of the large wave image.

Controls the X and Y direction and speed of the small wave image.

Controls the amount of visual refraction you can see from above the water's surface; this is the “wobbly” effect you can see when you look at an object that is underwater.

Controls the amount of visual refraction you can see from below the water's surface. This is the “wobbly” effect you can see when you look at an object that is above the water.

Controls how waves and reflections are mixed. Increasing this setting increases the amount of distortion you see in reflections as a result of wave activity.

Many explanations taken from this SL wiki page.

• Skies
• Water
• Days

• My Environments window

• Parcel Details -> Environment
• Region details -> Environment

• Second Life EEP wiki
• SL's post EEP Is Out! Introducing the Environmental Enhancement Project for a full description.
• For complete instructions, see SL’s Knowledge Base: Environment Editor
• For discussion you can follow SL’s EEP forum.
• Here’s a thread where you can give Feedback to SL.
• For those interested, you can see a filtered list of current issues with EEP in the official SL viewer on SL’s bug-reporting site. Remember to log into the site using your SL user name and password.

• See Inara Pey’s blog post Environmental Enhancement Project: A Primer.
• Inara Pey also has a blog post on this Firestorm EEP Beta: Firestorm 6.4.5 Beta: EEP and Camera Presets.
• Inara Pey also has an EEP tutorial.

Note: Approximately 200 Windlight settings have already been imported and can be found in Library → Environments folder. They are also visible in Quick Preferences and can be selected there.

If you wish to adapt or modify one of the built-in EEP settings, copy it from the Library to your Settings folder:

1. Expand the folders in Library → Environments → Days, Skies, or Water.
2. Right-click and copy as desired to your Inventory → Settings folder.

To import your other old Windlight settings into EEP:

1. Create a new Settings item in inventory (right click Settings folder or a subfolder → New Settings → New Sky, Water, or Day Cycle).
2. Open that new settings item.
3. Select the Import button; this will open a file picker dialog.
4. Navigate to where you have stored your Windlight XML files and select the file you would like to import:
   • Windows:
     • C:\Program Files\Firestorm_64\app_settings\windlight (old built-in Windlights)
     • C:\Users\User\AppData\Roaming\Firestorm_x64\user_settings\windlight (personalized custom files)
   • Mac
     • ~/Applications/Firestorm_64; right click > show package contents > Contents/Resources/windlight (old built-in Windlights)
     • ~/Library/Application Support/Firestorm/User Settings/Windlight (personalized custom files)

You should import Windlights of the same type as the editor you have open (Day Cycle, Sky, or Water). For example, to import a Sky, create and open a Sky setting from inventory. On your hard drive, you should find the files laid out as follows: ./windlight/days ./windlight/skies ./windlight/water.

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

• Starfields: Step by step gimp tutorial here.
  Starfields can be used as cloud textures, but in that case, they need to be grey-scale.
• Planets:Creating Planets and Planetary Rings in GIMP

• How can I easily create cloud texture maps?

The purpose of this section is to provide help for those new to Second Life, irrespective of the viewer used or their entry point into SL. Given that different viewers are available, where possible, the information given assumes that the official Second Life viewer is the being used.

If you are looking for information on Firestorm features and functions, click here. If you need help with Firestorm viewer, click here. We also offer classes on how to use the Firestorm viewer. See this page for the schedule and in-world locations.

You can join Second Life via the web page given here:

• Create Second Life Account

If you want to invite friends to join, then please do share the link above with them.

• What is Second Life?
• Huck’s absolute beginner’s guide to Second Life for the coronavirus curious
• General Second Life Resources

• How Does Clothing Work?
• How Do I Mod My Shape?
• Where Can I Get Good Free Stuff?
• How Do I Use Furniture?
• How Do I Use the Camera?
• How Can I Earn L$ in SL?
• Why Am I Wearing a Box? (Unpacking Boxes)
• How Do I Talk to People?
• How Does My Inventory Work?
• How to Make a Landmark/Set Home
• What Are Groups?
• What Should I Know About Mesh Bodies, Heads and Omega Appliers?
• What Do All Those Acronyms Mean?
• Why Do I See Some People as Colored Blobs?
• How Can I Defend Against Bad People?

• SL Knowledge Base
• Second Life YouTube Channel

• Getting Started in Second Life
• Chat, IMs, Voice
• Appearance Mini-Series Videos
• Shopping & Buying Linden Dollars
• Getting a Home in Second Life - Premium Members
• How To Get Help

• Exploring Second Life
• Popular Entertainment
• Firestorm Gateway Scifi Portal
• Games Made in Second Life - Tabletop Gaming in Virtual Worlds
• Learning Made in Second Life - CNDG
• Tyrah and the Curse of the Magical Glytches
• Horizons Adventure
• Paleoquest

Dashboard - Second Life

My Second Life

Second Life Forums

Second Life Community

Knowledge Base - Second Life

• How to Contact Customer Support
• Linden Homes
• Creating, Managing, Moderating and Disbanding Groups
• Group Owned Land
• Tilia FAQ

• Second Life Wiki - Welcome Page
• Second Life Wiki - Limits
• Second Life Wiki - Good Building Practices
• Second Life Wiki - Aditi / Beta Grid

• Firestorm Wiki - Help for New Residents
• Inara Pey: Living in a Modem World - SL TUTORIALS INDEX
• Inara Pey: Living in a Modem World - TUTORIAL: RAISING ABUSE REPORTS IN SECOND LIFE
• Second Life Grid Survey - Region Database
• Second Life Avatar Data

Second Life Twitter

Second Life Grid Status Twitter

Linden Lab Twitter

Second Life Official Flickr Photos

Second Life Official Flickr Group

Second Life Instagram

Second Life Facebook

Second Life YouTube

• Ivory Tower Library of Primitives
• Particle Laboratory Learning Center
• The Vehicle Laboratory Learning Center
• Texture Tutorials
• College of Scripting Music & Science
• Builder's Brewery
• Caledon Oxford Lecture Hall
• Happy Hippo Building School
• The Tower - History of Second Life 1999-2020

• Alchemy Viewer
• Catznip Viewer
• Firestorm Support English
• Kokua Viewer
• Black Dragon Viewer
• Singularity Viewer
• Cool VL Viewer Forum

Firestorm 6.3.9 (58205) Release Notes

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

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

Firestorm 6.3.9 (58205) Release Notes

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

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

Please read https://support.microsoft.com/en-au/help/4520411/adobe-flash-end-of-support before considering installing flash. Flash has a LONG history of very serious security issues. If someone is providing content that only works with flash, please contact them and let them know that flash will be end of life in the near future, this means there will be NO security updates from the vendor beyond that point. Nobody should be forcing flash on anyone in this day and age, it is 2020, not 2001 anymore.

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

• Mac - 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.
  Choose the correct operating system under Step 1.
  Choose FP 32 for Safari and Firefox – NPAPI under Step 2.
  Install Flash.

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

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

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

for Linux only

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

• Growl for Windows– As of November 2018 this site is dead. Users who already have Growl installed can continue to use it for the time being. Windows users may be able to download a copy from its github release page.

• Mac– This site will lead you to the Mac App Store for downloading. Please note the reviews and the update status of Growl before purchasing; Firestorm cannot guarantee its functionality.

• Linux: Growl is implicit in libnotify, which should come already installed in most distros. However, if you are on a 64-bit Linux, you may need to install the 32-bit version of libnotify. For ubuntu and similar (like mint), run the following command:
  sudo apt-get install libnotify4:i386

Windows only

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

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

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

• Latest driverLast checked 24/05/2020 - Windows: 445.87 (2020.4.15) - Linux: 440.82 (2020.4.7)

• Latest driverLast checked 24/05/2020 - Windows: Adrenalin 2020 Edition 20.2.2 (3/5/2020) - Linux: 20.10 (4/16/2020)
  

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

https://vcs.firestormviewer.org/

Firestorm 6.3.2 (58052) Release Notes

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

Firestorm 6.2.4 (57588) Release Notes

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

Firestorm 6.0.2 (56680) Animesh Release Notes

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

This procedure is used for building Firestorm for Linux. It is the only recommended procedure for building Firestorm for Linux.

This procedure is based on discussions with the Firestorm Linux Development team and is the only one recommended for Firestorm for Linux. System requirements are:

1. Ubuntu 16.04.6_x64
2. 8GB or more RAM Low Memory Caution
3. 64GB hard drive space
4. 4 or more core CPU (you could get by with 2 cores, but the process will take much longer)

Due to the age of the build OS, it is recommended that you use a Virtual machine, ensuring the guest can meet the hardware requirements.

This procedure may or may not work on other Linux distributions.

This only needs to be done once.

Typically, Linux source code is stored in a src directory in your home directory. So:

mkdir ~/src

A large number of development libraries must be installed on the build system. Some may already be installed:

sudo apt install libatk1.0-dev libatk-bridge2.0-dev libatspi2.0-dev/xenial libcups2-dev libcurl4-openssl-dev libfreetype6-dev \
libglu1-mesa-dev libgtk2.0-dev libgtkglext1-dev libnss3-dev libssl-dev libpango1.0-dev \
libpangox-1.0-dev libpangomm-1.4-dev libx11-xcb1 libxcb1-dev libxcb-composite0-dev libxcb-cursor-dev \
libxcb-dri3-dev libxcb-screensaver0-dev libxcb-util-dev libxcb-util0-dev libxcb-xkb-dev libxcomposite-dev \
libxcursor-dev libxdamage-dev libxi-dev libxinerama-dev libxkbcommon-x11-dev libxrandr-dev \
libxss-dev 

The following packages are the tools necessary for building the viewer. Some may already be installed.

sudo apt install build-essential gdb mesa-common-dev python-pip unzip \
x11proto-dri2-dev x11proto-dri3-dev x11proto-randr-dev x11proto-xf86dri-dev \
x11proto-xinerama-dev x11proto-scrnsaver-dev xcb xcb-proto 

Cmake version 3.18 is required but not available in Ubuntu's repositories, we have to build it from source

wget https://github.com/Kitware/CMake/releases/download/v3.18.0/cmake-3.18.0.tar.gz
tar xvf cmake-3.18.0.tar.gz
cd cmake-3.18.0
./bootstrap --parallel=$(nproc) --prefix=/usr && make -j $(nproc) && sudo make install

To ensure the best compatibility, we'll also build git from source

cd ~/src
sudo apt install dh-autoreconf libcurl4-gnutls-dev libexpat1-dev \
  gettext libz-dev libssl-dev asciidoc xmlto docbook2x install-info
wget -O git-2.28.0.tar.gz https://github.com/git/git/archive/v2.28.0.tar.gz 
tar -zxf git-2.28.0.tar.gz
cd git-2.28.0
make configure
./configure --prefix=/usr
make -j $(nproc) all doc info
sudo make install install-doc install-html install-info

When you need to update git, use

git clone git://git.kernel.org/pub/scm/git/git.git

Or, you can install git from the Ubuntu repository:

sudo apt install git

Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild from Linden Lab, version 1.1 or above.

sudo pip install --upgrade pip
sudo pip install autobuild

There are two required repositories, the viewer itself and the build variables. An optional third repository is used to configure and package FmodStudio.

cd ~/src
git clone https://vcs.firestormviewer.org/phoenix-firestorm

This will create a folder called phoenix-firestorm and add all the source files. If you desire, you can choose a different folder name by adding the name to the end of the command:

git clone https://vcs.firestormviewer.org/phoenix-firestorm NewDestinationDirectory

The rest of this document will assume the default directory, phoenix-firestorm

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations.

cd ~/src
git clone https://vcs.firestormviewer.org/fs-build-variables

Although not required, including FmodStudio in your build will improve your audio-based experience in SL.

cd ~/src
git clone https://vcs.firestormviewer.org/3p-libraries/3p-fmodstudio
cd ~/src/3p-fmodstudio

Open the file called build-cmd.sh and look at the fifth line down, it begins with FMOD_VERSION. This is the version of the API you need to download.

The FMOD Studio API can be downloaded here (requires creating a free account to access the download section). Log in as needed, then go to https://www.fmod.com/download. Click FMOD Studio Suite to expand that, then scroll down to FMOD Engine.

Click the button representing the version you're after, then click the Download link for the Linux file.

Copy that file to the ~/src/3p-fmodstudio directory.

export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables
autobuild build -A 64 --all
autobuild package -A 64

Near the end of the output you will see the package name written and the md5 hash below it, similar to:

wrote !/home/username/src/3p-fmodstudio/fmodstudio-2.01.02-linux64-202161533.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

cd ~/src/phoenix-firestorm

Copy the FMOD Studio path and md5 value from the package process into this command:

autobuild installables edit fmodstudio platform=linux64 hash=<md5 value> url=file:///<fmodstudio path>

For example:

autobuild installables edit fmodstudio platform=linux64 hash=c3f696412ef74f1559c6d023efe3a087 url=file:///!/src/3p-fmodstudio/fmodstudio-2.00.07-linux64-200912220.tar.bz2

Start by initializing the variables

export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

You can add that to ~/.bashrc or ~/.profile so they execute automatically, or execute them before you run autobuild.

cd ~/src/phoenix-firestorm
autobuild configure -A 64 -c ReleaseFS_open

This will set up to compile with all defaults and without non-default libraries. It will fetch any additional necessary libraries.

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.
• clean will cause autobuild to remove any previously compiled objects and fetched packages. It can be useful if you need to force a reload of all packages
• package will result in a bzip2 archive of the completed viewer. Enabled by default, you would have to use -DPACKAGE:BOOL=Off to disable it
• chan will set a unique channel (and the name) for the viewer, appending whatever is defined to “Firestorm-”. By default, the channel is “private” followed by your computer's name.
• fmodstudio will tell autobuiild to use the FmodStudio package when compiling.

Most switches start with a double-dash (--). And if you use any switches you must enclose them with a double-dash at the start and an optional double-dash at the end.

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE

Examples:

autobuild configure -A 64 -c ReleaseFS_open -- -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -c ReleaseFS_open -- --clean
autobuild configure -A 64 -c ReleaseFS_open -- --chan="MyBuild"

In the last example, the channel and resulting viewer name would be “Firestorm-MyBuild”.

The first time you configure, several additional files will be downloaded from Firestorm and Second Life sources. These are mostly binary packages maintained outside the viewer development itself. And if you use the –clean switch, you will re-download them all.

autobuild build -A 64 -c ReleaseFS_open

Be sure to use the fmodstudio and chan switches again.

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -A 64 -c ReleaseFS_open – –clean [more switches]). For clarity, they are mentioned separately.

If you build the viewer using a virtual machine (guest), you will need to copy the viewer files over to your host or to a different machine in order to use the viewer. Your guest may not have sufficient resources to run the viewer. The rsync program can make copying easy and accurate. And if you build the viewer again, the options included in the command example will cause rsync to only copy the new files, cutting down on the time needed to copy.

The build process created an ready-to-use viewer as well as a compressed archive. The archive can be copied or moved to any shared filesystem, such as a flash or cloud drive, and using it would be no different than using the official release.

cp ~/src/phoenix-firestorm/build-linux-x86_64/newview/Phoenix*.tar.* /path/to/shared/drive

or

mv ~/src/phoenix-firestorm/build-linux-x86_64/newview/Phoenix*.tar.* /path/to/shared/drive

When copying the ready-to-run folders and files, use

rsync -rptgoDLK --update --progress ~/src/phoenix-firestorm/build-linux-x86_64/newview/packaged/* /path/to/destination

Using rsync has the advantage of updating the destination, replacing only those files that changed or are missing, which takes much less time than copying and replacing every file.

Create the desktop launcher after copying to the destination machine

cd /path/to/firestorm
etc/refresh_desktop_app_entry.sh

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

cd /path/to/firestorm
./firestorm

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

• Firestorm Self-Compilers group:Firestorm Self Compilers is free to join, fellow self-compilers may be able to offer assistance.

• IRC: The #phoenixviewer-dev channel is the best place to look for solutions.
  A lot of self-compilers and project developers hang out there and are ready to help you.

• Jira:JIRA may contain resolved issues related to the error you're seeing.
  Search using the error you encountered. Or create a new issue to report an error in this document, or if a code change causes a build process to fail.

• Included documentation: In the Firestorm program directory are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date. Also, in the firestorm script file are comments and options you can adjust.

• Virtual Memory Exhausted, or similar out-of-memory issues

  may occur if you are building the viewer for the first time, or re-building after a very large set of changes were added. Sometimes restarting the build command will let you recover, sometimes you have to restart the build system. To avoid that from happening, add a lot of swap space, something on the order of 2GB or more. This page shows you how.

• Missing libraries/applications/packages This may occur if you did not or could not install the packages shown above, or are attempting to use this procedure with a different Linux OS, or are attempting to build a 32-bit viewer. Start over, making sure you are using the right OS, reinstall all packages as listed, and do not attempt to make a 32-bit viewer.

• Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet. Compiling with FModStudio may resolve this issue.

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program directlry, you will find various commented options. Uncommenting one or more may help restore sound, as can compiling with FModStudio. Refer also to the README.Linux.txt and README-linux-voice.txt files in the program directory.

• Voice Won't Connect Refer to this link or the relevant link on this page to ensure your computer is correctly configured.

This page describes all necessary steps to build the Firestorm viewer for Linux, on Debian 10, using the updated build infrastructure introduced with Linden Lab's project Alex Ivy. It assumes you are using Debian 10, that your normal user has sudo privileges and that all standard updates have been applied using apt *upgrade*

Minimum hardware required: At least 4GB RAM with 4GB+ swap, a modern dual-core CPU and 32GB available HDD space. Minimum recommended: 8GB or more RAM, CPU with 4 or more real cores and 32GB available HDD space.

This is needed for compiling any viewer based on the Linden Lab open source code and only needs to be done once.

All installations are done with default settings (unless told explicitly) - if you change that, you're on your own!

The required tools, some of which may already be installed, are:

make | cmake | g++ | gdb | git | python-pip

sudo apt install --install-recommends make cmake g++ gdb git python-pip

(the –install-recommends flag tells apt to install all packages recommended by each named package.)

These libraries may be included with your distribution, and some may already be installed:

sudo apt install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that automates the configure and build processes.

sudo pip install --upgrade pip
sudo pip install autobuild

This will install autobuild and add a link in the exec path.

Typically, source code is stored in your home directory, in a subdirectory called src. Your home directory shound have at least 32GB available before downloading the source code.

mkdir ~/src #This may throw an error if the directory already exists
cd ~/src

This document will assume that all downloaded code will go into this src directory.

In order to make it easier to build collections of related packages (such as the viewer and all the library packages that it imports) with the same compilation options, Autobuild expects a file of variable definitions. This can be set using the environmenat variable AUTOBUILD_VARIABLES_FILE.

cd ~/src
git clone https://vcs.firestormviewer.org/fs-build-variables
source fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

There are several repositories available, in but the one wea re after is the development repository. You can grab all the sources if you wish, but but keep in mind that each FS source requires around 110MB initially and around 4.3GB after the binaries have been built, plus possible compiling overhead.

git clone https://vcs.firestormviewer.org/phoenix-firestorm

This can take a bit, it's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

If you want to use FMOD Studio to play sounds within the viewer, you will have to download your own copy. FMOD Studio can be downloaded here (requires creating a free account to access the download section).

cd ~/src
git clone https://vcs.firestormviewer.org/3p-libraries/3p-fmodstudio

• After you have cloned the repository, copy the downloaded FMOD Studio installer file to ~/src/3p-fmodstudio
• If you downloaded a different version of FMOD Studio that is currently used in the viewer, you will have to modify the file build-cmd.sh in the root of the repository. Right at the top, you find the version number of FMOD Studio you want to package (one short version without separator and one long version). Change these values to the version you downloaded:

FMOD_VERSION="20007"
FMOD_VERSION_PRETTY="2.00.07"

cd ~/src/3p-fmodstudio
autobuild build -A 64 --all
autobuild package -A 64

Near the end of the output you will see the package name written and the md5 hash below it:

wrote !/src/3p-fmodstudio/fmodstudio-2.00.07-linux64-200912220.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

where {version#} is the version of FMOD Studio (like 2.00.03) and {build_id} is an internal build id of the package.

cd ~/src/phoenix-firestorm

Copy the FMOD Studio path and md5 value from the package process into this command:

autobuild installables edit fmodstudio platform=linux64 hash=<md5 value> url=file:///<fmodstudio path>

For example:

autobuild installables edit fmodstudio platform=linux64 hash=c3f696412ef74f1559c6d023efe3a087 url=file:///!/src/3p-fmodstudio/fmodstudio-2.00.07-linux64-200912220.tar.bz2

 cd ~/src/phoenix-firestorm
 autobuild configure -A 64 -c ReleaseFS_open

This will configure Firestorm to be built with all defaults and without third party libraries.

autobuild configure -v -c ReleaseFS_open

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• -A <architecture> sets the target architecture, that is if you want to build a 32bit or 64bit viewer (32bit is default if omitted).
• –fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps above for this to work.
• –package makes sure all files are added to a compressed tar file for easy distribution and storage.
• –chan <channel name> lets you define a custom channel name for the viewer
• -LL_TESTS:BOOL=<bool> controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.

Examples:

• To build a 64bit viewer with FMOD Studio and to create an installer package, run this command in the Windows command window:

  autobuild configure -A 64 -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

• To build a 64bit viewer without FMOD Studio and without installer package, run this command:

  autobuild configure -A 64 -c ReleaseFS_open -- --chan MyViewer -DLL_TESTS:BOOL=FALSE

Make sure you include the same architecture parameter and switches (except clean) you used while configuring the viewer:

autobuild build -A 64 -c ReleaseFS_open

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -A 64 -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged
./firestorm

Your file browser/file manager many not know how to execute a script. Check the settings for your file browser. In Nautilus, for example, open Preferences > Behavior tab, change the action for executable text files to either Run or Ask.

Copy or move the contents of ~/src/phoenix-firestorm/build-linux-x86_64/newview/packaged to a place that can be access by the PC you want to install Firestorm on. Cloud-based storage, NAS or removable media would do.

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

• Self-Compilers peer supportFirestorm Self Compilers is free to join, fellow self-compilers may be able to offer assistance.
• IRC: The #phoenixviewer-dev channel is the best place to look for solutions.
  A lot of self-compilers and project developers hang out there and are ready to help you.

• Jira:JIRA may contain resolved tickets.
  Search using the error you encountered.

• Included documentation: In the Firestorm root folder are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date.

If you found a procedural error in this document, please let us know in as much detail as you can, either contact the author (preferred) or discuss on IRC.

• Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Debian repositories, so make sure you did not disable those. If you find that a library or application is in a different package for your system, contact the team with the name of the library or application, the name of its package and your Linux OS so that information can be checked and added here.

• Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

This page describes all necessary steps¹⁾ to build the Firestorm viewer for Linux on Ubuntu 20.04, using Linden Lab's project Alex Ivy infrastructure. It assumes you are using Ubuntu 20.04 Focal Fossa, that your normal user has sudo privileges and that all standard updates have been applied using apt *upgrade*.

To successfuly compile Firestorm your computer must have at least 4GB RAM with 4GB+ swap, a modern dual-core CPU and 32GB available HDD space. However we strongly recommended you have 8GB or more RAM, a modern CPU with 4 or more real cores and 32GB available HDD space. You may require more HDD space if you compile different viewers, or different variations of Firestorm.

We're going to follow some conventional ideas on compiling software. Primarily, we will create a directory to contain all the source files. Open a terminal (in which we will work from here on).

cd #to jump to the home directory
mkdir -p src/sl/vorbis src/python-pip
cd src

Now to install the various programs used to build the viewer.

All installations are done with default settings (unless told explicitly) - if you change that, you're on your own!

The required tools, some of which may already be installed, are:

sudo apt install --install-recommends make cmake curl doxygen gdb git python2 python2-dev python-all

(the –install-recommends flag tells apt to install all packages recommended by each named package.)

Pip for Python 2.7 is not available to Ubuntu 20.04, so it takes a couple extra steps to install it

cd ~/src/python-pip
curl https://bootstrap.pypa.io/get-pip.py --output get-pip.py
sudo python2 get-pip.py
cd ~/src

In at least one case, a required symlink (/usr/bin/python) was missing. Ensure that it exists, and is pointing to Python 2.7.

sudo ln -f -s /usr/bin/python2 /usr/lib/python

These libraries may be included with your distribution, and some may already be installed:

sudo apt install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libpython-all-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-dev

Autobuild is a Linden Lab resource that automates the configure and build processes.

sudo pip2 install autobuild

This will install autobuild and add a link in the exec path.

In order to make it easier to build collections of related packages (such as the viewer and all the library packages that it imports) with the same compilation options, Autobuild expects a file of variable definitions. This can be set using the environmenat variable AUTOBUILD_VARIABLES_FILE.

cd ~/src/sl
git clone https://vcs.firestormviewer.org/fs-build-variables
source fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=$HOME/src/sl/fs-build-variables/variables

There are several repositories available, in but the one wea re after is the development repository. You can grab all the sources if you wish, but but keep in mind that each FS source requires around 110MB initially and around 4.3GB after the binaries have been built, plus possible compiling overhead.

git clone https://vcs.firestormviewer.org/phoenix-firestorm

This can take a bit, it's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

Credit for the vorbis file goes to Marissa Orloff. She states that when recompiling this the following changes were made: in ogg_vorbis build.sh in line 91 needs to be edited to remove LL_release. aclocal and automake need symlinks 1.15 > 1.16

cd ~/src/sl/vorbis
wget https://fireandicegrid.net/downloads/ogg_vorbis-1.3.3-1.3.6.200930615-linux64-200930615.tar.bz2
cd ../phoenix-firestorm
autobuild installables edit ogg_vorbis platform=linux64 hash=d888b4916006c28471b4f103854526c3 url=file://$HOME/src/sl/vorbis/ogg_vorbis-1.3.3-1.3.6.200930615-linux64-200930615.tar.bz2

If you want to use FMOD Studio to play sounds within the viewer, you will have to download your own copy. FMOD Studio can be downloaded here (requires creating a free account to access the download section).

cd ~/src/sl
git clone https://vcs.firestormviewer.org/3p-libraries/3p-fmodstudio

• After you have cloned the repository, copy the downloaded FMOD Studio installer file to ~/src/sl/3p-fmodstudio
• Currently, FMOD Studio is at version 2.01.01, and that's what 3p-fmodstudio is expecting to use. If you plan to use a different version, you will have to modify the file build-cmd.sh in the root of the repository. Right at the top, you find the version number of FMOD Studio you want to package (one short version without separator and one long version). Change these values to the version you downloaded:

FMOD_VERSION="20101"
FMOD_VERSION_PRETTY="2.01.01"

cd ~/src/sl/3p-fmodstudio
autobuild build -A 64 --all
autobuild package -A 64

Near the end of the output you will see the package name written, including the path, and the md5 hash below it. For example:

wrote /home/user/src/sl/3p-fmodstudio/fmodstudio-2.01.01-linux64-201831958.tar.bz2
md5 a648d0a332768cab58b377566e415c88

cd ~/src/sl/phoenix-firestorm

Copy the FMOD Studio path and md5 value from the package process into this command:

autobuild installables edit fmodstudio platform=linux64 hash={md5 value} url=file://{wrote value}

For example:

autobuild installables edit fmodstudio platform=linux64 hash=a648d0a332768cab58b377566e415c88 url=file:///home/user/src/sl/3p-fmodstudio/fmodstudio-2.01.01-linux64-201831958.tar.bz2

 cd ~/src/sl/phoenix-firestorm
 autobuild configure -A 64 -c ReleaseFS_open

This will configure Firestorm to be built with all defaults and without third party libraries.

autobuild configure -v -c ReleaseFS_open

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• -A <architecture> sets the target architecture, that is if you want to build a 32bit or 64bit viewer (32bit is default if omitted).

When passing one or more of the following options, they must be separated first with a double dash, which denotes the start of an options list.

• –fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps above for this to work.
• –package makes sure all files are added to a compressed tar file for easy distribution and storage.
• –chan <channel name> lets you define a custom channel name for the viewer
• –no-opensim removes opemsim support, limiting the accessible grids to SL's Agni and Aditi.
• –avx causes the viewer to build with the AVX CPU instruction support. Similarly, –avx2 enabled AVX2 support.
• -LL_TESTS:BOOL=<bool> controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.

Examples:

• To build a 64bit viewer with a custom channel name, FMOD Studio and to create an installer package, run this command:

  autobuild configure -A 64 -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

• To build a 64bit viewer without FMOD Studio and without an installer package, run this command:

  autobuild configure -A 64 -c ReleaseFS_open -- --chan MyViewer -DLL_TESTS:BOOL=FALSE

Make sure you include the same architecture parameter and switches (except clean) you used while configuring the viewer:

autobuild build -A 64 -c ReleaseFS_open

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -A 64 -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.

Create the desktop launcher

cd ~/src/sl/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

cd ~/src/sl/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged
./firestorm

Your file browser/file manager many not know how to execute a script. Check the settings for your file browser. In Nautilus, for example, open Preferences > Behavior tab, change the action for executable text files to either Run or Ask.

Copy or move the contents of ~/src/sl/phoenix-firestorm/build-linux-x86_64/newview/packaged to a place that can be access by the PC you want to install Firestorm on. Cloud-based storage, NAS or removable media would do.

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

• Self-Compilers peer supportFirestorm Self Compilers is free to join, fellow self-compilers may be able to offer assistance.
• IRC: The #phoenixviewer-dev channel is the best place to look for solutions.
  A lot of self-compilers and project developers hang out there and are ready to help you.

• Jira:JIRA may contain resolved tickets.
  Search using the error you encountered.

• Included documentation: In the Firestorm root folder are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date.

If you found a procedural error in this document, please let us know in as much detail as you can, either contact the author (preferred) or discuss on IRC.

• Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Debian repositories, so make sure you did not disable those. If you find that a library or application is in a different package for your system, contact the team with the name of the library or application, the name of its package and your Linux OS so that information can be checked and added here.

• Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet

• No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

• Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

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

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

There are two workarounds:

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

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

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

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

Make sure Xcode is installed, it's a free download from Apple. Make sure cmake is installed, use at least a 2.8.x version.

• If you are using OSX 10.6, Xcode 3 will be used.
• If you are using OSX 10.7 “Lion” or OSX 10.8 “Mountain Lion”, the build will use Xcode 4.
• If you are using OSX 10.9, the build will use Xcode 5 and the Clang compiler.

If you want to use licensed FMOD Ex or KDU build libraries (they are optional) you have to provision these yourself. If you're licensing these with Phoenix-Firestorm, ask for the libraries for fmodex and kdu. Put them into:

      /opt/firestorm

If you're a community builder, you'll need to build these libraries yourself, then change your autobuild.xml file to point to your own versions, or create a different autobuild.xml with your customizations, and use this with autobuild instead of our default autobuild.xml There are some examples of how to build FMOD Ex on the LL Wiki and opensource-dev mailing list. We've created a non-KDU build target to make this easier. Everywhere you see “ReleaseFS” below, use “ReleaseFS_open” instead. This will perform the same build, using openjpeg instead of KDU.

Available premade firestorm-specific build targets:

ReleaseFS		(includes KDU, FMOD)
ReleaseFS_open		(no KDU, no FMOD)
RelWithDebInfo_open	(no KDU, no FMOD)

To build firestorm:

      autobuild build -c ReleaseFS                        

Other examples:

      autobuild configure -c ReleaseFS                    # basic configuration step, don't build, just configure
      autobuild configure -c ReleaseFS -- --clean         # clean the output area first, then configure
      autobuild configure -c ReleaseFS -- --chan Private-Yourname   # configure with a custom channel

      autobuild build -c ReleaseFS --no-configure              # default quick rebuild
      autobuild build -c ReleaseFS --no-configure -- --clean   # Clean rebuild

Any of the configure options can also be used (and do the same thing) with the build options. Typical LL autobuild configure options should also work, as long as they don't duplicate configuration we are already doing.

Logs:

      Look for logs in build-darwin-i386/logs

Output:

      Look for output in build-darwin-i386/newview/Release

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

All installations are done with default settings (unless told specific) if you change that you’re on your own.

You will need a copy of the OSX 10.6 SDK, which can be found in Xcode 4.3.3 for Lion. You can obtain this using a free DeveloperID at https://developer.apple.com/

Once you have the Xcode 4.3.3 disc image, mount it on your system. Now, download and run this shell script:

xcode_fix.sh

#!/bin/sh

echo 'Linden fix for Xcode 4.6 to have 10.6SDK so it can build older branches.'

echo 'Be sure to have the xcode_4.3_for_lion.dmg mounted! This script pulls from that volume!'

echo 'Creating temporary directory. . .'

mkdir temp

pushd temp

echo 'Copying 10.6SDK. . .'

cp -R /Volumes/Xcode/Xcode.app/Contents//Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk .

echo 'Linking darwin10 folders as darwin11. . .'

pushd MacOSX10.6.sdk/Developer/usr/llvm-gcc-4.2/lib/gcc/

ln -s i686-apple-darwin10 i686-apple-darwin11

popd

pushd MacOSX10.6.sdk/usr/lib/gcc/

ln -s i686-apple-darwin10 i686-apple-darwin11

popd

pushd MacOSX10.6.sdk/usr/lib/

ln -s i686-apple-darwin10 i686-apple-darwin11

popd

echo 'Changing ownership and moving SDK to machine. . . Password required for sudo commands.'

sudo chown -R root:wheel MacOSX10.6.sdk

sudo mv MacOSX10.6.sdk/ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs

popd

rm -rf temp

echo 'Xcode fix complete.'

If that finishes successfully, you're ready for the next step.

• First, install Mac Ports from http://www.macports.org/
• Next, using Mac Ports, install Mercurial and CMake. Open a terminal window and type:

sudo port install mercurial cmake

* You may prefer using Homebrew to Mac Ports which can be found here http://brew.sh/
* Install the required tools with this command:

brew install mercurial cmake

Python 2.7 is also required, but will be installed as a dependency to Mercurial.

Autobuild is a Linden Lab resource that does all the hard work.

In a Terminal window type:

mkdir ~/tmp
cd ~/tmp
hg clone http://hg.secondlife.com/autobuild/
cd autobuild
./setup.py
sudo ./setup.py install

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. For this document, I will assume $HOME/firestorm.

mkdir ~/firestorm
cd ~/firestorm
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/

This can take a while, it's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

Note: This typically needs to only be done once since fmodex rarely changes.

• Enter these commands into the command prompt:

hg clone https://bitbucket.org/NickyD/3p-fmodex
cd 3p-fmodex
autobuild build
autobuild package

Near the top of the output you will see the package name written and the md5 hash below it:

wrote /Users/kittin/tmp/3p-fmod/fmod-3.75-darwin-20130105.tar.bz2'
md5 3b0d38f2a17ff1b73c8ab6dffbd661eb''

Next, update Firestorms autobuild.xml file to use your FMOD Ex.

cd /firestorm/phoenix-firestorm-lgpl
cp autobuild.xml my_autobuild.xml
export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Copy the fmodex path and md5 value from the package process into this command:

autobuild installables edit fmodex platform=darwin hash=<md5 value> url=file:///<fmod path>

For example:

autobuild installables edit fmodex platform=darwin hash=c3f696412ef74f1559c6d023efe3a087 url=file://$HOME/firestorm/3p-fmodex/fmodex-3.75-darwin-20130105.tar.bz2

Note: Having to copy autobuild.xml and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to autobuild.xml and do not send up a modified autobuild.xml when you do an hg push.

If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new terminal you will need to reset the environment variable with

export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

cd ~/firestorm/phoenix-firestorm-lgpl

 autobuild configure -c ReleaseFS_open

This will compile with all defaults and without third party libraries.

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• FMOD (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in Fmod_using_autobuild for this to work.
• LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE

Example:

autobuild configure -c ReleaseFS_open -- -DLL_TESTS:BOOL=FALSE -DFMOD:BOOL=TRUE

If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new terminal you will need to reset the environment variable with

export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

cd ~/firestorm/phoenix-firestorm-lgpl
autobuild build -c ReleaseFS_open --no-configure

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling will take quite a bit of time.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -c ReleaseFS [– config options] . I find it is clearer if these steps are done separately, but can save a bit of time if done together.

• Kittin Ninetails
• Cinder Biscuits

As of revision 46075 of the main Firestorm development repository, the Linden Lab toolchain-update codebase has been merged into Firestorm. This represents a major change in the tools required to build the viewer.

With this change, the viewer and its libraries must be built with Xcode 6, CMake 3, and a metadata-capable version of Linden Lab's autobuild tool. Xcode 6 will only run on OS X 10.9 (Mavericks) or later; the last version to run on Mavericks is 6.2. As of this writing, Xcode 6.3.2 is current; that version only runs on OS X 10.10 (Yosemite).

If you want to build a 64-bit version, you must be at least at revision 46220.

You will need to install the following tools:

• Xcode. It's a free download from Apple. If you're using Mavericks, you will need to download Xcode 6.2 from the Apple Developers Connection site. You'll need an Apple ID to sign up for that if you haven't. If you're on Yosemite, you can get Xcode without an ADC login.
  • You will need to install the command line tools. To do this, after you've copied the Xcode application to your Applications folder, open a command line (Terminal, or equivalent) window, and issue the command

    xcode-select --install

• CMake version 3.
  • Again, you will need to install the command line links. The menu option to do this from within CMake is broken, and has been for several versions. From your command line prompt, issue the following command:

    sudo /Applications/CMake.app/Contents/MacOS/CMake

  • This will launch the CMake application with root permissions. Once you've done that, select Tools→Install for Command Line Use from the CMake menu. When that completes, exit CMake.
• The latest version of the Mercurial source code management system.
• Nicky Dasmijn's customized version of the Linden Lab autobuild tool.
  • Use

    hg clone https://bitbucket.org/NickyD/autobuild-1.0

    to put it somewhere convenient.

  • Add it to your PATH environment variable. The OS X-approved way to do this is to issue the following two commands:

    sudo ln -s <path/to/the/directory> /usr/local/bin/autobuild
    echo '/usr/local/bin/autobuild/bin' | sudo tee /etc/paths.d/99-autobuild

This will not take effect until the next time you open a Terminal window.

• The pip Python package installation tool, which is required for the next step. Follow the installation instructions on the pip installation page. You will need to run get-pip.py with sudo.
• The llbase Python package used by autobuild. Issue this command:

  sudo pip install llbase

If you want to use licensed FMOD Ex or KDU build libraries (they are optional) you have to provide these yourself. If you're building Firestorm as part of the project team, ask for the libraries for fmodex and kdu. Put them into /opt/firestorm .

If you're a community builder, you'll need to build these libraries yourself, then change your autobuild.xml file to point to your own versions, or create a different autobuild.xml with your customizations, and use this with autobuild instead of our default autobuild.xml There are some examples of how to build FMOD Ex on the LL Wiki and opensource-dev mailing list.

We've created a non-KDU build target to make this easier. Everywhere you see “ReleaseFS” below, use “ReleaseFS_open” instead. This will perform the same build, using openjpeg instead of KDU and omitting FMOD Ex.

Available premade firestorm-specific build targets:

ReleaseFS		(includes KDU, FMOD)
ReleaseFS_open		(no KDU, no FMOD)
RelWithDebInfo_open	(no KDU, no FMOD)

To build firestorm:

      autobuild build -c ReleaseFS                        

Other examples:

      autobuild configure -c ReleaseFS                    # basic configuration step, don't build, just configure
      autobuild configure -c ReleaseFS -- --clean         # clean the output area first, then configure
      autobuild configure -c ReleaseFS -- --chan Private-Yourname   # configure with a custom channel

      autobuild build -c ReleaseFS --no-configure               # default quick rebuild
      autobuild build -c ReleaseFS --no-configure -- --clean    # Clean rebuild

      autobuild configure -c ReleaseFS_open --            # configure with no third-party libraries
      autobuild configure -c ReleaseFS_open -- --fmodex   # configure with FMOD Ex but no KDU

Any of the configure options can also be used (and do the same thing) with the build options. Typical LL autobuild configure options should also work, as long as they don't duplicate configuration we are already doing.

Logs: Look for logs in build-darwin-i386/logs.

Output: Look for output in build-darwin-i386/newview/Release

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. For this document, I will assume $HOME/firestorm.

mkdir ~/firestorm
cd ~/firestorm
hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/

This can take a while. It's a rather large download.

Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during compilation. Some need to be manually prepared and are not normally required when using an open source configuration (ReleaseFS_open).

Note: This typically needs to only be done once since fmodex rarely changes.

• Enter these commands into the command prompt:

hg clone https://bitbucket.org/NickyD/3p-fmodex
cd 3p-fmodex
autobuild build
autobuild package

Near the top of the output you will see the package name written and the md5 hash below it:

wrote /Users/tonya/3p-fmodex/fmodex-44453-darwin-201505171651-r21.tar.bz2
md5 3b0d38f2a17ff1b73c8ab6dffbd661eb

Next, update Firestorms autobuild.xml file to use your FMOD Ex.

cd ~/firestorm/phoenix-firestorm-lgpl
cp autobuild.xml my_autobuild.xml
export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Copy the fmodex path and md5 value from the package process into this command:

autobuild installables edit fmodex platform=darwin hash=<md5 value> url=file:///<fmod path>

For example:

autobuild installables edit fmodex platform=darwin hash=3b0d38f2a17ff1b73c8ab6dffbd661eb url=file:///Users/tonya/3p-fmodex/fmodex-44453-darwin-201505171651-r21.tar.bz2

Note: Having to copy autobuild.xml and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to autobuild.xml and do not send up a modified autobuild.xml when you do an hg push.

If you are building with FMOD Ex and have followed the previous FMOD Ex setup instructions AND you are now using a new terminal you will need to reset the environment variable with

export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

cd ~/firestorm/phoenix-firestorm-lgpl

 autobuild configure -c ReleaseFS_open

This will compile with all defaults and without third party libraries.

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

• FMODEX (bool) controls if the FMOD Ex package is incorporated into the viewer. You must have performed the FMOD Ex installation steps in Fmod_using_autobuild for this to work. This is the switch the –fmodex build argument sets.
• LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE

Example:

autobuild configure -c ReleaseFS_open -- -DLL_TESTS:BOOL=FALSE -DFMOD:BOOL=TRUE

There is one other switch you can set. The -m64 switch tells autobuild to build a 64-bit version of the viewer. Unlike the others, this one goes before the build or configure argument, as in

autobuild -m64 configure -c ReleaseFS_open

It must be specified on both the configure and build commands. If you want to build a 64-bit viewer after building for 32 bits, or vice versa, you must do the first build when you change the architecture with –clean; otherwise, the viewer may build, but will almost certainly refuse to run.

If you are building with FMOD Ex and have followed the previous FMOD Ex setup instructions AND you are now using a new terminal you will need to reset the environment variable with

export AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then:

cd ~/firestorm/phoenix-firestorm-lgpl
autobuild build -c ReleaseFS_open --no-configure

Now, sit back, read War and Peace, calculate π to 50 places, tour the country, whatever you desire. Compiling may take quite a bit of time, depending on how fast your machine is and how much else you're doing.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -c ReleaseFS [– config options] .) Some find it is clearer if these steps are done separately, but can save a bit of time if done together.

• Kittin Ninetails
• Cinder Biscuits
• Reworked for the toolchain update by Tonya Souther

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

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

• 0079Galadriel
• briannainchains
• Hilary Querrien
• MarcSeven Lubitsch
• nuttidoxieg4 merryman
• panterapolnocy
• Sirus Plunkett
• Starwolff2000

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