• Show Hover Tips: This allows you to set what hover tips, if any, you see. Disable this to disable all hover tips. Otherwise, enable it and then you can opt to indicate which hover tips you want to show:
  • on All Objects
  • on Land
    
    
  • Hovertip Trigger Delay: Allows you to choose how long your mouse has to hover over something before you get a hovertip. You can specify different delays for:
    • Tooltips
    • Avatars
    • Objects
      
      
  • Show extended information in hover tips: If this is enabled, hovertips will show details about the object your mouse is over, such as the owner, prim count, etc. Otherwise, hover tips will show just the object name.
  • Show avatar group titles in hovertips: If enabled, avatars' current group titles will display, along with the name, when your mouse over them.

• Floating text fade distance (in m): Sets the distance where floating text starts to fade.
• Floating text fade range (in m): Sets the range it takes for floating text to go from fully visible to fully invisible.

• UI Scaling (may cause side effects): Adjust the slider to choose the UI size. The maximum value depends on your OS: Eg, for Win10, it is 4.5, for earlier Windows, 2.5.
  NOTE that too high may mean you cannot see all of your UI. This may also “break” some UI elements.
  • Automatically detect UI scaling factor: (Windows only) Have FS determine the best possible value for your system.

• Script Dialogs per Object: Controls how many dialogs get opened:
  • One per object - means if a second one opens either the first or second will not appear.
  • One per Object & Channel - means you can have more than one per object but only if they use different channels to interact.
  • Unconstrained - means you can see as many menus/dialogs as may be generated.
    • Remove “Block” button: Popup windows that are generated by scripts have a “Block” button on them; this allows you to easily mute the object that sent the popup, in cases of popup spam griefing. If you find this confusing and think you might click it by mistake, then you can disable it here.
      Note: muting an object also mutes the object owner; do not block popups from vendors without very good reason, or you will not receive items you purchase from them.
      You can review your listed of blocked people and objects in the Block/Mute List.
• Script Dialogs Position: You can select where on the screen scripted popup windows should appear.
  • Animate Script Dialogs: Enable this to replicate old style (V1) behavior when opening script dialogs. Only works if they open at the top of the screen.

• Visible rows per script dialog: Maximum number of lines visible in a script dialog window.

• Use Pie Menu: Allows you to have pie menus (on by default). If disabled, this gives the V2-style vertical drop down instead. You can override the colors used by the pie menu in Preferences→ Colors -> Miscellaneous.
  • Enable text animation: If enabled, the text within the pie is also animated.
  • Enable outer ring shade: Adds shading to the outside of the ring, to further draw attention to the selected “slice”.
• Group Group Notices and chiclets in Top Right: Moves other dialogs (group notices, payments, etc.) to the topright corner (V1 style).
• Hide group and IM chat chiclets: If this is enabled, the chiclets representing open and new IM and group chat messages will be hidden, leaving on the general chat bubble; if this is clicked, you will get a list of open IMs/groups chats.
• Use legacy list layout for Notifications window: Enable this to use the old style notifications window.
• Remap shortcuts already used by Linux (Linux only;requires restart): Shortcuts already used by Linux (Ctrl-Alt-Fn) will be remapped to use Ctrl-Shift instead.

• Flashing IM tabs override: allows you to fine tune how long and fast the IM tabs flash:
  • Number of times IM tabs flash
  • IM tab flash rate (Hz)

• Show traffic indicator in upper right corner of the screen: Enable this if you want to display a small traffic meter in the upper right corner of the menu bar. This will show your current packet loss (left bar), and bandwidth usage (right bar).
  • Use legacy period mean per second display for lag meter: If enabled, Firestorm will use the legacy method of showing the period mean per second value in the meter instead of the current observed value.
  • Clicking on traffic indicator opens Statistics instead of the Lag meter: Opens Statistics instead of Lag meter.
• Show media controls in top menu: If you disable this, the media controls are removed from the upper right of the screen. You can still acess volume controls in Preferences→ Sound & Media -> Sounds, if needed, or just re-enable this option.
• Show Location in top menu: Shows the current region and parcel names in the top menu bar.
  • Show simulator channel in top menu: Shows the region channel name in the status bar. Nothing is shown for Main Channel regions.
• Show Menu Search: Enable searching the top menu bar.
• Show Currency Balance: Display your L$ balance in the menu bar.
• Enable mouse rollover popup on status bar menu icons: If enabled, displays tooltips when you mouse over items in the top menu bar.

• Show Favorites Bar: Display the contents of your Favorites folder.
• Show Navigation and Search Bar: Add this bar to the top of the screen.
  • Show Search Bar: Allows the search portion of the navigation bar to be enabled/disabled

• Open avatar profile directly when clicking on its name: If enabled, when you click on someone's name in chat, it opens the profile immediately. With this disabled, you get a small summary window.
• Use web profiles by default: Displays user profiles as web profiles rather than in a profile window.
• Disable automatic opening of block list: Enable this option if you do not want the block (mute) list to open when you block a person or object.
• 'Friends' and 'Groups' in 'Comm' menu opens the V5 based windows: If enabled, Friends and Groups will open in the People panel; otherwise they will open in the Contacts panel.
• Use legacy object properties: If enabled, this will show the old style window when right clicking an item in Inventory and selecting Properties. If disabled, properties will be shown within the Inventory window instead.

• Use stand-alone windows:
  • Group profiles: If enabled, group profile windows will open in separate windows; if disabled, they will open in the same window, with the second opened replacing the first.
  • Teleport history: if enabled, teleport history will open in a window separate from the landmarks window.
  • Block/mute list: Keeps the list of blocked residents separate from the people panel.
  • Landmarks, place details and teleport history details: Similar to the above, but keeps each type of “location” window separate, rather than grouping onto a single window.

• Extend teleport history by: Enable these options to record additional information in your teleport history:
  • Position
  • Date

• Contact list options: Options concerning what is shown in your friends list, and how it is sorted.
  Note that some options have no effect if you have the corresponding option disabled in Prererences → General. For example, if you have disabled display names, then sorting your friends list by display name will have no effect, and therefore is best set to Username.
  • Visible name columns: Here you can select which name colums to shwo in your friends list: username, display name, or full name (see below).
  • Sort list by: What to use to sort your friends list, username or display name.
  • Show full name as: a full name can be shown as Username (Display name), or Display name (username).
  • Show permissions column: If enabled, this shows what permissions you have granted to each friends (eg, online status, edit rights, showing location on map, etc), and which they have granted to you.
  • Show search filter: adds a search box to the list window.

• Inventory Options:
  • Hide empty system folders from inventory: If enabled, the inventory window will not display any system folders (eg, Favorites, Landmarks, etc) that have nothing in them.
  • Show the Received Items folder in normal inventory: If enabled, this folder will be show in the normal inventory list of folders, rather than as a panel under the folder list.
    • Always show Received Items buttons at th bottom of inventory: Only available if the option above is enabled. When this is on, you will also have the button showing on the inventory window.
  • Allow separate search terms on each tab in inventory: If enabled, you can enter different words/phrases in the search bar of the Inventory window: each of Inventory, Recent and Worn can be searched independently.

• Notification Display Settings (Popups, console, toasts): This is where you can fine tune the way your “Toasts” look and act:
  • Space between lowest Toast and bottom (pixels)
  • Notification Toast life (seconds): How long group notices remain open.
  • Tip Toast life (seconds): applies to notificants such as after a TP, you see “Teleport completed from…”. Also includes the friend on/offline notification toasts.
  • Nearby Chat Toast life (seconds)
  • Nearby Chat Toast z-offset (pixels)
  • Nearby Chat Toast fade time (seconds)
  • Startup toast life (seconds)
  • Normal Toast fade time (seconds)
  • Gap between Toasts (pixels)
  • Height of Overflow Toast (pixels)
  • Width of Nearby Chat Toast (%)

• Show toasts in front of other windows: If enabled, toasts will always stay above (cover) any other open windows; otherwise, other widows will be allowed to cover, and potentially hide, toasts.
• Use new region restart notification: Enable this to use the new system for region restart notifications, which can include a distinctive sound and screen shake.
  The alert sound feature can be enabled/disabled in Preferences → Sound & Media -> UI Sounds 3.
  • Don't shake my screen when the region restart alert message is shown: Check this to disable the screen shake feature.

• Font Scheme: Allows you to choose one of the following fonts from the drop down menu.
  • Dyslexia:
    
  • Celestia medium redux:¹⁾
    
  • Droid:
    
  • Mobi:
    
  • Ubuntu:
    
  • Liberation:
    
  • Deja Vu:
    
  • Roboto:
    
  • Noto:
    
• Font Size Adjustment: Lets you change the size of the font. NOTE that this may cause issues.
• Chat Line spacing: spacing between lines of text.
• Folder Item Height: Height of items in inventory.

• Show Hover Tips: This allows you to set what hover tips, if any, you see. Disable this to disable all hover tips. Otherwise, enable it and then you can opt to indicate which hover tips you want to show:
  • on All Objects
  • on Land
    
    
  • Hovertip Trigger Delay: Allows you to choose how long your mouse has to hover over something before you get a hovertip. You can specify different delays for:
    • Tooltips
    • Avatars
    • Objects
      
      
  • Show extended information in hover tips: If this is enabled, hovertips will show details about the object your mouse is over, such as the owner, prim count, etc. Otherwise, hover tips will show just the object name.
  • Show avatar group titles in hovertips: If enabled, avatars' current group titles will display, along with the name, when your mouse over them.

• Floating text fade distance (in m): Sets the distance where floating text starts to fade.
• Floating text fade range (in m): Sets the range it takes for floating text to go from fully visible to fully invisible.

• UI Scaling (may cause side effects): Adjust the slider to choose the UI size. The maximum value depends on your OS: Eg, for Win10, it is 4.5, for earlier Windows, 2.5.
  NOTE that too high may mean you cannot see all of your UI. This may also “break” some UI elements.
  • Automatically detect UI scaling factor: (Windows only) Have FS determine the best possible value for your system.

• Script Dialogs per Object: Controls how many dialogs get opened:
  • One per object - means if a second one opens either the first or second will not appear.
  • One per Object & Channel - means you can have more than one per object but only if they use different channels to interact.
  • Unconstrained - means you can see as many menus/dialogs as may be generated.
    • Remove “Block” button: Popup windows that are generated by scripts have a “Block” button on them; this allows you to easily mute the object that sent the popup, in cases of popup spam griefing. If you find this confusing and think you might click it by mistake, then you can disable it here.
      Note: muting an object also mutes the object owner; do not block popups from vendors without very good reason, or you will not receive items you purchase from them.
      You can review your listed of blocked people and objects in the Block/Mute List.
• Script Dialogs Position: You can select where on the screen scripted popup windows should appear.
  • Animate Script Dialogs: Enable this to replicate old style (V1) behavior when opening script dialogs. Only works if they open at the top of the screen.

• Visible rows per script dialog: Maximum number of lines visible in a script dialog window.

• Use Pie Menu: Allows you to have pie menus (on by default). If disabled, this gives the V2-style vertical drop down instead. You can override the colors used by the pie menu in Preferences→ Colors -> Miscellaneous.
  • Enable text animation: If enabled, the text within the pie is also animated.
  • Enable outer ring shade: Adds shading to the outside of the ring, to further draw attention to the selected “slice”.
• Group Group Notices and chiclets in Top Right: Moves other dialogs (group notices, payments, etc.) to the topright corner (V1 style).
• Hide group and IM chat chiclets: If this is enabled, the chiclets representing open and new IM and group chat messages will be hidden, leaving on the general chat bubble; if this is clicked, you will get a list of open IMs/groups chats.
• Use legacy list layout for Notifications window: Enable this to use the old style notifications window.
• Remap shortcuts already used by Linux (Linux only;requires restart): Shortcuts already used by Linux (Ctrl-Alt-Fn) will be remapped to use Ctrl-Shift instead.
• Prevent statistics window from gaining focus

• Flashing IM tabs override: allows you to fine tune how long and fast the IM tabs flash:
  • Number of times IM tabs flash
  • IM tab flash rate (Hz)

• Show traffic indicator in upper right corner of the screen: Enable this if you want to display a small traffic meter in the upper right corner of the menu bar. This will show your current packet loss (left bar), and bandwidth usage (right bar).
  • Use legacy period mean per second display for lag meter: If enabled, Firestorm will use the legacy method of showing the period mean per second value in the meter instead of the current observed value.
  • Clicking on traffic indicator opens Statistics instead of the Lag meter: Opens Statistics instead of Lag meter.
• Show media controls in top menu: If you disable this, the media controls are removed from the upper right of the screen. You can still acess volume controls in Preferences→ Sound & Media -> Sounds, if needed, or just re-enable this option.
• Show Location in top menu: Shows the current region and parcel names in the top menu bar.
  • Show simulator channel in top menu: Shows the region channel name in the status bar. Nothing is shown for Main Channel regions.
• Show Menu Search: Enable searching the top menu bar.
• Show Currency Balance: Display your L$ balance in the menu bar.
• Enable mouse rollover popup on status bar menu icons: If enabled, displays tooltips when you mouse over items in the top menu bar.

• Show Favorites Bar: Display the contents of your Favorites folder.
• Show Navigation and Search Bar: Add this bar to the top of the screen.
  • Show Search Bar: Allows the search portion of the navigation bar to be enabled/disabled

• Open avatar profile directly when clicking on its name: If enabled, when you click on someone's name in chat, it opens the profile immediately. With this disabled, you get a small summary window.
• Use web profiles by default: Displays user profiles as web profiles rather than in a profile window.
• Disable automatic opening of block list: Enable this option if you do not want the block (mute) list to open when you block a person or object.
• 'Friends' and 'Groups' in 'Comm' menu opens the V5 based windows: If enabled, Friends and Groups will open in the People panel; otherwise they will open in the Contacts panel.
• Use legacy object properties: If enabled, this will show the old style window when right clicking an item in Inventory and selecting Properties. If disabled, properties will be shown within the Inventory window instead.

• Use stand-alone windows:
  • Group profiles: If enabled, group profile windows will open in separate windows; if disabled, they will open in the same window, with the second opened replacing the first.
  • Teleport history: if enabled, teleport history will open in a window separate from the landmarks window.
  • Block/mute list: Keeps the list of blocked residents separate from the people panel.
  • Landmarks, place details and teleport history details: Similar to the above, but keeps each type of “location” window separate, rather than grouping onto a single window.

• Extend teleport history by: Enable these options to record additional information in your teleport history:
  • Position
  • Date

• Contact list options: Options concerning what is shown in your friends list, and how it is sorted.
  Note that some options have no effect if you have the corresponding option disabled in Prererences → General. For example, if you have disabled display names, then sorting your friends list by display name will have no effect, and therefore is best set to Username.
  • Visible name columns: Here you can select which name colums to shwo in your friends list: username, display name, or full name (see below).
  • Sort list by: What to use to sort your friends list, username or display name.
  • Show full name as: a full name can be shown as Username (Display name), or Display name (username).
  • Show permissions column: If enabled, this shows what permissions you have granted to each friends (eg, online status, edit rights, showing location on map, etc), and which they have granted to you.
  • Show search filter: adds a search box to the list window.

• Inventory Options:
  • Hide empty system folders from inventory: If enabled, the inventory window will not display any system folders (eg, Favorites, Landmarks, etc) that have nothing in them.
  • Show the Received Items folder in normal inventory: If enabled, this folder will be show in the normal inventory list of folders, rather than as a panel under the folder list.
    • Always show Received Items buttons at th bottom of inventory: Only available if the option above is enabled. When this is on, you will also have the button showing on the inventory window.
  • Allow separate search terms on each tab in inventory: If enabled, you can enter different words/phrases in the search bar of the Inventory window: each of Inventory, Recent and Worn can be searched independently.

• Notification Display Settings (Popups, console, toasts): This is where you can fine tune the way your “Toasts” look and act:
  • Space between lowest Toast and bottom (pixels)
  • Notification Toast life (seconds): How long group notices remain open.
  • Tip Toast life (seconds): applies to notificants such as after a TP, you see “Teleport completed from…”. Also includes the friend on/offline notification toasts.
  • Nearby Chat Toast life (seconds)
  • Nearby Chat Toast z-offset (pixels)
  • Nearby Chat Toast fade time (seconds)
  • Startup toast life (seconds)
  • Normal Toast fade time (seconds)
  • Gap between Toasts (pixels)
  • Height of Overflow Toast (pixels)
  • Width of Nearby Chat Toast (%)

• Show toasts in front of other windows: If enabled, toasts will always stay above (cover) any other open windows; otherwise, other widows will be allowed to cover, and potentially hide, toasts.
• Use new region restart notification: Enable this to use the new system for region restart notifications, which can include a distinctive sound and screen shake.
  The alert sound feature can be enabled/disabled in Preferences → Sound & Media -> UI Sounds 3.
  • Don't shake my screen when the region restart alert message is shown: Check this to disable the screen shake feature.

• Font Scheme: Allows you to choose one of the following fonts from the drop down menu.
  • Dyslexia:
    
  • Celestia medium redux:¹⁾
    
  • Droid:
    
  • Mobi:
    
  • Ubuntu:
    
  • Liberation:
    
  • Deja Vu:
    
  • Roboto:
    
  • Noto:
    
• Font Size Adjustment: Lets you change the size of the font. NOTE that this may cause issues.
• Chat Line spacing: spacing between lines of text.
• Folder Item Height: Height of items in inventory.

The pages below have been updated to reflect changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.4 goes to public release.

• Avatar Menu: Favorite Wearables. A window to hold frequently used items such as HUDs and items for quick attach/detach using double click to add. Creates a protected subfolder of links #Wearable Favorites inside #Firestorm folder. See also Toolbar Buttons.

• Avatar Menu: Toolbar Buttons. Added Beacons and Favorite Wearables

