Quantcast
Channel: Phoenix Firestorm Project - Wiki
Viewing all 5258 articles
Browse latest View live

antivirus_whitelisting - Add Settings and Chat folders for what to whitelist

$
0
0

Whitelisting the Viewer in Anti-Virus Software (plus Firewalls and Anti-Malware Sofware)

Introduction

Some anti-virus programs (and firewalls and anti-malware 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 slow or non-functional. There is at least one anti-virus program which will scan every file placed on your computer, even if created by an authorized program. This can affect Firestorm (or any viewer) in that it will scan each and every texture placed in cache, slowing down performance of the viewer significantly, keeping objects and/or textures from rezzing, and keeping CPU usage high.

There is nothing we can do about this. However, it should be possible for you to tell your anti-virus (firewalls/anti-malware) that the viewer is safe; you will need to whitelist the viewer program as well as some components.

The following is a list of some protection software and how to whitelist. Naturally we cannot provide instructions for all existing programs, 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.

In the instructions below, substitute “firewall” or “anti-malware program” for “anti-virus” as needed.

Click Here if you were advised to reinstall

Reinstalling

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.
  3. REBOOT your computer to make sure that the AV is not running anymore.
  4. If needed, download the viewer from here.
  5. Reinstall the viewer.
    • On Windows, make sure you do not install it back to the default folder suggested; INSTALL TO A NEW FOLDER. This step is vital.
    • On Mac, simply reinstall to your Application folder as usual.

What to Whitelist

In your anti-virus program, whitelist the following, per the instructions below (or better, consult the manual for your anti-virus software):

  • The viewer:
    • On Windows the viewer install folder is by default
      • 64-bit - C:\Program Files\Firestormx64-Release
      • 32-bit - C:\Program Files\Firestorm-Release
      • 32-bit on x64 - C:\Program Files (x86)\Firestorm-Release
        Inside this, the viewer itself (firestorm.exe), slplugin.exe, slvoice.exe and dullahan_host.exe (inside llplugin folder)
    • On Mac: the Firestorm application (normally in your Applications folder)
    • On Linux: the executables in /path/to/installation/bin/ (do-not-directly-run-firestorm-bin, dullahan_host, SLPlugin and SLVoice)
  • The 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 64-bit: C:\Users\[USERNAME]\AppData\Local\Firestorm_x64
      • Windows 32-bit: C:\Users\[USERNAME]\AppData\Local\Firestorm
      • Mac: /Users/[USERNAME]/Library/Caches/Firestorm
      • Linux: /home/[USERNAME]/.firestorm_x64/cache
  • The Settings 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 settings folder:
      • Windows 64-bit: C:\Users\[USERNAME]\AppData\Roaming\Firestorm_x64
      • Windows 32-bit: C:\Users\[USERNAME]\AppData\Roaming\Firestorm
      • Mac: /Users/[YOUR USERNAME]/Library/Application Support/Firestorm
      • Linux: /home/[USERNAME]/.firestorm_x64 (which also contains the cache)
  • The Chat Transcripts folder
    • In its default location, this is the same as the Settings folder. If you have relocated your chat files, then note that path.

REBOOT your computer at this time.

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.

Re-enable your anti-virus software if you disabled it, and run the viewer again, repeating the tests above.

Whitelisting Steps for Specific AV Software

If you don't find your antivirus program listed, or the instructions are out
of date, check the help files or support site for your antivirus program.

Adaware free

  • Open the Adaware user interface
  • Click Scan Computer (second icon from top)
  • Go to Manage Exclusions and click View
  • Click Add
  • Navigate to main Firestorm application folder
  • Click OK
  • Repeat for Firestorm folders in User/Local

Advanced System Care

If you run the “junk files cleanup” function, then Advanced System Care is liable to trash your settings. Further to this, this program can also severely interfere with viewer connection to SL servers, as documented here.

Avast

2019-09-18 Update

it seems that in the early hours of 2019-09-18, an update was issues for Avast, and that update began “mangling” Firestorm. One user 1) provided the following:

I went into my Avast Virus Chest and scrolled to the bottom of the list where the Firestorm file to see if there was still a way to make an exception there….on the far right, after highlighting it, I saw 3 dots and there is an option there to Restore and Add Exception. I clicked it and it said The File was Happily Restored!

So what this is about is just to let you know that I didn't have to go through the procedure to Whitelist, in case you want to let others know who may have put it in the chest.

I reinstalled Firestorm over my present one just so I could get the shortcut (icon) again…logged on and all is well.

Basic Whitelisting

Refer to this page for how to whitelist. Please ensure that you whitelist both the viewer and the viewer cache folder.

If you cannot save snapshots to your hard drive
  1. Go to Settings → General tab
  2. Go to 'Blocked and allowed apps'
  3. Click 'Allow App' and scroll the list of programs to find Firestorm and select it (see picture below)

AVG

  • 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.
2019-09-18 Update

it seems that in the early hours of 2019-09-18, an update was issues for AVG, and that update began “mangling” Firestorm.

Bullguard

  1. Open Bullguard as normal
  2. Click on “Settings”
  3. Click on “Advanced”
  4. Go to “Antivirus” in the lefthand column
  5. Open the menu (down arrow)
  6. Select “Tuning”
  7. In the selection of tick boxes on the righthand panel, select Skip File/Folders
  8. Click on Files/Folders
  9. This will bring up a probably empty set of lines, so click on the “+” sign
  10. This should allow you to navigate to the particular folder, in this case the Firestorm Cache folder
  11. Select that and it will appear in the first line of the box
  12. To add other Firestorm folders listed at the top of this wiki page, repeat as needed
  13. Here is also a check box to allow you to skip processes. The procedure is the same: Click on “process”
  14. Click “+” and navigate to the .exe you wish to whitelist
  15. Close Bullguard.

Credits: Thanks to user Aishagain for this information.

Comodo

Apparently Comodo adds a green border round the viewer screen. This can safely be ignored.

F-Secure

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

Gatekeeper (Mac OS X)

Gatekeeper is not an antivirus. It is Apple software that checks software the first time you run it to make sure it is from a known developer. It will flag Firestorm as unknown and will ask you if you want to let it run.

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.

Kaspersky

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.

Malwarebytes

For general whitelisting steps, visit Exclude detections in Malwarebytes on Windows devices

McAfee

We do not have specific details for McAfee. Check the McAfee control panel, or visit McAfee Consumer Support

Norton

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
Download Intelligence

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.

Panda Cloud Antivirus Free (version 2.1.1)

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

PC Tools Spyware Doctor

  • 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.9 and later).
  • This will add the plugin(s) to the global whitelist.

Webroot

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:

Windows Defender/Microsoft Security Essentials

Basic Exclusions

https://support.microsoft.com/en-us/help/4028485/windows-add-an-exclusion-to-windows-defender-antivirus

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

  • Open Settings and in the search field at the top right enter defender
  • In Windows Defender click Virus & Threat Protection → Virus & Threat Protection Settings → Exclusions → Add or remove exclusions
  • 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-Releasex64.exe
    • Click the Exclude This file button
    • Repeat this for SLPlugin and SLVoice - and dullahan_host.exe (for FS 5.1.7 and later).
    • Repeat this for 32-bit Firestorm ( C:\Program Files (x86) )
Can't Save Files to Hard Drive (Snapshots, Chat Files, Backups, etc.)

Additionally, if you're on Windows 10 and you can't save snapshots to your hard drive (https://jira.firestormviewer.org/browse/FIRE-23347), adding the viewer folders to the exclusion list may not be enough if you have 'Controlled Folder Access' enabled; you will need to add Firestorm to the allowed apps.

Try following these steps:

  1. Right click your Windows Defender icon on your system tray > View Security Dashboard > Virus and threat Protection > Virus & Threat Protection Settings > Controlled Folder Access
  2. Click the 'Manage Controlled Folder Access' link
  3. Under 'Controlled Folder Access' click the 'Allow an App through Controlled Folder Access' link
  4. Click '+ Add an allowed app'
  5. Browse to the viewer executable in the installation folder, left click to select , click Open at the bottom of the files explorer.

Alternatively, you can also simply disable the Controlled Folder Access feature by clicking the on/off button after Step #2.

Can't run Firestorm installer

See this page.


See this page for documentation on Firestorm 5.0.11 (53634) and earlier.
1)
Thank you, Sophie Katsu!

new_residents:earning_lindens - [Linden Lab Games]

$
0
0

How Can I Earn L$ in SL?

Related tutorial videos: Shopping & Buying Linden Dollars

Camping for Items and Lindens

“Camping” is a way of earning a small amount of lindens or other objects by sitting in one spot for a certain amount of time. Here is an example.

Traffic Attractor Games

These are usually fishing games or coin hunting games. You will be paid a small amount (1 linden dollar for 15 minutes for example) to increase traffic. Traffic has a mild influence on search result listings.

The games vary, so be sure to read the “how to play” in the note cards, websites and group descriptions.

Fishing Games

In fishing games you will have to purchase baits and a fishing kit and start earning Lindens by fishing.

To do so you go to places that set up a fishing buoy and cast your lines (individual games differ on how you do this, usually some kind of HUD is involved).

Once you have earned enough Lindens in your HUD you can cash out those Lindens either directly from the Game HUD or from a cash terminal the game provides. Some of these games are listed below:

Coin Hunting Games

In coin hunting games you will run around and collect coins that are scattered across an area. to collect the coins, click them, wait till the countdown is done and then answer a small riddle to proof you're human, once that is done the amount shown on the coin you clicked will be added to your balance.

Cashing out is similar to fishing games, either by the HUD or a Cash Terminal.

Some coin games are shown below:

Many of the companies above will also have other less popular games besides coin hunting and or fishing.

Disclaimer: Please take note that most of those games have advanced options that will cost you (basically you invest into the game and are rewarded by the possibility of earning more). But you can also lose money that way, by paying more than you earn back. So until you understand the finer details it's my best advice to stay with the free basic kits and cheapest baits/seeds you can get.

Linden Lab Games

Well those previous games are nice but sometimes they send you to unpleasant places, some are even places you cannot enter (adult regions with gaming areas are notorious for hosting those games). Wouldn't it be great if you could also earn Lindens in a guaranteed safe for work environment?

Well yes, thanks to Linden Labs you can. Hop over to Portal Park and there either enter Paleo Quest or Linden Realms and follow the instructions. You will be given a temporary HUD / attachment while there, no purchase necessary.

Both of these games have a story line and a quest but more important to you I guess is that you can earn Lindens there.

In Linden Realms you have to collect crystals and bring them to the crystal collector machines to redeem them for Lindens. In Paleo Quest it's Dinosaur parts.

The main difference between these games is: While in both games you can die (and believe me, you will, and you will often)

In Linden Realms your crystals are untouched by death, in Paleo Quest you will lose every thing you collected upon death, but you will need way less items for cash-out in Paleo Quest and the competition also isn't as fierce … which ever you prefer is up to you (I highly recommend trying both though, even if it is just to see the beautiful landscapes the Lindens and Moles have built there)

Finding a Job

Inworld Employment/Want Ads page for Second Life

More information about making money in SL?

Also, Use the Search Shortcut Ctrl + F to search for employment agencies. There are many groups where you can search for jobs and ask for information from other members of the group. Some places may want to only hire people whose avatar is more than 30 days old.

Bringing Funds in from Bank/Paypal

The easiest way to get L$ is to buy them, either via the viewer, or from the SL dashboard.

Sell a product

Make unique and marketable items, from objects such as clothing or houses, to programming scripts and sell them within the game or at the marketplace.

You could also become a reseller for fixed commissions; use ctrl f inside Second Life and search for Commission Sales.

file_a_jira - [Creating an account]

$
0
0

How to File a JIRA

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

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

Creating an account

In order to do anything except view Firestorm issues, you will need an account on Jira. Creating an account is very easy:

  1. Log into SecondLife using any viewer.
  2. Send an IM to Willow Wilder, Anastasia Horngold, or Whirly Fizzle. In the IM, indicate that you need a Jira account and PROVIDE A WORKING EMAIL ADDRESS IN YOUR FIRST MESSAGE. The email address is important because it's the only way Jira can contact you. Please don't make us ask you for an email address, as this can slow your request down.
  3. If none of these Jira administrators respond (and please remember - they have SL lives too and are not always available), please ask in a Firestorm support group for a moderator to help. The moderator will pass your request on.
  4. If you have not received a Jira invitation email in 24 hours, be sure to check your spam filter; then ask a support group moderator.
  5. When you receive the Jira invitation email, follow its instructions to create your account. Please use your SL avatar name as your Jira username, and where it asks for your real name, again use your SL avatar name. We do not need your RL name.
  6. If you run into any problems signing on, contact a Firestorm Support group moderator and let them know. They will alert a Jira administrator.

NOTE: You are currently reading a wiki page. This is not the Jira web site. Do not attempt to log in to the wiki. Follow the link below to reach the Jira.

Creating an Issue

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

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

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

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

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

How To Give Us Your Logs

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

NOTE: Please do this, even if you have crash logging enabled.

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

Firestorm 64-bit
Windows 8.1 and 10 C:\Users\[USERNAME]\AppData\Roaming\Firestorm_x64\
(or use the environment variable %APPDATA%)
Mac /Users/[YOUR USERNAME]/Library/Application Support/Firestorm/
Linux ~/.firestorm_x64/
Firestorm 32-bit
Windows 8.1 and 10 C:\Users\[USERNAME]\AppData\Roaming\Firestorm\
(or use the environment variable %APPDATA%)

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

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

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

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

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

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

Working in Your Issue

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

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

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

Further reading: How to Report Bugs Effectively

1) , 2)
Phoenix isn't mentioned here because it is no longer under development, nor being supported.

new_residents:calling_posts_sm.png - created

new_residents:pose_balls_in_air_sm.png - created

new_residents:furniture

$
0
0

How Do I Use Furniture?

In SL, you will find furniture of all kinds, from chair, to couches, bed, beach towels and so on. So, how so you use them?

In some case, when you move your mouse over the furniture, the mouse cursor will change to a chair icon.
If that happens, then simply left click and you will automatically sit on the furniture.
You may get a menu like this, and you can choose how you want to sit by clicking on the buttons.

If the cursor does not change, then try using right click, then select “Sit” from the menu.

Some older furniture requires that you first click the furniture and select a starting animation. It will rez out one or more pose balls.
You can see them in this picture

You then right click on a pose ball, and either a menu will come up, or you will just sit.

Many items of furniture will offer menus which allow you to select from a choice of poses for that furniture. Sometimes you will get a menu as soon as you sit; other times, you can click for a menu after you have sat. And as noted, furniture that uses pose balls generally requires you to click before sitting, to select the starting pose.

In some instances, you will be asked for permission to animate your avatar; you will need to select “Yes” for this, or nothing will happen.

Dancing in Second Life

Dance machines at clubs either have a calling post, pose balls somewhere in the ceiling, and now there is a new dance post that lines you and others up in different formations.
Example of the Calling Posts are shown below. The multicolor ones are for couples. This pink one is a new kind, click on it and then you click on a green triangle on the floor. You'll dance in different formations with the other avatars who have clicked it.

If you don't see a calling post, then look up at the ceiling or sky, and you'll see pose balls.
Usually blue has male dances, pink or red has female dances, and multicolored are for couples. (See photo below)

Many Dance clubs have dance pads as well. Right click on the circle (the pad) and when it asks if you'd like to dance, click “yes”. You may or may not get a menu of dances.

As you can see, there are many ways to dance, which may be initially confusing, but you will get the hang of it with practice.

new_residents:furniture_menu.png - created

new_residents:appearance_editing_shape_menu.png - created


fs_radar

$
0
0

Radar

The standalone radar window can be opened either via its toolbar button, or top menu, World → Radar.

Radar Window

Radar is presently sortable by name, age, seen and range. Just click on the appropriate button.

  • Bold name indicates a friend, italics indicates the person is muted.
  • The untitled column to the right of Name shows whether the person is speaking on voice
  • The next column will display a green square if the person is in the same region as you, yellow if in the same parcel (ie, yellow and green, usually, for both same parcel and same region).
  • The next shows if the person is typing.
  • This column indicates is the person is sitting.
  • The next column will show a $ sign if the person has payment info on file, and a $$ for payment info used.
  • Then comes Avatar has notes, which will contain an N if you put notes on that person's profile.
  • Age indicates the avatar's age in days.
  • Seen is the length of time the person has been within radar range.
  • Range shows their current distance, in meters. Use of bolding and color distinguishes chat range, shout range, and beyond.
    • Green = Chat Range ( 0-19m )
    • Yellow = Shout Range ( 20-99m )
    • Red = Beyond chat range ( 100m + )
    • Bold = Chat is visible/not blocked by parcel privacy

When you right click on a person's name you get the following options:

  • View Profile: Opens a window showing the person's profile.
  • Add Friend: This option is only shown if the person is not already on your friends list. It will send a friendship request.
  • Remove Friend: This option is only shown if the person is on your friends list. Clicking it will dissolve the friendship. Currently, the other person is not informed, but one copy of your calling card will be removed from the person's Calling Cards folder (a second copy will remain there until/unless they choose to delete it; if the person is logged in at the time, the removed copy will appear in their Trash).
  • IM: Opens an IM to the person.
  • Call: Initiates a private voice conversation with the other person. Naturally, both need to have voice enabled and functioning.
  • Map: If your friend gave you map rights, this item will be enabled. If clicked, it will open the world map and show the person's current location.
  • Track: shows a beacon allowing to you locate the person and track their movement. (Versions after 3.2.2 only.)
  • Share: If you click this entry, an IM window opens; you can then drag and drop inventory items into it, to give them to the other person.
  • Pay: Opens a window, which you can use to pay the other person L$. Some default values are shown, or you can type the number in manually.
  • Offer Teleport: Click this if you wish to offer to teleport the person to your present location.
  • Teleport To: Teleports you to the other person's location.
  • Zoom In: If enabled, moves your camera to view the other person.
  • Block/Unblock: aka Mute/Unmute. This mutes the other person, completely blocking them from contacting you. You will not see anything they type in local chat or receive any IMs they might send, and all inventory offers made will be automatically declined. Use with caution; muting a person can also mute their objects, which means that if you make a purchase from them, you are likely to not receive what you paid for.
  • Report: Allows you to file an abuse report against the selected avatar. This should not be done lightly and never be misused. Click here for more information on what an abuse report is.
  • Freeze: Estate managers/owners can use this to freeze an avatar's movements. This is a tool to be used in cases of griefing and not to be used frivolously.
  • Parcel Eject/Ban: If selected, this will eject and ban the avatar from the parcel you are in. You must have the appropriate rights in that parcel or this will not work.
  • Estate Kick/Ban: Similar to the above, but operates at the estate level. Therefore, this is only available to estate managers or owners.
  • Estate Teleport Home: Selecting this will teleport the avatar to his/her home location. This does not ban them, however, and may fail if they have no home location set or if that location is not accessible (eg, the region is down).

The Sprocket/Gear icon in the Radar window (bottom left, in some skins) has a menu similar to the one you get when right-clicking on an avatar. Here, select a name from the radar list, then click the gear menu for options.

The List icon, to the right of the gear, has the following radar functions:

  • Show Minimap above Radar: If enabled, the panel expands upward to show a minimap of the current area.
  • Limit Results to Specific Radius: If selected, a slider will appear at the bottom of the window, to the right of the sprocket/gear. Here you may change the range at which the radar is active. This allows you to monitor smaller areas than the radar normally can report. Useful if you only are interested in a parcel rather than an entire region and those adjoining. If you wish to have radar report at max range all the time, it is more efficient to just disable this option.
  • Show muted and blacklisted Avatars: If enabled, radar will list people you have muted and/or derendered.
  • Radar Name Format: Allows you to select how you want names to be displayed in the radar. Available options depend on how you have preferences set for display names and user names.
  • Displayed Columns: You can enable or disable specific columns in the list. Handy if you want to reduce the overall width.
  • Color names based on distance: same as the option in PreferencesColors -> Name tags.
  • Report To: allows you to select whether to show radar notifications to chat or as notification toasts.
  • Local chat distance ring in Minimap: Show chat raneg on the minimap. Same as the option in Preferences → Colors -> Minimap.
  • Report Entering Draw Range: If enabled, this will report to chat when someone enters your draw distance range.
  • Report Leaving Draw Range: If enabled, this will report to chat when someone leaves your draw distance range.
  • Report Entering Chat Range: If enabled, this reports to chat whenever someone enters chat range (20m).
  • Report Leaving Chat Range: If enabled, this reports to chat whenever someone leaves chat range (20m).
  • Report Entering your Region: Enable this to have the radar report people entering the region you are currently in.
  • Report Leaving your Region: Enable this to have the radar report people leaving the region you are currently in.
  • Report Enter Alerts to Scripts: If enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
  • Report Exit Alerts to Scripts: If this is enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
  • Enhance Radar with LSL Bridge: ENhance radar functionality via the Bridge. Used to improve distance calculations.
  • Open Blocked Residents & Objects:

    This displays the list of people and objects you have blocked (muted).

The '+' icon, to the right to the sprocket/gear, when clicked, will give the following message: “Friends can give permissions to track each other on the map and receive online status updates.” And it will ask you if you want to offer friendship to an Avatar that you highlighted. If they are already on your friends list, the '+' sign will be greyed out.

On the bottom row are the following buttons, providing quick access to functions that are available when right clicking a person's name:

  • Profile
  • IM
  • Call
  • Share

people_nearby_tab

$
0
0

People Panel

There is a helpful tutorial video here.

Nearby (Radar)

People Panel - Nearby/Radar

Radar is presently sortable by name, age, seen and range. Just click on the appropriate button.

* Bold name indicates a friend, italics indicates the person is muted.

  • The untitled column to the right of Name shows whether the person is speaking on voice
  • The next column will display a green square if the person is in the same region as you, yellow if in the same parcel (ie, yellow and green, usually, for both same parcel and same region).
  • The next shows if the person is typing.
  • This column indicates is the person is sitting.
  • The next column will show a $ sign if the person has payment info on file, and a $$ for payment info used.
  • Then comes Avatar has notes, which will contain an N if you put notes on that person's profile.
  • Age indicates the avatar's age in days.
  • Seen is the length of time the person has been within radar range.
  • Range shows their current distance, in meters. Use of bolding and color distinguishes chat range, shout range, and beyond.
    • Green = Chat Range ( 0-19m )
    • Yellow = Shout Range ( 20-99m )
    • Red = Beyond chat range ( 100m + )
    • Bold = Chat is visible/not blocked by parcel privacy

