Other suggestions below.

1. Open Default Programs by clicking the Start button and then clicking Default Programs.
2. Click Associate a file type or protocol with a program.
3. Click the file type or protocol that you want the program to act as the default for.
4. Click Change program.

In Firefox, goto Tools → Options → Applications Tab and scroll to Secondlife. Look to see if Firestorm is listed, if not, select “other”, then browse your hard drive to find the Firestorm.exe, click on it, select Open, then click Ok. (Reference: Applications panel—Set how Firefox handles different types of files.)

OR

Download and install the regular SL viewer - but don't run it.

OR

Try this if the above does not work:
http://www.linuxforums.org/forum/gaming-games-multimedia-entertainment/104105-how-firefox-calls-secondlife-slurls.html

Download and install the regular SL viewer - but don't run it.

If none of the above works, then try this as a last resort fix. Go into Chrome settings, the advanced Settings, at the bottom, then Reset Chrome. Please note that this will wipe all your customized Chrome settings.

The application that handles a URL is a system-wide setting, not tied to any one browser. You can change the setting like this:

• Download RCDefaultApp 2.1 from the RubiCode download page. Yes, it really will run on current versions of OS X, even though it also runs all the way back to 10.2.
• Install it according to the instructions int he README file.
• Go to the Apple menu at the top left. Select System Preferences… then Default Apps (near the bottom), then the URLs tab. Now scroll down until you see secondlife in the list on the left. Click on it.
• Now select the application you wish to use.

• Open Firefox and in the address bar type in “about:config”
• Now right click anywhere on that page and choose New and then Boolean to create a new Boolean entry, when prompted for the name of the entry enter “network.protocol-handler.expose.secondlife” (without quotes) then set the entry to 'false', click ok and your just about done.
• Now the next time you click a slurl you will be prompted to choose an application to open it with, just browse to the folder you installed Firestorm into and select the file named 'firestorm' (a shell script file). Then before you click Ok, make sure you check the little box to make Firefox remember your choice on how to open slurls. ¹⁾

Information gleaned from this page.

There is an alternative to clicking a link in a browser to have it pass control to the viewer. Some actually find this work around to be faster and use it normally:

• right click the SLURL link in your web browser and copy to clipboard
• in the viewer, paste the link into your local chat and hit Enter.
• open local chat history
• click the link shown there; you will be shown the location info with the option to teleport direct to it.

The fist thing to check is the viewer settings: Preferences → Network & Files → Connections, in the Web Browser section, make sure Use My Browser… is selected.

If you get an error saying that no program is associated with the action, or that it doesn't know how to hand that action, make sure your computer settings show that there is a default web browser. An easy way to tell is to open your browser; if you are asked to make it the default, then you need to do so.

To use the Restrained Love features built in to Firestorm you need to follow a few simple steps:

• Press CTRL-P to open the Preferences panel
• Go to Firestorm
• Move on to Extras
• Check on “Allow Remote Scripted Viewer Controls (RLVa)”
• Go to User Interface
• Move on to Interface Windows
• Uncheck“Hide empty system folders from inventory”
• Confirm your changes by clicking Ok in the right corner

After this you have to restart Firestorm to get RLVa working. Additionally you usually need to get a so-called Relay. This is an attachment you wear that enables objects in-world to interact with your viewer. These Relays are usually free of charge and come as HUDs or pieces of jewelry you wear. It's recommended to get a “Multi Relay”, so you can be controlled by more than one device at the same time.

If you also want to enable traps and toys to put folders into your inventory, you need go through a few additional steps:

• Click on the RLVa menu
• UncheckForbid Give to #RLV
• Open your Inventory (CTRL-I)
• Right click on My Inventory
• Select New Folder
• Rename the new folder to #RLV (be sure to use uppercase letters, exactly as shown here)

Now you should be able to accept inventory from traps and toys, which will automatically be moved into the #RLV folder tree.

Users of RLV enabled viewers often run into the problem that devices can take off certain attachments or clothing layers, destroying the look of their avatar. For example, RLV devices that offer shoes to be taken off also detach left and right foot attachments. For certain avatar types that use prim attachments for their feet, this destroys the overall look. You can fix this issue by using locking scripts that prevent the respective attachment from being taken off, but this has a couple of disadvantages:

# It uses additional scripts # You can't detach or take off these prims and clothing layers without unlocking them first

The solution is using the (nostrip) tag. Adding this tag to the nam of an item or a folder instructs the RLV system to ignore these items when a detach or remove clothes command is sent. For this to work you must have the items in your #RLV folder tree. Together with the leading period “.” this can be used to make avatar folders that contain the bare minimum necessary to make up your look. The “.” makes sure this folder will not show up in a device's shared outfit list.

To prevent a single item from being taken off by RLV devices, simply add the tag (nostrip) to the name, separated by a blank space:

Female Hair

will become

Female Hair (nostrip)

If the item is no modify you can put it into a folder by itself and add the (nostrip) tag to the folder.

To have your complete avatar safe from RLV devices, you can make a folder for it and add all parts of your avatar that are essential for its look. Then give it a name that has a “.” as first character (to hide it from RLV shared outfit devices) contains the (nostrip) tag at the end:

.Female Fox Avatar (nostrip)

This will make sure that no important parts of your avatar will be taken off, all other parts still can be removed as usual.

• Marine Kelley's Object Sharing Tutorial

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

• Your ISP is throttling or blocking the voice service;
• failure of the Vivox service;
• voice issues on the region you are on;
• voice being throttled by bandwidth set incorrectly - please check it by following the instructions here;
• voice hardware (mic, headset) not configured correctly in your operating system settings;
• voice hardware not configured correctly in the viewer;
• another application has your voice hardware in use (example, Skype);
• your anti virus software has “mangled” the voice application; see steps on this page: here.
• your firewall is blocking slvoice. Add slvoice to your firewall's exclusion/allow list.

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

Steps:

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

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

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

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

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

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

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

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

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

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

You can also try adjusting your bandwidth as explained here.

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

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

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

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

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

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

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

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

• Try a relog, or even a reboot of the computer.

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

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

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

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

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

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

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

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

Some have issues with voice on Firestorm - specifically, “stuttering”, or SLVoice crashing when you unplug a USB device. The only work-around currently is to swap out the voice files.

• To this end, download this file; save it to your hard drive. Make sure you do not have Firestorm running. Then extract the files to your Firestorm install folder. (For Firestorm 32-bit viewer, this is typically located at C:\Program Files\Firestorm on 32 bit Windows, and C:\Program Files (x86)\Firestorm on Windows 64-bit. For Firestorm 64-bit Viewer, this is typically located at C:\Program Files\Firestorm.) When prompted, allow the replacement of existing files.

Try disabling compatibility mode, if enabled:

• Locate your desktop shortcut for Firestorm (if you use the pinned application on the task bar, make sure you pin the Firestorm shortcut, not the running viewer)
• Right click on the icon and select Properties
• Select the Compatibility tab
• Find “Run this program in compatibility mode for:” if it is set then disable this
• Make sure “Run as Administrator” is enabled (if this is greyed out, then you're probably already running as administrator, so you can ignore this step).
• Click Apply.
• Now log back into the viewer, and see if voice works (do you have the white dot over your head?). If not, go to Preferences→ Sound & Media -> Voice and disable voice; wait a few moments, then re-enable. ¹⁾

On Windows 7, if you find yourself being able to talk but not hear what others say, then a possible solution is to use the sound drivers from Vista. (This needs further confirmation.)

Every linux distro is different; and each distro may have more than one window manager to further complicate things. So tips can't be “absolute”; you will need to experiment and see what works for you. The following have been suggested by some as effective. But first….

In the Firestorm install directory, there's a text file (originally from LL) with tips on getting voice to work in linux. If you haven't read that, then you can try to see if it helps.

• Make sure you have ALSA and/or FMODEX available. FMODEX is supplied with Firestorm, normally. If you look at Help → About Firestorm, you should see a line that resembles this:
  Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.11.753 / OpenAL Community / OpenAL Soft: PulseAudio Software
  If that says “none” then you have no audio driver available to Firestorm and need to install one.

• Edit the firestorm shell script and remove the #. That will force LL to use FMOD rather than ALSA. Some say this is how to get voice working.

#export LL_BAD_OPENAL_DRIVER=x

• Some swear that the problem is PulseAudio, so you can try to remove that from your system. Be warned, however, that this could cause more problems than it solves. Make sure you remove only Pulse and not half the OS.
• Be sure to have the correct devices select in Firestorm for voice:
  
  Preferences → Sound & Media → Voice → Audio Device Settings (button) … input and output may not work if left at default; they may need to go to a specific device like “ALSA Capture on [device name]”.

Below are results for selected linux distros, based on input from Phoenix and Firestorm users. This will be updated as more information becomes available.

• ubuntu 16.04 64 bit + FS64: The following command installs a few 32-bit libs and voice works after. Maybe you need fewer 32-bit libs but that needs further investigation.
  Apparently, arch requires these as well - or some of them - though the exact lib name may be different.

sudo apt-get install gstreamer0.10-pulseaudio:i386 libidn11:i386 libuuid1:i386 libstdc++6:i386

• A new option is a debug setting, FSLinuxEnableWin32VoiceProxy, which when enabled will cause Firestorm to launch the Windows version of SLVoice.exe via WINE. To use this, you need to ensure that WINE is installed; install WINE with your package manager. An existing WINE profile/prefix is not needed, but will be used if present. Depending on your system, it may take several seconds before voice comes up.
  NOTES:
  * If you disable voice and then re-enable too quickly, WINE may not successfully restart and voice may fail to re-enable. If you get the warning that there was a problem connecting, you will need to relog before voice will re-enable. Thirty seconds between disable and enable should be enough.
  * There is a known related issue here
  * To speed up the initial loading of voice, use

  wine-preloader $HOME/path/to/firestorm/bin/win32/SLVoice.exe

  before launching Firestorm

If you are unable to connect to voice and you are also having problems with teleporting and/or loading your friends list, perhaps along with other things, then see the “Mac-specific” section of this page for instructions and more explanation.

Some Mountain Lion users experience a problem with voice output, while input works fine (that is, you can hear but you can't speak). To fix this, open the voice preferences for your viewer (Preferences→ Sound & Media -> Voice in Firestorm). Click the device settings button and select “built-in microph” as the audio input device and click OK. Reopen Preferences and go back to the device settings button to ensure you're getting sound in on the mic.

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:

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

Note: This is not the same as rainbow colors in-world.

If you see rainbow colors after logout and you have MSI True Color or f.lux installed on your system, do the following steps in order:

1. Uninstall MSI True Color if installed.
2. Install f.lux from https://justgetflux.com/ if not installed.
3. Uninstall f.lux using the f.lux uninstaller, not the Windows uninstaller from Windows programs & features / add/remove programs.
4. When running the uninstaller it will give you the option to reset to the windows default color profile; say Yes. (Running this uninstaller is the only way we have found to get rid of the MSI True Color profile.)

Refer to http://jira.phoenixviewer.com/browse/FIRE-12561. Also see the alternate workaround at the comment dated 13/Apr/17

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.

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.

This is a known issue with Windows 7, 64-bit Operating System and affects other programs in addition to Second Life viewers. And it may happen on Windows 8.1 and Windows 10.

Please try the following - but NOT while logged in.

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

• Right click the task bar and choose Task Manager. Alternatively, click the Start button and type Task Manager, then click on the result. Option 3, press Ctrl+Alt+Del and choose Task Manager from the list.
• 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).

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

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

For additional suggestions, see the page on Severe Lag.

Possible reasons why HUDs may stop working:

• Disconnected during a teleport after restarting a region. See BUG-5034.

• Script (running) state is lost when logged out during forced teleport. See BUG-41379.

• There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.

Below are things you can try to get the items working again.

First of all:

• Go to Top Menu → Avatar → Avatar Health → Refresh Attachments. See if that fixes the items.
• Relog then test the items again. That may be enough. If not, read on.

Things to try:

• Check for location issues:
  • Make sure you are in a region that has scripts enabled.
  • Go to other regions and test the items there. This will rule out technical problems with the original region.
  • If you have RLV enabled, disable it (Preferences → Firestorm, top option), relog, then try again.

Stay in a script-enabled region to do all of the following:

• Attempt to get scripts running:
  • Try removing and reattaching the items.
  • If the items are modifiable, try resetting them or setting their scripts to running: Inventory, right-click the item → Edit, and while it is in Edit, go to Build menu → Scripts → Reset Scripts, or Build menu → Scripts→ Set Scripts to Running).

• Identify broken items:
  • Try removing all the HUDs and other attachments and testing them one at a time: test each one, then remove it, then test another.
  • If you have original copies of the items, try detaching the ones you are currently wearing and using a fresh copy from the original.
  • If an item is no-mod and you can't get it to start running again, and you don't have another copy, you will need to request a new copy from the creator.
  • Note: If the non-working HUDs are for your mesh body parts (or other scripted attachments), you probably will need to use fresh copies of the original HUDS and the body parts – every part, from scratch (not copies of the broken ones).

