MonitorSizeOverride; The Only DepthHack You'll Ever Need...
  3 / 4    
Hi guys, just checking, does this work for Compatibility Mode, or real 3D only? Thanks
Hi guys, just checking, does this work for Compatibility Mode, or real 3D only? Thanks

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#31
Posted 09/23/2016 10:54 PM   
I guess you need to restart the computer each time you make a change to the registry..? because from what i know it only reads the registry at startup of windows, you probably can't log out/in, but a full restart?
I guess you need to restart the computer each time you make a change to the registry..? because from what i know it only reads the registry at startup of windows, you probably can't log out/in, but a full restart?

Computer: i7 2600K @4.8GHz / Asus Sabertooth P67 Rev3 / 32GB Corsair Vengeance / GTX 980ti / 34" Samsung S34E790C
Projectors: BenQ W700 / BenQ MH741

#32
Posted 09/24/2016 12:45 AM   
[quote="vurt72"]I guess you need to restart the computer each time you make a change to the registry..? because from what i know it only reads the registry at startup of windows, you probably can't log out/in, but a full restart?[/quote] That's not necessary. You just need to run the script with admin rights. As the first post says, the Nvidia driver is looking for the MonitorSizeOverride value when you start a game.
vurt72 said:I guess you need to restart the computer each time you make a change to the registry..? because from what i know it only reads the registry at startup of windows, you probably can't log out/in, but a full restart?


That's not necessary. You just need to run the script with admin rights.

As the first post says, the Nvidia driver is looking for the MonitorSizeOverride value when you start a game.

i7-4770k @ 4.3GHz
EVGA GTX 1080Ti
16GB 2400MHz DDR3
1TB SanDisk SSD
2TB 7200RPM HDD
Windows 10 x64

#33
Posted 09/24/2016 05:55 AM   
[quote="The_Nephilim"]Hey All, There is a newer one of these depth hacks tricks but made in the registry. I don't remember who made it or found it but the newer one made this one obsolete.. There was 2 ways too apply the fix one with a registry entry and one was a Bat file little bit like this.. The only difference you did not need to run the bat file before each game run.. I will try and see if I can find that thread and make a new post in there.. I will if I find it report it back to this thread..[/quote]This IS that post... I changed the title because some people weren't understanding it(?) [quote="The_Nephilim"]OK here is the files I have as I could not find the thread: [code]REM @Echo Off Title MonitorSizeOverride Set "$MonitorSize=15" Set /A "$MonitorSize=%$MonitorSize%*2" Call Cmd /c Exit /b %$MonitorSize% Set "$Hex=%=EXITCODE%" For /F "tokens=* delims=0" %%? in ("%$Hex%") do (Set "$Hex=%%?") if Exist "%PROGRAMFILES(X86)%" Set "$Wow=Wow6432Node\" Set "$Key="HKLM\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSizeOverride"" Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof [/code] here is registry edit way: [code] Change MonitorSize, Save as Reg, Merge into Registry 1.Windows Registry Editor 2. 3.[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D] 4."MonitorSizeOverride"=dword:00000082 Notes:Value must be in Hex and is normally double the Monitor's diagonal size... 82 in Hex = 130 in Decimal(65*2), converter here... also Remove Wow6432Node\ on x86/32bit Machines. [/code] Remember you only need to run the file or do ther registry entry once or after each new video card update of the drivers.. the batch file was made in case you are not familiar with editing the registry.. Remember you need only run these one time not each time before running the game.. [/quote]Everything in my first is up to date as far as I know and that 1st script you posted is wrong/old, I figured out later(a few post in) MonitorSizeOverride doesn't use a doubled Value, like MonitorSize does.
The_Nephilim said:Hey All,

There is a newer one of these depth hacks tricks but made in the registry. I don't remember who made it or found it but the newer one made this one obsolete..

There was 2 ways too apply the fix one with a registry entry and one was a Bat file little bit like this..

The only difference you did not need to run the bat file before each game run.. I will try and see if I can find that thread and make a new post in there.. I will if I find it report it back to this thread..
This IS that post... I changed the title because some people weren't understanding it(?)

The_Nephilim said:OK here is the files I have as I could not find the thread:

REM @Echo Off
Title MonitorSizeOverride
Set "$MonitorSize=15"
Set /A "$MonitorSize=%$MonitorSize%*2"
Call Cmd /c Exit /b %$MonitorSize%
Set "$Hex=%=EXITCODE%"
For /F "tokens=* delims=0" %%? in ("%$Hex%") do (Set "$Hex=%%?")
if Exist "%PROGRAMFILES(X86)%" Set "$Wow=Wow6432Node\"
Set "$Key="HKLM\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSizeOverride""
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof


here is registry edit way:

Change MonitorSize, Save as Reg, Merge into Registry
1.Windows Registry Editor

2.

3.[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D]

4."MonitorSizeOverride"=dword:00000082

Notes:Value must be in Hex and is normally double the Monitor's diagonal size... 82 in Hex = 130 in Decimal(65*2), converter here... also Remove Wow6432Node\ on x86/32bit Machines.


Remember you only need to run the file or do ther registry entry once or after each new video card update of the drivers.. the batch file was made in case you are not familiar with editing the registry..

Remember you need only run these one time not each time before running the game..
Everything in my first is up to date as far as I know and that 1st script you posted is wrong/old, I figured out later(a few post in) MonitorSizeOverride doesn't use a doubled Value, like MonitorSize does.
#34
Posted 09/24/2016 04:22 PM   
There's a lot of misconceptions going on in these last few posts... I'll try to clear some of it up. [quote="vurt72"]I dont get this to be honest, since there are depth settings already? But this goes beyond even that? What would you suggest that i use for my projector (64")? Thanks[/quote]For a 64" Screen the Default Value would be 64 dec/40 hexadecimal or 64 in the BAT version or 40 in the REG version... if it's still not enough, Depth @ 100% and Convergence properly tweaked, then you can go lower than your actual screen size. Personally I had to go a bit lower to get 100% Depth to match my IPD(Interpupillary Distance)... lower MonitorSize = higher Depth(Separation). [quote="SnickerSnack"]Hi guys, just checking, does this work for Compatibility Mode, or real 3D only? Thanks[/quote]No, sorry... I've tried tons of things to find something that would work. Honestly I'd suggest looking into using [url=https://forums.geforce.com/default/topic/959175/]SuperDepth3D[/url] instead... it's so much more robust than CompatibilityMode. [quote="vurt72"]I guess you need to restart the computer each time you make a change to the registry..? because from what i know it only reads the registry at startup of windows, you probably can't log out/in, but a full restart?[/quote]...like oneup03 pointed out, that is dead wrong. The Registry is actually read multiple times when starting a game and on every Alt+Tab.
There's a lot of misconceptions going on in these last few posts... I'll try to clear some of it up.

vurt72 said:I dont get this to be honest, since there are depth settings already? But this goes beyond even that?

What would you suggest that i use for my projector (64")?

Thanks
For a 64" Screen the Default Value would be 64 dec/40 hexadecimal or 64 in the BAT version or 40 in the REG version... if it's still not enough, Depth @ 100% and Convergence properly tweaked, then you can go lower than your actual screen size. Personally I had to go a bit lower to get 100% Depth to match my IPD(Interpupillary Distance)... lower MonitorSize = higher Depth(Separation).

SnickerSnack said:Hi guys, just checking, does this work for Compatibility Mode, or real 3D only? Thanks
No, sorry... I've tried tons of things to find something that would work. Honestly I'd suggest looking into using SuperDepth3D instead... it's so much more robust than CompatibilityMode.

vurt72 said:I guess you need to restart the computer each time you make a change to the registry..? because from what i know it only reads the registry at startup of windows, you probably can't log out/in, but a full restart?
...like oneup03 pointed out, that is dead wrong. The Registry is actually read multiple times when starting a game and on every Alt+Tab.
#35
Posted 09/24/2016 04:42 PM   
Good to know about the registry, lots of guides tells that you must restart the computer for registry changes to take effect. I measured my projector screen again to be sure, it's actually 75" heh.. i tried a low value in the .bat (32" i belive it was) to me there was no difference.
Good to know about the registry, lots of guides tells that you must restart the computer for registry changes to take effect.

I measured my projector screen again to be sure, it's actually 75" heh.. i tried a low value in the .bat (32" i belive it was) to me there was no difference.

Computer: i7 2600K @4.8GHz / Asus Sabertooth P67 Rev3 / 32GB Corsair Vengeance / GTX 980ti / 34" Samsung S34E790C
Projectors: BenQ W700 / BenQ MH741

#36
Posted 09/24/2016 06:00 PM   
Ok... not sure what's going on there, not much to go on. Are you using the scripts in the first post? ...my post? ...not the one The_Nephilim posted?(that one doubles the Value(halves Depth) like I mentioned above...) Did you run the script as Admin? Did you double-check that is was written to the Registry? Did you try the Reg version? ...did you try a before and after without the glasses on? Measure the Depth/Separation at the screen? ...is Depth @ 100%? Personally I run the 3D test app from the Control Panel, the text on the background(NVIDIA) gives a good representation of what max depth is set at in-game.
Ok... not sure what's going on there, not much to go on.

Are you using the scripts in the first post? ...my post? ...not the one The_Nephilim posted?(that one doubles the Value(halves Depth) like I mentioned above...)

Did you run the script as Admin?

Did you double-check that is was written to the Registry?

Did you try the Reg version?

...did you try a before and after without the glasses on? Measure the Depth/Separation at the screen?

...is Depth @ 100%?

Personally I run the 3D test app from the Control Panel, the text on the background(NVIDIA) gives a good representation of what max depth is set at in-game.
#37
Posted 09/24/2016 06:47 PM   
Played around with it some more, and yeah, there might be some difference heh, the pop-out effect looks kind of messed up at extreme values (as in low values, like 25). Will have to try a value of maybe 65 or so. I use this: @Echo Off Title MonitorSizeOverride Set "$MonitorSize=25" Call Cmd /c Exit /b %$MonitorSize% Set "$Hex=%=EXITCODE%" For /F "tokens=* delims=0" %%? in ("%$Hex%") do (Set "$Hex=%%?") if Exist "%PROGRAMFILES(X86)%" Set "$Wow=Wow6432Node\" Set "$Key="HKLM\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSizeOverride"" Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Played around with it some more, and yeah, there might be some difference heh, the pop-out effect looks kind of messed up at extreme values (as in low values, like 25). Will have to try a value of maybe 65 or so.

I use this:

@Echo Off
Title MonitorSizeOverride
Set "$MonitorSize=25"
Call Cmd /c Exit /b %$MonitorSize%
Set "$Hex=%=EXITCODE%"
For /F "tokens=* delims=0" %%? in ("%$Hex%") do (Set "$Hex=%%?")
if Exist "%PROGRAMFILES(X86)%" Set "$Wow=Wow6432Node\"
Set "$Key="HKLM\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSizeOverride""
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof

Computer: i7 2600K @4.8GHz / Asus Sabertooth P67 Rev3 / 32GB Corsair Vengeance / GTX 980ti / 34" Samsung S34E790C
Projectors: BenQ W700 / BenQ MH741

#38
Posted 09/24/2016 09:12 PM   
Yeah it looks like everything's in order... this is very YMMV as far as how much your actual MonitorSize will add, some are closer to actual than others by Default and it can be a little harder to discern the difference, unlike Convergence. You can go higher than your IPD but that can cause eyestrain and make things look weird, especially the higher you go... and it's debatable whether or not your eyes can even focus on that type of Separation, I don't think they can when it's past your IPD. Personally I set everything up with the glasses off, Depth/MonitorSizeOverride to just slightly over my IPD measured at the screen and Convergence dependent upon the type of game... the subtle 'extra' Depth coupled with a properly tweaked Convergence is what works best for me.
Yeah it looks like everything's in order... this is very YMMV as far as how much your actual MonitorSize will add, some are closer to actual than others by Default and it can be a little harder to discern the difference, unlike Convergence.

You can go higher than your IPD but that can cause eyestrain and make things look weird, especially the higher you go... and it's debatable whether or not your eyes can even focus on that type of Separation, I don't think they can when it's past your IPD.

Personally I set everything up with the glasses off, Depth/MonitorSizeOverride to just slightly over my IPD measured at the screen and Convergence dependent upon the type of game... the subtle 'extra' Depth coupled with a properly tweaked Convergence is what works best for me.
#39
Posted 09/24/2016 09:52 PM   
[quote="EGY-SuperOne"]Hello It's my first time to found out about Depth Hack what I understand is that when we lower the monitor size from the registry we let nvidia driver think we got smaller monitor size to increase the 3D Depth so if we lower the monitor size by half and the 3D depth slider is on 100% it's actually is 200% The old hack which is MonitorSize would reset it's value to it's default every time you run a game, But the new or old as you said which is MonitorSizeOverride will not reset it's value. I used your Batch Version and here is a pic from my registry: [img]https://i.imgur.com/1bTeyOG.png[/img] The 3D Depth slider is on 100% but it's actually 200% now right ? and to get back to the default 3D Depth all I have to do is delete MonitorSizeOverride ? BTW do people actually play with 200% or more depth. Thanks a lot TsaebehT. [/quote] I did it right to double the 3D Depth on my 24 inch monitor ? and also to get back to the default 3D Depth all I have to do is delete MonitorSizeOverride ? Thanks
EGY-SuperOne said:Hello

It's my first time to found out about Depth Hack
what I understand is that when we lower the monitor size from the registry
we let nvidia driver think we got smaller monitor size to increase the 3D Depth
so if we lower the monitor size by half and the 3D depth slider is on 100% it's actually is 200%

The old hack which is MonitorSize would reset it's value to it's default every time you run a game,
But the new or old as you said which is MonitorSizeOverride will not reset it's value.

I used your Batch Version and here is a pic from my registry:

Image

The 3D Depth slider is on 100% but it's actually 200% now right ?

and to get back to the default 3D Depth all I have to do is delete MonitorSizeOverride ?

BTW do people actually play with 200% or more depth.

Thanks a lot TsaebehT.


I did it right to double the 3D Depth on my 24 inch monitor ?
and also to get back to the default 3D Depth all I have to do is delete MonitorSizeOverride ?

Thanks

#40
Posted 09/25/2016 05:26 PM   
Based on your screen cap, your depth will be the exact same with or without the MonitorSizeOverride. The MonitorSize value gets cut in half when the driver uses it, so it's 24 either way. To double your depth you would need to put 12 in MonitorSizeOverride. You could probably delete it or set it back to 24 to go back to normal.
Based on your screen cap, your depth will be the exact same with or without the MonitorSizeOverride.
The MonitorSize value gets cut in half when the driver uses it, so it's 24 either way.
To double your depth you would need to put 12 in MonitorSizeOverride.
You could probably delete it or set it back to 24 to go back to normal.

i7-4770k @ 4.3GHz
EVGA GTX 1080Ti
16GB 2400MHz DDR3
1TB SanDisk SSD
2TB 7200RPM HDD
Windows 10 x64

#41
Posted 09/25/2016 07:38 PM   
[quote="oneup03"]Based on your screen cap, your depth will be the exact same with or without the MonitorSizeOverride. The MonitorSize value gets cut in half when the driver uses it, so it's 24 either way. To double your depth you would need to put 12 in MonitorSizeOverride. You could probably delete it or set it back to 24 to go back to normal.[/quote] MonitorSizeOverride and MonitorSize use the same value right but MonitorSizeOverride Override MonitorSize ? also as I understand from here: [url]http://3dvision-blog.com/tag/depth-hack/[/url] "Each number from the value 44 represents half an inch size, so that is why 44 actually represents a 22-inch monitor size with the idea that when you can change the size in half of inch you get better control than with 1 inch. So what you need to do in order to increase the maximum depth level is to actually decrease the size of the monitor, if you for example set it to 22 decimal (16 HEX) value this will mean that you have 11-inch display and you’ll get double the depth (100% more)." So the normal value for 24 inch monitor is 48 for 100% 3D depth and to get to 200% 3D depth I should lower 48 by half which is the value 24 for 200% 3D depth So MonitorSizeOverride should be 24 or I didn't understand correctly ? Thank you.
oneup03 said:Based on your screen cap, your depth will be the exact same with or without the MonitorSizeOverride.
The MonitorSize value gets cut in half when the driver uses it, so it's 24 either way.
To double your depth you would need to put 12 in MonitorSizeOverride.
You could probably delete it or set it back to 24 to go back to normal.


MonitorSizeOverride and MonitorSize use the same value right
but MonitorSizeOverride Override MonitorSize ?

also as I understand from here: http://3dvision-blog.com/tag/depth-hack/

"Each number from the value 44 represents half an inch size, so that is why 44 actually represents a 22-inch monitor size with the idea that when you can change the size in half of inch you get better control than with 1 inch. So what you need to do in order to increase the maximum depth level is to actually decrease the size of the monitor, if you for example set it to 22 decimal (16 HEX) value this will mean that you have 11-inch display and you’ll get double the depth (100% more)."

So the normal value for 24 inch monitor is 48 for 100% 3D depth
and to get to 200% 3D depth I should lower 48 by half which is the value 24 for 200% 3D depth
So MonitorSizeOverride should be 24

or I didn't understand correctly ?

Thank you.

#42
Posted 09/25/2016 09:39 PM   
okay I'm very sorry I just noticed this: "It also looks like the Drivers aren't doubling/halving the MonitorSizeOverride Value like they do with the MonitorSize Value, so instead of the usual 24" Monitor getting a 48 MonitorSize Value with this 'hack' a 24" Monitor would get a 24 MonitorSizeOverride Value and just like all the DepthHacks the lower you go the more you increase the Depth Multiplier... so 1/2 your MonitorSize Value would be equal to 100% Depth, 1/4 would equal 200% Depth, 1/8 should relativity equal 400%, and so on..." Thanks a lot oneup03 and TsaebehT.
okay I'm very sorry I just noticed this:

"It also looks like the Drivers aren't doubling/halving the MonitorSizeOverride Value like they do with the MonitorSize Value, so instead of the usual 24" Monitor getting a 48 MonitorSize Value with this 'hack' a 24" Monitor would get a 24 MonitorSizeOverride Value and just like all the DepthHacks the lower you go the more you increase the Depth Multiplier... so 1/2 your MonitorSize Value would be equal to 100% Depth, 1/4 would equal 200% Depth, 1/8 should relativity equal 400%, and so on..."

Thanks a lot oneup03 and TsaebehT.

#43
Posted 09/25/2016 09:45 PM   
@EGY-SuperOne No need to be sorry, I should be apologizing. I rewrote the end of that section to clarify it a bit more... originally I was referring to actual screen/monitor size(1/2 = 200%) but typed MonitorSize(1/2 = 100%) so that's where the confusion originally came from. I was meaning to reply to your post last night but I got side-tracked sorry about that. Unfortunately when referring to MonitorSize, it's not always correct in the Registry so it makes it harder when discussing it... not everyone's 100% is equal as it probably would/should be if it were. So there's 2 main uses for this: 1) To correct for an incorrect MonitorSize Value in the Registry. 2) To go 'beyond' the 100% Depth limit. Also some games have very shallow/limited range that we might want to push a but further... I remember one that just barely looked like it was in 3D until I pushed MonitorSize down into the single digits([url=https://forums.geforce.com/default/topic/700536/]link[/url]) for just those types of issues I'd suggest just running a DepthHack script prior to the game because MonitorSizeOverride is always on until it's deleted. I could make a script to delete MonitorSizeOverride in the Registry I guess, if anyone's interested...
@EGY-SuperOne

No need to be sorry, I should be apologizing. I rewrote the end of that section to clarify it a bit more... originally I was referring to actual screen/monitor size(1/2 = 200%) but typed MonitorSize(1/2 = 100%) so that's where the confusion originally came from. I was meaning to reply to your post last night but I got side-tracked sorry about that.

Unfortunately when referring to MonitorSize, it's not always correct in the Registry so it makes it harder when discussing it... not everyone's 100% is equal as it probably would/should be if it were. So there's 2 main uses for this:

1) To correct for an incorrect MonitorSize Value in the Registry.

2) To go 'beyond' the 100% Depth limit.

Also some games have very shallow/limited range that we might want to push a but further... I remember one that just barely looked like it was in 3D until I pushed MonitorSize down into the single digits(link) for just those types of issues I'd suggest just running a DepthHack script prior to the game because MonitorSizeOverride is always on until it's deleted.

I could make a script to delete MonitorSizeOverride in the Registry I guess, if anyone's interested...
#44
Posted 09/26/2016 02:03 AM   
[quote="TsaebehT"] [quote="SnickerSnack"]Hi guys, just checking, does this work for Compatibility Mode, or real 3D only? Thanks[/quote]No, sorry... I've tried tons of things to find something that would work. Honestly I'd suggest looking into using [url=https://forums.geforce.com/default/topic/959175/]SuperDepth3D[/url] instead... it's so much more robust than CompatibilityMode.[/quote] I read a little of the SuperDepth thread, but it only works through 3DTV Play, right? It isn't a solution for my 27" monitor, right? I've never used my Plasma for gaming much due to input lag. I'm just more comfortable with the 27" ASUS.
TsaebehT said:

SnickerSnack said:Hi guys, just checking, does this work for Compatibility Mode, or real 3D only? Thanks
No, sorry... I've tried tons of things to find something that would work. Honestly I'd suggest looking into using SuperDepth3D instead... it's so much more robust than CompatibilityMode.


I read a little of the SuperDepth thread, but it only works through 3DTV Play, right? It isn't a solution for my 27" monitor, right? I've never used my Plasma for gaming much due to input lag. I'm just more comfortable with the 27" ASUS.

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#45
Posted 09/26/2016 10:10 PM   
  3 / 4    
Scroll To Top