When you right click on a person's name you get the following options:

  • View Profile: Opens a window showing the person's profile.
  • Add Friend: This option is only shown if the person is not already on your friends list. It will send a friendship request.
  • Remove Friend: This option is only shown if the person is on your friends list. Clicking it will dissolve the friendship. Currently, the other person is not informed, but one copy of your calling card will be removed from the person's Calling Cards folder (a second copy will remain there until/unless they choose to delete it; if the person is logged in at the time, the removed copy will appear in their Trash).
  • IM: Opens an IM to the person.
  • VoiceCall: Initiates a private voice conversation with the other person. Naturally, both need to have voice enabled and functioning.
  • Map: If your friend gave you map rights, this item will be enabled. If clicked, it will open the world map and show the person's current location.
  • Track: shows a beacon allowing to you locate the person and track their movement. (Versions after 3.2.2 only.)
  • Share: If you click this entry, an IM window opens; you can then drag and drop inventory items into it, to give them to the other person.
  • Pay: Opens a window, which you can use to pay the other person L$. Some default values are shown, or you can type the number in manually.
  • Offer Teleport: Click this if you wish to offer to teleport the person to your present location.
  • Teleport To: Teleports you to the other person's location.
  • Zoom In: If enabled, moves your camera to view the other person.
  • Invite to group: allows you to invite the person to a group you belong to; opens the Groups selector window.
  • Get Script Info: Displays the script info for the avatar; requires that the Firestorm bridge be enabled and worn.
  • Block/Unblock: aka Mute/Unmute. This mutes the other person, completely blocking them from contacting you. You will not see anything they type in local chat or receive any IMs they might send, and all inventory offers made will be automatically declined. Use with caution; muting a person can also mute their objects, which means that if you make a purchase from them, you are likely to not receive what you paid for.
  • Report: Allows you to file an abuse report against the selected avatar. This should not be done lightly and never be misused. Click here for more information on what an abuse report is.
  • Freeze: Estate managers/owners can use this to freeze an avatar's movements. This is a tool to be used in cases of griefing and not to be used frivolously.
  • Parcel Eject/Ban: If selected, this will eject and ban the avatar from the parcel you are in. You must have the appropriate rights in that parcel or this will not work.
  • Estate Kick/Ban: Similar to the above, but operates at the estate level. Therefore, this is only available to estate managers or owners.
  • Estate Teleport Home: Selecting this will teleport the avatar to his/her home location. This does not ban them, however, and may fail if they have no home location set or if that location is not accessible (eg, the region is down).
  • Derender: Temporarily derenders the avatar.
  • Derender + Blacklist: Derenders and blacklists the avatar. This derender is permanent - unless you remove the person from the blacklist; see this page.
  • Render Settings: Fly-out menu offers options to Render Normally (default), Do Not Render, Render Fully.

The Sprocket/Gear icon at the top of the Nearby tab has the same functions as the right click menu for individual avatar names.

The List icon, to the right of the gear, has the following radar functions:

  • Show Minimap above Radar: If enabled, the panel expands upward to show a minimap of the current area.
  • Limit Results to Specific Radius: If selected, a slider will appear at the bottom of the window, to the right of the sprocket/gear. Here you may change the range at which the radar is active. This allows you to monitor smaller areas than the radar normally can report. Useful if you only are interested in a parcel rather than an entire region and those adjoining. If you wish to have radar report at max range all the time, it is more efficient to just disable this option.
  • Show muted and blacklisted Avatars: If enabled, radar will list people you have muted and/or derendered.
  • Radar Name Format: Allows you to select how you want names to be displayed in the radar. Available options depend on how you have preferences set for display names and user names.
  • Displayed Columns: You can enable or disable specific columns in the list. Handy if you want to reduce the overall width.
  • Color names based on distance: same as the option in PreferencesColors -> Name tags.
  • Report To: allows you to select whether to show radar notifications to chat or as notification toasts.
  • Local chat distance ring in Minimap: Show chat range on the minimap. Same as the option in Preferences → Colors -> Minimap.
  • Report Entering Draw Range: If enabled, this will report to chat when someone enters your draw distance range.
  • Report Leaving Draw Range: If enabled, this will report to chat when someone leaves your draw distance range.
  • Report Entering Chat Range: If enabled, this reports to chat whenever someone enters chat range (20m).
  • Report Leaving Chat Range: If enabled, this reports to chat whenever someone leaves chat range (20m).
  • Report Entering your Region: Enable this to have the radar report people entering the region you are currently in.
  • Report Leaving your Region: Enable this to have the radar report people leaving the region you are currently in.
  • Report Enter Alerts to Scripts: If enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
  • Report Exit Alerts to Scripts: If this is enabled, the radar will send an avatar UUID to scripts. For more information, please refer to this page.
  • Enhance Radar with LSL Bridge: Enhance radar functionality via the Bridge. Used to improve distance calculations.
  • Open Blocked Residents & Objects:

    This displays the list of people and objects you have blocked (muted).

The '+' icon, to the right of the list (radar) icon, when clicked, will give the following message: “Friends can give permissions to track each other on the map and receive online status updates.” And it will ask you if you want to offer friendship to an Avatar that you highlighted. If they are already on your friends list, the '+' sign will be greyed out.

See this page for documentation on Firestorm 5.0.11 (53634) and earlier.

radar-6-4-13.png - created

quit_dialog.png - created

prefs-notifications-alerts.png - created

never_show_arrow.png - created

always_show_arrow.png - created


new_residents:start - [Happenings Around the Gateway & Grid]

$
0
0

For New Residents

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

Joining Second Life

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

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

Help For New Residents

Video Tutorials

Activities in Second Life

Happenings Around the Gateway & Grid

Shopping Spree for New Avatars - Contact Frank Sinatra (frankasinatra)

Dance Party Schedule at the Dow Forest: (Time: 1-3 pm slt)

  • March 27th - THEME: PJ Party (remember we are G-rated)

fs_older_downloads_new - [Edit - Pane]

$
0
0

Firestorm - Older Releases


Firestorm 6.4.12 (62831) Release

Firestorm 6.4.12 (62831) Release Notes

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

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Windows Setup.exe
MD5 Checksum: 1EC526D25881CF9D559902A65D254B85
SHA1 Checksum: 0C04A3BA1057ABEFF2FE350B0DDA174B761DB4CE
File Size: 117 MB (122,955,343 bytes)
Windows
32-bit
32 and 64 SL only Full Release Firestorm Release 6.4.12.62831 32 bit Windows setup.exe
MD5 Checksum: 82CC75C2987F380E41A2D76F5C84B6AD
SHA1 Checksum: 987163817543E62228F37614AD17989FFABF37CF
File size: 112 MB (117,095,904 bytes)
Windows
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.4.12.62831OS 64 bit Windows Setup.exe
MD5 Checksum: 440F267236E7507B6E2398C920EE9C4E
SHA1 Checksum: E2CEAED5455DAEA70AA3E89E9A1889A03D1ED7B0
File size: 116 MB (121,618,492 bytes)
Windows
32-bit OpenSim
32 and 64 OpenSim only Full Release Firestorm Release 6.4.12.62831OS 32 bit Windows setup.exe
MD5 Checksum: 9B438C032AE521486DC4FC3BDAE208AC
SHA1 Checksum: 8D77972C2C6A476E20BEEFBD2E836C6A92838AF3
File size: 111 MB (115,910,399 bytes)

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Intel Mac.dmg
MD5 Checksum: 2159B237EE5DAEF870AEAFDA8557D679
SHA1 Checksum: CD3135CB416B7530B544A47050FE2792D80E25DA
File size: 183 MB (192,160,108 bytes)
Mac
32-bit
32 and 64 SL only n/a n/a
Mac
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.4.12.62831OS 64 bit Intel Mac.dmg
MD5 Checksum: 1730251999CDC8F500CAA269B4DE9D14
SHA1 Checksum: D841F0BE68AB7450F211927920A302609719922B
File size: 181 MB (189,946,057 bytes)
Mac
32-bit OpenSim
32 and 64 OpenSim only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Linux.tar.bz2
MD5 Checksum: 91FFDC888E4431C835C97B48FE7C8724
SHA1 Checksum: 331CE0807E2C596B39A6FCDD80F92830E9A93CF0
168 MB (175,719,800 bytes)
Linux
32-bit
32 and 64 SL only n/a n/a
Linux
64-bit OpenSim
64-bit only OpenSim Only Full Release Firestorm Release 6.4.12.62831OS 64 bit Linux.tar.bz2
MD5 Checksum: 7088355DDF2E627D024B26F618FECC1B
SHA1 Checksum: 05E63163BFF311C961EF81F2FA543B3B7FBDF4B9
File size: 167 MB (175,076,128 bytes)
Linux
32-bit OpenSim
32 and 64 OpenSim Only n/a n/a


Firestorm 6.3.9 (58205) Release

Firestorm 6.3.9 (58205) Release Notes

“n/a” in the table below means “not available”.

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit SL
64-bit only SL only Full Release Firestorm Release 6.3.9.58205 64 bit Windows Setup.exe
MD5 Checksum: 158DB232BEBFB0D12F1CB1D91613E596
Windows
32-bit SL
32 and 64 SL only Full Release Firestorm Release 6.3.9.58205 32 bit Windows setup.exe
MD5 Checksum: 43132552ECB5277F5BA58676C467563C
Windows
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.3.9.58205OS 64 bit Windows Setup.exe
MD5 Checksum: 068D09D240665203EACA21CC68FFF52C
Windows
32-bit OpenSim
32 and 64 OpenSim only Full Release Firestorm Release 6.3.9.58205OS 32 bit Windows setup.exe
MD5 Checksum: E4B2895C3445FB97A51C68C70484910D

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit SL
64-bit only SL only Full Release Firestorm Release 6.3.9.58205 64 bit Intel Mac.dmg
MD5 Checksum: 7CAA12CB90D64C26195FB6F8517AA707
Mac
32-bit SL
32 and 64 SL only n/a n/a
Mac
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.3.9.58205OS 64 bit Intel Mac.dmg
MD5 Checksum: 51F7CC302846F94971C36F86BA95CEBB
Mac
32-bit OpenSim
32 and 64 OpenSim only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit SL
64-bit only SL only Full Release Firestorm Release 6.3.9.58205 64 bit Linux.tar.bz2
MD5 Checksum: 335E758C5088C6F2038D035C37DAE3A9
Linux
32-bit SL
32 and 64 SL only n/a n/a
Linux
64-bit OpenSim
64-bit only OpenSim Only Full Release Firestorm Release 6.3.9.58205OS 64 bit Linux.tar.bz2
MD5 Checksum: 93861134A1173758110A57C4EDCF9D36
Linux
32-bit OpenSim
32 and 64 OpenSim Only n/a n/a


Firestorm 6.3.2 (58052) Bakes On Mesh Release

Firestorm 6.3.2 (58052) Release Notes

“n/a” in the table below means “not available”.

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit
64-bit only SL only Full Release Firestorm Release 6.3.2.58052 64 bit Windows Setup.exe
MD5 Checksum: 22D4173CD14803AE99F0592D1813171A
Windows
32-bit
32 and 64 SL only Full Release Firestorm Release 6.3.2.58052 32 bit Windows setup.exe
MD5 Checksum: AD980B6F8297E182F82740B3DAAC28EA

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit
64-bit only SL only Full Release Firestorm Release 6.3.2.58052 64 bit Intel Mac.dmg
MD5 Checksum: DC8CA6ADBE9862ECD2BD5A1A18DC4BB7
Mac
32-bit
32 and 64 SL only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit
64-bit only SL only Full Release Firestorm Release 6.3.2.58052 64 bit Linux.tar.bz2
MD5 Checksum: CF3B34B07C50AD43D9952117F1FB60CF
Linux
32-bit
32 and 64 SL only n/a n/a


Firestorm 6.0.2 (56680) Animesh Release

OpenSim only; blocked for Second Life.

Firestorm 6.0.2 (56680) Animesh Release Notes

“n/a” in the table below means “not available”.

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit OpenSim
64-bit only OpenSim Full Release Firestorm Release 6.0.2.56680OS 64 bit Windows Setup.exe
MD5 Checksum: 08a67070083a1399997db2aaa102d8df
Windows
32-bit OpenSim
32 and 64 OpenSim Full Release Firestorm Release 6.0.2.56680OS 32 bit Windows setup.exe
MD5 Checksum: 9ddaac654820a5168c1f4bed4603fc6b

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit OpenSim
64-bit only OpenSim Full Release Firestorm Release 6.0.2.56680OS 64 bit Intel Mac.dmg
MD5 Checksum: 5c152ac11982c01b25edcadef26e9366
Mac
32-bit OpenSim
32 and 64 OpenSim n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit OpenSim
64-bit only OpenSim Full Release Firestorm Release 6.0.2.56680OS 64 bit Linux.tar.bz2
MD5 Checksum: c11857b11dbb4a4accfc785529d63451
Linux
32-bit OpenSim
32 and 64 OpenSim Full Release Firestorm Release 6.0.2.56680OS 32 bit Linux.tar.bz2
MD5 Checksum: 9e20172f32789f68671c0be8bcdd8315