• Check for interference:
  • Look in Inventory > Current Outfit folder, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached.¹⁾
  • Check that HUDs are not overlapping each other on the screen (and so preventing you from clicking).

• Check for issues with attachment points:
  • If any HUDs are sharing the same HUD attachment point, try moving them to separate HUD attachment points:
    Inventory → Right-click → Detach from Yourself, then Inventory → Right-click → Attach to HUD, and choose an unused point.
  • Even if they are not sharing attachment points, try moving them to different attachment points.

• Test basic functionality:
  1. Rez a fresh cube
  2. Add the default script to it
  3. Take it into inventory
  4. Attach it to a HUD point
  5. Touch the HUD and see if there is script output in Local chat.

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, http://maps.secondlife.com/secondlife/Firestorm%20Ghost%20Town/24/11/4000
• JU: Junkyard University, http://maps.secondlife.com/secondlife/Junkyard%20Blues%20South/112/204/22

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

*All times SLT*

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

A HUD's orientation data (position and rotation) data is stored with the HUD when it's detached. It is relative to the attach point, not to the viewer. (Any attached object has its orientation data saved when it's detached)

Possible reasons why HUDs may stop working:

• Disconnected during a teleport after restarting a region. See BUG-5034.

• Script (running) state is lost when logged out during forced teleport. See BUG-41379.

• There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.

Note: While this issue most commonly affects HUDs, it can also affect any and all other scripted attachments you were wearing when the breakage happened.

There are a few things you can try to get the items working again.

It is possible to make an object or avatar “invisible” - for you only. It is useful in many situations, such as photography, for example, if an object is in your view and you do not wish it in the picture.

NOTE: There is a tutorial video on this topic here.

This is permanent derender; it will survive teleports and relogging. For more information, see the Asset Blacklist.

• To derender an object: Right click it and select Derender → Blacklist from the menu.
• To rerender an object:
  • From the top menu bar, select World → Asset Blacklist. Find the item you wish to remove, click it to highlight it, then click the Remove selected items from blacklist button.
  • You will then need to force a view refresh: TP out and back OR relog. Changing your active group may also work.

Temporary derendering will last until a view change is forced in some way.

• To derender an object: Right click it and select Derender → Temporary from the menu.
• To rerender an object: Simply teleport out of the region, wait a minute or two for your viewer's memory to clear, and then tp back; or relog. Changing your active group may also work.

Note that in Preferences→ Move & View -> View, there is Re-render temporary derendered objects after teleport, which controls whether temporarily derendered obejcts will re-render after TP or not until after a relog.

Attachments get new UUIDs every time they are reattached; therefore, derendering an attachment will only be effective until the wearer detaches the item.

For up to date information on how to manage your SL Marketplace listings, it is best to consult SL documentation directly.

• Managing your Marketplace store
• Linden Lab Official:Viewer-Managed Marketplace FAQ

Phishing is not new in Second Life. One case results in people seeing a message appear on their screens, repeatedly, saying that their account has been compromised, and that they should call a certain phone number.

Under no circumstances should you call that number!

LL have done a blog post about this. Beyond what they say, we would like to offer the following advice.

1) Identify the object and/or avatar sending the message:

• Click the text at the start of the message, before the “:'”. Note that this text may consist of a single punctuation mark or even just a space, so it may be hard to see.
• Should there be no name at all, then go to Preferences → Chat → Visuals, and enable Mark objects with (no name) when they speak to avoid spoofing.
• You should now see (no name) in front of the spam message, so click that for information.
• Now you can use this information in the following steps.

2) File an abuse report with SL. This excellent blog post gives information on how to do that in the most effective way. File it under fraud. If at all possible, include the exact coordinates of the object.

3) Block the object and/or owner. You may then return to enjoying to Second Life.

4) For added mental peace, you may wish to change your Second Life password on the SL website.

So you have the latest viewer and still can't see mesh - what's the deal?

Well, it isn't necessarily automatic. Depending on your specific hardware, certain settings that need to be enabled for mesh, may be set off by default.

Go to Preferences→ Graphics -> General; then enable Basic Shaders.

If this remains greyed out, then increase the level of Render Quality until Basic Shaders becomes enabled and can be checked.

Make sure you have a reasonable draw distance. If you have difficulty rendering mesh, lower it; if your draw distance is over 128, set it to 128, or less. (The optimal value for draw distance is entirely dependent on your own hardware; you will need to experiment to find what works best for you.)

In some cases, worn mesh attachments will not render properly still. Go to Preferences→ Graphics -> Rendering and disable both of the Alpha Mask Rendering options.

There are also rare instances of glitches where mesh that you are wearing appears worn by another avatar (yes, it is bizarre!). In that case, try going to Preferences → Graphics → General, and enable Hardware Skinning.

In some cases, low-end graphics cards or very old graphics drivers may require you to turn hardware skinning off rather than on. Before doing this, please try updating your graphics drivers and review the other options on this page, as turning hardware skinning off may reduce your performance.

If you have Webroot SecureAnywhere Antivirus, see Webroot Issues. For other antivirus apps, see our Whitelisting Guide, and be sure to whitelist all parts of the viewer. This may need to be done from scratch each time you upgrade to a new version.

If mesh is simply slow to appear, but does appear eventually, that is not necessarily a problem with mesh itself; please work through this page: Slow Rezzing.

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.

If none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, type in Mesh2MaxConcurrentRequests and gradually decrease (not increase) the value. (If Advanced is not visible on the top menu bar, press Ctrl-Alt-D.) If it does not help, try increasing the value from the default. Under no circumstances should you increase this beyond 64. Please see this comment on a related JIRA ticket for an explanation of the possible drawbacks of increasing this setting. Additionally, we recommend returning it to default once the mesh you're trying to see is visible.

In most cases, this is due to the mesh item being made low LOD so as to reduce its land impact. You should never try to resolve this by increasing LOD above the maximum allowed in Preferences → Graphics → General (4), as that would result in greatly increased memory uses usually leading to a significantly increased rate of crashing. Rather, the issue is inherent in how the mesh item was made. So you either live with it, or replace the item.

This happens more frequently for those using ATI/AMD graphics and drivers, but has been seen occasionally with Nvidia graphics and drivers as well. Visit Graphics Glitches for ways to address this.

If you can see most mesh fine but a specific mesh item fails to render and/or displays a pyramid, triangle, or ducky when it's first worn or rezzed, then read on. This is caused by mesh that fails to load, and in many cases is a result of having too high a draw distance in the presence of a lot of complex mesh.

• Reduce draw distance significantly, then relog. That often clears the problem.
• If that doesn't help, reboot all your network hardware and then your computer.
• (If the problem occurs only on selected regions, it could simply be a symptom of region lag–see http://wiki.phoenixviewer.com/lag for information. In this case, there may be nothing you can do about it.)
• If this still doesn't help, then:

• Make sure you have hidden folders shown; see here. Then browse to:

• On Windows Vista, 7, 8 and 10: C:\Users[USERNAME]\AppData\Roaming\Firestorm or
  C:\Users\[USERNAME]\AppData\Roaming\Firestorm_x64
  (or use the environment variable %APPDATA% then drill down to the folder noted)
• On a Mac: /Users/[YOUR USERNAME]/Library/Application Support/Firestorm
• On Linux: ~/.firestorm
• In this Firestorm folder, open the folder that has the name of your affected account, e.g. whirly_fizzle
• Delete the files named texture_list_last.xml and texture_list_home.xml
• Login and see if the troublesome meshes then load.

• Back up your settings - see http://wiki.phoenixviewer.com/backup_settings
• Wipe your settings manually, as explained in http://wiki.phoenixviewer.com/fs_clearing_settings
• Log back in and see if the mesh renders correctly. If it does…
• Restore your settings (see the backup page above), then check the mesh again.

In Preferences → Graphics → General, make sure Basic Shaders and Hardware Skinning are enabled.

If certain mesh objects are invisible on Firestorm 5.0.11 on OpenSim grids, set the debug setting FSEnforceStrictObjectCheck to False. To change that setting, go to top menu, Advanced (Ctrl-Alt-D to enable Advanced, if it isn't), Show Debug Settings. Type in FSEnforceStrictObjectCheck, set to False, then close the DebugSettings window.
On OpenSim grids, mesh should never be uploaded using “Analyze”. Analyze should only be used on grids that support Havok.
On Firestorm 5.0.11, mesh uploaded with Analyze is likely to render invisible when FSEnforceStrictObjectCheck is set to true.
An in-depth discussion about this problem can be found here.