No problem at all ... I didn't need it before recent driver releases botched my setup but now I'm using it myself, personally I have my main one set the depth @ 50% and the MonitorSize also @ about 50% of my screen size, that way I can still go higher in-game if necessary. I've been using the 'Loops Until Changed' once since I created it and it's been working flawlessly, even with Alt+Tabs. I also added it to my Startup AutoHotKey script so whenever I want to run it all I have to do is hit Crtl+Shift+M and it runs.
No problem at all ... I didn't need it before recent driver releases botched my setup but now I'm using it myself, personally I have my main one set the depth @ 50% and the MonitorSize also @ about 50% of my screen size, that way I can still go higher in-game if necessary. I've been using the 'Loops Until Changed' once since I created it and it's been working flawlessly, even with Alt+Tabs. I also added it to my Startup AutoHotKey script so whenever I want to run it all I have to do is hit Crtl+Shift+M and it runs.
[quote="TsaebehT"][quote="Foulplay99"]Can anyone possibly link a decent pair of usb rechargeable DLP glasses that compare well against the 3D Vision 2 glasses?[/quote]I grabbed a couple of the cheaper ones to try out, I'll let you know how they work out when I get them.[/quote]
These sucked, I couldn't get far enough away from the screen to reduce the crosstalk enough (I can only get 9-10' from my screen ... and then there's a wall:) and at my normal playing distance (5-6') the crostalk is [u]extreme[/u] I couldn't play using them ... I don't think I would have even bothered ordering them if I had seen the second image of them but the person I got them from only had images like this:
[img]http://i.ebayimg.com/00/s/NDkwWDY0MA==/z/k38AAOxyVaBSsxEi/$_12.JPG[/img]
The angle of the lenses cause extreme crosstalk on my setup, if I turn my head to compensate for the ghosting in one lens then the other lens winds up ghosting even more so.
[img]http://i.ebayimg.com/00/s/NTg1WDc4MA==/z/LeoAAOxyNo9SsxEg/$_12.JPG[/img]
Foulplay99 said:Can anyone possibly link a decent pair of usb rechargeable DLP glasses that compare well against the 3D Vision 2 glasses?
I grabbed a couple of the cheaper ones to try out, I'll let you know how they work out when I get them.
These sucked, I couldn't get far enough away from the screen to reduce the crosstalk enough (I can only get 9-10' from my screen ... and then there's a wall:) and at my normal playing distance (5-6') the crostalk is extreme I couldn't play using them ... I don't think I would have even bothered ordering them if I had seen the second image of them but the person I got them from only had images like this:
The angle of the lenses cause extreme crosstalk on my setup, if I turn my head to compensate for the ghosting in one lens then the other lens winds up ghosting even more so.
[quote="TsaebehT"]If the game/Alt+Tab'n doesn't reset the MonitorSize then this one should work like a charm, you run it before running the game, it sets the MonitorSize and then watches the Value, when you run the game which changes the MonitorSize, it quickly resets it back to your desired Value and exits ... Save as bat, Run as Admin, and change the Value of $MonitorSize to either match, or lower than your display's size (eg. SET $MonitorSize=120 would be for a 120" DLP screen) ...
Loops Until Changed:
[code]@ECHO OFF
if [%$MIN%]==[$MIN] GOTO :MIN
SET $MIN=$MIN
START /MIN CMD /c "%~dpnx0"
GOTO :EOF
:MIN
SET $MonitorSize=50
SET /a "$MonitorSize=%$MonitorSize%*2"
CALL CMD /c EXIT /b %$MonitorSize%
SET $HEX=%=EXITCODE%
for /f "tokens=* delims=0" %%A in ("%$HEX%") DO (SET $HEX=%%A)
if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\
SET $KEY="HKLM\SOFTWARE\%$WOW%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSize"
REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f
:BEGIN
REG QUERY %$KEY% | FIND /i "0x%$HEX%" >NUL
if ERRORLEVEL 1 REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f& GOTO :EOF
if ERRORLEVEL 0 ECHO>NUL& GOTO BEGIN
[/code]
[/quote]
Thanks for this, it appears to work well for me.
Tomorrow I'm taking my H5360BD on the road for a dual 3D projector Dark Souls coop LAN party. Praise the Helixmod! I'll be using a smaller 65" screen, which only gets me about 2/3 max separation with depth set to 100%, so this sort of temporary easy fix is just what I needed. Normally I don't need it at home as with my receiver in the HDMI chain I evidently get a monitor size value of 55 inches, while I project on a 90" screen.
TsaebehT said:If the game/Alt+Tab'n doesn't reset the MonitorSize then this one should work like a charm, you run it before running the game, it sets the MonitorSize and then watches the Value, when you run the game which changes the MonitorSize, it quickly resets it back to your desired Value and exits ... Save as bat, Run as Admin, and change the Value of $MonitorSize to either match, or lower than your display's size (eg. SET $MonitorSize=120 would be for a 120" DLP screen) ...
Loops Until Changed:
@ECHO OFF
if [%$MIN%]==[$MIN] GOTO :MIN
SET $MIN=$MIN
START /MIN CMD /c "%~dpnx0"
GOTO :EOF
:MIN
SET $MonitorSize=50
SET /a "$MonitorSize=%$MonitorSize%*2"
CALL CMD /c EXIT /b %$MonitorSize%
SET $HEX=%=EXITCODE%
for /f "tokens=* delims=0" %%A in ("%$HEX%") DO (SET $HEX=%%A)
if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\
SET $KEY="HKLM\SOFTWARE\%$WOW%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSize"
REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f
:BEGIN
REG QUERY %$KEY% | FIND /i "0x%$HEX%" >NUL
if ERRORLEVEL 1 REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f& GOTO :EOF
if ERRORLEVEL 0 ECHO>NUL& GOTO BEGIN
Thanks for this, it appears to work well for me.
Tomorrow I'm taking my H5360BD on the road for a dual 3D projector Dark Souls coop LAN party. Praise the Helixmod! I'll be using a smaller 65" screen, which only gets me about 2/3 max separation with depth set to 100%, so this sort of temporary easy fix is just what I needed. Normally I don't need it at home as with my receiver in the HDMI chain I evidently get a monitor size value of 55 inches, while I project on a 90" screen.
Hi, I think I got it working but in game I do NOT see an increase in separation in the depth?? Should I get more separation with this file below:??
At a far Object the max separation is ONLY an Inch shouldn't it be more??
1.@ECHO OFF
2.if [%$MIN%]==[$MIN] GOTO :MIN
3.SET $MIN=$MIN
4.START /MIN CMD /c "%~dpnx0"
5.GOTO :EOF
6.:MIN
7.SET $MonitorSize=50
8.SET /a "$MonitorSize=%$MonitorSize%*2"
9.CALL CMD /c EXIT /b %$MonitorSize%
10.SET $HEX=%=EXITCODE%
11.for /f "tokens=* delims=0" %%A in ("%$HEX%") DO (SET $HEX=%%A)
12.if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\
13.SET $KEY="HKLM\SOFTWARE\%$WOW%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSize"
14.REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f
15.:BEGIN
16.REG QUERY %$KEY% | FIND /i "0x%$HEX%" >NUL
17.if ERRORLEVEL 1 REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f& GOTO :EOF
18.if ERRORLEVEL 0 ECHO>NUL& GOTO BEGIN
There shouldn't been any line numbers in the *.bat, they usually don't copy and paste. Anyway, reasons why it might just close are there's an error in the code(like line numbers, or a single line of code getting spread across two by wordwrap) or it can't write to the registry(running the Loop version would show ERROR: Access Denied but running the Change&Quit version would just Exit(I might be able to do something about that)) ... I updated my posts([url=https://forums.geforce.com/default/topic/673425/3d-vision/some-questions-regarding-acer-h5360-5360bd/post/4099076/#4099076]Loop Version[/url], [url=https://forums.geforce.com/default/topic/673425/3d-vision/some-questions-regarding-acer-h5360-5360bd/post/4100030/#4100030]Change&Quit Version[/url]) on the previous page with code that will unlock the keys and allow them to be written.
As far as the "if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\" goes that just checks if you're running a 32/64bit OS and adjust the script accordingly.
As far as getting more depth out of it that's different per each user's setup, I made the script so it works like NVIDIA's drivers(MonitorSize x 2 mainly for DLP users to be able to set up up their larger screen sizes) the DepthHack part of it is just setting the MonitorSize lower than you actual (Screen)MonitorSize and again this setting is based on your tastes but for instance you have an 80" screen, you could try setting the MonitorSize to about half your screen's size.
Set $MonitorSize=40
On my setup setting it to half my screen size winds up giving me too much depth if I max it out(100%) and if I set it at my screen size it's just about right.
There shouldn't been any line numbers in the *.bat, they usually don't copy and paste. Anyway, reasons why it might just close are there's an error in the code(like line numbers, or a single line of code getting spread across two by wordwrap) or it can't write to the registry(running the Loop version would show ERROR: Access Denied but running the Change&Quit version would just Exit(I might be able to do something about that)) ... I updated my posts(Loop Version, Change&Quit Version) on the previous page with code that will unlock the keys and allow them to be written.
As far as the "if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\" goes that just checks if you're running a 32/64bit OS and adjust the script accordingly.
As far as getting more depth out of it that's different per each user's setup, I made the script so it works like NVIDIA's drivers(MonitorSize x 2 mainly for DLP users to be able to set up up their larger screen sizes) the DepthHack part of it is just setting the MonitorSize lower than you actual (Screen)MonitorSize and again this setting is based on your tastes but for instance you have an 80" screen, you could try setting the MonitorSize to about half your screen's size.
Set $MonitorSize=40
On my setup setting it to half my screen size winds up giving me too much depth if I max it out(100%) and if I set it at my screen size it's just about right.
[quote="TsaebehT"]There shouldn't been any line numbers in the *.bat, they usually don't copy and paste. Anyway, reasons why it might just close are there's an error in the code(like line numbers, or a single line of code getting spread across two by wordwrap) or it can't write to the registry(running the Loop version would show ERROR: Access Denied but running the Change&Quit version would just Exit(I might be able to do something about that)) ... I updated my posts([url=https://forums.geforce.com/default/topic/673425/3d-vision/some-questions-regarding-acer-h5360-5360bd/post/4099076/#4099076]Loop Version[/url], [url=https://forums.geforce.com/default/topic/673425/3d-vision/some-questions-regarding-acer-h5360-5360bd/post/4100030/#4100030]Change&Quit Version[/url]) on the previous page with code that will unlock the keys and allow them to be written.
As far as the "if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\" goes that just checks if you're running a 32/64bit OS and adjust the script accordingly.
As far as getting more depth out of it that's different per each user's setup, I made the script so it works like NVIDIA's drivers(MonitorSize x 2 mainly for DLP users to be able to set up up their larger screen sizes) the DepthHack part of it is just setting the MonitorSize lower than you actual (Screen)MonitorSize and again this setting is based on your tastes but for instance you have an 80" screen, you could try setting the MonitorSize to about half your screen's size.
Set $MonitorSize=40
On my setup setting it to half my screen size winds up giving me too much depth if I max it out(100%) and if I set it at my screen size it's just about right.[/quote]
Dude This is AWESOME.. I found my Error I did NOT have that other file running too.. I have the separation now beyond an inch and all I can say is WOW IT looked more like I was there then ever before..
IF I was the President of NVidia I would fire all the 3D guys and Hire you to get this implemented.. Did I say WOW and How Awesome this little program is Geeze what I have been missing all these years..
I do use DLP Projectors and have a Triple Proj. Setup and I must say this is a MUST for ANYONE using a DLP PRoj. Dude I owe you a six pack or something.. Seriously when I get paid I can Paypal you some money for doing this or a six pack of your choice or something..This is Superb!! :)
TsaebehT said:There shouldn't been any line numbers in the *.bat, they usually don't copy and paste. Anyway, reasons why it might just close are there's an error in the code(like line numbers, or a single line of code getting spread across two by wordwrap) or it can't write to the registry(running the Loop version would show ERROR: Access Denied but running the Change&Quit version would just Exit(I might be able to do something about that)) ... I updated my posts(Loop Version, Change&Quit Version) on the previous page with code that will unlock the keys and allow them to be written.
As far as the "if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\" goes that just checks if you're running a 32/64bit OS and adjust the script accordingly.
As far as getting more depth out of it that's different per each user's setup, I made the script so it works like NVIDIA's drivers(MonitorSize x 2 mainly for DLP users to be able to set up up their larger screen sizes) the DepthHack part of it is just setting the MonitorSize lower than you actual (Screen)MonitorSize and again this setting is based on your tastes but for instance you have an 80" screen, you could try setting the MonitorSize to about half your screen's size.
Set $MonitorSize=40
On my setup setting it to half my screen size winds up giving me too much depth if I max it out(100%) and if I set it at my screen size it's just about right.
Dude This is AWESOME.. I found my Error I did NOT have that other file running too.. I have the separation now beyond an inch and all I can say is WOW IT looked more like I was there then ever before..
IF I was the President of NVidia I would fire all the 3D guys and Hire you to get this implemented.. Did I say WOW and How Awesome this little program is Geeze what I have been missing all these years..
I do use DLP Projectors and have a Triple Proj. Setup and I must say this is a MUST for ANYONE using a DLP PRoj. Dude I owe you a six pack or something.. Seriously when I get paid I can Paypal you some money for doing this or a six pack of your choice or something..This is Superb!! :)
Updated(8/9/15): Updated the Main, Loop and Prompt scripts(bats/zip) to throttle them back a little a few of you were complaining about CPU usage. The main/normal script is the one you should be using in most cases as it should only run before the game and exit once the game has started.
Updated(8/28/14): Apparently 'Run as Admin' doesn't like the @ symbols in the naming scheme either, updated the bats/zip ... and added a few very minor tweaks to the Scripts.
Updated(6/23/14): The auto-minimizing code wasn't working properly if they were run [s]from[/s] a directory that contained any spaces and they had an at symbol(@) in their names(@DepthHackEngine), adding double-quotes to the passed parameter seems to have fixed it! :)
The 'THNX' is more than enough, I'm just doing what I can to help ... luckily for you guys I'm a little obsessed with shell scripting. :)
I added a failsafe to the scripts so if it can't write the registry key it shows an error, pauses, and then quits. If it does this you need to run the 'Run(AsAdmin)First:' code. This only has to be run once to allow the key/value to be written(not everytime you want to use the DepthHack scripts), and most likely once again after any new driver installs.
I might eventually make a thread for these but for now they can go here, three new versions. The 2 from before, Loop & Once(Changed), just updated with the failsafe and a few other minor tweaks, plus a new 'Debug' version for games that aren't working properly with the 'Once' version.
Change the Value of $MonitorSize to either match, or lower than your display's size (eg. SET $MonitorSize=120 would be for a 120" DLP screen) ... or set it even lower for more Depth(Personally, I set it at half my screen size and set depth at 50% so I can go higher in-game if necessary)
[url=https://www.dropbox.com/s/xrc6i5zh6ryh8wl/%40DepthHackEngine.zip]ZippedUp&LinkedForTheLazy[/url] :)
[quote]Change the following line in the DepthHack*.bat to match your desired Value(eg. for a 120" Screen Set $MonitorSize=120 or set it lower for more Depth):
Set $MonitorSize=33
_AllowRunAsAdmin.bat(Optional*): Only needs to be run once and only once(not every time you want to use the DepthHack) ... as Admin, to allow the DepthHack* Scripts to write the MonitorSize Registry Value without the need to be Run as Admin every time. This way you can run a specific DepthHack from a hot key(AHK) and it seamlessly minimizes itself to the taskbar without the UAC prompt.
_DepthHackEngine.bat: Works with most games, run it before the game(via hot key or shortcut key) When the game starts the Drivers resets the MonitorSize Value and the Script detects it, sets it back to your desired Setting and exits. With most games the Drivers only Reset the Value once.
_DepthHackEngineLoop.bat: Some games will for some reason either keep triggering the Drivers to Reset the Value or at the very least do it more than once(FarCry3 after they added fake 3D), running this one will constantly loop, checking the Value and Setting it back when necessary.
_DepthHackEngineDebug.bat: Is the 'looping' version that outputs 'timestamps' to a file whenever the Registry MonitorSize Value is changed by the Drivers, 'for debugging' purposes.
_DepthHackEnginePrompt.bat: Same as _DepthHackEngine.bat but Prompts you to Enter a MonitorSize.
*if _AllowRunAsAdmin.bat isn't used to unlock the Permissions to the Registry Key then the DepthHack Scripts must be Run as Admin.
Notes:Use Ctrl+C(then Y and Enter) to Exit the Scripts properly, otherwise 'Reg/Find' may get 'stuck' continuously running in the Task Manager.
[/quote]Run(AsAdminOnceBeforeUsingDepthHackScriptsIfNecessary):
[code]@Echo Off
if Exist "%PROGRAMFILES(X86)%" Set $Wow=Wow6432Node\
> %TEMP%\Allow.txt (
Echo \Registry\Machine\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D [1 5 7 17]
Echo MonitorSize = REG_DWORD 0x00000666
)
:Loop
RegIni "%TEMP%\Allow.txt"||Echo Try Again?&&Pause&&Goto :Loop[/code]
DepthHackEngine:(RunsQueryOnce)
[code]@Echo Off
Title DepthHackEngine
if [%$Min%]==[Min] Goto :Loop
Set $MonitorSize=33
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 "MonitorSize"
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Set $Min=Min
Start "" /Min Cmd /c ""%~dpnx0""
Goto :Eof
:Loop
Title DepthHackEngine: Use Ctrl+C to Exit Properly
if [%Stasis%] NEQ [%Time:~0,10%] (
Set "Stasis=%Time:~0,10%"
Reg Query %$Key%|Find /i "0x%$Hex%">Nul
if errorlevel 1 Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f&&Goto:Eof
if errorlevel 0 Echo>Nul&&Goto :Loop
)
Goto:Loop
[/code]
DepthHackEngineLoop:(InfiniteQueryLoop)
[code]@Echo Off
Title DepthHackEngineLoop
if [%$Min%]==[Min] Goto :Loop
Set $MonitorSize=33
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 "MonitorSize"
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Set $Min=Min
Start "" /Min Cmd /c ""%~dpnx0""
Goto :Eof
:Loop
Title DepthHackEngine: Use Ctrl+C to Exit Properly
if [%Stasis%] NEQ [%Time:~0,10%] (
Set "Stasis=%Time:~0,10%"
Reg Query %$Key%|Find /i "0x%$Hex%">Nul
if errorlevel 1 Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f
if errorlevel 0 Echo>Nul&&Goto :Loop
)
Goto:Loop
[/code]
DepthHackEngineDebug(SeeBelow):
[code]@Echo Off
Title DepthHackEngineDebug
if [%$Min%]==[Min] Goto :Loop
if Exist DepthHackEngine.Log Del DepthHackEngine.Log
Set $MonitorSize=33
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 "MonitorSize"
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Set $Min=Min
Start "" /Min Cmd /c ""%~dpnx0""
Goto :Eof
:Loop
Title DepthHackEngine: Use Ctrl+C to Exit Properly
Reg Query %$Key%|Find /i "0x%$Hex%">Nul
if errorlevel 1 Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f&&Echo %TIME%>>DepthHackEngine.Log
if errorlevel 0 Echo>Nul&&Goto :Loop
[/code]
To use the Debug(Loop+Logging) version just run it, then run the game that isn't working with the main(RunsQueryOnce) version, after you're in-game quit out and post the timestamps in the DepthHackEngine.Log.edit: [s]I just found out there's an issue with the auto-minimizing part of the script that doesn't work well when run from 'Program Files (x86)', if running from within this directory remove the at symbol(@) from the filename of the batch file.[/s] Fixed! :)
Updated(8/9/15): Updated the Main, Loop and Prompt scripts(bats/zip) to throttle them back a little a few of you were complaining about CPU usage. The main/normal script is the one you should be using in most cases as it should only run before the game and exit once the game has started.
Updated(8/28/14): Apparently 'Run as Admin' doesn't like the @ symbols in the naming scheme either, updated the bats/zip ... and added a few very minor tweaks to the Scripts.
Updated(6/23/14): The auto-minimizing code wasn't working properly if they were run from a directory that contained any spaces and they had an at symbol(@) in their names(@DepthHackEngine), adding double-quotes to the passed parameter seems to have fixed it! :)
The 'THNX' is more than enough, I'm just doing what I can to help ... luckily for you guys I'm a little obsessed with shell scripting. :)
I added a failsafe to the scripts so if it can't write the registry key it shows an error, pauses, and then quits. If it does this you need to run the 'Run(AsAdmin)First:' code. This only has to be run once to allow the key/value to be written(not everytime you want to use the DepthHack scripts), and most likely once again after any new driver installs.
I might eventually make a thread for these but for now they can go here, three new versions. The 2 from before, Loop & Once(Changed), just updated with the failsafe and a few other minor tweaks, plus a new 'Debug' version for games that aren't working properly with the 'Once' version.
Change the Value of $MonitorSize to either match, or lower than your display's size (eg. SET $MonitorSize=120 would be for a 120" DLP screen) ... or set it even lower for more Depth(Personally, I set it at half my screen size and set depth at 50% so I can go higher in-game if necessary)
Change the following line in the DepthHack*.bat to match your desired Value(eg. for a 120" Screen Set $MonitorSize=120 or set it lower for more Depth):
Set $MonitorSize=33
_AllowRunAsAdmin.bat(Optional*): Only needs to be run once and only once(not every time you want to use the DepthHack) ... as Admin, to allow the DepthHack* Scripts to write the MonitorSize Registry Value without the need to be Run as Admin every time. This way you can run a specific DepthHack from a hot key(AHK) and it seamlessly minimizes itself to the taskbar without the UAC prompt.
_DepthHackEngine.bat: Works with most games, run it before the game(via hot key or shortcut key) When the game starts the Drivers resets the MonitorSize Value and the Script detects it, sets it back to your desired Setting and exits. With most games the Drivers only Reset the Value once.
_DepthHackEngineLoop.bat: Some games will for some reason either keep triggering the Drivers to Reset the Value or at the very least do it more than once(FarCry3 after they added fake 3D), running this one will constantly loop, checking the Value and Setting it back when necessary.
_DepthHackEngineDebug.bat: Is the 'looping' version that outputs 'timestamps' to a file whenever the Registry MonitorSize Value is changed by the Drivers, 'for debugging' purposes.
_DepthHackEnginePrompt.bat: Same as _DepthHackEngine.bat but Prompts you to Enter a MonitorSize.
*if _AllowRunAsAdmin.bat isn't used to unlock the Permissions to the Registry Key then the DepthHack Scripts must be Run as Admin.
Notes:Use Ctrl+C(then Y and Enter) to Exit the Scripts properly, otherwise 'Reg/Find' may get 'stuck' continuously running in the Task Manager.
@Echo Off
if Exist "%PROGRAMFILES(X86)%" Set $Wow=Wow6432Node\
> %TEMP%\Allow.txt (
Echo \Registry\Machine\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D [1 5 7 17]
Echo MonitorSize = REG_DWORD 0x00000666
)
:Loop
RegIni "%TEMP%\Allow.txt"||Echo Try Again?&&Pause&&Goto :Loop
DepthHackEngine:(RunsQueryOnce)
@Echo Off
Title DepthHackEngine
if [%$Min%]==[Min] Goto :Loop
Set $MonitorSize=33
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 "MonitorSize"
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Set $Min=Min
Start "" /Min Cmd /c ""%~dpnx0""
Goto :Eof
:Loop
Title DepthHackEngine: Use Ctrl+C to Exit Properly
if [%Stasis%] NEQ [%Time:~0,10%] (
Set "Stasis=%Time:~0,10%"
Reg Query %$Key%|Find /i "0x%$Hex%">Nul
if errorlevel 1 Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f&&Goto:Eof
if errorlevel 0 Echo>Nul&&Goto :Loop
)
Goto:Loop
DepthHackEngineLoop:(InfiniteQueryLoop)
@Echo Off
Title DepthHackEngineLoop
if [%$Min%]==[Min] Goto :Loop
Set $MonitorSize=33
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 "MonitorSize"
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Set $Min=Min
Start "" /Min Cmd /c ""%~dpnx0""
Goto :Eof
:Loop
Title DepthHackEngine: Use Ctrl+C to Exit Properly
if [%Stasis%] NEQ [%Time:~0,10%] (
Set "Stasis=%Time:~0,10%"
Reg Query %$Key%|Find /i "0x%$Hex%">Nul
if errorlevel 1 Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f
if errorlevel 0 Echo>Nul&&Goto :Loop
)
Goto:Loop
DepthHackEngineDebug(SeeBelow):
@Echo Off
Title DepthHackEngineDebug
if [%$Min%]==[Min] Goto :Loop
if Exist DepthHackEngine.Log Del DepthHackEngine.Log
Set $MonitorSize=33
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 "MonitorSize"
Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f||Pause&&Goto :Eof
Set $Min=Min
Start "" /Min Cmd /c ""%~dpnx0""
Goto :Eof
:Loop
Title DepthHackEngine: Use Ctrl+C to Exit Properly
Reg Query %$Key%|Find /i "0x%$Hex%">Nul
if errorlevel 1 Reg Add %$Key% /t REG_DWORD /d %$MonitorSize% /f&&Echo %TIME%>>DepthHackEngine.Log
if errorlevel 0 Echo>Nul&&Goto :Loop
To use the Debug(Loop+Logging) version just run it, then run the game that isn't working with the main(RunsQueryOnce) version, after you're in-game quit out and post the timestamps in the DepthHackEngine.Log.edit: I just found out there's an issue with the auto-minimizing part of the script that doesn't work well when run from 'Program Files (x86)', if running from within this directory remove the at symbol(@) from the filename of the batch file. Fixed! :)
Well I have to say Thank You again for the debug tool. Funny I ran it and the game worked is that what it is supposed to do??
I have the timestamps and here they are not sure what it means tho:
19:27:57.41
19:27:57.42
19:28:26.83
19:28:26.84
19:32:29.32
19:32:29.32
That is the entire log.. What does it mean??
No problem at all ... Yeah it's supposed to work, it's just the looping version plus logging. So it's constantly Querying the registry for a change to the MonitorSize and then setting it back to your setting, I personally don't like to have it constantly Querying(100s of times a sec) the registry but it's safer than constantly writing it(100s of times a sec).
Basically it means the drivers reset the MonitorSize value six times before the game actually started ... all the testing I did before releasing the first version of this, it only reset it once at the game's start. I'll have to look into it a bit more ... see if I can find a constant or a pattern.
Just curious, are you running the latest and (not so)greatest drivers? If you wouldn't mind running it a few more times here and there, to check if it's always six times, I could make it loop accordingly ... for that matter ... I could make a 'learning' version that logs the amount of times it's reset on the first run and then loops as many times accordingly after but something like that'd probably be better off run directly from each game's directory.
No problem at all ... Yeah it's supposed to work, it's just the looping version plus logging. So it's constantly Querying the registry for a change to the MonitorSize and then setting it back to your setting, I personally don't like to have it constantly Querying(100s of times a sec) the registry but it's safer than constantly writing it(100s of times a sec).
Basically it means the drivers reset the MonitorSize value six times before the game actually started ... all the testing I did before releasing the first version of this, it only reset it once at the game's start. I'll have to look into it a bit more ... see if I can find a constant or a pattern.
Just curious, are you running the latest and (not so)greatest drivers? If you wouldn't mind running it a few more times here and there, to check if it's always six times, I could make it loop accordingly ... for that matter ... I could make a 'learning' version that logs the amount of times it's reset on the first run and then loops as many times accordingly after but something like that'd probably be better off run directly from each game's directory.
I am running the 314.22 drivers. for me they are the last drivers that makes my Triplescreen work.. I did try the 324.27 but they where a little problematic 314.22 seems to be the best as far as triplescreen goes for me anyhow..
Yes I can run the debug tool a few more times if needed not a problem.. Also will I need to run it on any game or just the DCS World which that last test was run for??
I am running the 314.22 drivers. for me they are the last drivers that makes my Triplescreen work.. I did try the 324.27 but they where a little problematic 314.22 seems to be the best as far as triplescreen goes for me anyhow..
Yes I can run the debug tool a few more times if needed not a problem.. Also will I need to run it on any game or just the DCS World which that last test was run for??
Tsae,
It appears it does it more then 6 times I ran a long mission last night and there where about 20 or so values in there.. I just ran a hour mission and I saw these inputs in the log:
4:11:18.05
4:11:31.60
4:11:59.93
4:14:52.67
4:16:44.04
4:20:29.58
4:22:03.33
4:22:48.29
4:36:50.93
4:38:17.74
5:06:32.99
So it appears it runs more then 6 times according to the last 2 tests I ran.. IF I keep running the simulation that log would fill to infinity I believe..
It appears it does it more then 6 times I ran a long mission last night and there where about 20 or so values in there.. I just ran a hour mission and I saw these inputs in the log:
So it appears it runs more then 6 times according to the last 2 tests I ran.. IF I keep running the simulation that log would fill to infinity I believe..
Thanks, yeah I'll have to mess around with it if I ever get a chance, see if it happens on a single screen. The game may be switching resolutions, refresh rate, or between 2D and 3D ... something's triggering it. I've tried a ton of games and this is the first one I've seen behave this way, even the fake3d one I had as issue with stayed set once the game was started.
You said the non-debug/looping version was working for other games, just not this one(DCSW), right? You could either use the loop version or look into the other method of locking the registry key, I'd still suggest using my [url=https://forums.geforce.com/default/topic/519243/3d-vision/maximum-depth-hack-go-beyond-100-/post/4194134/#4194134]scripts[/url] for method that too ... I had issues with that method, one was not being able to take screenshots. If you're really interested in that method I could look into making a script that only 'temporarily' locks it while the game is running.
Thanks, yeah I'll have to mess around with it if I ever get a chance, see if it happens on a single screen. The game may be switching resolutions, refresh rate, or between 2D and 3D ... something's triggering it. I've tried a ton of games and this is the first one I've seen behave this way, even the fake3d one I had as issue with stayed set once the game was started.
You said the non-debug/looping version was working for other games, just not this one(DCSW), right? You could either use the loop version or look into the other method of locking the registry key, I'd still suggest using my scripts for method that too ... I had issues with that method, one was not being able to take screenshots. If you're really interested in that method I could look into making a script that only 'temporarily' locks it while the game is running.
WEll I run the Debug with DCSW and the 3D Seperation trick works fine.. I Don't need to run the debug with the other games I use ONLY with DCSW...
Well while this method for now is fine with me if you have an easier way to get this to work Im all ears but it really is not much to run a little bat file.. :)
I, do have a question How do I determine the MAX Seperation in games of the separation, as now I can go Beyond and inch of separation up too 3 inches..
I, figure either it is the Real Life Seperation you have in the Real World for me is 2inches.. To Determine this I put my Finger up at a Static Distant Tree or telephone pole I then close my right eye and put the left eye ligned up with the object. I then Open the other eye while closing the opposite and NOTE the Distance between the Static Target and my new mark for me came out to about 2 Inches, or is it the Seperation of your Pupils center? for me is 3Inches??
I am curious to know I have searched the Internet for an answer nobody seems to know..
WEll I run the Debug with DCSW and the 3D Seperation trick works fine.. I Don't need to run the debug with the other games I use ONLY with DCSW...
Well while this method for now is fine with me if you have an easier way to get this to work Im all ears but it really is not much to run a little bat file.. :)
I, do have a question How do I determine the MAX Seperation in games of the separation, as now I can go Beyond and inch of separation up too 3 inches..
I, figure either it is the Real Life Seperation you have in the Real World for me is 2inches.. To Determine this I put my Finger up at a Static Distant Tree or telephone pole I then close my right eye and put the left eye ligned up with the object. I then Open the other eye while closing the opposite and NOTE the Distance between the Static Target and my new mark for me came out to about 2 Inches, or is it the Seperation of your Pupils center? for me is 3Inches??
I am curious to know I have searched the Internet for an answer nobody seems to know..
Personally, I'm using a 65" DLP HDTV and go by the distance between my eyes(Interpupillary Distance or IPD as everyone calls it), roughly. I don't like having my Depth(Separation) maxed out, mine's set up so my Depth is at 50%, that way I can go higher or lower in-game if needed. It's also set up so that 50% gives me roughly my IPD at 'infinity' in games.
Usually I'll set my games up with my DLP Link glasses off and then tweak them to suit with the glasses on ... what ever looks right, in a first person perspective games I'll walk up to a wall and adjust Convergence so the texture on the wall is aligned and in a 3rd person perspective game I'll usually start off by aligning the character I'm playing as ... and then dial it back a bit, for some reason anymore than an inch or so of 'popout' bugs my eyes if I have to focus on it.
You can go higher than your IPD, your eyes can kind of 'adjust' to it, but I'm not sure you can ever actually focus on it. Easiest way to check is set it a bit higher and then focus on infinity and wave your hand back and forth blocking your view alternately ... if you see infinity shifting left and right you're not actually focusing on it, your eyes/mind is just adjusting to it. That said if you never bother to look at the mountains or the sky much, I don't really think it matters. Just tweak it to what ever looks good and is comfortable for you, sometimes an exaggerated 3D looks better than a realistic one.
Personally, I'm using a 65" DLP HDTV and go by the distance between my eyes(Interpupillary Distance or IPD as everyone calls it), roughly. I don't like having my Depth(Separation) maxed out, mine's set up so my Depth is at 50%, that way I can go higher or lower in-game if needed. It's also set up so that 50% gives me roughly my IPD at 'infinity' in games.
Usually I'll set my games up with my DLP Link glasses off and then tweak them to suit with the glasses on ... what ever looks right, in a first person perspective games I'll walk up to a wall and adjust Convergence so the texture on the wall is aligned and in a 3rd person perspective game I'll usually start off by aligning the character I'm playing as ... and then dial it back a bit, for some reason anymore than an inch or so of 'popout' bugs my eyes if I have to focus on it.
You can go higher than your IPD, your eyes can kind of 'adjust' to it, but I'm not sure you can ever actually focus on it. Easiest way to check is set it a bit higher and then focus on infinity and wave your hand back and forth blocking your view alternately ... if you see infinity shifting left and right you're not actually focusing on it, your eyes/mind is just adjusting to it. That said if you never bother to look at the mountains or the sky much, I don't really think it matters. Just tweak it to what ever looks good and is comfortable for you, sometimes an exaggerated 3D looks better than a realistic one.
I am currently having trouble with Elderscrolls online minimizing when using the 2 bat files here.. While it does fix the depth, I keep having the game minimize to desktop whilst clicking the mouse like in combat..
So far ONLY ESO Minimises to desktop whilst running the bat files.. I do know it has something to do with the bat files running because when I run the game without the bat files it is fine weird...
I was wondering what could be done to counter this issue whilst the bat files run and in ESO??
THNX for the fixes they have been very immersive so far..
I am currently having trouble with Elderscrolls online minimizing when using the 2 bat files here.. While it does fix the depth, I keep having the game minimize to desktop whilst clicking the mouse like in combat..
So far ONLY ESO Minimises to desktop whilst running the bat files.. I do know it has something to do with the bat files running because when I run the game without the bat files it is fine weird...
I was wondering what could be done to counter this issue whilst the bat files run and in ESO??
THNX for the fixes they have been very immersive so far..
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
These sucked, I couldn't get far enough away from the screen to reduce the crosstalk enough (I can only get 9-10' from my screen ... and then there's a wall:) and at my normal playing distance (5-6') the crostalk is extreme I couldn't play using them ... I don't think I would have even bothered ordering them if I had seen the second image of them but the person I got them from only had images like this:
The angle of the lenses cause extreme crosstalk on my setup, if I turn my head to compensate for the ghosting in one lens then the other lens winds up ghosting even more so.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Thanks for this, it appears to work well for me.
Tomorrow I'm taking my H5360BD on the road for a dual 3D projector Dark Souls coop LAN party. Praise the Helixmod! I'll be using a smaller 65" screen, which only gets me about 2/3 max separation with depth set to 100%, so this sort of temporary easy fix is just what I needed. Normally I don't need it at home as with my receiver in the HDMI chain I evidently get a monitor size value of 55 inches, while I project on a 90" screen.
At a far Object the max separation is ONLY an Inch shouldn't it be more??
1.@ECHO OFF
2.if [%$MIN%]==[$MIN] GOTO :MIN
3.SET $MIN=$MIN
4.START /MIN CMD /c "%~dpnx0"
5.GOTO :EOF
6.:MIN
7.SET $MonitorSize=50
8.SET /a "$MonitorSize=%$MonitorSize%*2"
9.CALL CMD /c EXIT /b %$MonitorSize%
10.SET $HEX=%=EXITCODE%
11.for /f "tokens=* delims=0" %%A in ("%$HEX%") DO (SET $HEX=%%A)
12.if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\
13.SET $KEY="HKLM\SOFTWARE\%$WOW%NVIDIA Corporation\Global\Stereo3D" /v "MonitorSize"
14.REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f
15.:BEGIN
16.REG QUERY %$KEY% | FIND /i "0x%$HEX%" >NUL
17.if ERRORLEVEL 1 REG ADD %$KEY% /t REG_DWORD /d %$MonitorSize% /f& GOTO :EOF
18.if ERRORLEVEL 0 ECHO>NUL& GOTO BEGIN
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
As far as the "if EXIST "%PROGRAMFILES(X86)%" SET $WOW=Wow6432Node\" goes that just checks if you're running a 32/64bit OS and adjust the script accordingly.
As far as getting more depth out of it that's different per each user's setup, I made the script so it works like NVIDIA's drivers(MonitorSize x 2 mainly for DLP users to be able to set up up their larger screen sizes) the DepthHack part of it is just setting the MonitorSize lower than you actual (Screen)MonitorSize and again this setting is based on your tastes but for instance you have an 80" screen, you could try setting the MonitorSize to about half your screen's size.
Set $MonitorSize=40
On my setup setting it to half my screen size winds up giving me too much depth if I max it out(100%) and if I set it at my screen size it's just about right.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Dude This is AWESOME.. I found my Error I did NOT have that other file running too.. I have the separation now beyond an inch and all I can say is WOW IT looked more like I was there then ever before..
IF I was the President of NVidia I would fire all the 3D guys and Hire you to get this implemented.. Did I say WOW and How Awesome this little program is Geeze what I have been missing all these years..
I do use DLP Projectors and have a Triple Proj. Setup and I must say this is a MUST for ANYONE using a DLP PRoj. Dude I owe you a six pack or something.. Seriously when I get paid I can Paypal you some money for doing this or a six pack of your choice or something..This is Superb!! :)
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Updated(8/28/14): Apparently 'Run as Admin' doesn't like the @ symbols in the naming scheme either, updated the bats/zip ... and added a few very minor tweaks to the Scripts.
Updated(6/23/14): The auto-minimizing code wasn't working properly if they were run
froma directory that contained any spaces and they had an at symbol(@) in their names(@DepthHackEngine), adding double-quotes to the passed parameter seems to have fixed it! :)The 'THNX' is more than enough, I'm just doing what I can to help ... luckily for you guys I'm a little obsessed with shell scripting. :)
I added a failsafe to the scripts so if it can't write the registry key it shows an error, pauses, and then quits. If it does this you need to run the 'Run(AsAdmin)First:' code. This only has to be run once to allow the key/value to be written(not everytime you want to use the DepthHack scripts), and most likely once again after any new driver installs.
I might eventually make a thread for these but for now they can go here, three new versions. The 2 from before, Loop & Once(Changed), just updated with the failsafe and a few other minor tweaks, plus a new 'Debug' version for games that aren't working properly with the 'Once' version.
Change the Value of $MonitorSize to either match, or lower than your display's size (eg. SET $MonitorSize=120 would be for a 120" DLP screen) ... or set it even lower for more Depth(Personally, I set it at half my screen size and set depth at 50% so I can go higher in-game if necessary)
ZippedUp&LinkedForTheLazy :)
Run(AsAdminOnceBeforeUsingDepthHackScriptsIfNecessary):
DepthHackEngine:(RunsQueryOnce)
DepthHackEngineLoop:(InfiniteQueryLoop)
DepthHackEngineDebug(SeeBelow):
To use the Debug(Loop+Logging) version just run it, then run the game that isn't working with the main(RunsQueryOnce) version, after you're in-game quit out and post the timestamps in the DepthHackEngine.Log.edit:
I just found out there's an issue with the auto-minimizing part of the script that doesn't work well when run from 'Program Files (x86)', if running from within this directory remove the at symbol(@) from the filename of the batch file.Fixed! :)[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
I have the timestamps and here they are not sure what it means tho:
19:27:57.41
19:27:57.42
19:28:26.83
19:28:26.84
19:32:29.32
19:32:29.32
That is the entire log.. What does it mean??
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Basically it means the drivers reset the MonitorSize value six times before the game actually started ... all the testing I did before releasing the first version of this, it only reset it once at the game's start. I'll have to look into it a bit more ... see if I can find a constant or a pattern.
Just curious, are you running the latest and (not so)greatest drivers? If you wouldn't mind running it a few more times here and there, to check if it's always six times, I could make it loop accordingly ... for that matter ... I could make a 'learning' version that logs the amount of times it's reset on the first run and then loops as many times accordingly after but something like that'd probably be better off run directly from each game's directory.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Yes I can run the debug tool a few more times if needed not a problem.. Also will I need to run it on any game or just the DCS World which that last test was run for??
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
It appears it does it more then 6 times I ran a long mission last night and there where about 20 or so values in there.. I just ran a hour mission and I saw these inputs in the log:
4:11:18.05
4:11:31.60
4:11:59.93
4:14:52.67
4:16:44.04
4:20:29.58
4:22:03.33
4:22:48.29
4:36:50.93
4:38:17.74
5:06:32.99
So it appears it runs more then 6 times according to the last 2 tests I ran.. IF I keep running the simulation that log would fill to infinity I believe..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
You said the non-debug/looping version was working for other games, just not this one(DCSW), right? You could either use the loop version or look into the other method of locking the registry key, I'd still suggest using my scripts for method that too ... I had issues with that method, one was not being able to take screenshots. If you're really interested in that method I could look into making a script that only 'temporarily' locks it while the game is running.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Well while this method for now is fine with me if you have an easier way to get this to work Im all ears but it really is not much to run a little bat file.. :)
I, do have a question How do I determine the MAX Seperation in games of the separation, as now I can go Beyond and inch of separation up too 3 inches..
I, figure either it is the Real Life Seperation you have in the Real World for me is 2inches.. To Determine this I put my Finger up at a Static Distant Tree or telephone pole I then close my right eye and put the left eye ligned up with the object. I then Open the other eye while closing the opposite and NOTE the Distance between the Static Target and my new mark for me came out to about 2 Inches, or is it the Seperation of your Pupils center? for me is 3Inches??
I am curious to know I have searched the Internet for an answer nobody seems to know..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Usually I'll set my games up with my DLP Link glasses off and then tweak them to suit with the glasses on ... what ever looks right, in a first person perspective games I'll walk up to a wall and adjust Convergence so the texture on the wall is aligned and in a 3rd person perspective game I'll usually start off by aligning the character I'm playing as ... and then dial it back a bit, for some reason anymore than an inch or so of 'popout' bugs my eyes if I have to focus on it.
You can go higher than your IPD, your eyes can kind of 'adjust' to it, but I'm not sure you can ever actually focus on it. Easiest way to check is set it a bit higher and then focus on infinity and wave your hand back and forth blocking your view alternately ... if you see infinity shifting left and right you're not actually focusing on it, your eyes/mind is just adjusting to it. That said if you never bother to look at the mountains or the sky much, I don't really think it matters. Just tweak it to what ever looks good and is comfortable for you, sometimes an exaggerated 3D looks better than a realistic one.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
So far ONLY ESO Minimises to desktop whilst running the bat files.. I do know it has something to do with the bat files running because when I run the game without the bat files it is fine weird...
I was wondering what could be done to counter this issue whilst the bat files run and in ESO??
THNX for the fixes they have been very immersive so far..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit