Phoenix Viewer implements Parcel Windlight, as well as LL's Region Windlight. Thus, individual parcels, and entire regions, can have unique settings to enhance the environment.

If you have your own preferred setting that you wish to use, and do not wish to have it changed to whatever is set at parcel or region level, then you need to disable these features.

Open the Preferences window (Ctrl-P or from the top menu bar, select Edit → Preferences)
Go to the Phoenix tab → Page 2 → Windlight
Disable Automatically change environment to use region/parcel settings from region
If you also wish to never allow parcel windlight changes, and inhibit the pop-up messages that request that, disable: Use Phoenix Parcel Windlight sharing (Experimental)
Click Apply, then Ok.

↧

ati - [How to Determine What Version of Catalyst / Crimson You Have]

February 25, 2019, 1:34 am

≫ Next: graphics_crashes_and_glitches - [Viewer Freezing]

≪ Previous: phoenix:wl_change_on_tp

ATI, AMD, crash, pink, Raptr, VBO, Catalyst, Windows

AMD/ATI Video Card Specifics

Download AMD Drivers & Software https://support.amd.com/en-us/download
AMD Graphics Drivers and Software Download and Installation FAQhttps://support.amd.com/en-us/kb-articles/Pages/AMDGraphicsSoftwareandDriversFAQ.aspx

If you have an AMD/ATI graphics card then you may need to do these steps (ATI drivers don't seem to support OpenGL graphics very well, and SL viewers use OpenGL, as opposed to DirectX).

Graphics Glitches

Graphics Artifacts

If you occasionally see an explosion of colored shards and shapes across your screen, these are graphics visual artifacts, and there are various causes for them. One is the lack of OpenGL support with ATI/AMD graphics cards and drivers. While ATI/AMD graphics can be good graphics cards, the drivers can also be finicky for SL.

The workaround to clear away the artifacts is found in Preferences - Graphics - Hardware Settings - Enable OpenGL Vertex Buffer Objects. Toggle that setting off, then back on again when you see the artifacts. You want to keep this setting enabled as it gives a considerable boost to your FPS.

For ease of access, you can add this setting to your Quick Preferences. The debug setting is RenderVBOEnable and use a simple Radio on/off option http://wiki.phoenixviewer.com/fs_quick_preferences#adding_removing_settings

Crashing

VBO is known to cause crashes in multiple different scenarios with older graphics cards. So one thing to try:

Disable VBO: Run the viewer and before logging in, press Ctrl-P to bring up the Preferences window. Then click on Graphics → Hardware Settings tab. Make sure that “Enable OpenGL Vertex Buffer Objects” is not checked. Note this may result in lower FPS.

The AMD Raptr software is known to cause viewers - and games - to crash. This has been discussed on Steam; for example, see this thread. Check to see if you have Raptr installed; if so, try uninstalling it.

Cannot unlink linksets using keyboard shortcut Ctrl+Shift+L [AMD ReLive]

AMD ReLive has been discovered to interfere with unlinking shortcut Ctrl+Shift+L. See Linden Lab bug report BUG-226375.
For more information, including how to disable AMD ReLive, see AMD's support page.

The World is Pink

If you are seeing everything pink, the issue is the graphics card driver. The best solution is to update the graphics card drivers.

If for any reason, this is not an option:

Enable the Advanced menu with Ctrl-Alt-D, if it isn't already
Then Advanced → Debug settings → RenderMaxTextureIndex → Set this to zero
This should fix the pink textures but may also cause a drop in your FPS (Frames per second)

Alternately, you can go to Preferences→ Graphics -> Hardware Settings→ Enable OpenGL Vertex Buffer Objects - and disable that.

How to Determine What Version of Catalyst / Crimson You Have

13.9	Windows Graphics Driver Version: 8.17.0010.1230	OpenGL Version: 4.2.12422 Compatibility Profile Context 13.152.0.0
14.4	Windows Graphics Driver Version: 8.17.0010.1280	OpenGL Version: 4.2.12874 Compatibility Profile Context 14.100.0.0
15.7	Windows Graphics Driver Version: 8.17.0010.1395	OpenGL Version: 4.2.13397 Compatibility Profile Context 15.200.1046.0
15.7.1	Windows Graphics Driver Version: 8.17.0010.1404	OpenGL Version: 4.2.13399 Compatibility Profile Context 15.200.1062.1002
15.9 Beta	Windows Graphics Driver Version: 8.17.0010.1404 ¹⁾	OpenGL Version: 4.2.13399 Compatibility Profile Context 15.200.1062.1004
15.11 Beta	Windows Graphics Driver Version: 8.17.0010.1404	OpenGL Version: 4.2.13399 Compatibility Profile Context 15.201.1151.1007 “Crimson”
Crimson Edition 15.30.1025	Windows Graphics Driver Version: 8.17.0010.1429	OpenGL Version: 4.2.13416 Compatibility Profile Context 15.300.1025.1001
unknown	Windows Graphics Driver Version: 8.17.0010.1452	OpenGL Version: 4.2.13431 Compatibility Profile Context 16.150.2401.1002
16.7.2	Windows Graphics Driver Version: 8.17.0010.1460	OpenGL Version: 4.2.13441 Compatibility Profile Context 16.200.1035.1001

Known Good ATI Driver

Before doing anything else, if you used a work-around “fix” of copying Catalyst driver DLLs into the Firestorm folder, them please remove those DLLs before proceeding with the install of any new driver.

Catalyst 15.7.1 drivers or newer.

Catalyst 15.7.1 drivers or newer.
Rather than relying on the built-in Windows driver update function, visit the AMD site directly and update from there; click here to locate the drivers for your system.

¹⁾

See this AMD page for known issues: http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspx

↧

graphics_crashes_and_glitches - [Viewer Freezing]

February 26, 2019, 3:32 am

≫ Next: slow_rez - [Slow Rez]

≪ Previous: ati - [How to Determine What Version of Catalyst / Crimson You Have]

crash, graphics, rainbow, not responding, freezing, nVidia, Windows, MSI True Color, flux

Graphics Crashes and Glitches

If You Have Changed Any Debug Settings

Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example, go to the top menu, Advanced → Debug Settings (press Ctrl-Alt-D to enable Advanced, if it isn't):

RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
TextureLoadFullRes should never be enabled (in other words, it should be set to FALSE).

If you are advised to raise LOD above 4, please disregard that advice.

Similarly, there is a notecard going round which suggests settings to prevent graphics crashes. Sadly, those settings can often result in perfectly ordinary content refusing to render. So if you have changed debug settings per such a notecard, revert them.

For both the cases above, should you not remember what settings you changed, then proceed as follows:

Back up your settings as explained here.
Then wipe settings by following the instructions on this page.
Log back in and see if this fixes your problem. If it does, you can try a restore and see if the issue returns.
If the problem does return, wipe settings again and set them from scratch.

Driver Not Responding

"Display driver stopped responding and has recovered" error in Windows

If you are getting the error in the title, then please refer to this page, this page or this page for those using Intel graphics for possible solutions.

With thanks to Skua Sarrasine for having found the first of these.

nVidia Driver Error Code 7 (or 3)

Symptom:“This is a bug thats only experienced with Firestorm running. Basically, at seemingly random, but very infrequent times, my dual screens will bug out, producing two displays of solid colour, randomly. Sometimes Windows will return saying it recovered from an error code 7 or 3.”

Some research turned up this for error code 7; it suggests setting physX to CPU. And that seems to have solved the issue.

Note also the (apparent) interaction with Chrome.

Viewer Not Responding

This is a known issue with Windows 7, 8.1, and 10 with a 64-bit operating system; it affects other programs in addition to Second Life viewers.

Please try the following - but NOT while logged in.

Windows 7

Go to the Start button
Type services.msc and then press enter.
Wait until the services window pops up.
You may have to expand the window a bit to see the services.
Look for DesktopWindowManager.
- If it is running, right click it and select Stop. Wait until it stops.
- You will probably see your desktop transparency window borders go flat. No worries.
Right click again and select Properties.
- In the Startup type, select Manual. Click OK.

Windows 8.1/10

Open the Task Manager, by one of the following methods…
1. Right click the task bar and choose Task Manager.
2. Click the Start button and type Task Manager, then click on the result.
3. Press Ctrl+Alt+Del and choose Task Manager from the list.
4. Press Ctrl+Shift+Esc.
Click More Details link at the bottom if needed
Look at the several column headers, they will show a percentage of use. Memory or Disk may show a high percentage when Firestorm is not responding.
Click on one of the high-percentage column headers to sort the processes. The top one is likely the cause. If it's your antivirus, make sure you have whitelisted Firestorm and its cache (refer to this page for whitelisting guidance).

Viewer Freezing

If you find the Firestorm seems to freeze up every so often, then try these things, one at a time, testing after each one:

Viewer freezes while “Loading world…“– If you have Intel HD 620 or Intel HD 630, and Windows 10 – This is an Intel driver issue. The fix is to roll back to driver 24.20.100.6025. Download Legacy Intel® Graphics Driver for Windows® 10 Version: 24.20.100.6025 (Ref. BUG-225655.)
If you have chat saving enabled, and have a large number of chat transcript files, these could be causing the freezes. (Ref. FIRE-11322.) Try moving your chat transcripts elsewhere and see if the freezing stops.
You can find your chat transcripts by going to Preferences→ Network & Files -> Directories→ Conversation logs and transcripts location; click the Open button.
Set Preferences → Network & Files → Directories → Cache Size to maximum (9984MB or the maximum space available, whichever is less)
Ensure that your antivirus software is not scanning the viewer cache folder. See Whitelisting the Viewer in Anti Virus Software for more information.
If you have ever enabled “Full Res Textures”, disable this setting. Top menu bar, Develop→ Rendering → Full Res Textures (dangerous). Ensure that this is NOT checked. (Ctrl-Alt-Q to enable Develop, if it isn't.)
Advanced → Debug Settings → Set FastCacheFetchEnabled to FALSE - then relog.
Ctrl-Alt-D to enable Advanced, if it isn't.
Preferences → Graphics → Hardware Settings → Viewer Texture Memory Buffer - raise this as high as it will go. Then relog. (64-bit version only)
Tip from a user: Windows users: If you're running CrashPlan, open the “Advanced” section of “Backup” settings and uncheck “Back up open files.”
Tip from a user: Windows users: If you have “Magic Control Technology Display Utility” (MCTDUtil.exe), disable it. See https://www.file.net/process/mctdutil.exe.html.
Tip from a user: Linux users: Turn off compositing, see if it helps.

For additional suggestions, see the page on Severe Lag.

↧

slow_rez - [Slow Rez]

February 26, 2019, 8:32 pm

≫ Next: firestorm_classes

≪ Previous: graphics_crashes_and_glitches - [Viewer Freezing]

slow rez, rez, grey, Webroot, lag, packet loss, draw distance, bandwidth

Slow Rez

If things around you remain grey for a long time, or objects take a long time to pop into position, this is essentially because the data has not yet been sent to your viewer. There are a number of possible causes, and solutions or at least work-arounds:

If you have Webroot SecureAnywhere antivirus installed, refer to this page.

Power down your router and/or modem. This generally means unplugging it from the power source. Leave them disconnected for at least a full minute before reconnecting. Wait for them to complete the power up sequence, then reboot your computer.

Teleport out, then back in.

The region is badly lagged (many avatars present, too many scripts running, etc.) and so the region server is using all its time processing and has very little time left over to deliver textures and other data to you. The best way to cope with this is to reduce the demand you make; in other words, reduce your draw distance, even to 12m or less, and wait until textures and objects have loaded before you increase it again.

You are experiencing packet loss or, more generally, have a poor network connection. Or your bandwidth slider may be set too high. Bring up the stats bar with Ctrl-Shift-1 and check Packet Loss and Ping Sim. Ideally, packet loss should be 0.0%, and Ping Sim under 200ms.

Determine optimal bandwidth: refer here.

You can also try to have less textures draw all at once by reducing draw distance when you teleport. You can do this manually, or make use of the built in Progressive Draw Distance function.

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

Another possibility is that DNS look-up is failing. Try changing DNS to google; see this page for details.

Some other program on your computer might be interfering with your viewer's connection to SL, like a firewall or anti-virus. Try disabling them temporarily, to see if things improve. If they do, you have isolated the problem. Whitelisting the viewer and cache folder would probably help.

It has been reported that on Windows, the Aero background theme will also lead to textures refusing to rez, due to how much memory this feature consumes. Uninstalling that should help.

If mesh items, specifically, never rez, see Mesh Issues.

Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more or having other issues, including very slow rez. Please see this page for more.

↧

firestorm_classes

February 28, 2019, 1:27 am

≫ Next: motd - [Event Messages of the Day.]

≪ Previous: slow_rez - [Slow Rez]

²(

help, classes

Firestorm Classes

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

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

Locations are indicated in the far right column as follows:

FS: Firestorm Support region classroom, * Firestorm Classroom
JU: Junkyard University, * Junkyard University Classroom

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

Unscheduled classes may also be held on an impromptu basis. If this happens, a notice will be sent in Firestorm Support English. secondlife:///app/group/3a1be8d4-01f3-bc1a-2703-442f0cc8f2dd/about

*All times SLT*

Fri	1 March	2 Am – Introduction to Firestorm and the Wiki (TEXT ONLY) This class gives you an overview of the Firestorm Viewer and of our greatest informational resource, our Wiki, including search tips.	FS
Sat	2 March	tba – Clean Install (TEXT ONLY) Learn how to correctly and quickly perform this most fundamental and important of tasks. Recommended to take Settings Backup class first.	FS
Sun	3 March	tba – Menus 1 (TEXT ONLY) We will be covering the menus on the top bar, from Avatar through Help.	FS
Mon	4 March	1 Am – Menus 2 (TEXT ONLY) We will cover the Advanced and Develop menus in the top bar.	FS
Tue	5 March	9 Am – Odds & Ends 1 (TEXT ONLY) This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.	FS
Wed	6 March	tba – Odds & Ends 2(TEXT ONLY) Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more.	FS
Thu	7 March	7 Am – Preferences Set 1 (TEXT ONLY) We will cover some of the Firestorm preferences (General, Chat, Privacy), based on our current release.	FS
Fri	8 March	2 Am – Preferences Set 2 (TEXT ONLY) We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release.	FS
Sat	9 March	tba – Preferences Set 3(TEXT ONLY) We will cover some of the Firestorm preferences (Move & View, Advanced, Firestorm), based on our current release.	FS
Sun	10 March	tba – QuickPrefs Customization + Lag (TEXT ONLY) Two mini-classes in one. One discusses the causes of lag in SL. The other explains how to customize your Quick Preferences.	FS
Mon	11 Feb	1 Am – Preferences Set 4 (TEXT ONLY) We will cover some of the Firestorm preferences (Colors, Skins, Notifications, User Interface, Sounds and Media).	FS
Tue	12 March	9 Am – Reporting Bugs, Requesting Features (TEXT ONLY) Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need.	FS
Wed	13 March	tba – Avatar Complexity and Graphics Presets (TEXT ONLY) Learn how to boost performance with av complexity and improve usability with the presets.	FS
Thu	14 March	7 Am – Firestorm Skins (TEXT ONLY) This class covers the differences among Firestorm's many skin options, including the Vintage Classic and Colorable User Interface skins.	FS
Fri	15 March	2 Am – Animation Overrider (TEXT ONLY) On Firestorm, you can save scripts and HUD space by running your AO animations through the viewer. Learn how to set up and get the most out of this feature.	FS
Sat	16 March	tba – Basic Troubleshooting (TEXT ONLY) An introduction to basic methods to start locating problems. Focused on Firestorm but some parts are non-viewer-specific.	FS
Sun	17 March	tba – Backing up Settings and Logs (TEXT ONLY) This class covers how to save your settings and chat logs on your computer. Recommended to take this before the Clean Install class.	FS
Mon	18 Feb	1 Am – Contact Sets (TEXT ONLY) There is a cool feature called Contact Sets that lets you organize your Contact List. We'll cover how to set them up and use this epic feature.	FS

↧

motd - [Event Messages of the Day.]

February 28, 2019, 3:04 am

≫ Next: fs_compiling_firestorm_windows - [NSIS (Unicode)] NSIS v3+ required now

≪ Previous: firestorm_classes

Firestorm Message of the Day.

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!

I missed it! Make it come back!

Oh hi! I didn't see you come in! You're probably here because you missed the message of the day. It went by too fast, it was too 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.)

About the Message of the Day.

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.

Event Messages of the Day.

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: Forgotten Gatcha New User Pet Gifts
New to SL and feeling lonely, overwhelmed or confused with it all? Come get your personal pet for the holidays to keep you company while exploring! Get them here till they run out! https://wiki.phoenixviewer.com/pets_for_new_residents

MOTD: EVENT: Spoonful of Sugar Festival 2019 to Benefit MSF/Doctors Without Borders
Spoonful of Sugar Festival 2019 to Benefit MSF/Doctors Without Borders is now accepting applications for participation in their September event! To sign up http://thesosfestival.com/spoonful_of_sugar_become_a_sponsor.html

Preset Messages of the Day.

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

Security: Keep your Second Life account and your computer safe!

Release: What's the current Firestorm release version and where do I get it?

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;

Firestorm Message of the Day, Firestorm Security!

MOTD: SECURITY: Firestorm Downloads
Firestorm Security! Never download Firestorm from a website that is not firestormviewer.org! Alternate download locations should not be trusted! Firestorm downloads - https://www.firestormviewer.org/downloads/

Firestorm Message of the Day, Firestorm Release!

MOTD: RELEASE: Current Firestorm release version is 5.1.7.55786
Firestorm Release! The current Firestorm release version is 5.1.7.55786! Not on it? Get it here! Get it now! READ THE BLOG POST! https://www.firestormviewer.org/firestorm-release-v5-1-7-55786/

Firestorm Message of the Day, Firestorm Tips!

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'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

Firestorm Message of the Day, Firestorm Help!

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

Firestorm Message of the Day, Firestorm Gateway! Coming soon!

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

Firestorm Message of the Day, Firestorm Fun!

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

Notes

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

¹⁾

A 1 - 7 in the MotD priority list.

↧

fs_compiling_firestorm_windows - [NSIS (Unicode)] NSIS v3+ required now

March 1, 2019, 12:50 am

≫ Next: wearing_entire_inventory

≪ Previous: motd - [Event Messages of the Day.]

Firestorm Windows Builds

This page describes all necessary steps to build the Firestorm viewer for Windows, using the updated build infrastructure introduced with Linden Lab's project Alex Ivy.

NOTE: This description is NOT valid for building versions of the viewer prior to the Alex Ivy merge (revision 54609)!

Please note that we do not give support for compiling the viewer on your own. However, there is a self-compilers group in Second Life that can be joined to ask questions related to compiling the viewer: Firestorm Self Compilers

Install required development tools

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

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

Windows

Install Windows 10 Pro 64bit using your own product key
Alternatively: Install Windows 7 or 8.1 Pro 64bit

Microsoft Visual Studio 2013 Professional

Install Visual Studio 2013 Professional
Note: If you don't own a copy of Visual Studio 2013 Professional, you might consider installing the Community version (requires creating a Microsoft account if you do not already have one ) (If the download link for 2013 on visualstudio.com leads to a dead page even after logging in and out and back in again, try Googling “Visual Studio 2013 Community update 5 download” for a direct link. MS has recently changed things with accounts and the free subscriptions.)
- Run the installer as Administrator (right click, “Run as administrator”)
- Uncheck all the “Optional features to install:” - they are not required

DirectX SDK

Download and install DirectX SDK (June 2010)
- Run the installer as Administrator (right click, “Run as administrator”)
- At the Installation Options screen, set everything except the DirectX Headers and Libs to “This feature will not be installed”

Tortoise Hg

Download and install TortoiseHg 3.2.3 or newer (64bit)
- Note: No option available to install as Administrator
- Use default options (path, components etc.)
- Add the following directory to your path:
```
C:\Program Files\TortoiseHG
```

CMake

Download and install at least CMake 3.4.3 (32bit is only option)
- Run the installer as Administrator (right click, “Run as administrator”)
- At the “Install options” screen, select “Add CMake to the system PATH for all users”
- For everything else, use the default options (path, etc.)
- Make sure that the following directory was added to your path:
```
C:\Program Files (x86)\CMake\bin
```

Cygwin

Download and install Cygwin 64 (64bit)
- Run the installer as Administrator (right click, “Run as administrator”)
- Use default options (path, components etc.) *until* you get to the “Select Packages” screen
- Add additional packages:
  - Devel/patch
- Use default options for everything else
- Make sure that the following directory was added to your path.:
```
C:\Cygwin64\bin
```

Python

Download and install the most recent version of Python 2.7 (32bit)
- Linden Lab advises to use the 32bit version as the VMP requires it. However, Firestorm currently doesn't use VMP, so the 64bit version might work (use at own risk!)
- Note: No option available to install as Administrator
- Use default options (path, components etc.) until you get to the “Customize Python” screen
- Change “Add python.exe to Path” to “Will be installed on local hard drive”
- Add the Python installation dir to the system path:
```
C:\Python27
```

Intermediate check

Confirm things are installed properly so far by opening a Cygwin terminal and enter:

cmake --version
hg --version
python --version

If they all report sensible values and not “Command not found” errors, then you are in good shape.

The Cygwin terminal is only needed for testing. All commands for actually building the viewer will be run from the Windows command shell.

Set up Autobuild and Python

Install Boostrip pip
- Download (Save As) get-pip.py and copy to a temp folder
- Open Windows Command Prompt
- Switch to that temp folder and execute it:
```
python get-pip.py
```
- Pip will be installed
- Add the following directory to your path:
```
C:\Python27\Scripts
```

Install Autobuild
- Open Windows Command Prompt and enter:
```
pip install hg+https://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild
```
- Autobuild will be installed. Earlier versions of Autobuild could be made to work by just putting the source files into your path correctly; this is no longer true - Autobuild must be installed as described here.

Set environment variable AUTOBUILD_VSVER to 120

Check Autobuild version to be 1.1.7 or higher:
```
autobuild --version
```

NSIS

If you plan to package the viewer and create an installer file, you must install the NSIS from the official website.
Not required unless you need to build an actual viewer installer for distribution, or change the NSIS installer package logic itself

If you want to package the viewer built on a revision prior to 57033, you must install the Unicode version of NSIS from here - the installer from the NSIS website WILL NOT work!

Setup viewer build variables

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

Clone the build variables repository:

hg clone https://hg.phoenixviewer.com/fs-build-variables <path-to-your-variables-file>

Set the environment variable AUTOBUILD_VARIABLES_FILE to
```
<path-to-your-variables-file>\variables
```

Configure Visual Studio 2013 (optional)

Start the IDE
Navigate to Tools> Options> Projects and Solutions> Build and Run and set maximum number of parallel projects builds to 1.

Set up your source code tree

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, it is assumed that you created a folder c:\firestorm.

c:
cd \firestorm
hg clone https://hg.phoenixviewer.com/phoenix-firestorm-lgpl

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

Prepare third party libraries

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

FMOD Studio using Autobuild

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

Make sure to download the FMOD Studio API and not the FMOD Studio Tool!

c:
cd \firestorm
hg clone https://bitbucket.org/Ansariel/3p-fmodstudio

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

FMOD_VERSION="11005"
FMOD_VERSION_PRETTY="1.10.05"

Continue on the Windows command line:

c:
cd \firestorm\3p-fmodstudio
autobuild build --all
autobuild package

While running the Autobuild build command, Windows might ask if you want to allow making changes to the computer. This is because of the FMOD Studio installer being executed. Allow these changes to be made.

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

wrote C:\firestorm\3p-fmodstudio\fmodstudio-{version#}-windows-{build_id}.tar.bz2
md5 c3f696412ef74f1559c6d023efe3a087

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

cd \firestorm\phoenix-firestorm-lgpl
cp autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

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

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

For example:

autobuild installables edit fmodstudio platform=windows hash=c3f696412ef74f1559c6d023efe3a087 url=file:///C:\firestorm\3p-fmodstudio\fmodstudio-1.10.02-windows-180191431.tar.bz2

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

Configuring the viewer

Open the Windows command prompt.

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

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then enter:

 c:
 cd \firestorm\phoenix-firestorm-lgpl
 autobuild configure -c ReleaseFS_open

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

Note: Configuring the viewer for the first time will take some time to download all the required third-party libraries. As of Autobuild 1.1, the download progress is hidden by default. If you want to watch the download progress, you can use the verbose option to display a more detailed output:

autobuild configure -v -c ReleaseFS_open

Configuration switches

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

-A <architecture> sets the target architecture, that is if you want to build a 32bit or 64bit viewer (32bit is default if omitted).
–fmodstudio controls if the FMOD Studio package is incorporated into the viewer. You must have performed the FMOD Studio installation steps in FMOD Studio using Autobuild for this to work.
–package makes sure all files are copied into viewers output directory. You won't be able to start your compiled viewer if you don't enable package or do 'compile' it in VS.
–chan <channel name> lets you define a custom channel name for the viewer
-LL_TESTS:BOOL=<bool> controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
more of them.

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

Examples:

To build a 32bit viewer with FMOD Studio and to create an installer package, run this command in the Windows command window:
```
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE
```

To build a 64bit viewer without FMOD Studio and without installer package, run this command:
```
autobuild configure -A 64 -c ReleaseFS_open -- --chan MyViewer -DLL_TESTS:BOOL=FALSE
```

Building the viewer

There are two ways to build the viewer: Via Windows command line or from within Visual Studio.

Building from the Windows command line

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

set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

Then run the Autobuild build command. Make sure you include the same architecture parameter you used while configuring the viewer:

autobuild build -A 64 -c ReleaseFS_open --no-configure

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

Building from within Visual Studio

Inside the Firestorm source folder, you will find a folder named build-vc120-<architecture>, with <architecture> either being 32 or 64, depending on what you chose during the configuration step. Inside the folder is the Visual Studio solution file for Firestorm, called Firestorm.sln.

Double-click Firestorm.sln to open the Firestorm solution in Visual Studio.
From the menu, choose Build → Build Solution
Wait until the build is finished

Parallel building of pre Alex Ivy viewers

Older versions of the viewer before the merge of Linden Lab's project Alex Ivy use Autobuild 1.0 that is incompatible with the build process as it is now. By default it is not possible to install two different versions of Autobuild on the same computer at the same time. Making use of virtualenv will overcome this problem, allowing simultaneous installations of Autobuild 1.0 and Autobuild 1.1 in two distinct “virtual” Python environments.

Install virtualenv

Install virtualenv by opening a Windows command prompt and enter:

pip install virtualenv

This requires the Boostrip pip already installed. After virtualenv has been installed, you can create virtual Python environments using the command

virtualenv <virtual-environment-name>

This will create the directory <virtual-environment-name> within the Python installation folder and add some required folders and files. Among these files is a batch file called activate.bat in the folder Scripts. To switch to the newly created virtual environment execute the activate.bat batch file. After switching to the virtual environment, your command prompt will be prepended by the name of the virtual environment.

In this example we will create a virtual environment called “Autobuild11”:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat

Your command prompt should look like this now:

(Autobuild11) C:\

After you switched to a particular virtual environment, you can now install as described in Set up Autobuild and Python.

Complete example:

virtualenv Autobuild11
c:\Python27\Autobuild11\Scripts\Activate.bat
pip install hg+https://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild

Configuring and building the viewer

Configuring and building the viewer from the Windows command line is basically identical as described in Building from the Windows command line with the difference that you now have to call the activate script first:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE
autobuild build -A 64 -c ReleaseFS_open --no-configure

If you plan to build the viewer from within Visual Studio, you will have to configure the viewer the same way as if you were to build from the Windows command line:

c:
\Python27\Autobuild11\Scripts\Activate.bat
cd \firestorm\phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open -- --fmodstudio --package --chan MyViewer -DLL_TESTS:BOOL=FALSE

To be able to build from Visual Studio, you will have to set a Windows environment variable called VIRTUAL_ENV pointing at the virtual Python environment to use, in our example “C:\Python27\Autobuild11”. Now open the Firestorm Visual Studio solution to start Visual Studio and build the viewer.

NOTE: Setting the VIRTUAL_ENV environment variable only has an effect if building a version greater or equal than 53671! If you plan to build older versions of Firestorm, it is advised to install Autobuild 1.0 as the default Autobuild version and create a virtual environment for Autobuild 1.1!

Troubleshooting

SystemRootsystem32: unbound variable

When trying to execute the Autobuild build command, you might encounter an error similar to

../build.cmd.sh line 200: SystemRootsystem32: unbound variable

This error is caused by the order of the items in the Windows “path” environment variable. Autobuild exports all paths set in the “path” environment variable into Cygpath names and variables. Since these Windows “paths” can also contain variables like %SystemRoot% and they can also depend on each other, it is important to keep the dependency order intact. Example:

%SystemRoot%
%SystemRoot%\system32
%SystemRoot%\System32\Wbem

The following screenshot shows the correctly ordered paths containing variables and depending on each other.

↧

wearing_entire_inventory

March 1, 2019, 4:23 am

≫ Next: antivirus_whitelisting -

≪ Previous: fs_compiling_firestorm_windows - [NSIS (Unicode)] NSIS v3+ required now

wearing entire inventory, inventory

Wearing Your Entire Inventory

If you find yourself suddenly starting to wear your entire inventory (or some large part of it), here are some suggestions for how to fix the problem. Please do them one at a time; the initial methods are simpler than later ones, and will often work. If a method fails, then move on to the next one. Please also follow the instructions as exactly as possible.

Note: If you have RLVa (Remote Scripted Viewer Controls) enabled, disable it and relog before beginning the following steps. Open your Preferences (Ctrl-P or Avatar menu → Preferences), and go to Preferences → Firestorm → Extras. Uncheck “Allow Remote Scripted Viewer Controls (RLVa)” and then relog.

Method 1

Open the Current Outfit folder (no, don't click on the Worn tab; find the Current Outfit folder), and shift select blocks of 10 or so worn items and Right click → detach from yourself.

Note: Do not attempt to remove too many worn links in one go, or you will likely crash or freeze. Also note that you cannot detach your skin, shape, bald hairbase or eyes links.

Detach everything showing worn in Current Outfit folder that you can and then delete all unworn links a few at a time (again, dont delete too many at once or you may freeze/crash).

Once you are only left with skin, shape, baldy and eyes worn, you may wish to empty trash as there may be hundreds of links in there.

Now you are safe to replace outfit normally

Method 2

If the above doesn't solve the problem, the fix below usually works - though it may need to be repeated a couple of times:

Go to Hippo Hollow
Make a temporary folder in your inventory; in that, put a *copy* of your skin, shape, hair base and eyes - and if you like, a base layer garment like jeans or a dress. NO PRIMS
Right click the folder you just made, and select Replace Outfit. No Add, not wear, but REPLACE
Once that has done, relog to last location - ie, back to Hippo Hollow.
Make sure you are still wearing only the things from the temporary folder you made
At this point, you can put your normal avatar back on.

↧

antivirus_whitelisting -

March 3, 2019, 2:09 am

≫ Next: fs_error_message_list - [Messages Mentioning Media]

≪ Previous: wearing_entire_inventory

whitelist in antivirus, antivirus, Adaware Free, Advanced System Care, Avast, AVG, BitDefender, Gatekeeper, Kaspersky, McAfee, MS Essentials, MS Defender, Norton, Panda, PcTools, Webroot

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

Introduction

Some anti-virus programs (and firewalls and anti-malware programs) will incorrectly flag a viewer - or necessary components of a viewer - as a virus or threat. They may remove the suspected part completely, rendering all or part of the viewer slow or non-functional. There is at least one anti-virus program which will scan every file placed on your computer, even if created by an authorized program. This can affect Firestorm (or any viewer) in that it will scan each and every texture placed in cache, slowing down performance of the viewer significantly, keeping objects and/or textures from rezzing, and keeping CPU usage high.

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

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

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

Known Issues

See the Malwarebytes tab below.

Reinstalling and Whitelisting

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:

Uninstall the viewer normally.
Disable the anti-virus software completely
REBOOT your computer to make sure that the AV is not running anymore.
Reinstall the viewer.
- On Windows, make sure you do not install it back to the default folder suggested; INSTALL TO A NEW FOLDER. This step is vital.
- On Mac, simply reinstall to your Application folder as usual.
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 dullahan_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
- REBOOT your computer at this time.
Run the viewer to ensure that it is working correctly; do a test of search and voice to ensure that both work, checking that the respective plugins get loaded. LOG OUT of the viewer.
Re-enable your anti-virus software and run the viewer again, repeating the tests above.

Whitelisting Steps for Specific AV Software

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

Adaware free

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

Advanced System Care

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

Avast

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

AVG

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

BitDefender

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.

Bullguard

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

Credits: Thanks to user Aishagain for this information.

F-Secure

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

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

Gatekeeper (Mac OS X)

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

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

Kaspersky

In order to create an exclusion rule:

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

Rules can apply to the following protection components:

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

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

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

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

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

Malwarebytes

Recent updates of Malwarebytes on Windows 7 causes the viewer to lock up or crash at log in or shortly after. Also affects SL Viewer. Toggle off the Real Time Web Protection module for now and reboot PC. Refer to this JIRA for more info and workarounds.

Recent updates of Malwarebytes on Windows 10 causes object and texture corruption. Also affects SL Viewer. Toggle off the Real Time Web Protection module or disable Malwarebytes and reboot PC. Refer to this JIRA for more info and workarounds.

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

McAfee

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

Microsoft Security Essentials/Windows Defender

Basic Exclusions

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

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

Open Settings and in the search field at the top right enter defender
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) )

Real Time Web Protection Issues

Recent updates of Windows Defender cause object and texture corruption. Also affects SL Viewer. Toggle off the Real Time Web Protection module or disable Defender and reboot PC. Refer to this JIRA for more info and workarounds.

Can't Save Files to Hard Drive (Snapshots, Chat Files, Backups, etc.)

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

Try following these steps:

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

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

Can't run Firestorm installer

See this page https://wiki.phoenixviewer.com/fs_install_crash#windows.

Norton

Add exclusion to Auto-Protect and Risk scan

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

Download Intelligence

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

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

Panda Cloud Antivirus Free (version 2.1.1)

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

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

PC Tools Spyware Doctor

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

Webroot

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

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

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

For additional information:

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

↧

fs_error_message_list - [Messages Mentioning Media]

March 3, 2019, 3:46 am

≫ Next: windows_edit_path_environment_variable.png

≪ Previous: antivirus_whitelisting -

error messages

Error Messages

This is a collection of error messages seen in SL. Some are system messages; some are viewer-generated. The list is by no means complete.

If you get an error message that is not on this page, please:

Report it in Firestorm Support English (in-world support group)
Or File a Jira alerting us to it (please provide the complete, exact wording of the message; a screenshot is also helpful).
If you found a solution or explanation, please let us know that too.

Thanks!

Messages Mentioning Animations

Error	Remedy
“PERMISSION_TRIGGER_ANIMATION permission not set”	This message usually comes from an AO or other scripted item, dropped in world. It can also come from a badly scripted object that doesn't check it has perms before animating, such as a badly written poseball.

Messages Mentioning Attachments, Clothing, Body Parts, or Other Wearables

Error	Remedy
“You can't attach multiple objects to one spot” message when detaching from avatar.	That will happen if the user somehow has a coalesced object in their Current Outfit folder. Delete that link from the Current Outfit folder.
“The outfit folder contains no clothing, body parts, or attachments.”	See Empty Outfits

Messages Mentioning Certificates

Error	Remedy
“Unable to find a valid certificate”	See Second Life: Unable_to_find_a_valid_certificate.

Messages Mentioning Credentials or Passwords

Error	Remedy
“We were unable to decode the file storing your saved login credentials” (or) “Failed to decode login credentials”	See Failed to Decode Login Credentials

Messages Mentioning Clock or Time

Error	Remedy
“Unable to connect to Second Life. Often this means that your computer's clock is set incorrectly. Please go to Control Panels and make sure the time and date are set correctly.”	See Second Life: Clock is set incorrectly.

Messages Mentioning Connections or Networks

Error	Remedy
“Unable to establish a secure connection to the login server”	See Second Life: Unable to establish a secure connection to the login server .
“Second Life has detected corruption in either your network transmissions or the files it's attempting to read on your hard drive. You might also be logging in from an invalid location.”	See Second Life: Mangled network data.
“ERR_CONNECTION_RESET Code: -101”	There are many google hits for this; your solution may vary, so please research this on the web. One user has reported that the problem was caused by an ad blocker.

Messages Mentioning Media

No Media Plugin was found to handle the “text/html” mime type. Media of this type will be unavailable.	http://wiki.phoenixviewer.com/fs_media and/or http://wiki.phoenixviewer.com/antivirus_whitelisting
media_plugin_cef error	http://wiki.phoenixviewer.com/antivirus_whitelisting

Messages Mentioning Regions

Error	Remedy
“Unable to create item that has caused problems on this region.”	1) Have the region restarted; this will usually fix it. 2) If a region restart doesn't clear it up, the sim owner may need to ask LL to move the sim to another server channel.
“We are sorry, Linden Lab has discovered degraded performance on your connection to the region you are on. You will need to restart Second Life and log into a new region for the next 30 minutes to an hour. We apologize for the inconvenience.”	Delete landmarks, especially favorite landmarks. If they point to an invalid location, it can cause this message. This may also mean exactly what it says; follow the instructions.

Messages Mentioning SLVoice, SLPlugin, or LLCefLib

Error	Remedy
“Do you want the application 'SLVoice' to accept incoming network connections?”	Mac – This is a message from your computer's firewall. You should choose “Allow” for voice to work.

Messages Mentioning Teleports or Access to Destinations

Error	Remedy
“Sorry, you do not have access to that teleport destination.”	1) This may mean that you're not on the access list. Talk to the owner. 2) This may mean that the location is temporarily closed to public access. Try later.
“Teleport failed. Failed to grant capabilities.”	This may mean that the region is having temporary problems. Try again later.
“Teleport failed. No valid parcel could be found.”	This may mean the location no longer exists. (There may be other reasons for this message; please let us know if you find one.)

