Many thanks Helifax!
I am starting to test and began with AC: Odyssey. When I activated the patch with ctrl-shift-t, I got the audio cue, but f10 and f12 didn't seem to make any difference in the separation.
I alt-tabbed out of the game and found that CMU was generating a message along the lines of "couldn't activate conversion/separation"
Any ideas?
I am starting to test and began with AC: Odyssey. When I activated the patch with ctrl-shift-t, I got the audio cue, but f10 and f12 didn't seem to make any difference in the separation.
I alt-tabbed out of the game and found that CMU was generating a message along the lines of "couldn't activate conversion/separation"
[quote="TheBigDogma"]Many thanks Helifax!
I am starting to test and began with AC: Odyssey. When I activated the patch with ctrl-shift-t, I got the audio cue, but f10 and f12 didn't seem to make any difference in the separation.
I alt-tabbed out of the game and found that CMU was generating a message along the lines of "couldn't activate conversion/separation"
Any ideas?[/quote]
Are you running it "As Administrator" ? (And you did put the game's exe filename in the ini file.)
Edit:
I just tried AC:O and everything is working fine.
I am starting to test and began with AC: Odyssey. When I activated the patch with ctrl-shift-t, I got the audio cue, but f10 and f12 didn't seem to make any difference in the separation.
I alt-tabbed out of the game and found that CMU was generating a message along the lines of "couldn't activate conversion/separation"
Any ideas?
Are you running it "As Administrator" ? (And you did put the game's exe filename in the ini file.)
Edit:
I just tried AC:O and everything is working fine.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="TheBigDogma"]Sorry... I'm a dolt - forgot activating the game in the .ini.[/quote]
:)
For AC: Odyssey, I made this ini file:
[code]
[General]
; MAKE SURE THERE ARE NO SPACES in this section between "=" and the value!
; Name of the Game EXE
GameExecutable="ACOdyssey.exe"
; Auto start and Patch once the "GameExecutable" is found. (Delay: 10 seconds, to give time for the game to start and render.)
; Recommendation: Only set this to "true" WHEN you are happy with the shortcuts and the profile and you don't need to constantly re-load the ini file!
AutoStart=false
; Delay in Seconds between the game is started and it actually starts rendering.
; This must be updated with each game! (The Patching will fail, if we try to Patch too soon, as the driver is NOT loaded yet.)
; Hoewever it is still possible to manually enable it with "CTRL + SHIFT + T".
; A value of 0 will default to 10 seconds if "Autostart=true"
AutoStartDelay = 15
; Enable Nvidia 3D Vision Compatibility Mode Profile Update:
; False - don't update the Nvidia Profile. True - update the Nvidia Profile with the specified values.
; This will only happen when the "GameExecutable" is detected!
2DDEnableUpdates=true
; This value is also used in Nvidia 3D Vision Compatibility Mode. Most of the times a value of "0x00000001" is enough!
; However, it might not always be the case!
; By default the driver initialises this to 0x00000023!
; A value of 0x0 will be ignored and not written to the Profile.
StereoTexture = 0x00000023
; The magic value that tells how Compatibility Mode should work.
; For a list of possible values see http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings
; Or you can use Nvidia Inspector and look in an existing Profile for "0x709ADADA" and copy the value from there.
; A value of 0x0 will be ignored and not written to the Profile.
2DDHUDSettings=0x00000102
; Default Convergence for CM Mode.
; A value of 0.0 will be ignored and not written to the Profile.
; Convergence can be between 0.2 and 1.0. (Anything else and the driver will clamp it. Honestly there is no need for any other value).
2DDConvergence= 0.909160
; Comments that will appear in the Nvidia Overlay when CM is enabled.
; A value of ="" (empty string) will be ignored.
2DD_Notes="Powered by 3DVision CM Unleashed - made by Helifax."
[Key_Settings]
; See https://docs.microsoft.com/en-us/windows/desktop/inputdev/virtual-key-codes for the KEYBOARD VK_ keys!
; For XBOX Controller use the following keys:
; XINPUT_GAMEPAD_DPAD_UP
; XINPUT_GAMEPAD_DPAD_DOWN
; XINPUT_GAMEPAD_DPAD_LEFT
; XINPUT_GAMEPAD_DPAD_RIGHT
; XINPUT_GAMEPAD_START
; XINPUT_GAMEPAD_BACK
; XINPUT_GAMEPAD_LEFT_THUMB
; XINPUT_GAMEPAD_RIGHT_THUMB
; XINPUT_GAMEPAD_LEFT_SHOULDER
; XINPUT_GAMEPAD_RIGHT_SHOULDER
; XINPUT_GAMEPAD_A
; XINPUT_GAMEPAD_B
; XINPUT_GAMEPAD_X
; XINPUT_GAMEPAD_Y
; Usage: "NewKey(key, separation, convergence, type)".
; NewKey(
; - Virtual Key
; - Separation Factor
; - Convergence Value
; - Type:
; - once (all lower caps)
; - hold (all lower caps)
; - toggle (all lower caps)
;)
; Possible values:
; -1 - value is ignored
; Separation:
; - 1.0 means 100% of the current Separation.
; - 2.2 means 220% of the current Separation.
; Convergence:
; - values from 0.200 to 1.000 (The Driver CLAMPS between these values, and you don't need anything above or lower anyway.)
;
; Ex: NewKey(VK_F1, -1.0, 1.0, once) -> On key F1, don't set the separation, set convergence to 1.0, JUST once (when you press the key).
; Ex: NewKey(T, 1.0, -1.0, toggle) -> On key T, set 100% separation, don't set convergence, as a toggle (Pressing T again, will set you back to the previous values.)
; Ex: NewKey(XINPUT_GAMEPAD_LEFT_SHOULDER, 0.15, 0.22, hold) -> On XBOX controller Left Shoulder button, set 15% separation, 0.22 Convergence, AS LONG as you HOLD the button!
; 10% Separation
NewKey(VK_F10, 0.10, -1, once)
;220% Separation
NewKey(VK_F12, 2.5, -1, toggle)
; Game-Play Convergence + SEAPARATION 250%
NewKey(VK_F2, 2.5, 0.909160, once)
NewKey(XINPUT_GAMEPAD_RIGHT_THUMB, 2.5, 0.909160, once)
; MENUs
NewKey(VK_TAB, 0.50, -1.0, once)
NewKey(M, 0.50, -1.0, once)
NewKey(I, 0.50, -1.0, once)
; BACK TO GAMEPLAY
NewKey(VK_ESCAPE, 2.5, 0.909160, once)
; XBOX
NewKey(XINPUT_GAMEPAD_START, 0.50, -1.0, toggle)
NewKey(XINPUT_GAMEPAD_BACK, 0.50, -1.0, once)
[End]
[/code]
Maybe it will help you out:)
TheBigDogma said:Sorry... I'm a dolt - forgot activating the game in the .ini.
:)
For AC: Odyssey, I made this ini file:
[General]
; MAKE SURE THERE ARE NO SPACES in this section between "=" and the value!
; Name of the Game EXE
GameExecutable="ACOdyssey.exe"
; Auto start and Patch once the "GameExecutable" is found. (Delay: 10 seconds, to give time for the game to start and render.)
; Recommendation: Only set this to "true" WHEN you are happy with the shortcuts and the profile and you don't need to constantly re-load the ini file!
AutoStart=false
; Delay in Seconds between the game is started and it actually starts rendering.
; This must be updated with each game! (The Patching will fail, if we try to Patch too soon, as the driver is NOT loaded yet.)
; Hoewever it is still possible to manually enable it with "CTRL + SHIFT + T".
; A value of 0 will default to 10 seconds if "Autostart=true"
AutoStartDelay = 15
; Enable Nvidia 3D Vision Compatibility Mode Profile Update:
; False - don't update the Nvidia Profile. True - update the Nvidia Profile with the specified values.
; This will only happen when the "GameExecutable" is detected!
2DDEnableUpdates=true
; This value is also used in Nvidia 3D Vision Compatibility Mode. Most of the times a value of "0x00000001" is enough!
; However, it might not always be the case!
; By default the driver initialises this to 0x00000023!
; A value of 0x0 will be ignored and not written to the Profile.
StereoTexture = 0x00000023
; Or you can use Nvidia Inspector and look in an existing Profile for "0x709ADADA" and copy the value from there.
; A value of 0x0 will be ignored and not written to the Profile.
2DDHUDSettings=0x00000102
; Default Convergence for CM Mode.
; A value of 0.0 will be ignored and not written to the Profile.
; Convergence can be between 0.2 and 1.0. (Anything else and the driver will clamp it. Honestly there is no need for any other value).
2DDConvergence= 0.909160
; Comments that will appear in the Nvidia Overlay when CM is enabled.
; A value of ="" (empty string) will be ignored.
2DD_Notes="Powered by 3DVision CM Unleashed - made by Helifax."
; Possible values:
; -1 - value is ignored
; Separation:
; - 1.0 means 100% of the current Separation.
; - 2.2 means 220% of the current Separation.
; Convergence:
; - values from 0.200 to 1.000 (The Driver CLAMPS between these values, and you don't need anything above or lower anyway.)
;
; Ex: NewKey(VK_F1, -1.0, 1.0, once) -> On key F1, don't set the separation, set convergence to 1.0, JUST once (when you press the key).
; Ex: NewKey(T, 1.0, -1.0, toggle) -> On key T, set 100% separation, don't set convergence, as a toggle (Pressing T again, will set you back to the previous values.)
; Ex: NewKey(XINPUT_GAMEPAD_LEFT_SHOULDER, 0.15, 0.22, hold) -> On XBOX controller Left Shoulder button, set 15% separation, 0.22 Convergence, AS LONG as you HOLD the button!
; BACK TO GAMEPLAY
NewKey(VK_ESCAPE, 2.5, 0.909160, once)
; XBOX
NewKey(XINPUT_GAMEPAD_START, 0.50, -1.0, toggle)
NewKey(XINPUT_GAMEPAD_BACK, 0.50, -1.0, once)
[End]
Maybe it will help you out:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Made a new update to version 1.0.14:
- Fixed misspelled ini file name.
- Added Profile Support (a Folder Profiles will now hold all the ini files. At startup, it will ask you which ini file to load. this way you can have an ini file for each game you want to play!).
:)
Made a new update to version 1.0.14:
- Fixed misspelled ini file name.
- Added Profile Support (a Folder Profiles will now hold all the ini files. At startup, it will ask you which ini file to load. this way you can have an ini file for each game you want to play!).
:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Just found some time for testing (was v 1.0.12). Unfortunately the tool doesn`t work on my system: Win 7, driver 416.34.
I tried RE2 and AC:Odyssey. Ini files should be correct (GameExecutable="re2.exe" and GameExecutable="ACOdyssey.exe", used Your ini file above).
The tool also detects the game:
"Game executable re2.exe (x64) found!" or "Game executable ACOdyssey.exe (x64) found!"
When CM is activated and I press sh+ctrl+t I can't hear a plug sound and the tool shows permanently
"Detecting entry point for separation patching..."
but obviously without success. CPU usage changes from 0 (before game start) to 13% and RAM usage from 2.956K (before game start) to 3.464K and remains constant. Hotkeys for separation/convergence have no effect.
When I exit the game the tool says:
"Starting cleanup...
Application has exited! Nothing to restore!"
(so it didn't freeze)
I have to go to bed now so more feedback tomorrow.
Update: same results with v 1.0.14 (like 1.0.12 run as admin). For version 1.0.14 I got a message from Avast Antivirus but also with adding the tool to the withelist and disabling Avast I got the same results.
Using Your ini for AC:Odyssey updates the profile correctly, the overlay says "Powered by 3DVision CM Unleashed - made by Helifax.". But nevertheless it stucks with "Detecting entry point for separation patching..."
Just found some time for testing (was v 1.0.12). Unfortunately the tool doesn`t work on my system: Win 7, driver 416.34.
I tried RE2 and AC:Odyssey. Ini files should be correct (GameExecutable="re2.exe" and GameExecutable="ACOdyssey.exe", used Your ini file above).
The tool also detects the game:
"Game executable re2.exe (x64) found!" or "Game executable ACOdyssey.exe (x64) found!"
When CM is activated and I press sh+ctrl+t I can't hear a plug sound and the tool shows permanently
"Detecting entry point for separation patching..."
but obviously without success. CPU usage changes from 0 (before game start) to 13% and RAM usage from 2.956K (before game start) to 3.464K and remains constant. Hotkeys for separation/convergence have no effect.
When I exit the game the tool says:
"Starting cleanup...
Application has exited! Nothing to restore!"
(so it didn't freeze)
I have to go to bed now so more feedback tomorrow.
Update: same results with v 1.0.14 (like 1.0.12 run as admin). For version 1.0.14 I got a message from Avast Antivirus but also with adding the tool to the withelist and disabling Avast I got the same results.
Using Your ini for AC:Odyssey updates the profile correctly, the overlay says "Powered by 3DVision CM Unleashed - made by Helifax.". But nevertheless it stucks with "Detecting entry point for separation patching..."
My original display name is 3d4dd - for some reason Nvidia changed it..?!
[quote="ddr0390"]Just found some time for testing. Unfortunately the tool doesn`t work on my system: Win 7, driver 416.34.
I tried RE2 and AC:Odyssey. Ini files should be correct (GameExecutable="re2.exe" and GameExecutable="ACOdyssey.exe", used Your ini file above).
The tool also detects the game:
"Game executable re2.exe (x64) found!" or "Game executable ACOdyssey.exe (x64) found!"
When CM is activated and I press sh+ctrl+t I can't hear a plug sound and the tool shows permanently
"Detecting entry point for separation patching..."
but obviously without success. CPU usage changes from 0 (before game start) to 13% and RAM usage from 2.956K (before game start) to 3.464K and remains constant. Hotkeys for separation/convergence have no effect.
When I exit the game the tool says:
"Starting cleanup...
Application has exited! Nothing to restore!"
(so it didn't freeze)
I have to go to bed now so more feedback tomorrow.[/quote]
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.
Edit:
I just tested 416.34 on Windows 10 (Can't test it on Windows 7) and I see no problem.
Make sure you start the Patching AFTER the game started RENDERING. If you do it before, well yes, since the UDM driver (DLL) is not loaded, the signature scan will fail as it's not yet in the process address space. As for the other thing, the app doesn't hang. It did exactly that: Was scanning for a possible signature match. Normally it takes around 1 second to find it, but if it fails it can take some time until it finishes scanning the whole memory space used by the DLL (I can optimise this later).
ddr0390 said:Just found some time for testing. Unfortunately the tool doesn`t work on my system: Win 7, driver 416.34.
I tried RE2 and AC:Odyssey. Ini files should be correct (GameExecutable="re2.exe" and GameExecutable="ACOdyssey.exe", used Your ini file above).
The tool also detects the game:
"Game executable re2.exe (x64) found!" or "Game executable ACOdyssey.exe (x64) found!"
When CM is activated and I press sh+ctrl+t I can't hear a plug sound and the tool shows permanently
"Detecting entry point for separation patching..."
but obviously without success. CPU usage changes from 0 (before game start) to 13% and RAM usage from 2.956K (before game start) to 3.464K and remains constant. Hotkeys for separation/convergence have no effect.
When I exit the game the tool says:
"Starting cleanup...
Application has exited! Nothing to restore!"
(so it didn't freeze)
I have to go to bed now so more feedback tomorrow.
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.
Edit:
I just tested 416.34 on Windows 10 (Can't test it on Windows 7) and I see no problem.
Make sure you start the Patching AFTER the game started RENDERING. If you do it before, well yes, since the UDM driver (DLL) is not loaded, the signature scan will fail as it's not yet in the process address space. As for the other thing, the app doesn't hang. It did exactly that: Was scanning for a possible signature match. Normally it takes around 1 second to find it, but if it fails it can take some time until it finishes scanning the whole memory space used by the DLL (I can optimise this later).
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="Helifax"]
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.[/quote]
See my update of the post above ;)
I will install a new driver tomorrow!
Helifax said:
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.
See my update of the post above ;)
I will install a new driver tomorrow!
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Just getting back into Nvidia 3D after about a decade, mostly because of monitor changes. My last working Nvidia 3D driver is 162.50 I think on an old system. There was no compatibility mode then to the best of my knowledge.
I'm gathering, from your explanation of it in another thread here, CM is about the same thing as Tridef's power 3D or Vorpx's Z-buffer 3D as opposed to real or geometrically based 3D?
I just looked at your images cross-eyed, they are stunning to say the least. Much better than I have experienced with Tridef or VorpX fakery.
Waiting on a few things to arrive for my new Nvidia 3D set-up, I'm sure I will need to get some things sorted with the knowledge you provided. Thanks for all you do.
Just getting back into Nvidia 3D after about a decade, mostly because of monitor changes. My last working Nvidia 3D driver is 162.50 I think on an old system. There was no compatibility mode then to the best of my knowledge.
I'm gathering, from your explanation of it in another thread here, CM is about the same thing as Tridef's power 3D or Vorpx's Z-buffer 3D as opposed to real or geometrically based 3D?
I just looked at your images cross-eyed, they are stunning to say the least. Much better than I have experienced with Tridef or VorpX fakery.
Waiting on a few things to arrive for my new Nvidia 3D set-up, I'm sure I will need to get some things sorted with the knowledge you provided. Thanks for all you do.
[quote="ddr0390"][quote="Helifax"]
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.[/quote]
See my update of the post above ;)
I will install a new driver tomorrow![/quote]
Yes Avast normally scans it the first time since it's "new". Later it will stop as it's digitally signed (otherwise it will scan it every single time you run it Oo).
Yes, it would be quite interesting to see if a new driver will help out. If it will, I could then go back to Windows 7 (somehow again) and try that driver and see what is particular about it:)
Helifax said:
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.
See my update of the post above ;)
I will install a new driver tomorrow!
Yes Avast normally scans it the first time since it's "new". Later it will stop as it's digitally signed (otherwise it will scan it every single time you run it Oo).
Yes, it would be quite interesting to see if a new driver will help out. If it will, I could then go back to Windows 7 (somehow again) and try that driver and see what is particular about it:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Hi Helifax first I would like to say thank you and excellent work again.. I tried this in Elite Dangerous and DCS world so far..
Now I was getting some weird graphic asnamoly around edges of the Cockpit glass in both games.. I was wondering if this artifact is normal with CM Mode??
Other then that I was able to get shadows and everything working in DCS World which was awesome.. I am going to tinker around some more and find a depth/Convergance setting that looks good.. I have the separation good just need to toy with the convergance..
Thank you again and I am going to try it out in some other games too..
Hi Helifax first I would like to say thank you and excellent work again.. I tried this in Elite Dangerous and DCS world so far..
Now I was getting some weird graphic asnamoly around edges of the Cockpit glass in both games.. I was wondering if this artifact is normal with CM Mode??
Other then that I was able to get shadows and everything working in DCS World which was awesome.. I am going to tinker around some more and find a depth/Convergance setting that looks good.. I have the separation good just need to toy with the convergance..
Thank you again and I am going to try it out in some other games too..
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I am starting to test and began with AC: Odyssey. When I activated the patch with ctrl-shift-t, I got the audio cue, but f10 and f12 didn't seem to make any difference in the separation.
I alt-tabbed out of the game and found that CMU was generating a message along the lines of "couldn't activate conversion/separation"
Any ideas?
Are you running it "As Administrator" ? (And you did put the game's exe filename in the ini file.)
Edit:
I just tried AC:O and everything is working fine.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
:)
For AC: Odyssey, I made this ini file:
Maybe it will help you out:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
- Fixed misspelled ini file name.
- Added Profile Support (a Folder Profiles will now hold all the ini files. At startup, it will ask you which ini file to load. this way you can have an ini file for each game you want to play!).
:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
I tried RE2 and AC:Odyssey. Ini files should be correct (GameExecutable="re2.exe" and GameExecutable="ACOdyssey.exe", used Your ini file above).
The tool also detects the game:
"Game executable re2.exe (x64) found!" or "Game executable ACOdyssey.exe (x64) found!"
When CM is activated and I press sh+ctrl+t I can't hear a plug sound and the tool shows permanently
"Detecting entry point for separation patching..."
but obviously without success. CPU usage changes from 0 (before game start) to 13% and RAM usage from 2.956K (before game start) to 3.464K and remains constant. Hotkeys for separation/convergence have no effect.
When I exit the game the tool says:
"Starting cleanup...
Application has exited! Nothing to restore!"
(so it didn't freeze)
I have to go to bed now so more feedback tomorrow.
Update: same results with v 1.0.14 (like 1.0.12 run as admin). For version 1.0.14 I got a message from Avast Antivirus but also with adding the tool to the withelist and disabling Avast I got the same results.
Using Your ini for AC:Odyssey updates the profile correctly, the overlay says "Powered by 3DVision CM Unleashed - made by Helifax.". But nevertheless it stucks with "Detecting entry point for separation patching..."
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Out of curiosity, try to upgrade your driver to 417.x or 418.x and see if it works then. (I did test it on a range of drivers, but who knows... On windows 7 I only tested 391.35 and 418.71 or whatever.)
Also, do you have any anti-virus thingy that might interfere? I tried with Avast and regular Windows Defender.
Edit:
I just tested 416.34 on Windows 10 (Can't test it on Windows 7) and I see no problem.
Make sure you start the Patching AFTER the game started RENDERING. If you do it before, well yes, since the UDM driver (DLL) is not loaded, the signature scan will fail as it's not yet in the process address space. As for the other thing, the app doesn't hang. It did exactly that: Was scanning for a possible signature match. Normally it takes around 1 second to find it, but if it fails it can take some time until it finishes scanning the whole memory space used by the DLL (I can optimise this later).
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
See my update of the post above ;)
I will install a new driver tomorrow!
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I'm gathering, from your explanation of it in another thread here, CM is about the same thing as Tridef's power 3D or Vorpx's Z-buffer 3D as opposed to real or geometrically based 3D?
I just looked at your images cross-eyed, they are stunning to say the least. Much better than I have experienced with Tridef or VorpX fakery.
Waiting on a few things to arrive for my new Nvidia 3D set-up, I'm sure I will need to get some things sorted with the knowledge you provided. Thanks for all you do.
Yes Avast normally scans it the first time since it's "new". Later it will stop as it's digitally signed (otherwise it will scan it every single time you run it Oo).
Yes, it would be quite interesting to see if a new driver will help out. If it will, I could then go back to Windows 7 (somehow again) and try that driver and see what is particular about it:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Now I was getting some weird graphic asnamoly around edges of the Cockpit glass in both games.. I was wondering if this artifact is normal with CM Mode??
Other then that I was able to get shadows and everything working in DCS World which was awesome.. I am going to tinker around some more and find a depth/Convergance setting that looks good.. I have the separation good just need to toy with the convergance..
Thank you again and I am going to try it out in some other games too..
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