The status bar, menu's increases with convergence? But with some games it is locked?
With some games, mostly older games, the status bars are locked and with some not. With games like fear, HL2, Fable, COD2 the status bar changes with the convergence. Is there anything I could change in these games "setup" to lock their status bars or menus?
With some games, mostly older games, the status bars are locked and with some not. With games like fear, HL2, Fable, COD2 the status bar changes with the convergence. Is there anything I could change in these games "setup" to lock their status bars or menus?
[quote name='Fedelity-RSA' post='497834' date='Jan 28 2009, 11:37 AM']With some games, mostly older games, the status bars are locked and with some not. With games like fear, HL2, Fable, COD2 the status bar changes with the convergence. Is there anything I could change in these games "setup" to lock their status bars or menus?
Please help
Thanks[/quote]
Yes and no. This is more a function of the game's profile.
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
[quote name='Fedelity-RSA' post='497834' date='Jan 28 2009, 11:37 AM']With some games, mostly older games, the status bars are locked and with some not. With games like fear, HL2, Fable, COD2 the status bar changes with the convergence. Is there anything I could change in these games "setup" to lock their status bars or menus?
Please help
Thanks
Yes and no. This is more a function of the game's profile.
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
[quote name='Chopper' post='497904' date='Jan 28 2009, 08:53 PM']Yes and no. This is more a function of the game's profile.
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
[quote name='Chopper' post='497904' date='Jan 28 2009, 08:53 PM']Yes and no. This is more a function of the game's profile.
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
The Heads-Up-Display is set too close to your virtual eyes in the 3d gamespace in many games.
In order to try and fix a badly positioned HUD you need frontplane control. I don't know why
they took the hotkey config option out of the nvidia stereo contol panel in newer driver versions,
but the hotkey functions still may be in the driver anyway. Here's how to tell:
Look in the windows registry under Nvidia Corporation\Global\Stereo3D
If there are entries there like RHWAtScreenLess/More and RHWLesssAtScreenLess/More,
then those functions should be in the driver even if they don't show up in the nvidia
control panel. These are control hotkey settings for the backplane (BP) and frontplane (FP)
settings. Nvidia calls frontplane "screen-depth".
The default frontplane/backplane hotkey keystrokes are:
(this is what you need to get working in order to fix the Heads-Up-Display)
increase FP: Ctl-F10 --- pushes plane away from you
decrease FP: Ctl-F9 --- pulls plane towards you
(backplane is normally not important, but it's possible)
increase BP: Alt-F10 --- pulls plane towards you
decreaseBP: Alt-F9 --- pushes plane away from you
This is confusing because the increase/decrease push/pull functions are opposite.
The planes are imaginary vertical planes perpendicular to your line of sight.
Scenery behind the backplane becomes 2d (at screen-depth).
Scenery in front of the frontplane (closer to you) is put at screen depth.
You will see what I mean soon if you can get the nvidia test working.
Here's what you do:
1.) go to the nvidia stereo control panel and check all three boxes under
Stereo Compatibility Settings.
2.) start the stereo-3d nvidia-logo test (nvsttest), exit that, restart it.
One restart should be enough but restart it again if things still don't work.
This is done because many times the Compatibility Settings don't take
effect until the second start for some reason. (initialization problem?)
3.) optional but very helpful: edit registry so that Nvidia Corporation\Global\Stereo3D
contains a D_WORD of StereoOSDEnable and set it to 1.
This may cause your computer to crash when you start the test, so be warned.
I expect it to be fine for most people and worth the risk. If bad, try a different driver
version.
4.) increase separation if needed, then increase frontplane with glasses off untill you see
what it does. This could mean holding down the hotkey for 2 minutes or more.
Parts of the scene should snap to 2d starting from foreground to back.
Decreasing FP obviously moves the plane in the opposite direction (towards you).
5.) exit that and try to do this in your game to fix your HUD.
It's possible that your game will not want to start with HW-TnL disabled. Here's how
to test it:
Now HW-TnL should be disabled by steps 1 and 2 above. You can change step 1 to mean
only HW-TnL. Try to start your game. If it refuses, uncheck the box and run the nvidia
test 2 or 3 times to overcome same init problem as above. Test game again. It probably
works now. If this is your situation, I think you're out of luck unless another video card
works better but probably not. It seems like the FP never works in OpenGL games.
The NVSTTEST should be a DirectX 8 program by the way.
The backplane acts similarly but opposite and in back.
If you can't get the planes working in the nvsttest, then edit the registry directly:
find the NVSTTEST entry under
HKEY_LOCAL_MACHINE\SOFTWARE\Nvidia Corporation\Global\Stereo3D\GameConfigs
under NVSTTEST, create D_WORD entries
RHWGreaterAtScreen --- 3bd86ecc (frontplane)
RHWLessAtScreen --- 3ab0254e (backplane)
These settings put the frontplane past the small nvidia logo in the lower left corner so
it will be in 2d to prove that the FP works. It puts the backplane in front of the background
so it will be in 2d to prove that the BP works.
While you're at it, turn on the lasersight. It's good to see that working too.
LaserSight --- 1
LaserXAdjust --- 3f800000 (this means1.0 in floating point binary)
LaserYadjust --- 3f800000
Now start the test and play with the FP and BP so you understand it. Don't wear the
glasses while doing this. Well, you can take a look but it's visually confusing.
You should see that the lasersight (LS) is also affected by the frontplane. This fact could
be useful or not depending on your game and how you like your settings. You might also
notice that the LS behaves differently when HW-TnL is enabled or not. For my system it
works better when TnL is off and works horribly when TnL is on.
Got enough info yet? No? Newbies: you edit the registry by running regedit from
Start--->Run, then search for NVSTTEST
good luck and happy troubleshooting
PS: Please post your results with...
game and version and patches applied,
video card,
Windows version,
Nvidia driver version,
Nvidia Stereo driver version,
game's Direct-X or OpenGL version.
I think that's all the key info. Lets make a good database of this stuff.
Please help
Thanks
Please help
Thanks
Please help
Thanks[/quote]
Yes and no. This is more a function of the game's profile.
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
Regards,
Chopper
Please help
Thanks
Yes and no. This is more a function of the game's profile.
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
Regards,
Chopper
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
Regards,
Chopper[/quote]
Thanks
An earlier version of driver had a feature where you can adjust the driver's front plane to compensate for the interface problem. I don't think it is still there, though. I'll see if I can dig anything up.
Regards,
Chopper
Thanks
The Heads-Up-Display is set too close to your virtual eyes in the 3d gamespace in many games.
In order to try and fix a badly positioned HUD you need frontplane control. I don't know why
they took the hotkey config option out of the nvidia stereo contol panel in newer driver versions,
but the hotkey functions still may be in the driver anyway. Here's how to tell:
Look in the windows registry under Nvidia Corporation\Global\Stereo3D
If there are entries there like RHWAtScreenLess/More and RHWLesssAtScreenLess/More,
then those functions should be in the driver even if they don't show up in the nvidia
control panel. These are control hotkey settings for the backplane (BP) and frontplane (FP)
settings. Nvidia calls frontplane "screen-depth".
The default frontplane/backplane hotkey keystrokes are:
(this is what you need to get working in order to fix the Heads-Up-Display)
increase FP: Ctl-F10 --- pushes plane away from you
decrease FP: Ctl-F9 --- pulls plane towards you
(backplane is normally not important, but it's possible)
increase BP: Alt-F10 --- pulls plane towards you
decreaseBP: Alt-F9 --- pushes plane away from you
This is confusing because the increase/decrease push/pull functions are opposite.
The planes are imaginary vertical planes perpendicular to your line of sight.
Scenery behind the backplane becomes 2d (at screen-depth).
Scenery in front of the frontplane (closer to you) is put at screen depth.
You will see what I mean soon if you can get the nvidia test working.
Here's what you do:
1.) go to the nvidia stereo control panel and check all three boxes under
Stereo Compatibility Settings.
2.) start the stereo-3d nvidia-logo test (nvsttest), exit that, restart it.
One restart should be enough but restart it again if things still don't work.
This is done because many times the Compatibility Settings don't take
effect until the second start for some reason. (initialization problem?)
3.) optional but very helpful: edit registry so that Nvidia Corporation\Global\Stereo3D
contains a D_WORD of StereoOSDEnable and set it to 1.
This may cause your computer to crash when you start the test, so be warned.
I expect it to be fine for most people and worth the risk. If bad, try a different driver
version.
4.) increase separation if needed, then increase frontplane with glasses off untill you see
what it does. This could mean holding down the hotkey for 2 minutes or more.
Parts of the scene should snap to 2d starting from foreground to back.
Decreasing FP obviously moves the plane in the opposite direction (towards you).
5.) exit that and try to do this in your game to fix your HUD.
It's possible that your game will not want to start with HW-TnL disabled. Here's how
to test it:
Now HW-TnL should be disabled by steps 1 and 2 above. You can change step 1 to mean
only HW-TnL. Try to start your game. If it refuses, uncheck the box and run the nvidia
test 2 or 3 times to overcome same init problem as above. Test game again. It probably
works now. If this is your situation, I think you're out of luck unless another video card
works better but probably not. It seems like the FP never works in OpenGL games.
The NVSTTEST should be a DirectX 8 program by the way.
The backplane acts similarly but opposite and in back.
If you can't get the planes working in the nvsttest, then edit the registry directly:
find the NVSTTEST entry under
HKEY_LOCAL_MACHINE\SOFTWARE\Nvidia Corporation\Global\Stereo3D\GameConfigs
under NVSTTEST, create D_WORD entries
RHWGreaterAtScreen --- 3bd86ecc (frontplane)
RHWLessAtScreen --- 3ab0254e (backplane)
These settings put the frontplane past the small nvidia logo in the lower left corner so
it will be in 2d to prove that the FP works. It puts the backplane in front of the background
so it will be in 2d to prove that the BP works.
While you're at it, turn on the lasersight. It's good to see that working too.
LaserSight --- 1
LaserXAdjust --- 3f800000 (this means1.0 in floating point binary)
LaserYadjust --- 3f800000
Now start the test and play with the FP and BP so you understand it. Don't wear the
glasses while doing this. Well, you can take a look but it's visually confusing.
You should see that the lasersight (LS) is also affected by the frontplane. This fact could
be useful or not depending on your game and how you like your settings. You might also
notice that the LS behaves differently when HW-TnL is enabled or not. For my system it
works better when TnL is off and works horribly when TnL is on.
Got enough info yet? No? Newbies: you edit the registry by running regedit from
Start--->Run, then search for NVSTTEST
good luck and happy troubleshooting
PS: Please post your results with...
game and version and patches applied,
video card,
Windows version,
Nvidia driver version,
Nvidia Stereo driver version,
game's Direct-X or OpenGL version.
I think that's all the key info. Lets make a good database of this stuff.
Thank you.
The Heads-Up-Display is set too close to your virtual eyes in the 3d gamespace in many games.
In order to try and fix a badly positioned HUD you need frontplane control. I don't know why
they took the hotkey config option out of the nvidia stereo contol panel in newer driver versions,
but the hotkey functions still may be in the driver anyway. Here's how to tell:
Look in the windows registry under Nvidia Corporation\Global\Stereo3D
If there are entries there like RHWAtScreenLess/More and RHWLesssAtScreenLess/More,
then those functions should be in the driver even if they don't show up in the nvidia
control panel. These are control hotkey settings for the backplane (BP) and frontplane (FP)
settings. Nvidia calls frontplane "screen-depth".
The default frontplane/backplane hotkey keystrokes are:
(this is what you need to get working in order to fix the Heads-Up-Display)
increase FP: Ctl-F10 --- pushes plane away from you
decrease FP: Ctl-F9 --- pulls plane towards you
(backplane is normally not important, but it's possible)
increase BP: Alt-F10 --- pulls plane towards you
decreaseBP: Alt-F9 --- pushes plane away from you
This is confusing because the increase/decrease push/pull functions are opposite.
The planes are imaginary vertical planes perpendicular to your line of sight.
Scenery behind the backplane becomes 2d (at screen-depth).
Scenery in front of the frontplane (closer to you) is put at screen depth.
You will see what I mean soon if you can get the nvidia test working.
Here's what you do:
1.) go to the nvidia stereo control panel and check all three boxes under
Stereo Compatibility Settings.
2.) start the stereo-3d nvidia-logo test (nvsttest), exit that, restart it.
One restart should be enough but restart it again if things still don't work.
This is done because many times the Compatibility Settings don't take
effect until the second start for some reason. (initialization problem?)
3.) optional but very helpful: edit registry so that Nvidia Corporation\Global\Stereo3D
contains a D_WORD of StereoOSDEnable and set it to 1.
This may cause your computer to crash when you start the test, so be warned.
I expect it to be fine for most people and worth the risk. If bad, try a different driver
version.
4.) increase separation if needed, then increase frontplane with glasses off untill you see
what it does. This could mean holding down the hotkey for 2 minutes or more.
Parts of the scene should snap to 2d starting from foreground to back.
Decreasing FP obviously moves the plane in the opposite direction (towards you).
5.) exit that and try to do this in your game to fix your HUD.
It's possible that your game will not want to start with HW-TnL disabled. Here's how
to test it:
Now HW-TnL should be disabled by steps 1 and 2 above. You can change step 1 to mean
only HW-TnL. Try to start your game. If it refuses, uncheck the box and run the nvidia
test 2 or 3 times to overcome same init problem as above. Test game again. It probably
works now. If this is your situation, I think you're out of luck unless another video card
works better but probably not. It seems like the FP never works in OpenGL games.
The NVSTTEST should be a DirectX 8 program by the way.
The backplane acts similarly but opposite and in back.
If you can't get the planes working in the nvsttest, then edit the registry directly:
find the NVSTTEST entry under
HKEY_LOCAL_MACHINE\SOFTWARE\Nvidia Corporation\Global\Stereo3D\GameConfigs
under NVSTTEST, create D_WORD entries
RHWGreaterAtScreen --- 3bd86ecc (frontplane)
RHWLessAtScreen --- 3ab0254e (backplane)
These settings put the frontplane past the small nvidia logo in the lower left corner so
it will be in 2d to prove that the FP works. It puts the backplane in front of the background
so it will be in 2d to prove that the BP works.
While you're at it, turn on the lasersight. It's good to see that working too.
LaserSight --- 1
LaserXAdjust --- 3f800000 (this means1.0 in floating point binary)
LaserYadjust --- 3f800000
Now start the test and play with the FP and BP so you understand it. Don't wear the
glasses while doing this. Well, you can take a look but it's visually confusing.
You should see that the lasersight (LS) is also affected by the frontplane. This fact could
be useful or not depending on your game and how you like your settings. You might also
notice that the LS behaves differently when HW-TnL is enabled or not. For my system it
works better when TnL is off and works horribly when TnL is on.
Got enough info yet? No? Newbies: you edit the registry by running regedit from
Start--->Run, then search for NVSTTEST
good luck and happy troubleshooting
PS: Please post your results with...
game and version and patches applied,
video card,
Windows version,
Nvidia driver version,
Nvidia Stereo driver version,
game's Direct-X or OpenGL version.
I think that's all the key info. Lets make a good database of this stuff.
Thank you.