Messages Mentioning Textures

Error	Remedy
“# of textures discarded” message usually followed by a crash	Relog right away to prevent a crash. Then see Textures Discarded for things to do.

Messages Mentioning Video Cards, Drivers, or Hardware

Error	Remedy
“Firestorm is unable to run because your video card drivers did not install properly or are out of date, or are for unsupported hardware. Please make sure you have the latest video card drivers, and even if you do have the latest, try reinstalling them. If you continue to receive this message, contact the Second Life Support Portal”	See Intel Fix 32-Bit

Messages Mentioning Voice

Error	Remedy
“We're having trouble connecting to your voice server”…(server URL)…“Voice communications will not be available. Please check your network and firewall setup.”	This is the usual voice error message. See Voice Troubleshooting

Unclassified Messages

Error	Remedy
“Index out of range: 34 not in [ 0, 11]”	From the login screen, open the Debug Menu - Show Debug Settings - RenderDebugGL. Set to FALSE. Relaunch the viewer and login.
“newview/llappviewer.cpp(1838): Unhandled exception caught in bool” _cded LLAppViewer::frame(void): No diagnostic information available	If the error happens in only one region, clear cache
“Must supply a comment for control content”	The installation is corrupt. Uninstall Firestorm, delete the installer, clear your web browser's cache (or use a different browser) and download a fresh installer from http://www.firestormviewer.org/downloads/ and install that.
“cannot rez here because the owner does not allow it” (exact wording needed)	If you are trying to rez on top of mesh, rez on regular terrain or on a prim instead

