SL Crashes with nVIDIA Stereo driver

Hi,

I don't know if this problem is already known. If it is, then please apologize.

I tried to run SL with the nVIDIA stereo drivers for stereoscopic display enabled, but as soon as the login screen closes and the world should be displayed, SL instantly crashes and leaves me with a totally damaged nVIDIA driver and a flickering, corrupted screen, requiring a reboot to continue.

SL so far is the only program I came across which is that incompatible with the stereoscopic driver. Are there any chances to get this fixed ? Having SL in real 3D would really be nice (No, the stereoscopic SL viewer from umich is not an option, since this one only works with a geowall setup, not with shutter glasses).

w/ kind regards,
KA

I'm thinking I read somewhere that there is indeed a problem with that setup.. You might search the knowledge base and see if there is any fixes for that..

Hi,
except that the problem seems to be well known quite a long time, I could'n find anything - at least no solution. Given the fact that it is known that long and no fix has been made I guess the lindens have no intention to anything about it

I even tried to downgrade the driver. I enshured to use matching versions of the stereo an the graphics driver, but all that happened was that I totally messed up the system and then all 3D applications crashed, not just SL. So I did a roll-back, reinstalled the lated gfx driver and the most recent stereo driver, and everything again is like before: all 3D apps run fine in stereo mode - except SL, wich is the only one that ramms itself into the ground

I actually got SL to work ONCE in stereo 3-d after a reinstall using the 91.31 drivers a couple months ago. I had stereo going for approximately 10 minutes until I teleported and crashed with the same memory error I always get. I had most every fancy graphic setting turned off. I couldn't even tell you how I did it as it was more or less an accidental thing.

Filed as VWR-1343. We'll see if they'll fix it someday.

https://jira.secondlife.com/browse/VWR-1343

yep checked some time ago sl just don't like the stereo driver

Oh, they now at least noticed the bug and also promptly suggested a workaround: "Don't use the stereo driver." !

Indeed there even is a second workaround they forgot to mention: don't use SecondLife !

Actually there is an answer. Disable the ALL SL's the menus and stereoscopic 3D will work.

First make sure you have 3D enabled by a hotkey (bind it to something other than default as it interfers with a hotkey in SL). Log into SL and use CRTL + ALT +1 to turn off the hud/menus. Now enable stereo 3D with your hotkey and it should work. You can teleport and move around as you normally would. If you want to chat you'll have to turn off stereo 3D and enable the menus/hud again with the above hotkeys.

Remember this won't work with any 8000 series cards as there aren't really any S-3D drivers out for these cards.

Thanks for this hint. Unfortunately, this also didn't work. It didn't instantly crash, so I at least had the chance to get a glimpse of SL in read 3D. Nevertheless, after a few seconds it crashed.

The avatar and the world seem to be two completely independent things in SL, which are just composed over each other. The world looks fine in 3D, but the avatar appears to be stuck in the ground up to the hips. The prim hair disappears from the head and instead appears left or right beside it. I cannot move, since the ava does not respond in any way.

Seems to be a serious and complicated thing, thus they don't even try to fix it.

Kyra, what video card and drivers are you using? Just curious as I know of a few people with 6800's and another with a 7900 card that have it working. Did you get the typical memory write error when you crashed?

What is thiss proceedure for enabling 3d in these games, and what means do they operate red/blue, shutter, crosseyed?
Any one know?

Zen, In the classic (not the new type) Nvidia control panel you can set a hotkey for enabling and disabling S-3D. I only use shutter glasses but since there's a drop down menu for different types of S-3D (red/blue and so forth) you should be able to set a hotkey for the different types.

thanks, i figured it out and DLed the stereo drivers and caught the classic vrs starndard that you mentioned, it works great with my desktop 7600 machine but not anything yet with the 6150 laptop

My hardware is a XFX 7900GT w/ 256MB, running on a Core2Duo T7200 mainboard with 3.2GB RAM.

I cannot say what kind of error I get. SL makes a instant crash report, but I don't get a error message from windows stating the reason for the crash.

The stereo drivers are a hack, I know, since there is no generic real 3D support in OpenGL (and probably also not in DirectX). The most straight-forward way would be to actually add real stereoscopic support (i.e. quad buffering). I even tried to download the source and patch it myself, but so far I could not find the innermost rendering loop yet that could be encapsulated into a double rendering loop for stereoscopic display.

Kyra, have you tried disabling one of your cores in msconfig and rebooting with only one core. That fixes a lot of crashes in S-3D with dual cores with either AMD or Intel. You probably already know this but if it helps your or anyone else...

Click start, run, type in msconfig, click ok, click boot.ini, advanced options, then check numproc and then change it to 1, click ok and reboot. You'll get a box saying msconfig changed blah blah .. You can always go in and change it back to what it was if it doesn't work.

I hope it helps!

I dont know what I have but I lag alot then I crash. It is pissing me off. I was gone for a year or so because of this problem. I come back and it still does it? WTF!? Back to WoW I go. Stupid SL

This I have not done, but I pinned SL to one core using the 'cpu affinity' option in the taskmanager. However, this did nothing to solve the problem with SL, but I got 'Pangea Trees' working in stereoscopic mode this way.

Hi,

finally a statement from LL (quoted from JIRA):

translation: ... we are unable to fix this bug, so we declare it as non-existant ...

I've got no words for this.
I'm sorry, but I must say, eventually I've lost the interest in SL.