4:3 Aspect Ratio Has Wrong Maximum Depth Games played in 4:3 on a widescreen have decreased depth
When I play older games that only support 4:3 aspect resolutions on my widescreen 3D monitors, the image separation at maximum depth (100%) is much less than when I play other games at widescreen resolutions at maximum depth. That is, I am unable to get a true maximum depth with a 4:3 ratio game on a 16:10 monitor.

I had this problem with older nVidia stereoscopic drivers before 3DVision came out. I assumed it was confused by the screen width of the 4:3 game, which is much smaller than the physical screen width, in calculating the separation for maximum depth. What I would do to fix this was decrease the monitor's size in the driver's registry (you could do that in those days) to fool the driver into thinking the monitor's screen size was the same as the 4:3 frame.

Later drivers (but still before 3DVision) corrected this problem, so I didn't have to mess with the monitor size anymore. However, it seems the problem has returned for me with the latest 3DVision drivers.

I was about to try modifying the registry again to force the monitor size down as I did before, but I wanted to see if anyone knew of a better solution first. Also, nVidia, please fix this :)
When I play older games that only support 4:3 aspect resolutions on my widescreen 3D monitors, the image separation at maximum depth (100%) is much less than when I play other games at widescreen resolutions at maximum depth. That is, I am unable to get a true maximum depth with a 4:3 ratio game on a 16:10 monitor.



I had this problem with older nVidia stereoscopic drivers before 3DVision came out. I assumed it was confused by the screen width of the 4:3 game, which is much smaller than the physical screen width, in calculating the separation for maximum depth. What I would do to fix this was decrease the monitor's size in the driver's registry (you could do that in those days) to fool the driver into thinking the monitor's screen size was the same as the 4:3 frame.



Later drivers (but still before 3DVision) corrected this problem, so I didn't have to mess with the monitor size anymore. However, it seems the problem has returned for me with the latest 3DVision drivers.



I was about to try modifying the registry again to force the monitor size down as I did before, but I wanted to see if anyone knew of a better solution first. Also, nVidia, please fix this :)

#1
Posted 09/16/2011 06:14 AM   
Well, there isn't any elegant way to do this, so I went back to editing my registry. After further research I found that the MonitorSize entry is the diagonal length of the monitor times two, in hexadecimal. So my 17-inch laptop is by default 22 (34 decimal).

I tried to calculate an expression based on the 4:3 vs 16:10 problem above and my default MonitorSize in the registry. I forgot to write down what I did, and I will certainly post it here if I ever do, but I found that the ratio was 0.75. So, the "fake" 4:3 monitor size was 0.75 times the "true" 16:10 monitor size.

I found a few links with some scripts that are supposed to run the game and modify your registry simulaneously, but I wasn't able to get them to work. Nevertheless, here's one to get you started, from this very forum :)

http://forums.nvidia.com/index.php?showtopic=212298

I did create a batch script for myself, it's very simple, only one line, but here it is:

@REG ADD "HKLM\Software\Wow6432Node\NVIDIA Corporation\Global\Stereo3D" /v MonitorSize /t REG_DWORD /d 25 /f

34 * 0.75 = 25.5 in decimal, which in hex is rounded down to 19.

What I do is run the game, then switch back to the desktop, run the script, and then switch back to the game. It's cumbersome, but it worked for the game I was testing, which was Hitman: Contracts.

That's all I have for now; this thread may only be relevant to me but there you go :)
Well, there isn't any elegant way to do this, so I went back to editing my registry. After further research I found that the MonitorSize entry is the diagonal length of the monitor times two, in hexadecimal. So my 17-inch laptop is by default 22 (34 decimal).



I tried to calculate an expression based on the 4:3 vs 16:10 problem above and my default MonitorSize in the registry. I forgot to write down what I did, and I will certainly post it here if I ever do, but I found that the ratio was 0.75. So, the "fake" 4:3 monitor size was 0.75 times the "true" 16:10 monitor size.



I found a few links with some scripts that are supposed to run the game and modify your registry simulaneously, but I wasn't able to get them to work. Nevertheless, here's one to get you started, from this very forum :)



http://forums.nvidia.com/index.php?showtopic=212298



I did create a batch script for myself, it's very simple, only one line, but here it is:



@REG ADD "HKLM\Software\Wow6432Node\NVIDIA Corporation\Global\Stereo3D" /v MonitorSize /t REG_DWORD /d 25 /f



34 * 0.75 = 25.5 in decimal, which in hex is rounded down to 19.



What I do is run the game, then switch back to the desktop, run the script, and then switch back to the game. It's cumbersome, but it worked for the game I was testing, which was Hitman: Contracts.



That's all I have for now; this thread may only be relevant to me but there you go :)

#2
Posted 02/09/2012 08:33 AM   
Scroll To Top