Marketplace Messages

Please note that Marketplace has nothing to do with the viewer. These messages are noted simply for convenience.

Error	Significance
“We are unable to process your order at this time. Please try again later. You may add this item to your cart or save as a favorite.”	This message, noted 2019-02-15, means that you have been blocked by the item's seller.

↧

windows_edit_path_environment_variable.png

December 16, 2018, 7:22 am

≫ Next: fs_link_replace_602.png - created

≪ Previous: fs_error_message_list - [Messages Mentioning Media]

↧

fs_link_replace_602.png - created

January 26, 2019, 9:38 pm

≫ Next: fs_link_delete_602.png - created

≪ Previous: windows_edit_path_environment_variable.png

↧

fs_link_delete_602.png - created

January 26, 2019, 9:38 pm

≫ Next: fsg_gateway_team

≪ Previous: fs_link_replace_602.png - created

↧

fsg_gateway_team

March 3, 2019, 10:23 am

≫ Next: fs_611_prerelease - [JIRA New Features]

≪ Previous: fs_link_delete_602.png - created

help, new residents, gateway

Firestorm Gateway Team Members

Management

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

Helpers

Roleplay & SciFi Portal Team

Projects

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

↧

fs_611_prerelease - [JIRA New Features]

March 6, 2019, 7:43 am

≫ Next: avastblockedallowed.png - created

≪ Previous: fsg_gateway_team

Firestorm Beta 6.1.1. Prerelease

Changed Wiki Pages

The pages below have been updated to reflect some of the changes since Firestorm 6.0.2. Please do not bookmark them, as they will disappear once 6.1.1 goes to public release.

Other

Replace Links: Inventory - Replace Links. Added the ability to delete links without replacing. See FIRE-17695

Menus

Firestorm Top (Menu) Bar - Avatar: Avatar Health - Refresh Attachments - Added keyboard shortcut Alt+Shift+R. (See also Advanced Menu) In cases where attachments are “ghosted”, it will attempt to reattach them. Ghosted attachments are those that show attached to you but others don't see them.

RestrainedLove API: RLV v3.2.1 / RLVa v2.2.0

Catznip RLVa 2.2 Release Notes

Other changes and updates

Second Life Release Viewer version 6.1.0.524670
Release Notes for v6.1.0 (524670) - Second Life Viewer Released on February 26, 2019. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/6.1.0.524670

BugSplat viewer

Update changes This viewer introduces a revised updater, replacing the current Viewer Manager Process (VMP). Instead of running the VMP before every viewer session, we now run the updater as a child process of the viewer. Viewer notifications are used to alert the user to a pending update.

