

What is chat? Chat is essentially how we communicate with other residents in Second Life. There are two major categories of chat; Text chat and Voice chat. This page will focus on text chat. For info about voice chat, go here Voice.
There is a nicely detailed write-up of chat and IM windows, and associated Firestorm settings, here.
There are 4 types of chat:
Alternatively, you can choose to show the “send” button at the end of the nearby chatbar which you can select the chat type (whisper, say, or shout) but it will remain in whatever chat type until you change it. To enabled this “send” button, go to Preferences→ Chat -> Typing→ Show chat type / send chat button in chat bar.
The viewer has the ability to translate text into a language that you choose but you need to set up an account with Bing or Google to do so. See here for more information. Previously, Google provided free translation services, but this has now ended, and you must establish your own account with Bing or Google which may incur a cost. Please be aware that chat translation only works in nearby chat and not in IMs or group chat.
There are several ways to start an instant message:
Provided you are allowed to join a group chat, go to group tab in Contacts window and either double click on the group or select the group and press the IM/call button.
If you are in the group tab in the People Panel, double clicking on the group will start chat or you can right-click on the selected group and select chat.
To close the group chat window for the duration of the login session, press the X button at top right of that group window. If you want to close it temporarily, press the Zz button at top right to put the group in “snooze” mode. Snooze mode will close the chat for a set duration and after that duration is done, any new chat in that group will make that group's chat window open again. Chat group duration default time is set to 900s but can be changed in Preferences> Chat> Chat Window.
A conference is a private conversation with two or more Residents. It is similar to group chat, but more dynamic, since everyone on your friends list can be invited, as well as everyone where you got a calling card from.
To start a conference chat:
Note: Conferences are limited to twenty participants.
The terminology has changed so please read here.
To save or not save your chat logs and transcripts (nearby, IM/Group), go to Preferences→ Privacy -> Logs & Transcripts and select the options under Save:.
The location for the saved chat logs and transcripts depends on your operating system but can be found and changed in Network & Files -> Directories→ Conversation logs and transcripts location. Press the Set button to change it to a different folder.
If you are offline and an IM is sent to you, the IM is backlogged and will appear as a set of notification icons in the upper right or lower left of your Viewer when you log in.
The backlog can contain up to 25 IMs (cap limit), including inventory transfers, group invitations, and group notifications. If someone gives you an inventory item (generating an IM message), the message is placed in your inventory's Trash folder, and you can retrieve it when you return. If a scripted object sends the inventory, it is deleted immediately.
Second Life will keep the IMs in the backlog for 31 days. If you do not log in within the 31 days to view your IMs, they will be deleted.
To ensure you get your offline IMs and not get them capped, they can be sent to the email address that is connected to your contact information. To enable this option, go to Preferences→ Chat -> Notices→ check Email me IMs when I'm offline.
If you send a reply to an offline IM via email, the original sender will receive it as an IM. The email reply is limited to 1023 characters and must be sent within 5 days.
There are several ways to have your chat windows set up to your liking.
Docked in the conversations window:
As separate windows:
How to dock/undock the chat windows:
How to rearrange the IMs:
At the top of each Group and IM chat windows, there are a set of buttons that each has a different function.
How do I make the group chat look like the old style chat?
How do I change the size of the font in chat?
How do I get my Contacts window back:
See this page for documentation on Firestorm 4.7.7 (48706) and earlier.
If you have a problem using Firestorm, there are a number of ways in which you can get help. It is strongly recommended that you try the following, in order.
As of 1 Jan 2013, support for Phoenix Viewer has been discontinued. You may consult the Phoenix Viewer Wiki for information.
The viewer has extensive online documentation, explaining the features and how to use them. If there is some feature which you do not know how to use, then please consult the documentation.
If you have problems with things not working as they should, or are crashing a lot, or being disconnected, etc, then the best place to go is the troubleshooting section of our online wiki.
If the above do not provide a solution for you, or you need urgent help, then the best way is to contact one of our several in-world Firestorm support groups. Please view our tips, rules, and guidelines for our help groups here.
Please note, group chat lag can be a serious issue. So when you go to a support group for help, please bear in mind the following:
We hold in-world classes explaining how to use Firestorm, what the preferences and menus mean, and so on. A great way to learn how to use the viewer, with an opportunity to ask questions as well.
The class schedule is posted here.
If you believe you have found a bug - or if you were unable to get help from the wiki or in a support group - then please file a report via our JIRA (bug tracker). In order to best help, please supply basic information.
The Firestorm Support Team only provides support for the latest official release of Firestorm Viewer. Earlier versions, even those released by the Firestorm team, are subject to limited or no support.
CtrlAltStudio Viewer (CAS) is a third-party viewer that is substantially based on but unrelated to Firestorm. At present, its website tells users:
This is not to be interpreted to mean that users should seek help with CAS problems from the Firestorm Support Team. It concerns the development of the viewer, rather than support, which means the appropriate source for such information is the JIRA, where viewer bug reports and feature requests are handled.
Steps for addressing your CAS problem:
Even if the version of Firestorm you are running is the same as the current official version, we cannot provide support for it in our support groups if you built it on your own system. There might be subtle differences in build environments that generate unexpected results. Download the latest official version and test there before reporting your bug or seeking support.
Only the most recent official release of the viewer is supported. Additional previous versions continue to be available (usually the two most recent builds but sometimes one or two more) under the assumption that if they work for you, there is no need to force an update. If problems develop, however, you must update to the most recent version to receive assistance.
If you know or suspect that your problem is not a viewer bug:
If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.
This is a known issue with recent Intel graphics drivers, affecting other graphics applications besides SL viewers. Please refer to FIRE-21264 for information and known workarounds.
If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.
If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.
If you have Intel HD 2000 or 3000 graphics, refer to this page.
If your laptop has an Intel CPU and also has either an AMD or Nvidia graphics system, it may have the ability to switch between the Integrated Intel graphics or power savings, or the AMD/Nvidia for performance. But sometimes Firestorm isn't automatically configured to use the high performance graphics.
You can confirm this issue by looking at Help → About Firestorm and checking the name of the graphics card listed. If it says Intel, please follow the steps on this page.
This mysterious flashing problem has been reported numerous times now and after some investigation we believe we finally have a repro for what's causing the issue. We do not yet know the specifics of exactly which systems are affected.
Typically the issue arises when Worn Rigged Mesh is in view and has at least one texture containing alpha and set to alpha blend mode. Alpha masking and emissive mask do not reproduce the problem.
We have also verified that this reproduces using the Official LL Viewer.
The Following Table shows which systems and drivers we have tested and whether they reproduce the Flashing Issue.
Graphics Card | Driver | Operating System | Repoduced |
Intel(R) HD Graphics 530 | 10.18.0015.4271 | Windows 10 64-bit (Build 10240) | Yes |
Intel(R) HD Graphics 530 | 10.18.0015.4279 | Microsoft Windows 10 64-bit (Build 10240) | Yes |
Intel(R) HD Graphics 520 | 10.18.0015.4293 | Microsoft Windows 10 64-bit (Build 10586) | Yes |
Intel(R) HD Graphics 520 | 10.18.0015.4248 | Microsoft Windows 10 64-bit (Build 10240) | Yes |
Intel(R) HD Graphics 520 | 10.18.0015.4279 | Microsoft Windows 10 64-bit (Build 10240) | Yes |
Intel(R) HD Graphics 520 | 20.19.0015.4300 | Microsoft Windows 10 64-bit (Build 10586) | Yes |
Intel(R) HD Graphics 530 | 20.19.0015.4352 | Microsoft Windows 10 64-bit (Build 10586) | NO This Driver does NOT reproduce the issue |
The Driver Version linked in the above table (DRIVER VERSION: 15.40.14.64.4352 & 15.40.14.32.4352) Has not reproduced the issue for us and is the Driver we recommend that you download direct from Intel.
If you receive the following Message when installing the Intel Driver:
The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer.
This is an indication that you have an OEM Driver installed by the manufacturer. This Leaves you with two options:
At Your Own Risk
If decide to wait fro an update from your computer manufacturer, or are simply uncertain about removing an installed driver, the following steps may help to make things more tolerable for you until your drivers are updated.
Note: If you install the recommended driver above and still experience issues please read the related jira FIRE-17290 and add your details to the comments. Instructions for using the Jira can be found HERE
See this page for documentation on Firestorm 5.0.1 (52150) and earlier.
The events we promote on the viewer Message of the Day are:
The idea behind what we agree to promote and what we don't are simple. If it's going to benefit you financially either directly or indirectly (publicity stunt), we are not going to promote it. However, if it's purely for residents, hosted by residents with no profits or financial benefits either directly or indirectly to you or those involved, we will consider it. We have always been, and will always be, about the community.
We cannot however promote religious events or anything that may offend or exclude other races, creeds, cultures or persons. For example, we were asked to promote Memorial Day, and while we support troops all around the world 100%, it is an American event which other countries do not participate in. That makes it exclusionary and not something that qualifies for us to promote.
Note: we do not promote anything on the login page itself. Just the Message of the day.
(Information extracted from this blog post.)
We are no longer able to run Messages of the Day for 'hunt' type events as we're unable to verify all the locations contained in the hunt are suitable for a 'General' audience.
Partial day events, events that don't run all day and only run for a few hours1) will not receive a 24 hour Message of the day. It's a waste of valuable Message of the Day space. Approved partial day events Message of the Day will be run for two hours preceding the event and will end five minutes after your event has begun.2)The rule regarding this is still being discussed internally, it may go into effect or be removed.
Your Event must be suitable for a 'General' audience.
This includes the region hosting your event, as well as your web site and all its contents including any advertisements that may appear on your web pages, (not only the page we will be linking to in the MotD).
Events on 'Mature' regions will be considered on a case by case basis only and we must be given early access to your event space for assessment. 3) We will let you know the specific 'who' to give access to if needed when your MotD application is evaluated.4)
Adult events and events on 'Adult' regions will not be promoted in the Firestorm Message of the Day.
Firestorm isn't only used by adults. We also have minors who log in to Second Life using our viewer so we must keep our MotD safe for their experience as well.
If in doubt, ask yourself these questions:
Would I want my grandmother attending my event?
Would I ask a kindergarten class to attend my event?
Would I ask my co-workers to attend my event?
See Maturity ratings - Second Life, for more information about Second Life maturity ratings.
NOTE: The Message of the Day isn't designed to get people to your event, it's designed to get people to click your website link. It's up to your website to get people to want to visit your event.
Make sure the page on your website we will be linking to in the Message of the Day:
You should save promoting your overall web site and more information about your event for your event. Once people are at your event you can tell them what ever you want, it's your event! The page we link to in the Message of the Day should be focused on getting people to want to go to your event.
IMPORTANT:
We can NOT put a SLURL as a link in the Message of the Day, it won't work, it has to be a link to a live web page.
When designing the web page we will link to for your event;
Keep in mind, when people see the Message of the Day they are trying to log into Second Life, not your web page, if your web page doesn't give them what they want, and quickly, most won't stick around to find it.
Please please please be sure and promote your event in other mediums as well! See Priorities below as to why this is important!
The Firestorm Message of the Day priorities governing what Message of the Day will be run at any time are as follows:
This page and our MotD rules are subject to change without notice. You should check and read this page before submitting any Message of the Day request, even if we've run a Message of the Day for you previously.
If you have a community event that you would like promoted on our MOTD you can send a request to jessica.lyon@phoenixviewer.comlassie@phoenixviewer.com for consideration. We do not charge for promoting your event nor will we accept any benefits, financial or otherwise. Though you can expect we may attend your event . Please provide your in-world name and details to the event. All events we promote are required to have a website we can link to.
The name of your event in the subject of your email. For example, MotD Request for Watching Grass Grow Event.
And in the body of your request:
Once this is received your request will be evaluated for inclusion in the Firestorm MotD. If you don't hear back from us in a few days consider everything good to go. We will email you if we need more information or if something is missing.
If your MotD is declined you will be replied to as to why your event MotD wasn't accepted.Good luck with your event!
Included for transparency.
Coming soon!
Click here to apply for a Firestorm MotD (Doesn't work yet.)
But is still a good template for what you should send us in an email about your event!
For Phoenix documentation, please click here.
Wiki pages in other languages | ||||||
---|---|---|---|---|---|---|
Deutsch | Español | Francophone | Italiano | Nederlands | Polski | Русский |
The following videos are about the Firestorm AO:
For Phoenix documentation, please click here.
Wiki pages in other languages | ||||||
---|---|---|---|---|---|---|
Deutsch | Español | Francophone | Italiano | Nederlands | Polski | Русский |
The following videos are about the Firestorm AO:
For Phoenix documentation, please click here.
Wiki pages in other languages | ||||||
---|---|---|---|---|---|---|
Deutsch | Español | Francophone | Italiano | Nederlands | Polski | Русский |
Diese Dokumentation befindet sich im Aufbau. Vielen Dank für euer Verständnis.
Das Phoenix Viewer Projekt, Inc
Für die Dokumentation des alten Phoenix, bitte hier klicken.
As of 1 Jan 2013, support for Phoenix Viewer has been discontinued.
There is a “self help” group for those who wish to continue using Phoenix; copy/paste this URL into local chat, then open the local chat window and click the link for the group profile.
Important info concerning the future of Phoenix in SL is here.
For Firestorm documentation, please click here.
Seit dem 1 Januar 2013, wird der Phoenix Viewer nicht mehr unterstützt.
Es gibt eine englische “Selbsthilfegruppe” für die, die weiter Phoenix benutzen möchten; kopiere/einfüge diese URL in den lokalen chat und klicke dann auf den Link zum Gruppen Profil.
Dieses Wiki wird nicht entfernt, doch es wird auch nicht mehr aktualisiert.
Für die Firestorm Dokumentation, bitte hier klicken.
Wiki pages in other languages | ||||||
---|---|---|---|---|---|---|
Deutsch | Español | Francophone | Italiano | Nederlands | Polski | Русский |
See this page for documentation on Firestorm 4.6.7 (42398) and earlier.
This section covers issues related to audio, video and some aspects of search.
QuickTime is no longer needed for Windows users (and never was for linux users). Mac users, however, still need to have it.
Go to Preferences→ Sound & Media -> Sounds and make sure the volume sliders for streaming music and media are not all to the left and that there is no mute symbol (red no entry sign) on the speaker icon next to those. Make sure the Master Volume is not all to the left.
Check that Sound Source rolloff distance (Media tab) is correct; set back to default, if you changed it (5m and 30 respectively for min and max).
Go to Preferences→ Sound & Media -> Sounds and check that you have the Sounds and UI sliders up high enough and that there is no mute symbol (red no entry sign) on the speaker icon next to those.
Go to the top menu bar→ Advanced → Use Plugin Read Thread, and disable it, if it is enabled - or vice versa. (If you cannot see Advanced on the top menu, press Ctrl-Alt-D.)
If that doesn't help, first ensure that you have your bandwidth set correctly. Also, test the audio stream in your regular media player, and/or try a different audio stream in-world.
If the music volume fades as you cam around or edit objects, check the sound equalization settings in your operating system. For example, this may be caused by “Loudness equalization” being enabled in your speaker properties on Windows 7. (Refer to http://jira.phoenixviewer.com/browse/FIRE-19885.)
This error is due to Flash not being installed, or not installed correctly. See above.
If using a VEA4 TV, you get a “File could not be found” error, disable the IPv6 protocol in the Windows network adapter. Note that this is not recommended, but apparently is the only way to get this brand of TV to work.
If sound eventually cuts out on your computer while using Firestorm and the only way to get it back is to log off Firestorm, disable Audio Enhancement via the steps shown here. Another possibility is Loudness equalization; reference this JIRA.
Refer to this page for all Win10 issues.
Please ensure that you have the most recent version of Flash for Safari installed. You can get this via the normal update process, or from Adobe.
For streaming music on OS X 10.9 Mavericks, please refer to this page.
For users on Sierra, there are reports of media features (such as MOAP, TVs, web search, and web profiles) working more slowly. Ref. BUG-40552.
Both the 32-bit and 64-bit versions of Firestorm for Linux require 32-bit libraries to function. See this page for a link to your Linux flavor to verify you have all the needed audio-related packages installed and to troubleshoot stream issues.
See this page for documentation on Firestorm 4.7.9 (50527) and earlier.
These classes are based on our official Firestorm release and are conducted in voice and text except when otherwise noted. There's no need to talk, but you may want to be able to hear. We also usually have help available to answer questions in text. This schedule is subject to change.
Note that it is best if you are on Firestorm for the classes.
Locations are indicated in the far right column as follows:
Class times and days change regularly. Classes may be held any day of the week, with start times from 8am to 7pm SLT. Nonetheless, if the class times are still inconvenient you may prefer to watch recorded versions of some of these classes on YouTube.
*All times SLT*
Thursday | Aug 3 | 1:00PM – Basic Troubleshooting (TEXT ONLY) An introduction to basic methods to start locating problems. Focused on Firestorm but some parts are non-viewer-specific. | FS |
4:00PM – Firestorm Skins This class covers the differences among Firestorm's many skin options, including the Vintage Classic and Colorable User Interface skins. | FS | ||
Saturday | Aug 5 | 11:00AM – Contact Sets There is a cool feature called Contact Sets that lets you organize your contact list. We will cover how to set them up and use this epic feature. | FS |
Sunday | Aug 6 | 11:00AM – Introduction to Firestorm and the Wiki This class gives you an overview of the Firestorm Viewer and of our greatest informational resource, our Wiki, including search tips. | FS |
3:00PM – Menus 1 We will be covering the menus on the top bar, from Avatar through Help. | JU | ||
Monday | Aug 7 | 1:00PM – Menus 1 (TEXT ONLY) We will be covering the menus on the top bar, from Avatar through Help. | FS |
Tuesday | Aug 8 | 10:00AM – QuickPrefs Customization + Lag Two mini-classes in one. One discusses the causes of lag in SL. The other explains how to customize your Quick Preferences. | FS |
Wednesday | Aug 9 | 4:00PM – Backing up Settings and Logs This class covers how to save your settings and chat logs on your computer. Recommended to take this before the Clean Install class. | FS |
Thursday | Aug 10 | 1:00PM – Animation Overrider (TEXT ONLY) On Firestorm, you can save scripts and HUD space by running your AO animations through the viewer. Learn how to set up and get the most out of this feature. | FS |
Friday | Aug 11 | 9:00AM – Odds & Ends 1 This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems. | FS |
Saturday | Aug 12 | 4:00PM – Reporting Bugs, Requesting Features (TEXT ONLY) Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need. | FS |
Sunday | Aug 13 | 3:00PM – Menus 2 We will cover the Advanced and Develop menus in the top bar. | JU |
Monday | Aug 14 | 8:00AM – Preferences Set 3 We will cover some of the Firestorm preferences (Move & View, Advanced, Firestorm), based on our current release. | FS |
1:00PM – Preferences Set 4 (TEXT ONLY) We will cover some of the Firestorm preferences (Colors, Skins, Notifications, User Interface, Sounds and Media). | FS | ||
Tuesday | Aug 15 | 5:00PM – Preferences Set 2 We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release. | FS |
If things around you remain grey for a long time, or objects take a long time to pop into position, this is essentially because the data has not yet been sent to your viewer. There are a number of possible causes, and solutions or at least work-arounds: