Strange black prims no matter what viewer is used... help?

[Hitokage Indigo]

A friend of mine is trying to log into SL, he has tried numerous different viewers, and we have tried a bunch of settings changes.... but every time he logs in, he gets either an entirely pink world, or these weird black lines (prims?) slashing across his av and everyone else's.  Here's a screenshot:

https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-ash4/s720x720/421952_140520396071139_100003395391803_165768_516912179_n.jpg

He is working on a brand new laptop so even though it looks video-card related, it shouldn't be.  Not to mention that his card is not on the 'incompatible' list.

What is this weird effect and how can we get rid of it?

Thanks.

 

 

[Rolig Loon]

At the risk of repeating myself yet again (and again and again).....  You are not the only one.  Look down the list of questions before yours and you'll see several others for the past two weeks.  In fact, it's almost always a good idea to try searching first before you post a question that someone else has probably asked.

Some people who have ATI graphics cards are having the pink problem with the most recent V3 upgrade. It affects any of the newer viewers.  See http://jira.phoenixviewer.com/browse/FIRE-4945 .   For a quick but temporary solution, go to Preferences >> Graphics and disable Basic Shaders.  For a more permanent solution update the 12.1 Catalyst driver from http://support.amd.com/us/gpudownload/windows/Pages/radeonmob_win7-64.aspx?type=2.4.2&product=2.4.2....  or run the AMD driver autodetect tool to update: http://support.amd.com/us/gpudownload/windows/Pages/auto_detect.aspx. Updating your drivers will probably also clear up the funky black lines.  If not, go to Preferences >> Graphics >> Hardware Settings and disable OpenGL VertexBuffer Objects (VBO)

[Cinnamon Lohner]

Just because the laptop is new doesn't mean its loaded with the latest graphics drivers.  Don't know about your black lines, but the pink problem has been widely covered here in the forums since early February.  The problem is an ATI graphics driver bug in older drivers and the solution is to update the ATI drivers to latest version.  There are also some workarounds posted in the numerous threads on this issue, but the ultimate solution is updating the drivers.

--Cinn