• Avatar Menu: Show User Interface. Unchecking hides the user interface. Use Alt+Shift+U to show user interface again. Chiclets and script dialogs will remain visible. Navigation and Favorite bars will be hidden in next update.

• Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Shows the rendering weight of each worn attachment. Avatar Complexity

• Firestorm - Build 1: Script Editor Font. Allows you to select the name and size of the font used in the LSL script editor.
• User Interface - 2D Overlay: Prevent statistics window from gaining focus. If enabled, the statistics window will never receive focus when another window is closed. Actions such as changing graph layout for items are still possible when enabled.

Merged up to Linden Lab Version 5.1.3.513644
Release Notes for v5.1.3 (513644) - Second Life Viewer March 27, 2018
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.3.513644

• This release of the Viewer pulls in a raft of updates to the built in media support that were not quite ready to be integrated when the 64 bit Viewer (Alex Ivy) was released.
  It is comprised of various fixes, updates, security patches and improvements for CEF (Chromium Embedded Framework) that is the basis for the built in web browser and VLC that provides support for video media playback.
  In addition fixes are included to Dullahan (the third party library that uses CEF) as well as all the media plugin code itself.
  As per the Alex Ivy 64 bit viewer, there is no Linux version.
• Cookies
  The option to not accept cookies has been removed due to complexities of not doing so in the in-viewer browser. For a more controlled cookie experience, an external full-featured browser may be better.

AlexIvy 64bit - Fully merged up to LL's AlexIvy viewer https://community.secondlife.com/blogs/entry/2290-64-bit-viewers-for-all/ for Windows and Mac. As a result of this update, there is no Linux viewer available. The Linux community is working to resolve this and accordingly, there is no way to anticipate when a Linux viewer will be available for testing.

Chromium Embedded Framework (CEF) Dullahan updated:

• Dullahan: 1.1.1080
• CEF: 3.3325.1750.gaabe4c4.513446
• Chrome: 65.0.3325.146

FMOD Studio 1.10.04

KDU updated to v7.10.4.

Voice Update: Vivox Version 4.9.0002.27586

FIRE-6155 - Previewing an animation to upload while walking/sitting/flying results in the avatar getting stuck in that animation

FIRE-9070 - build window xyz colors not changing for rotate and size

FIRE-12249 - Develop - Render Metadata - Avatar Hitboxes makes eyes disappear

FIRE-13474 - Saving .dae with brackets in filename fails

FIRE-17518 - [CEF] Opening Preferences from the login screen breaks the login page layout.

FIRE-19704 - [Mac] Crash when upload Mesh 50499 - Calculate Weights and Fees (Mac El Capitan) - LLModelgetJointInfluences(LLVector3 const&)

FIRE-21974 - recovered script after crash is empty

FIRE-22175 - [Mac] [BUG-202965] [MAINT-8208] Firestorm crashes when I use a cube as physic when uploading a mesh model

FIRE-22179 - Preprocessor warning when last line in lsl include is a comment: generic lexer warning: Unterminated C++ style comment

FIRE-22214 - Script Editor - Missing Line numbers, Vintage Skin

FIRE-22241 - Copy paste inserting timestamps unexpectedly

FIRE-22268 - Firestorm crashing when deleting items

FIRE-22281 - [BUG-214575] [MAINT-8289] Deleting inventory directory while keeping [Delete] key preesed

FIRE-22288 - [Mac] [BUG-214585] [MAINT-8287] Creating an admin group role is back. While creating a role, in a new group, once you tick the manage ban list you crash.

FIRE-22297 - [Mac and Linux only?] FPS limiter not working (do not move to Support)

FIRE-22330 - Crash when taking photos

FIRE-22346 - [Opensim] Remove Avination from Grid Manager

FIRE-4963 - using animation upload window disables physics wearables

FIRE-5686 - undocked IM window does not stays at his place after relog and undock again

FIRE-16651 - Animation upload/preview breaks eye movement

FIRE-20866 - @stopim returns The other party is not under a @startim restriction when they are

FIRE-21719 - Copy-Paste a Folder doesnt copy the links to the new folder

FIRE-22148 - Group profile icons unload when Group Titles is opened

FIRE-22164 - Black Text against very dark background Firestorm Skin Dark Scheme Experience Edit WIndow.

FIRE-22167 - Show in Main View fail in 2nd Inventory Window

FIRE-22187 - Typo in Prefs - Chat - Visuals

FIRE-8784 - Align tool not working on some prims

FIRE-9561 - Items worn from Marketplace Tab do not show up as worn items

FIRE-21425 - [CEF] Problem with drop-down menus in internal web browser.

FIRE-21579 - [BUG-202634] [MAINT-8023] Missing support for internationalized domain names.

FIRE-22383 - Links in 1st life profile tab disappear after second save

FIRE-22438 - tp2 <own name> crashes the viewer

FIRE-15266 - Toolbar Button for Beacons

FIRE-20959 - Update in-world browser cipher suites

FIRE-22331 - [Opensim] Mesh uploaded with Analyze likely to render invisible

FIRE-22334 - Reset All Settings button misleading

FIRE-4595 - Paste as Link - in system generated folders like outfits

FIRE-16207 - [Starlight CUI] Contact Sets Panel text

FIRE-22116 - Pennys Windlight Presets

FIRE-5974 - Allow SEARCH to include Received Items Folder

FIRE-22354 - Beyond chat range diminish factor slider is confusing

FIRE-19520 - Add per-item render-weight display to Appearance window

FIRE-20809 - HUD Management, Favorite Wearables Folder (protected) and Toolbar Button

FIRE-20818 - Option to adjust font size in script editor

FIRE-21078 - Show Rendering Cost per attachment

FIRE-22115 - Jeans Windlight Presets

For instructions for Phoenix, please refer here.

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

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

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

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

• Open the 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 and User/Roaming

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.

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

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

Please see How to add antivirus exclusions (exceptions) in Bitdefender 2018
Also the User Manual, pages 99-100, for how to add exceptions to the Advanced Threat Defence Whitelist.

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

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

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

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

In order to create an exclusion rule:

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

Rules can apply to the following protection components:

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

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

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

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

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

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

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
• Click the Windows Defender Settings option.
• Exclude the cache
  • Click Add an Exclusion
  • Click Exclude a folder
  • Click in the address bar and type %LOCALAPPDATA% and press Enter
  • Click the Firestorm folder
  • Click the Exclude this folder button
  • Repeat this if you have more than one Firestorm folder (64-bit and 32-bit, for example)
• Exclude the viewer executables
  • Click the Exclude a .exe, .com or .scr process button
  • Navigate to C:\Program Files\Firestorm-Release64
  • Click Firestorm-bin
  • Click the Exclude This file button
  • Repeat this for SLPlugin and SLVoice - and llceflib_host (for FS 4.7.9 and later).
  • Repeat this for 32-bit Firestorm ( C:\Program Files (x86) )

Add exclusion to Auto-Protect and Risk scan

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

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

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

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

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

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

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

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

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

For additional information:

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

If you're looking for how to get your own event in the Firestorm Message of the Day, click here.
If you're looking for a missed MotD or more information on the current MotD rotation, keep reading!

Oh hi! I didn't see you come in! You're probably here because you missed the message of the day. It went by to fast, it was to long, or you clicked a link in a goofy motd set up to get you here!

Anyway, if you missed the message of the day and would like to see it again;
At the top of your screen find the “Content” menu and click it.
In the menu that drops down, way down at the bottom select, “Message of the Day”.

There it is, in your local chat as a system message.

[11:28:02] [Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd]

You can also scroll down this page and see ALL the current messages of the day in the “events, tips, help and gateway” message of the day rotation. (I keep this page bookmarked as a fast reference to important wiki pages.)

The Firestorm Message of the Day is currently running on a rotation of thirty eight preset tips, help, gateway and fun messages and/or a varying amount of event messages of the day. All of which are displayed at random when you log in depending on which “MotD Cartridge” is loaded. Go ahead, try it, relog, and unless the message of the day is promoting a special event¹⁾ you'll see something different.

The preset messages of the day are split between tips to make your Firestorm Viewer experience more efficient and enjoyable, help topics to help resolve common Firestorm Viewer issues, gateway to spread information about the Firestorm Gateway and fun just because.

I'll list the message of the day presets below so you can see what's in the rotation.

These are the current messages of the day for events which are currently running and have been approved for a Firestorm message of the day;

MOTD: EVENT: 2018 SciFi Expo Registration
The SciFi Expo in support of The American Cancer Society's RFL of SL is now accepting applications for their event running May 12 to 20! Click to sign up! https://slscifiexpo.wordpress.com

MOTD: EVENT: 2018 Rock Your Rack Registration
Rock Your Rack 2018 supporting the National Breast Cancer Foundation is now taking designer registrations for their October event! Click for more! https://rockyourrack.wordpress.com/about/designers/

MOTD: EVENT: SL15B Event Applications
Second Life Turns 15! SL15B is now accepting applications for Exhibitors, DJs, Live performers, Auditorium and Volunteers! Click for more! http://www.slcommunitycelebration.info/apply-now/

These are displayed randomly and are broken down into three groups;

Tips: Which provide tips on how to get the most out of the Firestorm Viewer and are meant to improve your Second Life experience in some way.

Help: Which provide assistance on self resolving common Firestorm problems which are seen the most in the Firestorm Viewer help groups. These may have also been requested by the Firestorm Support Team at some point.

Gateway: Coming soon! These provide information on what's going on at the Firestorm Gateway, events, event spaces, classes and more.

I'll break them into the same groups below;

MOTD: TIP: Firestorm Classes 1Temporarily removed from the rotation.
Did you know Firestorm has classes on how to use the Firestorm viewer? We even have an open question and answer session after each class! http://wiki.phoenixviewer.com/firestorm_classes

MOTD: TIP: Firestorm Classes 2Temporarily removed from the rotation.
Did you know Firestorm offers classes on how to get the most out of the Firestorm viewer? Click to find out more about these classes and when they are! http://wiki.phoenixviewer.com/firestorm_classes

MOTD: TIP: Avatar Complexity
Firestorm tip! Why is my friend a colored shape? What is this complexity popup thingy? Click here to find out more about this lag reducing feature! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings

MOTD: TIP: Complexity and the Slideshow
Firestorm tip! Are you at a busy club or event and Firestorm is running like a slide show? Try lowering your avatar complexity setting! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings

MOTD: TIP: FS Bridge, Trolls Not Included
Firestorm Tip! The Firestorm BRIDGE is enhancing your SL experience and you may not even know it! Click here to find out how! http://wiki.phoenixviewer.com/fs_bridge

MOTD: TIP: Can Not Log in to SL
Firestorm Tip! Can't log into Second Life? STOP! DO NOT reinstall firestorm! Save yourself a lot of trouble and check here first for possible grid issues https://status.secondlifegrid.net/

MOTD: TIP: Contact Sets
Firestorm Tip! Contact Sets allow you to organize friends and non friends into manageable groups and categories! Learn more about them at http://wiki.phoenixviewer.com/fs_contact_sets

MOTD: TIP: IM Tab Sorting
Firestorm tip! Did you know you can click and drag your IM tabs in the conversations window to sort them to your liking. For more chat tricks see http://wiki.phoenixviewer.com/fs_chat

MOTD: TIP: Customizable Quickprefs
Firestorm tip! Did you know you can add your most commonly used settings to the Quick Prefs? http://wiki.phoenixviewer.com/fs_quick_preferences

MOTD: TIP: Missed the MotD
Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd

MOTD: TIP: Outfits
Firestorm tip! Did you know the Outfits feature can help you quickly change what you&apos;re wearing without digging around in your inventory? http://wiki.phoenixviewer.com/my_outfits_tab

MOTD: TIP: Camera Controls
Firestorm tip! Something catching your eye? Hold down your ALT key and click it, then roll your mouse wheel! Interested in more? See http://wiki.phoenixviewer.com/fs_movement_and_camera#view

MOTD: TIP: Toolbars
Firestorm tip! Did you know you can add many of your commonly used Firestorm windows and floaters to the toolbars? http://wiki.phoenixviewer.com/toybox

MOTD: TIP: SL World Search
Firestorm tip! Looking for something in world but, can't find it? Try a search! http://wiki.phoenixviewer.com/floater_search

MOTD: TIP: Replace Links
Firestorm tip! Gah my inventory links are borkened! Have no fear, Replace Links are here! Fix those broken links, http://wiki.phoenixviewer.com/fs_linkreplace

MOTD: TIP: Skins
Firestorm tip! Wanna change the way firestorm looks? Then change it! http://wiki.phoenixviewer.com/preferences_skins_tab

MOTD: TIP: Settings Backup
Firestorm tip! Better safe than… NOOOOOOO! You should regularly back up your Firestorm settings. You never know when…. http://wiki.phoenixviewer.com/backup_settings

MOTD: TIP: Auto Replace
Firestrom tip! Firestone? Firestorm! If only Firestorm had an auto replace… Oh wait! It does! http://wiki.phoenixviewer.com/fs_auto_correct

MOTD: TIP: Preference Search
Firestorm tip! Is a Firestorm setting playing hide and seek and causing you to pull out your hair? Find it fast with preference search! http://wiki.phoenixviewer.com/fs_preferences

MOTD: TIP: Chat Shortcuts
Firestorm tip! Did you know when chatting you can hold down your ctrl key when you press enter to shout and the shift key to whisper? http://wiki.phoenixviewer.com/keyboard_shortcuts

MOTD: TIP: Keyword Alerts
Firestorm tip! Did you miss a message in chat? Did someone say your name while you were doing something else? Check out Keyword Alerts! http://wiki.phoenixviewer.com/preferences_chat_tab#keyword_alerts_tab

MOTD: TIP: FS Wiki
Firestorm Tip! Did you know Firestorm has its own wiki? Find out how features work, how to fix common viewer issues and more! Check it out, bookmark it, study it! http://wiki.phoenixviewer.com/

MOTD: TIP: Inventory Count
Firestorm Tip! Do you have more inventory than you thought you had? Inventory count now includes folders! Click for more http://wiki.phoenixviewer.com/my_inventory_tab

MOTD: TIP: Elements
Firestorm Tip! Elements? What is this, chemistry class? No silly, Elements is the count of Items/Folders in that folder! Click for more http://wiki.phoenixviewer.com/my_inventory_tab

MOTD: HELP: Bakefail Badness
Firestorm Help! Are you feeling overly misty as an orange cloud? Are you missing your avatar? Are you thinking, clouds belong in the sky, not on me! Click here to fix the cloud http://wiki.phoenixviewer.com/fs_bake_fail

MOTD: HELP: Camera Messed Up
Firestorm Help! HALP! I know my head looks awesome but I'm stuck staring down at the top of it! Why am I staring at my butt? What is wrong with my camera?! click click clickie! http://wiki.phoenixviewer.com/fs_camera

MOTD: HELP: Teleporting Woes
Firestorm Help! What is up with these teleport fails? Disconnected?! OMG again! Click here to help prevent TP issues! http://wiki.phoenixviewer.com/fs_tp_fail

MOTD: HELP: Slow Rezzing
Firestorm Help! Did you know many common rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/slow_rez

MOTD: HELP: Slow Rezzing Mesh
Firestorm Help! Did you know many common mesh rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/mesh_issues

MOTD: HELP: Getting Help NAO
Firestorm Help! HALP! My Firestorm is broken and I need help NAO! Have no fear, click here! http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Getting Help Dont Panic
Firestorm Help! Sudden viewer problems? Not sure what to do? Don't panic! check out our wiki: http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Voice Issues
Firestorm Help! Have you lost your voice? Firestorm voice not working for you? Why not drink a tall glass of http://wiki.phoenixviewer.com/fs_voice

MOTD: HELP: Rick and Morty Lost Login Info
Oh geez, Rick, Firestorm lost my login info again! Well, Morty, try starting here to fix it, http://wiki.phoenixviewer.com/fs_stored_passwords#failed_to_decode_login_credentials

MOTD: HELP: Help Help Help You
Firestorm Help! Need help? Help us help you! Learn how to use the Firestorm support group to get the best help! http://www.firestormviewer.org/firestorm-help-groups-tips-rules-and-guidelines/

MOTD: HELP: Second Life Account Questions
Firestorm Help! Need help with your Second Life account matters? Go to Avatar Menu - Account, or login to your Dashboard at https://secondlife.com/my/account/

MOTD: HELP: Dont Clear Your Cache
Firestorm Help! Having viewer problems? Please don't clear your cache or reinstall the viewer as the first thing you try. Instead, see this page for how to get help http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Missing Inventory
Firestorm Help! Ummmm, I know I had more things in my inventory than this! Help! I'm missing inventory! what can I do? http://wiki.phoenixviewer.com/fs_missing_inventory

MOTD: GATEWAY:
Keep an eye here for upcoming information regarding the Firestorm Gateway!

MOTD: FUN: Rhubarb Pie
Firestorm fun! Feeling hungry? try a Rhubarb Pie, Firestorm style! http://wiki.phoenixviewer.com/rhubarb_pie

This section is changing as we speak!

* if a main MOTD is set, that one is always shown
* if random MOTDs are set and no main MOTD is set, they will be randomly shown at login and during TP
* if an event MOTD is set, that is always shown at login and then, during TP either the main MOTD or one of the random MOTDs

Firestorm 5.0.11 (53634) Release Notes

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

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

• Windows 7 SP1, 8.1 and 10 32bit and 64bit are supported.
  Earlier versions of windows are not supported.

• Firestorm 5.0.11 will NOT even install on Windows XP.
• Firestorm 5.0.11 may install on Windows Vista but is likely to be very unstable.

• Windows 10 - Firestorm 5.0.11 is 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 5.0.11 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 5.0.11.

• Mac 10.9 or later OS X versions are supported.

• Mac PPC is not supported.
• Firestorm 5.0.11 viewer will NOT run on Mac 10.6, 10.7 or 10.8.

• Any distribution currently supported by its creator can run Firestorm. Some additional libraries and/or packages may be needed, they are listed on this page. And certain older unsupported hardware may not be able to support Firestorm.

Older versions of Firestorm are available here.

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

Firestorm 5.0.11, 5.0.7, 5.0.1 Release

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

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

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

Firestorm 5.0.11, 5.0.7, 5.0.1

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

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

for Linux only

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

Linux has this already

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

Windows only

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

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

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

• Latest driverLast checked 22/01/2018 - Windows: 390.65 (2018.1.8) - Linux: 384.111 (2018.1.4)

• Latest driverLast checked 22/01/2018 - Windows: Adrenalin Edition 17.12.1 (12/12/2017) - Linux: Linux Download Center
  

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

http://hg.phoenixviewer.com/

This procedure is used for building a 64-bit version of Firestorm 5.1 on 64-bit Ubuntu 16.04 LTS systems. It was tested and verified on Ubuntu 16.04.4. This procedure assumes that your system has been properly updated.

This procedure may not work on older versions of Linux, nor has it been tested on any other current or LTS version of Linux/Ubuntu or any other distribution/variant/derivative.

The build process requires at least 6GB RAM (8GB recommended) with swap, a modern quad-core CPU and at least 24GB available disk space.

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

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

sudo apt upgrade # to make sure all installed packages are current
sudo apt install --install-recommends bison bzip2 cmake curl doxygen flex g++-4.9 gdb m4 \
mercurial moreutils pkg-config python python-dev python-pip

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

The build environment needs to know to use gcc 4.9:

sudo update-alternatives --remove-all gcc
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 49 \
--slave /usr/bin/g++ g++ /usr/bin/g++-4.9 \
--slave /usr/bin/gcov gcov /usr/bin/gcov-4.9
sudo update-alternatives --config gcc

Note that this will “hide” the current gcc from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.

Firestorm 5.1, like the AlexIvy release of the Linden Lab viewer, is built with the USESYSTEMLIBS flag set, so that the libraries are installed on the user's system as needed and not shipped with - or maintained by - the viewer. This means that a large number of development libraries must be installed on the build system.

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

sudo apt install --install-recommends libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev \
libcairo2-dev libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev \
libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev libogg-dev \
libopenal-dev libpangox-1.0-dev libpng-dev libsdl1.2-dev libssl-dev libstdc++6 liburiparser-dev \
libvorbis-dev libx11-dev libxinerama-dev libxml2-dev libxmlrpc-epi-dev libxrender-dev zlib1g-dev

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

sudo pip install --upgrade pip
sudo pip install autobuild

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

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

cd ~/src

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

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

It will create a folder called phoenix-firestorm-lgpl. You can optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

pull_in_chunks.sh

#!/bin/bash
 
cd ~/src
hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..55000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.

cd ~src
hg clone https://bitbucket.org/Ansariel/fs-build-variables

Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.

cd ~/src/phoenix-firestorm-lgpl
source ../fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=~/src/fs-build-variables/variables

Unlike previous versions of autobuild, version 1.1 requires the address size switch after the command, not before it. If you want a 32-bit build, you must specify that; there is no default any longer.

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

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

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

• LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
  more of them.
• clean will cause autobuild to remove any previously compiled objects and fetched packages. It can be useful if you need to force a reload of all packages
• package will result in a bzip2 archive of the completed viewer. Enabled by default, you would have to use -DPACKAGE:BOOL=Off to disable it
• chan will append a string to “Firestorm-”, customizing the viewer name

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

Examples:

autobuild configure -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -c ReleaseFS_open -- --clean
autobuild configure -A 64 -c ReleaseFS_open -- --chan="My-Build" # sets the viewer name to "Firestorm-My-Build"

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

autobuild build -A 64 -c ReleaseFS_open

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

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

Create the desktop launcher

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

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

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

You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged to another location if you choose, and then launch firestorm from there. Example:

mkdir ~/Firestorm
cp -a ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

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

Firestorm Self Compilers is an unofficial group where self-compilers can ask questions and share ideas about Firestorm sources and builds.

TPV Self Compilers is similar, except that chat is not limited to Firestorm

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

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

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

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

At present, voice does not work. There are two workarounds:

Download this tarball and extract the contents to your Nightly or Tip's /bin folder. It is in a win32 folder because that's what the viewer is looking for.

Launch the viewer but don't log in. Open the Debug menu (if you don't see it, Preferences > Advanced, enable Show Advanced Menu), and select Show Debug Settings. In there, search for FSLinuxEnableWin32VoiceProxy and set that to TRUE. Close Debug Settings.

Note that you can change FSLinuxEnableWin32VoiceProxy while logged in, but make sure voice is disabled first.

In Release, in its /lib folder, locate “libvivoxoal.so.1” and copy that to your Nightly or Tip's /lib folder.

Make sure you set the FSLinuxEnableWin32VoiceProxy debug setting to FALSE for this workaround.

Autobuild.xml refers to a newer – and broken – version of openjpeg for 64-bit Linux. The workaround is to modify autobuild.xml as follows:

Locate autobuild in the Firestorm source folder and open it with a text editor. Search for openjpeg-1.5.1.180841553-linux64-180841553.tar.bz2 and replace it with http://downloads.phoenixviewer.com/openjpeg-1.4.201505150222-r26-linux-x64-201505150222-r26.tar.bz2 Just above that line is the hash 6098e555296583336b02f1a78b41b93a, replace that with f8a5ed12a0b45e0c48e04642ee736426 Save the file, then configure with the –clean option.

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

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

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

→ Help Wanted (RP)←

One of the goals of the Firestorm Gateway is to introduce New-To-SL Residents to the various things that they can do in SL, in hopes that they will find something they enjoy doing. The expectation is that they will be more inclined to keep using SL when they discover something they truly enjoy.

RolePlay is very popular in Second Life, so the Firestorm Gateway has dedicated a large space for SciFi Roleplay. The RolePlay space gives a new user the opportunity to visit RolePlay sets, and to observe and/or participate in Roleplay. This lets them figure out if RolePlay is something they might enjoy doing.

It is also a place where existing RolePlayers who don't have a RolePlay home can come and enjoy themselves. It is also a place where Existing RolePlay groups can come to demonstrate what their group is about and to recruit new members for their group.

The “magic” of the Firestorm Gateway RolePlay area is that it brings experienced RolePlayers and new-to-Roleplay users together in a fun/safe environment. It is a win-win situation. Existing RolePlay groups benefit, because they can meet new-to-Roleplay individuals and tell them about their groups. New-To-SL Residents win because they get to see/experience high quality RolePlay and decide if it is something they might enjoy doing. Individual RolePlayers win because they have a safe and drama-free place where they can come to RolePlay.

• Drop-In Roleplay - 24×7 Drop-In Generic Sci-Fi Rolepay. This takes place at Callahan's Spiral Galaxy on the top deck of the Tempus Space Station.
• Firestorm Gateway Starfleet - Independent Ships/Stations can partner with Firestorm Gateway
• Star Trek Roleplay - This takes place on the USS Gateway (a Sovereign Class Starship) at scheduled RolePlay times.
• Free-Form Roleplay - Individuals and Groups are permitted to user our RP facilities when they are not in use by scheduled RolePlay events. We have a generic SciFi Spaceship, the A.F.S.S Epsilon. We have a large space station where all decks except for the Upper Deck are available for space station RolePlay. We have a large Sovereign-Class StarTrek Starship called the USS Gateway.

(Please click the link for more information on each RolePlay Opportunity.)

An Alliance For Independent Ships/Stations That Want To Partner With Firestorm Gateway

Firestorm Gateway Starfleet (FGS) is an alliance of independent ships, stations, and RolePlayers who wish to retain their autonomy but be part of a larger group that provides resources and identity. FGS respects each ship’s right to determine their story-line, their Trek timeline/time-frame, their decisions on ranks and promotion criteria, etc. It also provides access to new-to-SL individuals who are interested in Trek RP.

FGS provides some resources for member-ships/stations. These include:

• free duty uniforms (with omega appliers for those avatars who have mesh bodies)
• a weapons system that works even in no-rez areas
• a sophisticated combadge system
• the ability to send notices to a group of over 1000 people interested in scifi RP
• a system to teleport interested new-to-SL residents from Firestorm gateway to your ship during your RP times.

It also provides the occasional shared ceremonies presided over by the Jessica Lyon, President of the United Federation of Planets (and team leader for Firestorm). And possibly most important, it gives you an opportunity to meet people who might become interested in joinng your crew

1. You must be “newbie friendly” at all times, as the purpose of this project is to introduce new-to-SL individuals to Trek RP and get them linked in with existing groups… so that they make connections and want to keep coming back to SL.
2. You MUST provide a 1 hour a week (or more if you want it to be longer) RP a week at a scheduled time on the Firestorm Gateway grounds. Newbies may drop in on the RP at any time during that hour, so you need to provide enough crew to sustain a small RP – but at the same time be flexible to allow the new people to join in if they so desire.
3. You must dress/talk/behave in a G manner while on the Firestorm Gateway.
4. Absolutely No Drama. Also no badmouthing other trek groups or individuals.