This viewer starts more quickly than with the VMP. It displays only one Taskbar or Dock viewer icon. Pinning that icon should behave exactly as expected, going forward.

Pinned icons for the Viewer Launcher and VMP-driven viewer may need to be deleted and recreated.

We still run the updater before _first_ launching a newly-installed Windows viewer, to address the potential problem of installing a 64-bit viewer on a Windows system that does not support it. Similarly, if you install a 32-bit viewer on a Windows system that can support the 64-bit viewer, it retrieves the 64-bit viewer instead.

Bugsplat If this viewer crashes, the crash report is sent to BugSplat rather than to Linden's internal crash reporting system.

(Third party developers: the existing Breakpad crash-reporting code is still present in the code base. BugSplat integration is enabled by a CMake variable.))

FMOD Studio 1.10.11 (updated Windows, Mac, Linux)

KDU v7.10.6 (Windows, Mac, Linux)

Voice Server Version: Vivox Version 4.9.0002.30313 (Mac and Windows)
Voice Opensim 4.6.0017.22050 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

Chromium Embedded Framework (CEF) Dullahan:

Dullahan: 1.1.1080
CEF: 3.3325.1750.gaabe4c4.513446
Chrome: 65.0.3325.146
Page of test URLs for Dullahan. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

JIRA Bug Fixes