downloads_new - created

$
0
0

Firestorm Viewer Downloads For Second Life

Firestorm Viewer is certified to be free of viruses and malware.

Current Release for Second Life

Firestorm 6.4.12 (62831) Release

Firestorm 6.4.12 (62831) Release Notes

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

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Windows Setup.exe
MD5 Checksum: 1EC526D25881CF9D559902A65D254B85
SHA1 Checksum: 0C04A3BA1057ABEFF2FE350B0DDA174B761DB4CE
File Size: 117 MB (122,955,343 bytes)
Windows
32-bit
32 and 64 SL only Full Release Firestorm Release 6.4.12.62831 32 bit Windows setup.exe
MD5 Checksum: 82CC75C2987F380E41A2D76F5C84B6AD
SHA1 Checksum: 987163817543E62228F37614AD17989FFABF37CF
File size: 112 MB (117,095,904 bytes)

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Intel Mac.dmg
MD5 Checksum: 2159B237EE5DAEF870AEAFDA8557D679
SHA1 Checksum: CD3135CB416B7530B544A47050FE2792D80E25DA
File size: 183 MB (192,160,108 bytes)
Mac
32-bit
32 and 64 SL only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Linux.tar.bz2
MD5 Checksum: 91FFDC888E4431C835C97B48FE7C8724
SHA1 Checksum: 331CE0807E2C596B39A6FCDD80F92830E9A93CF0
168 MB (175,719,800 bytes)
Linux
32-bit
32 and 64 SL only n/a n/a

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

Current Release for OpenSim

OpenSim versions of Firestorm do not have Havok. That only matters if you're uploading mesh objects and need to specify the mesh physics properties, or if you need to manipulate the region navmesh for pathfinding. The terms of the Havok license prohibit its use anywhere but Second Life, so it's not present in OpenSim versions.
In order to be able to login to grids other than Second Life, you need to enable a setting. From the login screen, go to
Viewer Menu → Preferences → Advanced → Allow login to other grids. Also see Grid Selector

Firestorm 6.4.12 (62831) Release

Firestorm 6.4.12 (62831) Release Notes

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

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.4.12.62831OS 64 bit Windows Setup.exe
MD5 Checksum: 440F267236E7507B6E2398C920EE9C4E
SHA1 Checksum: E2CEAED5455DAEA70AA3E89E9A1889A03D1ED7B0
File size: 116 MB (121,618,492 bytes)
Windows
32-bit OpenSim
32 and 64 OpenSim only Full Release Firestorm Release 6.4.12.62831OS 32 bit Windows setup.exe
MD5 Checksum: 9B438C032AE521486DC4FC3BDAE208AC
SHA1 Checksum: 8D77972C2C6A476E20BEEFBD2E836C6A92838AF3
File size: 111 MB (115,910,399 bytes)

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.4.12.62831OS 64 bit Intel Mac.dmg
MD5 Checksum: 1730251999CDC8F500CAA269B4DE9D14
SHA1 Checksum: D841F0BE68AB7450F211927920A302609719922B
File size: 181 MB (189,946,057 bytes)
Mac
32-bit OpenSim
32 and 64 OpenSim only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit OpenSim
64-bit only OpenSim Only Full Release Firestorm Release 6.4.12.62831OS 64 bit Linux.tar.bz2
MD5 Checksum: 7088355DDF2E627D024B26F618FECC1B
SHA1 Checksum: 05E63163BFF311C961EF81F2FA543B3B7FBDF4B9
File size: 167 MB (175,076,128 bytes)
Linux
32-bit OpenSim
32 and 64 OpenSim Only n/a n/a

Supported Operating Systems

Windows

  • Windows 8.1 and 10 32bit and 64bit are supported.
    Earlier versions of Windows are not supported.
  • Windows 10 - Firestorm 6.0.2 and later are compatible with Windows 10.
    However, if you are running Windows 10 on a system with an older Intel graphics card which does not support Windows 10 - Intel HD 2000, Intel HD 3000 or anything marked as “No” for Windows 10 on this list,
    you will only be able to run the 32bit versions of Firestorm 6.0.2 and later. even if you have a 64bit version of Windows 10.
    Please see this page for detailed instructions if you are running Windows 10 on an older unsupported Intel card and have problems running Firestorm 6.0.2 or later.

Mac

  • FS is built and tested on Catalina (10.15)
  • Some additional beta testing is done on OSes back to El Capitan (10.11)
  • Performance may vary on OSes prior to High Sierra (10.13) (Note: High Sierra reached End of Life in November 2020)
  • FS probably will not run on anything prior to El Capitan (10.11)

Linux

  • Ubuntu LTS (16.04, 18.04, 20.04) 64-bit is supported, as is any derivative or variant. We are unable to offer support for 32-bit Linux, or any other distribution.
  • For all other Linux distributions, feel free to submit details of your success and/or failure to any Firestorm team member or to the Firestorm Jira. Contributions may be included on our wiki to benefit others.
  • Some additional libraries and/or packages may be needed; they are listed on this page.
  • Older hardware may not be able to support Firestorm, even when a supported OS is installed.

Additional Downloads to Fix Problems

Windows

  • SLURLs not working in your browser, or choose to open with a different viewer (Windows)

Additional Downloads to Enhance User Experience

Quicktime

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

GStreamer

for Linux only

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

Growl

  • 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

Video Drivers

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

Nvidia Video Driver

  • Latest driverLast checked 08/12/2020 - Windows: 457.51 (2020.12.2) - Linux: 455.23.04 (2020.9.17)

ATI Video Driver

  • Latest driverLast checked 08/12/2020 - Windows: Adrenalin 2020 Edition 20.11.2 (11/18/2020) - Linux: 20.45 (11/18/2020)

Intel Video Driver

Source code

firestorm_change_log_6.4.13.63251 - created

downloads - old revision restored (2020/12/30 07:34)

$
0
0

Firestorm Viewer Downloads For Second Life

