> > > Date: Tue, 23 Apr 2002 15:19:12 -0700 > > From: Mark Hood <[EMAIL PROTECTED]> > > > > It could be that the nVidia stereo drivers support stereo by imposing > > restrictions on or reducing the available screen resolution, > color depth, or > > Z buffer depth. > > Following up on myself, I couldn't find any information to this effect on > nVidia's web site. One thing that I noticed, though, is that the > nVidia stereo > support seems to be an *override* mode -- that is, it coerces a > stereo image > out of an application or game that isn't designed to output stereo images.
Thanks for clarifying that. I /thought/ I had read that it supported the OpenGL stereo extension, but I probably got my self confused with something else (like the Elsa driver). That being said, I decided to upgrade to JDK 1.4 and J3D 1.3 Beta 1 (OpenGL) and give the Full-Screen Exclusive mode approach a try to see if the nVidia driver would kick into stereo mode. Basically, try to determine if the Canvas3D was the only thing in the Window set to full screen mode, then the nVidia driver would think it was a full screen OpenGL window, thereby kicking the nVidia driver into stereo mode. Well, when I turn on stereo mode in the driver and run my app, the JVM dies when I query the Canvas3D properties, before even showing anything on the screen. The JVM dump is attached, which may be of interest since the JVM is croaking in Canvas3D.createQueryContext(). Turning off stereo mode in the driver and the app runs fine. I'm going to back out the beta install and go back to 1.2 and see what happens. BTW, antialiased lines don't seem to be working with 1.3 beta in my app. Anything different there? Thanks, Simeon
hs_err_pid2004.log
Description: Binary data
