User Tools

Site Tools


Mesh Issues


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

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.

Some Mesh items Vanish if I Cam Out

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.

Spikes Going Off to "Infinity"

If you are using a fitted mesh capable version of Firestorm (4.6.1. or later) and using ATI/AMD graphics and drivers, certain non-rigged mesh items may display as a long stretch which points to the region coordinates 0,0,0. If you observe such long spikes, then try:

  • Ideally, you should update (or downgrade) to Catalyst Drivers Version 14.4 - or better yet, one of the latest 15.x drivers, if they are available for your graphics card. We've had reports these drivers fix the bug. Visit this page more on this.
  • Otherwise, go to Preferences - Graphics - General subtab - disable Hardware Skinning. This may result in a loss of FPS. Turn on the Statistics Panel using Ctrl Shift 1, disable Hardware Skinning and monitor your FPS. As this bug affects some non-rigged mesh items, and not all, you may determine that disabling Hardware Skinning is not worth the loss of FPS.

Pyramids / Ducks

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 for information. In this case, there may be nothing you can do about it.)
  • If this still doesn't help, then:

Method 1

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

Method 2

Crashing While Editing/Wearing Mesh

This appears to be specific to those with ATI/AMD graphics cards. Refer to this.

Worn Rigged Mesh Goes Invisible

This issue is specific to those using ATI/AMD graphics cards. Please refer to this.

Mesh Appears Splotchy, Blotchy, or Has Strange Patches of White or Colors

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

mesh_issues.txt · Last modified: 2017/09/28 09:05 by miro.collas