Firestorm Viewer is certified to be free of viruses and malware.

Current Release for Second Life

Firestorm 6.4.12 (62831) Release

Firestorm 6.4.12 (62831) Release Notes

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

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Windows Setup.exe
MD5 Checksum: 1EC526D25881CF9D559902A65D254B85
SHA1 Checksum: 0C04A3BA1057ABEFF2FE350B0DDA174B761DB4CE
File Size: 117 MB (122,955,343 bytes)
Windows
32-bit
32 and 64 SL only Full Release Firestorm Release 6.4.12.62831 32 bit Windows setup.exe
MD5 Checksum: 82CC75C2987F380E41A2D76F5C84B6AD
SHA1 Checksum: 987163817543E62228F37614AD17989FFABF37CF
File size: 112 MB (117,095,904 bytes)

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Intel Mac.dmg
MD5 Checksum: 2159B237EE5DAEF870AEAFDA8557D679
SHA1 Checksum: CD3135CB416B7530B544A47050FE2792D80E25DA
File size: 183 MB (192,160,108 bytes)
Mac
32-bit
32 and 64 SL only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit
64-bit only SL only Full Release Firestorm Release 6.4.12.62831 64 bit Linux.tar.bz2
MD5 Checksum: 91FFDC888E4431C835C97B48FE7C8724
SHA1 Checksum: 331CE0807E2C596B39A6FCDD80F92830E9A93CF0
168 MB (175,719,800 bytes)
Linux
32-bit
32 and 64 SL only n/a n/a

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

Current Release for OpenSim

OpenSim versions of Firestorm do not have Havok. That only matters if you're uploading mesh objects and need to specify the mesh physics properties, or if you need to manipulate the region navmesh for pathfinding. The terms of the Havok license prohibit its use anywhere but Second Life, so it's not present in OpenSim versions.
In order to be able to login to grids other than Second Life, you need to enable a setting. From the login screen, go to
Viewer Menu → Preferences → Advanced → Allow login to other grids. Also see Grid Selector

Firestorm 6.4.12 (62831) Release

Firestorm 6.4.12 (62831) Release Notes

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

Windows

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.4.12.62831OS 64 bit Windows Setup.exe
MD5 Checksum: 440F267236E7507B6E2398C920EE9C4E
SHA1 Checksum: E2CEAED5455DAEA70AA3E89E9A1889A03D1ED7B0
File size: 116 MB (121,618,492 bytes)
Windows
32-bit OpenSim
32 and 64 OpenSim only Full Release Firestorm Release 6.4.12.62831OS 32 bit Windows setup.exe
MD5 Checksum: 9B438C032AE521486DC4FC3BDAE208AC
SHA1 Checksum: 8D77972C2C6A476E20BEEFBD2E836C6A92838AF3
File size: 111 MB (115,910,399 bytes)

Mac

Version32/64-bitGridsHavokLevel of SupportDownload
Mac
64-bit OpenSim
64-bit only OpenSim only Full Release Firestorm Release 6.4.12.62831OS 64 bit Intel Mac.dmg
MD5 Checksum: 1730251999CDC8F500CAA269B4DE9D14
SHA1 Checksum: D841F0BE68AB7450F211927920A302609719922B
File size: 181 MB (189,946,057 bytes)
Mac
32-bit OpenSim
32 and 64 OpenSim only n/a n/a

Linux

Version32/64-bitGridsHavokLevel of SupportDownload
Linux
64-bit OpenSim
64-bit only OpenSim Only Full Release Firestorm Release 6.4.12.62831OS 64 bit Linux.tar.bz2
MD5 Checksum: 7088355DDF2E627D024B26F618FECC1B
SHA1 Checksum: 05E63163BFF311C961EF81F2FA543B3B7FBDF4B9
File size: 167 MB (175,076,128 bytes)
Linux
32-bit OpenSim
32 and 64 OpenSim Only n/a n/a

Supported Operating Systems

Windows

  • Windows 8.1 and 10 32bit and 64bit are supported.
    Earlier versions of Windows are not supported.
  • Windows 10 - Firestorm 6.0.2 and later are compatible with Windows 10.
    However, if you are running Windows 10 on a system with an older Intel graphics card which does not support Windows 10 - Intel HD 2000, Intel HD 3000 or anything marked as “No” for Windows 10 on this list,
    you will only be able to run the 32bit versions of Firestorm 6.0.2 and later. even if you have a 64bit version of Windows 10.
    Please see this page for detailed instructions if you are running Windows 10 on an older unsupported Intel card and have problems running Firestorm 6.0.2 or later.

Mac

  • FS is built and tested on Catalina (10.15)
  • Some additional beta testing is done on OSes back to El Capitan (10.11)
  • Performance may vary on OSes prior to High Sierra (10.13) (Note: High Sierra reached End of Life in November 2020)
  • FS probably will not run on anything prior to El Capitan (10.11)

Linux

  • Ubuntu LTS (16.04, 18.04, 20.04) 64-bit is supported, as is any derivative or variant. We are unable to offer support for 32-bit Linux, or any other distribution.
  • For all other Linux distributions, feel free to submit details of your success and/or failure to any Firestorm team member or to the Firestorm Jira. Contributions may be included on our wiki to benefit others.
  • Some additional libraries and/or packages may be needed; they are listed on this page.
  • Older hardware may not be able to support Firestorm, even when a supported OS is installed.

Additional Downloads to Fix Problems

Windows

  • SLURLs not working in your browser, or choose to open with a different viewer (Windows)

Additional Downloads to Enhance User Experience

Quicktime

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

GStreamer

for Linux only

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

Growl

  • 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

Video Drivers

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

Nvidia Video Driver

  • Latest driverLast checked 08/12/2020 - Windows: 457.51 (2020.12.2) - Linux: 455.23.04 (2020.9.17)

ATI Video Driver

  • Latest driverLast checked 08/12/2020 - Windows: Adrenalin 2020 Edition 20.11.2 (11/18/2020) - Linux: 20.45 (11/18/2020)

Intel Video Driver

Source code

Viewing all 5258 articles
Browse latest View live