FIRE-23012 - Windows 10's UTF8 beta breaks URL parsing
FIRE-23401 - Firestorm locks up Win 7 on login - Malwarebytes
FIRE-23641 - Show parcel name in world map feature fails if the parcel has a null name
FIRE-23663 - crash on using world map, xui file floater_world_map.xml might be corrupt
FIRE-23665 - starlightskin original teal - colors of some UI elements are from original orange
FIRE-23667 - missing 3p package

JIRA Improvements

FIRE-23603 - [LINUX] autobuild line 3666
FIRE-23657 - [OPENSIM] ViewerAsset on OpenSim

JIRA New Features

JIRA Translations

FIRE-23592 - Update Japanese translation

JIRA Tasks

Aditi / Beta Grid

If you haven't logged into the Aditi Grid recently, you will likely need to contact LL Support to gain access as well as have your inventory synced. Please review this page carefully http://wiki.secondlife.com/wiki/Aditi. Also ensure you have this viewer setting enabled in Preferences - Advanced - Allow login to other grids.

↧

avastblockedallowed.png - created

March 9, 2019, 4:44 am

≫ Next: fs_old_version_blocks - [Those Who Cannot Update]

≪ Previous: fs_611_prerelease - [JIRA New Features]

↧

fs_old_version_blocks - [Those Who Cannot Update]