Interested? Please contact Teresa Firelight.

Disons que par exemple vous avez dans vos différentes tenues quelques liens vers une chevelure. Puis à un moment donné vous décidez de la modifier. Vous la posez pour l'éditer, puis vous la reprenez dans votre inventaire. La chevelure aura alors une nouvelle UUID et tous les liens à cette chevelure dans votre inventaire se trouveront brisés. Ou bien encore, vous décidez de changer de shape, et vous voulez remplacer votre ancienne shape par la nouvelle dans toutes vos tenues.

Voici comment le faire en quelques clics :

• Trouver un des liens dans votre inventaire
• Faites un clic droit dessus et délectionnez “Replace links”
• Une petite fenêtre s'ouvre comme celle sur l'illustration ci-contre, affichant le nom du lien, et combien de liens comme clui-ci se trouvent dans votre inventaire.
• Localisez dans votre inventaire la chevelure modifiée ou la nouvelle shape,bref, le nouvel article
• Faites glisser cet article sur le champ “New” de la fenêtre
• Cliquer sur Start

NB Cette fonction est aussi très pratique si vous trouvez dans votre inventaire des liens brisés (broken link) que vous devez réparer.

See here for a description of what a cache is.

Clearing your cache this way will “cure” certain kinds of texture or inventory issues and is the suggested procedure before resorting to more drastic steps like Reinstalling the viewer.

• Open Preferences→ Network & Files -> Directories.
• Go to the first path “Cache Location” and click the “Open” button behind the path. This will open a file explorer window displaying your current cache location.
• Logout (close the viewer) and then delete everything inside the folder currently displayed in your file explorer.
• Should you not be able to start the viewer to bring up Preferences, then locate the folder manually. 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:

Delete everyting inside that folder.

Now continue as follows:

• Log back into SL, to a quiet region (try the Firestorm Support parcel or a Linden water region such as aich or hatton). On your inventory window, click “Recent Items”.
• Wait for your inventory to repopulate fully. The process may be sped up, if necessary, by typing random letters into the search bar.
• While inventory repopulates, do not teleport anywhere, and do not attempt to access anything in your inventory. Talk to people or surf the web.
• Watch as it repopulates. as long as you can see (Fetched…) at the top of the inventory window, it is still loading.
• Once inventory has repopulated, log out of SL once more, then log back in.

The “clear your cache” advice is something we resort to ONLY if the problem appears to be texture related. A full cache is almost always better than an empty one. You can clear parts of the cache, depending on the issue you're trying to resolve:

At this point, you should be back to normal… whatever “normal” happens to be that day in SL.

The Firestorm Gateway wishes to promote Trek and other SciFi Roleplay to those who are new to SL. Our goal is to get those new-to-SL residents who are interested in Scifi and/or Trek RP connected with people/organizations that RP regularly. This helps them make a personal connection and makes them more likely to want to stay active in SL. We invite existing Trek and Scifi RP organizations to partner with us. Partners would sponsor a weekly Roleplay in the Firestorm RP area, lasting a minimum of 1 hour. Your organization would have a scheduled weekly RP time, and would plan and lead the mission. You must provide a large enough crew that they could sustain it on their own in the event that no new residents come to any given RP session. Firestorm does have a mechanism to invite new people up to the Starship during the RP. Typically new people use it on any given RP session. Some will want to just watch and others will want to join in. Most of the time, we have been seeing 1 to 3 new people who want to join in the RP and another 5-10 who want to watch/observe part or all of the RP. But that can vary from week to week.

Firestorm RP partners are given the ability to send notices about their RP session to two separate groups.. one for those interested in RP (roughly 1000 members) and another for those new to SL (over 34,000 members atm). They are also allowed to send notices about special RP events in their organization to the RP list.

Your crew members will have the ability to interact with and make friends with the new-to-SL and new-to-RP people who attend your RP. Once they have established a basic relationship, they are free to invite these people to visit/tour your Ship/Station. If they show an interest, it is fine to invite them to join your organization as well.

Firestorm's goal in doing this is to help the new-to-SL residents who like SciFi RP to hook up with those established groups and/or independent ships already doing RP. If a new resident becomes involved in your organization, this is a win-win situation. You win because your organization grows. We win because the new resident is connected in SL and more likely to keep logging in and being active in SL.

If you would like more information or would like to partner your group with Firestorm Gateway, please contact Teresa Firelight.

The Firestorm Gateway has a large RP environment, consisting of a Generic Space Station (ISS Tempus), a generic space ship (FSS Epsilon) and a Trek Starship (USS Gateway). We do some scheduled RPs on them from time to time during the week, but most of the time they are open and available for people to use/enjoy. If you and some of your friends want to do your own RPs in the firestorm RP area, you are most welcomed to. We only have a few simple rules we ask you to follow:

1. Be friendly and inviting to others, especially to those who are new to SL.

2. Keep your RP (your dress, your conversation and your behavior) G rated while in the Firestorm RP area.

3. No drama, grieffing, badmouthing of other groups or individuals

Feel free to use the Firestorm Gateway Roleplay group chat to invite others to those RPs you do in the Firestorm Roleplay areas. Please do NOT use it to announce anything that is NOT taking place off of the Firestorm RP area.

La fenêtre des Préférences rapides fournissent un accès rapide aux paramètres les plus souvent utilisés par le biais d'un bouton sur la barre en bas de votre écran.

Ouvrez les Préférences rapides en cliquant sur le bouton portant le logo Firestorm (voir image ci-contre). Pour les fermer, cliquez le bouton de nouveau.

NB : Il existe un tutoriel en vidéo (en anglais) sur les Préférences rapides ici.

NB : Toutes les skins du viewer n'ont pas les mêmes options; l'ordre peut également différer.

• Draw Distance : Change votre distance d'affichage.
  Egalement dans Preferences > General > Draw distance.
• Max Particles : Nombre de particules à afficher.
  Egalement dans Preferences > General > Max particle count.
• Avatar Physics LOD: Régler sur 1 pour activer les effets physiques de l'avatar; sur 0 pour les désactiver complètement.
  Egalement dans Preferences > General > Avatar Physics.
• LOD Factor: Contrôle le niveau de détail des prims. Le paramétrage idéal se situe entre 2.0 et 3.2
  Egalement dans Preferences > General > Objects & Sculpts LOD.
• Max Avatars: Nombre d'avatars affichés pleinement sur l'écran. Réduire ce paramètre vous fait gagner beaucoup de FPS dans les endroits surpeuplés. Le réglage par défaut est de 3 pour les cartes graphiques de basse gamme et de 12 pour Mid/High/Ultra.
  Egalement dans Preferences > General > Max # of non-impostor avatars.
• Tags Offset: Vous permet d'ajuster la hauteur de votre tag au-dessus de l'avatar. Pratique pour les avatars non humains, du plus petit au plus grand, pour que le nom ne se trouve pas caché dans l'avatar, ou flottant trop loin.
  Egalement dans Preferences > Colors > Name Tags > Name tag Z-offset.
• Name Tags: pour afficher/cacher rapidement les tags au-dessus des têtes des avatars.
  Egalement dans Preferences > General > Name Tags : On/Off.
• LookAt Target: Affiche/cache les mires de LookAt (là où les avatars ont fixé leurs caméras).
  Egalement dans Preferences > Privacy > LookAt > Show LookAt targets.
• Color Under Cursor: Si activé, ce paramètre permet d'afficher les valeurs RGB et alpha sous le curseur de la souris; elles s'afficheront en blanc dans le coin en bas à droite de vore écran.
• Hover Height: Permet d'ajuster à la volée laposition de vorre avatar sur l'axe Z sans devoir aller modifier son apparence.
• Max Bandwidth: Pour régler la bande passante en Kbps (voir ici pour ajuster ce réglage au mieux).
  Egalement dans Preferencs > Network & Files > Connection > Maximum bandwidth.
• Max Complexity: Contrôle à partir de quelle complexité un avatar sera affiché en “silhouette”.
  Voir http://wiki.phoenixviewer.com/fs_avatar_complexity_settings_fr pour les infos sur la complexité de l'avatar.
• Use Region Windlight: Force le viewer à utiliser les réglages windlight de la région sur laquelle vous vous trouvez.
  Egalement dans menu World > Environment Editor > Use Region Settings.
• Windlight Sky: Réglages windlight du ciel. Utilisez les flèches < et > pour les visualiser rapidement.
• Windlight Water: Réglages windlight de l'eau. Utilisez les flèches < et > pour les visualiser rapidement.
• Day Cycle: Permet une sélection rapide de cycle jour-nuit.
• Heure du cycle jour-nuit: Faire glisser le slider pour changer l'heure. Le X à droite sert à se remettre à l'heure de la région.

On peut ajouter ou retirer des paramètres dans la fenêtre des Préférences Rapides en cliquant l'icône “outil” dans le coin en bas à droite. La fenêtre changera d'apparence comme dans l'image ci-contre.

• Pour ajouter un nouveau paramètre, cliquer le bouton +. Un nouveau contrôle vide est ajouté dans la fenêtre. Il faut maintenant l'associer à un paramètre de débogage (Debug Setting).
• Cliquer sur Choose et une lonue liste déroulante va apparaître; ce sont tous les paramètresde débogage du viewer; la liste de tous les paramètres de débogage de Firestorm se trouve ici pour référence.
• Sélectionner le paramètre que vous souhaitez ajouter.
• Dans l'espace à gauche de la liste déroulante, donnez le nom du paramètre que vous voulez.
• Le champ Type est automatiquement rempli par rapport au type de paramètre.
• Si le paramètre n'accepte que des nombres entiers, cliquer le case à cocher Integer.
• Pour certains paramètres, vous pouvez changer les valeurs minimum / maximum.Ne le faites pas sauf si vous êtes tout à fait sûr(e) de ce qu'elles représentent.

Pour ajouter plus de paramètres, cliquer le bouton + de nouveau, et recommencer.

Cliquer sur le nom du paramètre dans la partie haute de la fenêtre pour le mettre en surbrillance. Vous pouvez changer le nom du paramètre si vous le souhaitez. Vous pouvez également remplacer le paramètre par un autre complètement différent, ce qui peut être plus rapide que de supprimer le paramètre et en ajouter un autre.

A gauche de chaque paramètre de cette fenêtre se trouve une icône corbeille; cliquer la corbeille supprimera le paramètre des Préférences Rapides.

Lorsque vous avez effectué vos changements, cliquez le bouton “x” en bas de la fenêtre. Il est alors de se déco/reco pour enregistrer ses changements.

Si pour une quelconque raison vous voulez revenir aux Préférences Rapides par défaut, cliquez le bouton REset en bas. Attention : vous ne pourrez plus revenir à vos modifications.

The Quick Preferences Panel provides fast access to commonly used settings and is accessed via a button on the bottom bar.

Activate it by clicking the button with the Firestorm logo shown on the image on the right. To close it, press the button again, and it will appear released.

NOTE: There is a video tutorial about Quick Preferences here.

NOTE: Not all skins have all the options shown; the order may also be different.

• Draw Distance: Change your draw distance.
  (Also set in Preferences→ Graphics -> General.)

• Max Particles: Amount of particles to render.
  (Also set in Preferences→ Graphics -> General.)

• Avatar Physics LOD: Set to 1 to enable full support of avatar physics; 0 to disable entirely.
  (Also set in Preferences→ Graphics -> General.)

• LOD Factor: Controls level of detail of primitives (multiplier for current screen area when calculated level of detail). Ideal setting is between 2.0 and 3.0.
  (Also set in Preferences→ Graphics -> General.)

• Max Avatars: How many Avatars to fully render on screen. Lowering this greatly improves FPS in crowded situations. Requires Avatar Imposters to be on. The default is 3 for low graphics and 12 for Mid/High/Ultra.
  (Also set in Preferences→ Graphics -> General.)

• Tags Offset: Allows you to adjust the height of your name tag above your avatar. Handy for non human avatars, from tinies to large dragons, so the name isn't embedded in the avatar, or floating way above.

• Name Tags: quick toggle to enable/disable displaying tags over people's heads.

• LookAt Target: Enables showing crosshair to indicate where people have their camera focused.
  (Also set in Preferences→ Privacy -> LookAt.

• Color Under Cursor: If enabled, shows the current color and alpha values under the cursor; these are displayed in white text, on the lower right of your screen.

• Hover Height: It allows “on-the-fly” adjustments to be made to your avatar’s z-axis position without having to use the Edit Appearance Hover slider

• Max Bandwidth: Set your network bandwidth in Kbps (see here for best setting).
  (Also set in Preferences→ Network & Files.)

• Max Complexity: Controls at what point a visually complex avatar is shown as a jellydoll. ¹⁾

• Use Region Windlight: Forces the viewer to use the windlight settings set for the region.
  Same as enabling top menu→ World → Environment Editor → Environment Settings→ Use Region Settings.

• Windlight Sky: Windlight sky settings. Use the < and > arrows to quickly scroll.

• Windlight Water: Windlight water settings. Use the < and > arrows to quickly scroll.

• Day Cycle: Allows for a quick selection of a day cycle to use.

• Time of Day: Drag the slider to change the time of day. The X to the right will reset the time of day to region default.

It is possible to add or remove settings from the QuickPrefs window by clicking the wrench icon in the lower right corner. The window will change, and appear as shown to the right. This edit panel overlays the lower portion of the QuickPrefs window.

• To add a new setting, click the + button. A new “blank” control is added to the QuickPrefs window. Now it needs to be associated with a setting.
• Click on Choose and a long drop down list will appear; these are all the viewer debug settings; the list of Firestorm debug settings is given here for reference.
• Select the setting you wish to add.
• In the space to the left of the drop down, give the setting a name that you find meaningful, for what the setting does.
• The Type field is automatically filled in based on the type of setting.
• If the setting accepts only whole numbers, then click the Integer checkbox.
• For some settings, you can alter the minimum, maximum and increment values; do not do this unless you know exactly what they represent.

To add more settings, click the + button again, and repeat.

Simply highlight the setting by clicking on the name in the upper portion of the QuickPrefs window. You can then change the name of it to something you prefer, if you wish. Or you can replace it with a totally different setting, which may be faster than deleting the setting and then adding a new one.

To the left of each of the existing settings in the window, a trashcan icon now is shown; clicking this will remove the associated setting from the window.

When you have completed making changes, click the 'x' button in the lower edit panel. It is then best to relog to ensure that changes “stick'.

If for any reason you need or want to revert to the default layout of the Quick Preferences panel, then click the Reset button at the bottom. Note that this cannot be reversed.

Téléchargement de pilotes AMD: https://support.amd.com/fr-fr/download Guide de désinstallation de pilote AMD : https://support.amd.com/fr-fr/kb-articles/Pages/Radeon-Software-Uninstall.aspx Guide d'installation propre du pilote AMD : http://forums.cnetfrance.fr/topic/1363085-pilote-amd-radeon--mettre-a-jour-ou-reinstaller-proprement-son-driver/

Si vous avez une carte graphique AMD il est possible que vous deviez recourir à ces quelques solutions (les cartes AMD semblent ne pas fonctionner très bien avec OpenGL , donc avec les viewers SL)

Artéfacts graphiques

Si vous voyez parfois une explosion de formes et d'éclats de couleur sur votre écran, il s'agit d'artéfacts visuelles, et ils ont différentes origines. L'une d'entre elles est le fait que les cartes et pilotes AMD/ATI ont bien du mal à supporter OpenGL. Alors que ces cartes sont de bonne qualité, les pilotes, eux, sont souvent problématiques avec SL.

Pour pallier à ces artéfacts, allez dans PReferences > Grpahics > Hardware Settings > Enable OpenGL Vertex Buffer Objects. Désactivez ce paramètre, puis réactivez lorsque les artéfacts réapparaissent. Ce paramètres vous donne plus de FPS, vous avez donc intérêt à le garder actif autant que faire se peut.

Pour plus de facilité, vous pouvez ajouter ce paramètres à vos Préférences rapide (Quick Prefs). Le paramètre de débogage est RenderVBOEnable et vous aurez à votre disposition un simple bouton on/off. Voir ici : http://wiki.phoenixviewer.com/fs_quick_preferences_fr#ajouter_supprimer_des_parametres

Les VBOs ont la réputation d'être à la source de crashes avec certains modèles anciens de cartes graphiques.

• Désactivez les VBOs: ouvrez le viewer et avant de vous connecter, pressez Ctrl-P pour ouvrir les Préférences. Ensuite:
  • Firestorm: Cliquez sur l'onglet Graphics → Hardware Settings. Assurez-vous que “Enable OpenGL Vertex Buffer Objects” n'est pas coché.

Si vous voyez tout en rose, le problème provient du pilote graphique. La meilleure solution est de mettre à jour le pilote de votre carte graphique.

Si pour une raison ou une autre vous ne pouvez pas :

• Activez le Menu Advanced avec Ctrl-Alt-D, si vous ne le voyez pas.
• Ensuite allez dans Advanced → Show Debug Settings → RenderMaxTextureIndex → paramétrez sur zéro
• Vous ne devriez plus voir toutes ces textures roses mais cela peut également causer une baisse de FPS (Frames Per Second)

Sinon vous pouvez aller à Preferences→ Graphics -> Hardware Settings→ Enable OpenGL Vertex Buffer Objects - Désactivez ce paramètre.

cette page vous guidera pour Windows 7.

Ce tableau dans cette page est une bonne référence. Cependant, malheureusement AMD n'a pas conservé ce tableau à jour. Les pilotes manquants sont :

Catalyst 15.7.1

• Pilote Catalyst 15.7.1 ou plus récent.
• Plutôt que de compter sur la fonction automatique Windows de mise à jour du pilote, allez directement sur le site AMD et faite vote mise à jour à partir de là. Cliquez ici pout trouver le pilote correspondant à votre système.

Mouselook is a view familiar to gamers, particularly “first person shooter” games. It is required in some situations in Second Life, particularly in role play, where shooting weapons of some kind is needed.

In mouselook, mouse movement changes the camera view. Typically also, clicking the left mouse button activates an action, such as shooting.

First of all, check to be sure that mouselook functionality is enabled in Preferences→ Move & View -> Mouselook -> Enable Mouselook functionality.

Now, mouselook may be activated in a few ways:

• Use your mouse wheel to scroll forward, until mouselook kicks in. (You can exit mouselook the same way, by scroll back with your mousewheel.)
  NOTE: Make sure that Prefs → Move & View → View → Don't use mouse wheel to control zoom level of the camera is not enabled!
• By using the 'm' key on your keyboard. However, this requires that WASD movement be enabled, which is done in Preferences → Move & View -> Movement→ Pressing letter keys affects Movement.
• Open the camera controls floater: top menu, Avatar → Camera Controls. Click on the Camera Modes button (top right one), then Mouselook.
• Via the Advanced menu (if you don't have this enabled, press Ctrl-Alt-D to enable it), Shortcuts → Mouselook.

If you need to click on something while in mouselook, you need to press and hold the Alt key. This disables the “camera follows mouse” behavior that is normal in mouselook, and allows you to move your mouse over the object and click it.

Note that this holds for left click only, not right click.

User interface elements (such as your inventory) are normally hidden in mouselook; you can disable this fucntionality in Preferences; see the section below. However, some elements can still be accessed if you open them using shortcuts, such as Ctrl-I for Inventory. Again, you will need to press and hold the Alt key to do anything in the window.

These are all under Preferences→ Move & View -> Mouselook; please refer there for more information.

Please refer to this page.

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 are 4 types of chat:

• Local chat is where everyone within chat range can hear you.
• Group chat is where you can talk to a group as a whole.
• Instant messaging (IM) is where you can talk privately one on one to another individual.
• Ad Hoc (Conference) calls where you can talk to a group of people you select in an IM.

• Normal chat has a range of 20 meters. To use normal text chat, input your text in either the main chat bar at the bottom or in the nearby chat window.
• Shout has a range of 100 meters. To use shout, press ctrl + enter keys after inputting your text.
• Whisper has a range of 10 meters. To use whisper, press shift + enter keys after inputting your text.
• Instant messages, group chats and conference calls are grid wide.

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:

• To talk to a nearby avatar, right click on any part the avatar (not their attachments) or their name tag and select IM from the menu.
• From the friends list in the contacts window, select on the person’s name and press the IM/call button.
• From the friends list in the People Panel, select the person’s name and press the IM button at the bottom of that window.
• If person is already chatting, click on the name in the chat window, this will bring up a quick profile window, and press the IM button.
• In a person’s profile, press the Instant Message button.

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:

• Go to Conversations window → Contacts Tab → Friends and select each friend you want to include in the conference by pressing Ctrl + left click on mouse on each friend’s name and then press the IM/Call button.
• Go to the People Panel→ Friends tab and select each friend you want to include in the conference by pressing Ctrl + left click on mouse on each friend’s name and then right-click and select IM.
• If you already have an IM going with someone and want to add another resident, you have two ways to do this:
  • go to Inventory→ Calling Card folder and drag that resident’s calling card into the IM, or
  • press the “add someone to this conversation” button at top of the IM.
  • Drag and Drop the selected avatar in the current IM. Can drag and drop from the following windows:
    • Radar
    • Nearby Avatar tab in People window
    • Friends tab in People window
    • Friends tab in Contacts tab (Conversations window)
    • People Search tab in Search window
    • Contact sets

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:

• Go to Preferences→ Chat -> Chat Windows→ . Next to “Show IMs in”, tick Tabs and then relog.

As separate windows:

• Go to Preferences→ Chat -> Chat Windows. Next to “Show IMs in”, tick Separate Windows and then relog.

How to dock/undock the chat windows:

• There is a “tear off” button next to the 'x' (Close). Press that to dock and undock the chat window.

How to rearrange the IMs:

• Select and drag the IM tab to the order that you choose.

How do I make the group chat look like the old style chat?

• In Preferences, go to Chat -> Chat Windows, and check Use V1 style chat headers.

How do I change the size of the font in chat?

• In Preferences, go to Chat -> Chat Windows, and select the size that you prefer in “Chat window font size”

How do I get my Contacts window back:

• If your Contacts window is not showing, go to the top menu bar→ Comm menu → Contacts (Ctrl+Alt+Shift+F).
• If Contacts window is showing but undocked and there is no tear off button showing, go to top menu bar→ Preferences→ Advanced (Ctrl+Alt+D) → Debug Settings → Search for ContactsTornOFF and set to False.

This page discusses the various ways you can move your avatar and control your view, the camera. As you will see, there are several ways of doing each, and different people have different personal preferences as to which works best.

The page only convers basic methods, and some of the options available. Further options concenering movement and camera are in Preferences -> Move & View, and subtabs.

Your avatar can be moved in-world in several ways.

Move controls are enabled via the top menu bar, Avatar → Move Controls. This opens a small window, as shown here, which can be moved on the screen and left where you find it most unobtrusive, by left clicking a corner and dragging it on-screen.

You can use the up and down arrow keys on your keyboard to move your avatar forward and backward. The left and right arrow keys turn your avatar in the corresponding direction, after which again use up and down to walk.

To walk to the left or right (called “strafing”), press and hold a Shift key, and while holding it down, press the left or right arrow key.

When standing, use the PgUp key to jump, PgDn to crouch. To fly, use the Home key, or press and hold PgUp ¹⁾. Press Home again to stop flying.

Those used to video games may wish to use the WASD keys on the keyboard for movement. To do this, go to Preferences -> Move & View -> Movement→ Pressing letter keys affects movement. This enables the following movement mappings:

Note that if you have your cursor in any chat window (eg local chat, Neabyby, an IM window, etc), you will type instead of moving.)

NOTE 1: If you have enabled Preferences → Move & View → Movement → Use AZERTY keyboard layout, then WASD will not work correctly unless you actually have an AZERTY keyboard.
NOTE 2: If you have gestures active that use certain letter keys, this may interfere with your ability to use WASD.

It is also possible to move your avatar using your mouse.

First, you can left click your avatar to guide its direction, while using the arrow keys or WASD to walk.

However, you can also walk using only the mouse: left click your mouse button on your avatar or name tag. Keep the left mouse button pressed down, and then also click the right mouse button. Your avatar will start walking forward. Move your mouse to “pilot” your avatar.

Releasing either mouse button will stop walking.

This method also works while flying.

In Preferences -> Move & View -> Movement, you can enable Single click on land → Move to clicked point. Then if you left click somewhere on the ground, your avatar will immediately start walking to that point.

One way to enable running is to press Ctrl-R. after pressing this, you will run instead of walking. Press Ctrl-R again to disable running.

In Preferences -> Move & View -> Movement, you can enable Tap-tap-hold to run. With this on, if you press the up arrow key twice, quickly, you will start running. You will stop running once you release the up arrow. ²⁾

You can also strafe-run left or right by using the above method: press left or right arrow twice, quickly.

When using Mouse Movement, you can run by double right-clicking on your avatar, while holding the left mouse button down.

If you get stuck in run mode, please refer to this page.

Moving your camera around, separately from moving your avatar, is commonly called “camming.”

A good introductory video on using your camera can be found here.

Refer to this page for details on the camera controls window.

To move your camera around via the keyboard, see Camera Keyboard Shortcuts.

If your avatar is seated, you can use your keyboard to control your view. ³⁾ The left and right arrows will rotate the camera around your avatar, while the up and down keys will zoom in and out. ⁴⁾

Using the mouse to control the camera arguably gives the most precise control of it. This involves selecting something to focus the camera on, and then moving the camera view relative to that item.

To focus your camera on something (or someone), press and hold the Alt key on your keyboard (the viewer cursor changes into a mgnifying glass), then left click with your mouse. This, by the way, is also known as Zoom mode, and can be enabled with Ctrl-1 - which opens the toolbox in Zoom mode.

Camera control is then as follows:

You can control the position of the camera relative to your avatar.

• Shift-Mouse Scrollwheel: controls the vertical height of the camera.
• Ctrl-Mouse Scrollwheel: controls the tilt (up/down rotation) of the camera.

Other controls in Preferences -> Move & View -> View:

• View Angle: Changes the camera field of view
• Distance: Changes how far away from you the camera is.

Other camera settings can be controlled via top menu, World -> Photo & Video→ Camera Tools.

If you have moved your camera around and wish to return it to your preferred position (as set above), press Esc.

This does not reset the camera to built-in defaults. To do that, instead, press Shift-Esc.

If you find that your camera is zoomed in or out too far, use Ctrl-9 to reset the zoom level.

If none of these help fix your view problem, refer to this page for more suggestions.

Refer to this page for details on enabling and using mouselook.