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.
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, catalyst 14.9.2 Beta is known to cause this problem. Refer to FIRE-14871.
The same issue is known to happen with Catalyst 14.12, as documented here, where it is also evident that the same problem occurs with the official SL viewer.
The best thing is to uninstall the graphics card driver you have, and install 14.4 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.
Please refer to this page for more on that issue.
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:
|12.11 beta with .NET||Windows Graphics Driver Version: 8.17.0010.1169||OpenGL Version: 4.2.11995 Compatibility Profile Context|
|13.1||Windows Graphics Driver Version: 8.17.0010.1172||OpenGL Version: 4.2.12002 Compatibility Profile Context 188.8.131.52|
|13.2 beta||Windows Graphics Driver Version: 8.17.0010.1191||OpenGL Version: 4.2.12171 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.5 beta2||Windows Graphics Driver Version: 8.17.0010.1191||OpenGL Version: 4.2.12198 Compatibility Profile Context 22.214.171.124|
|13.6 beta||Windows Graphics Driver Version: 8.17.0010.1211||OpenGL Version: 4.2.12337 Compatibility Profile Context 126.96.36.199|
|13.6 beta2||Windows Graphics Driver Version: 8.17.0010.1211||OpenGL Version: 4.2.12337 Compatibility Profile Context 188.8.131.52|
|13.8 beta||Windows Graphics Driver Version: 8.17.0010.1234||OpenGL Version: 4.2.12438 Compatibility Profile Context 184.108.40.206|
|13.9||Windows Graphics Driver Version: 8.17.0010.1230||OpenGL Version: 4.2.12422 Compatibility Profile Context 220.127.116.11|
|unknown||Windows Graphics Driver Version: 8.17.0010.1247||OpenGL Version: 4.2.12618 Compatibility Profile Context 18.104.22.168|
|14.3 beta version 1.0||Windows Graphics Driver Version: 8.17.0010.1267||OpenGL Version: 4.2.12798 Compatibility Profile Context 13.350.1005.0|
|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 22.214.171.124|
|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.9.1 beta||Windows Graphics Driver Version: 8.17.0010.1315||OpenGL Version: 4.2.13084 Compatibility Profile Context 14.301.1004.0|
|14.9.2 beta||Windows Graphics Driver Version: 8.17.0010.1315||OpenGL Version: 4.2.13085 Compatibility Profile Context 14.301.1006.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|
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. So we recommend trying to use that version of the driver driver, if possible - which may imply rolling back your current one to that version.
Rather than relying on the built-in driver update function, visit the AMD site directly and update from there; click here to locate the drivers for your system. Do not use the autodetect feature; instead, scroll down to “Manually Select Your Driver” and supply the required information. Then once the results are displayed, click on Previous Drivers and Software and locate 14.4.
If 14.4 is a downgrade for you, please make very sure that you remove whatever driver you currently have installed before installing 14.4
Should 14.4 not be available for your graphics card, then perhaps try the work-arounds suggested above for your specific problem.
Another thing to try is to create a profile for the viewer you use, and then disable OpenGL Tripple Buffering.