March 10, 2019, 6:17 am

≫ Next: fs_empty_outfit - [3. Clean up some inventory folders]

≪ Previous: avastblockedallowed.png - created

Be sure to back up your settings before upgrading your viewer and before your version is blocked!

Firestorm Blocks

Before folks start screaming, “You don’t care about us!”, please realize it is only because we care that we are developing Firestorm for you, and it is because we care that we are enforcing blocks. It is important for everyone to be on current releases that support the virtual world platform, its features and its capabilities.

Why Block Old Versions?

First, we are under pressure by Linden Lab to do this, and we can either do it ourselves or adopt LL’s update system, which allows them to do it instead. Either we update you or LL does, but either way, folks, updating is quite inevitable. The LL viewer enforces updates, as do most software applications with a fair grace period. Our grace period will leave three versions available: the current version and the two before that.

Second, updating is necessary in order to keep everyone enjoying the same shared experience. Second Life is not immersive if we see things drastically differently from one another. This is going to sound harsh, but in some respects if you are using versions that can only render avatars gray and/or versions without mesh, you might as well be—and perhaps should be—using a text based viewer.

Third, since we are a small team of volunteers, we are limited in our ability to provide support for old versions of the viewer.

Those Who Cannot Update

We recognize there are some users who cannot update to a current version due to their computer systems not being modern enough. For you there are still a few options. In some cases, people who believe they cannot run later versions of Firestorm are actually experiencing a fixable issue with which support can help; see the troubleshooting guide on our wiki. Contrary to popular belief, it only takes a computer around a US$300 value or so to run Firestorm. Firestorm does not require a “gamers” computer. Just something from the last five to six years will usually do. A decent video card will go a long way and often is all that is needed to dramatically improve performance for you.

You can download the latest version from here; there's even a link to currently available older versions: http://www.firestormviewer.org/downloads/

Adapted from this blog post.

↧