> From the nVidia web site, it appears that the way the stereo > driver works is > that it recognizes the application being run and configures itself to that > application. The driver apparently has an application database > and knows the > details of how each application sets up its viewing parameters, > so it is able > to generate stereo views automatically without the application > itself being > aware that it is running in stereo.
...this is the registry root: HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs > Most of these applications > seem to be the > popular games, naturally, so it's highly unlikely that Java 3D will be > recognized and run properly in that mode. ...but perhaps we can figure out what the appropriate registry entry should be to /make/ it work... > There are a lot of parameters > affecting the stereo display that can be handled properly only if > Java 3D can > control the OpenGL or D3D pipeline itself. ...and the registry values that each game configuration has varies. A quick search for unique key names finds the following: AutoConvergence CommandLine FrustumAdjustMode RunTimeName StereoConvergence NoOrthoStereo RHWGreaterAtScreen RHWLessAtScreen AutoConvergenceAdjustPace OpenGL Link1 Link2 LaserSight I think the valid set of keys may be some subset of the ones found here: HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D I have searched nVidia's site for details on these but have come up dry. So I think your speculation that the driver changes the viewing parameters based on the program being run is correct. The trick will be figuring out how to create a provfile for Java3D and having it enabled when a Java3D app is run. Simeon =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
