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).
Furthermore, other types of graphics cards also require that the first step here be done; VBO is known to cause crashes in multiple different scenarios. So one thing to try:
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 by following the instructions here.
If you are seeing everything pink, the issue is the graphics card driver. The best solution is to update the Catalyst driver (which may imply reverting to an older version than you currently have); links are provided in the section "Known Good ATI Driver", below.
If for any reason, this is not an option:
If rigged mesh goes invisible when worn the issue is, again, the graphics card driver. In this case, several Catalyst drivers are known to cause this problem. Refer to FIRE-14871 and here, where it is also evident that the same problem occurs with the official SL viewer. 1)
The best thing is to uninstall the graphics card driver you have, and install 14.4, or the latest 15.x driver instead. More on this below.
Here are some work-arounds to solve the problem:
Windows: Updating the graphics card driver (which may imply reverting to an older version than you currently have) is likely a preferable solution; links are provided in the section "Known Good ATI Driver", below.
Mac: The issue has only been seen on Snow Leopard (OSX 10.6.8) so far. Since drivers are tied into the operating system on Macs, you would need to upgrade to Mountain Lion (OSX 10.8.3) for a permanent solution at this time. If that is not an option for you, then use the workarounds above.
This is a known issue with ATI Catalyst versions 12.2 through 12.4. If you have one of these versions, then you should update the graphics card driver; see below for more.
See below for how to update Catalyst, the graphics card driver.
Some have reported all manner of graphics glitches, including:
These can often be solved by updating the ATI driver; see below.
These issues have been reported with Catalyst versions 12.11 and 13.01. See if any of the following suggestions are helpful:
Updating the driver is a preferable solution; see below.
Windows 8.1 may install its own driver for ATI/AMD graphics cards. This does not work well with Firestorm. You will need to remove the Windows driver, then install the appropriate driver from the ATI/AMD website.
Another good reference is the table on this page. However, sadly, AMD have not kept it up to date. The drivers missing are:
|13.1||Windows Graphics Driver Version: 8.17.0010.1172||OpenGL Version: 4.2.12002 Compatibility Profile Context 184.108.40.206|
|13.4||Windows Graphics Driver Version: 8.17.0010.1191||OpenGL Version: 4.2.12217 Compatibility Profile Context 220.127.116.11|
|13.5||Windows Graphics Driver Version: 8.17.0010.1191||OpenGL Version: 4.2.12198 Compatibility Profile Context 18.104.22.168|
|13.9||Windows Graphics Driver Version: 8.17.0010.1230||OpenGL Version: 4.2.12422 Compatibility Profile Context 22.214.171.124|
|14.3||Windows Graphics Driver Version: 8.17.0010.1267||OpenGL Version: 4.2.12812 Compatibility Profile Context 13.352.1008.0|
|14.4||Windows Graphics Driver Version: 8.17.0010.1280||OpenGL Version: 4.2.12874 Compatibility Profile Context 126.96.36.199|
|14.7||Windows Graphics Driver Version: 8.17.0010.1299||OpenGL Version: 4.2.12967 Compatibility Profile Context 14.200.1004.0|
|14.9||Windows Graphics Driver Version: 8.17.0010.1315||OpenGL Version: 4.2.13084 Compatibility Profile Context 14.301.1004.0|
|14.11.1||Windows Graphics Driver Version: 8.17.0010.1315||OpenGL Version: 4.2.13092 Compatibility Profile Context 14.301.0.0|
|14.11.2||Windows Graphics Driver Version: 8.17.0010.1315||OpenGL Version: 4.2.13092 Compatibility Profile Context 14.301.0.0|
|14.12||Windows Graphics Driver Version: 8.17.0010.1333||OpenGL Version: 4.2.13283 Compatibility Profile Context 14.501.1003.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 2)||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|
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.x drivers have been solving the “invisible rigged mesh” bugs which have been a major problem for many.
If Catalyst 15.x is not available for your card, Catalyst 14.4 is believed to be a good driver version to use; it seems to fix all (or most) of the problems described on this page. This may imply rolling back your current driver to that version.
For a more detailed walk-through, have a look at this blog post.