3D Vision Compatibility Mode "Unleashed"
  20 / 25    
Just tried this tool for the first time, and here were my results: -Destiny 2: Load fine, but there is practically no depth. Definitely some, but not worth playing like that, IMO. The separation keys work, but the image stays mostly flat, like the depth buffer isn't really adding much, if any scaling to the separation (everything just gets separated by the same amount). It also had the eyes reversed, and I had to wear my glasses upside down. -The Division 2 (beta) and Vermintide 2: Tool cannot find place to patch separation and convergence values (f*cking EAC) -The Division 1: This game had CM working at launch, but since a patch at some point although I could get CM to load there would be absolutely 0 separation. Just tried with CMU and same result. When I print the separation and convergence values to the tool it has a -NAN value -AC Origins: First game where it kinda works. I can get decent and adjustable separation, but if certain things are present (like a dust cloud in one of the first areas) then it snaps to 0 separation until I move the camera away. Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections. I'm using the default profile settings on the default driver profiles for each game. Is there still a bit of driver profile hacking or profile swapping involved in getting a proper baseline for CM mode, and then use this tool to tweak things further? If so, do we have a compendum on what are some common good profiles that are used for when trying out profile swaps? Does it mainly come down to the 2DDHUDSettings value which determine how the CM will work? I vaguely recall trying out different values there back in the day, and it would have some impact on how things rendered (eg. whether the HUD would be at screen depth or pushed into depth), but I wasn't sure if that was just a result of it adjusting the separation and convergence values which we now have access to in the tool and whether that's not really needed to be messed with further. I'll start reading through this thread to see if anyone else has reported anything similar to these and any other solutions, but if anyone has any feedback that would be great.
Just tried this tool for the first time, and here were my results:

-Destiny 2: Load fine, but there is practically no depth. Definitely some, but not worth playing like that, IMO. The separation keys work, but the image stays mostly flat, like the depth buffer isn't really adding much, if any scaling to the separation (everything just gets separated by the same amount). It also had the eyes reversed, and I had to wear my glasses upside down.
-The Division 2 (beta) and Vermintide 2: Tool cannot find place to patch separation and convergence values (f*cking EAC)
-The Division 1: This game had CM working at launch, but since a patch at some point although I could get CM to load there would be absolutely 0 separation. Just tried with CMU and same result. When I print the separation and convergence values to the tool it has a -NAN value
-AC Origins: First game where it kinda works. I can get decent and adjustable separation, but if certain things are present (like a dust cloud in one of the first areas) then it snaps to 0 separation until I move the camera away. Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections.

I'm using the default profile settings on the default driver profiles for each game. Is there still a bit of driver profile hacking or profile swapping involved in getting a proper baseline for CM mode, and then use this tool to tweak things further? If so, do we have a compendum on what are some common good profiles that are used for when trying out profile swaps? Does it mainly come down to the 2DDHUDSettings value which determine how the CM will work? I vaguely recall trying out different values there back in the day, and it would have some impact on how things rendered (eg. whether the HUD would be at screen depth or pushed into depth), but I wasn't sure if that was just a result of it adjusting the separation and convergence values which we now have access to in the tool and whether that's not really needed to be messed with further.

I'll start reading through this thread to see if anyone else has reported anything similar to these and any other solutions, but if anyone has any feedback that would be great.

3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot

Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king

Posted 03/02/2019 09:32 PM   
[quote="DJ-RK"]Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections[/quote]You really gonna pissed Helifax there... Just use the Cyde Frustum, dude ! (See the CMU link in my signature) [quote="Helifax"][color="orange"]If people refuse to read, what can I do ? :)[/color][/quote] First post: [quote="Helifax"][color="orange"]Important: Adjust your in-game "Frustum" (CTRL+F11 by default) NOT TO STRETCH the image! By default the image is a bit stretched in CM (You can't see it since 100% NVidia separation is very low, but is very visible at higher depths). If you fail to do this, due to the stretching the result will be bad and can be headache inducing![/color][/quote] .
DJ-RK said:Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections
You really gonna pissed Helifax there...

Just use the Cyde Frustum, dude ! (See the CMU link in my signature)


Helifax said:If people refuse to read, what can I do ? :)


First post:
Helifax said:Important:
Adjust your in-game "Frustum" (CTRL+F11 by default) NOT TO STRETCH the image! By default the image is a bit stretched in CM (You can't see it since 100% NVidia separation is very low, but is very visible at higher depths).
If you fail to do this, due to the stretching the result will be bad and can be headache inducing!




.
[quote="DJ-RK"] -AC Origins: ... then it snaps to 0 separation until I move the camera away. Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections. I[/quote] Snaps to 0 is typical in AC games with CM, it's cause by anti-aliasing, you have to change your AA settings. For the strong distorsion, you just have to Ctrl F11 and then it's gone ;)
DJ-RK said:
-AC Origins: ... then it snaps to 0 separation until I move the camera away. Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections.

I

Snaps to 0 is typical in AC games with CM, it's cause by anti-aliasing, you have to change your AA settings.

For the strong distorsion, you just have to Ctrl F11 and then it's gone ;)

http://photos.3dvisionlive.com/chtiblue/album/530b52d4cb85770d6e000049/3Dvision with 55" LG OLED EG920 interlieved 3D (3840x2160) overide mode, GTX 2080 Ti XC Ultra EVGA, core i5 @4.3GHz, 16Gb@2130, windows 7&10 64bit, Dolby Atmos 5.1.4 Marantz 6010 AVR

Posted 03/02/2019 09:47 PM   
[quote="Dugom"][quote="DJ-RK"]Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections[/quote]You really gonna pissed Helifax there... Just use the Cyde Frustum, dude ! (See the CMU link in my signature) [quote="Helifax"][color="orange"]If people refuse to read, what can I do ? :)[/color][/quote] .[/quote] Nope, that's not it. I did cycle through the frustum options and make sure the frustum was set to not stretched. Appreciate the help, don't appreciate the assumption and condescending tone though. ;) [quote="chtiblue"][quote="DJ-RK"] -AC Origins: ... then it snaps to 0 separation until I move the camera away. Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections. I[/quote] Snaps to 0 is typical in AC games with CM, it's cause by anti-aliasing, you have to change your AA settings. For the strong distorsion, you just have to Ctrl F11 and then it's gone ;)[/quote] Thanks. I just tried Helifax's AC Odyssey profile and that got Origins working pretty good (including the fix for the bars on the side. Probably due to the StereoTexture setting of 0x00000023, rather than the default 0x00000001).. I was still get the occasional snap to 0 separation, but I'll try disabling AA with your suggestion.
Dugom said:
DJ-RK said:Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections
You really gonna pissed Helifax there...

Just use the Cyde Frustum, dude ! (See the CMU link in my signature)


Helifax said:If people refuse to read, what can I do ? :)





.


Nope, that's not it. I did cycle through the frustum options and make sure the frustum was set to not stretched. Appreciate the help, don't appreciate the assumption and condescending tone though. ;)

chtiblue said:
DJ-RK said:
-AC Origins: ... then it snaps to 0 separation until I move the camera away. Also, on both the left and right sides of the screen there is a strong distortion, similar to how CM halos look, but it's also like a mirror of what's on the screen right beside those sections.

I

Snaps to 0 is typical in AC games with CM, it's cause by anti-aliasing, you have to change your AA settings.

For the strong distorsion, you just have to Ctrl F11 and then it's gone ;)



Thanks. I just tried Helifax's AC Odyssey profile and that got Origins working pretty good (including the fix for the bars on the side. Probably due to the StereoTexture setting of 0x00000023, rather than the default 0x00000001).. I was still get the occasional snap to 0 separation, but I'll try disabling AA with your suggestion.

3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot

Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king

Posted 03/02/2019 09:55 PM   
[quote="DJ-RK"]Appreciate the help, don't appreciate the assumption and condescending tone though. ;)[/quote]Sorry... .
DJ-RK said:Appreciate the help, don't appreciate the assumption and condescending tone though. ;)
Sorry...


.
[quote="chtiblue"]Snaps to 0 is typical in AC games with CM, it's cause by anti-aliasing, you have to change your AA settings. For the strong distorsion, you just have to Ctrl F11 and then it's gone ;)[/quote] Oh Snap!! I'm making a mental note of this for future use, Thanx for posting this.
chtiblue said:Snaps to 0 is typical in AC games with CM, it's cause by anti-aliasing, you have to change your AA settings.

For the strong distorsion, you just have to Ctrl F11 and then it's gone ;)


Oh Snap!!

I'm making a mental note of this for future use, Thanx for posting this.

Posted 03/02/2019 09:58 PM   
[quote="Dugom"][quote="DJ-RK"]Appreciate the help, don't appreciate the assumption and condescending tone though. ;)[/quote]Sorry... .[/quote] Apology accepted. I know things can get a little touchy around here, and you were likely trying to make it so Helifax wouldn't have to be bothered and frustrated to respond accordingly, which was a noble intention! ;) Edit: Oh, and have an apology from me as well for being a little touchy myself.
Dugom said:
DJ-RK said:Appreciate the help, don't appreciate the assumption and condescending tone though. ;)
Sorry...


.


Apology accepted. I know things can get a little touchy around here, and you were likely trying to make it so Helifax wouldn't have to be bothered and frustrated to respond accordingly, which was a noble intention! ;)

Edit: Oh, and have an apology from me as well for being a little touchy myself.

3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot

Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king

Posted 03/02/2019 10:18 PM   
Some very interesting results you guys are getting! I am collecting them for future reference (In most games a stereoTexture = 1 seemed to be enough for CM, but it seems 0x23 is still required, found a couple of games needing that as well! I will update the default ini with 0x23 for future reference). A snap to separation 0 is indeed that: the depth buffer gets lost. I found 2 ways to avoid that: 1. Change AA setting (which was noted already) 2. In newer games that support dynamic resolution scale, SET THE RESOLUTION TO ANYTHING but 100% (Ex: 90% or 110% and it works fine - Resident Evil 2 comes to mind and is doing this).
Some very interesting results you guys are getting!
I am collecting them for future reference (In most games a stereoTexture = 1 seemed to be enough for CM, but it seems 0x23 is still required, found a couple of games needing that as well! I will update the default ini with 0x23 for future reference).

A snap to separation 0 is indeed that: the depth buffer gets lost.
I found 2 ways to avoid that:

1. Change AA setting (which was noted already)
2. In newer games that support dynamic resolution scale, SET THE RESOLUTION TO ANYTHING but 100% (Ex: 90% or 110% and it works fine - Resident Evil 2 comes to mind and is doing this).

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)

Posted 03/03/2019 12:15 AM   
@Dugom: Forgot to mention. Many thanks for your guide here: [url]https://forums.geforce.com/default/topic/1097032/3d-vision/3d-vision-compatibility-mode-quot-unleashed-quot-/post/6000537/#6000537[/url] I'll make an update on the OP with it;)
@Dugom:

Forgot to mention. Many thanks for your guide here:
https://forums.geforce.com/default/topic/1097032/3d-vision/3d-vision-compatibility-mode-quot-unleashed-quot-/post/6000537/#6000537

I'll make an update on the OP with 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)

Posted 03/03/2019 12:17 AM   
[quote="Helifax"]@Dugom: Forgot to mention. Many thanks for your guide[/quote]If it helps, then I'm glad. I think your first post is great. For some it really is because they like/need the informations, but for most it is to much at the same time, so they get lost and quit or skim/cursory read it from lack of time/motivation... I probably hate that as much as you do but that's how people are. All they wanna do is play and right away ! And I do understand them. Time is not to be wasted. So to help those, I try to be as precise and consive as I can, to get to the point they need. They'll apreciate that, I hope. .
Helifax said:@Dugom:
Forgot to mention. Many thanks for your guide
If it helps, then I'm glad.

I think your first post is great. For some it really is because they like/need the informations, but for most it is to much at the same time, so they get lost and quit or skim/cursory read it from lack of time/motivation...

I probably hate that as much as you do but that's how people are.

All they wanna do is play and right away ! And I do understand them. Time is not to be wasted.

So to help those, I try to be as precise and consive as I can, to get to the point they need. They'll apreciate that, I hope.




.
So turning off AA was the key to getting Destiny 2 working properly. I don't actually recall ever reading about AA affecting CM either here, or anywhere else, and I definitely have skimmed through the entire thread throughout today. It probably has been mentioned somewhere, but you might want to add that to the front page of this post as well or maybe even in the in tool instructions to save a few headaches. Also, I found more games with the side bands (Anthem and Destiny 2), and I think I now understand what Dugom was trying to say earlier, because using the frustum cycle options the 2 stretch modes pushes the bands offscreen and the 2nd mode doesn't look too bad. I just found it conflicting that in Helifax's instructions (which Dugom had quoted and said I didn't read/follow) he says NOT to use the stretched frustum modes, and I was certain that I had read prior and followed Heli's instructions properly, because the bands are there in the unstretched mode. So a bit of confusion from all that, sorry again for getting defensive/uptight about it. So, with that said, Helifax, assuming that those side bands are probably a natural product of CM mode and present in every game, are you actually suggesting that we play with those bands to preserve the game's aspect ratio (not sure if "aspect ratio" is the correct term for it)? Because I actually think that's down a bit more of a personal preference. I mean, yeah, the first stretched mode looks terrible (can't imagine anyone liking that setting), but the 2nd one almost isn't noticeable and gets rid of those bands (which to me definitely are noticeable)... in fact, I think that's actually what I saw when I loaded AC: Origins the 2nd time with your profile. It probably didn't elimintate the side bands like I thought, but rather it probably just loaded into that stretched mode and I didn't realize it was stretched because it looked ok (hope that makes sense). Meanwhile, I could definitely understand someone preferring not to distort the main image by any form of stretching and able to tolerate the side bands by focusing on the middle... so yeah, I think that comes down to personal preference. Anyway, I got a lot of my answers answered through all this. Thanks to those who responded, and a major thanks to Helifax for another awesome piece of work from him.
So turning off AA was the key to getting Destiny 2 working properly. I don't actually recall ever reading about AA affecting CM either here, or anywhere else, and I definitely have skimmed through the entire thread throughout today. It probably has been mentioned somewhere, but you might want to add that to the front page of this post as well or maybe even in the in tool instructions to save a few headaches.

Also, I found more games with the side bands (Anthem and Destiny 2), and I think I now understand what Dugom was trying to say earlier, because using the frustum cycle options the 2 stretch modes pushes the bands offscreen and the 2nd mode doesn't look too bad. I just found it conflicting that in Helifax's instructions (which Dugom had quoted and said I didn't read/follow) he says NOT to use the stretched frustum modes, and I was certain that I had read prior and followed Heli's instructions properly, because the bands are there in the unstretched mode. So a bit of confusion from all that, sorry again for getting defensive/uptight about it.

So, with that said, Helifax, assuming that those side bands are probably a natural product of CM mode and present in every game, are you actually suggesting that we play with those bands to preserve the game's aspect ratio (not sure if "aspect ratio" is the correct term for it)? Because I actually think that's down a bit more of a personal preference.

I mean, yeah, the first stretched mode looks terrible (can't imagine anyone liking that setting), but the 2nd one almost isn't noticeable and gets rid of those bands (which to me definitely are noticeable)... in fact, I think that's actually what I saw when I loaded AC: Origins the 2nd time with your profile. It probably didn't elimintate the side bands like I thought, but rather it probably just loaded into that stretched mode and I didn't realize it was stretched because it looked ok (hope that makes sense). Meanwhile, I could definitely understand someone preferring not to distort the main image by any form of stretching and able to tolerate the side bands by focusing on the middle... so yeah, I think that comes down to personal preference.

Anyway, I got a lot of my answers answered through all this. Thanks to those who responded, and a major thanks to Helifax for another awesome piece of work from him.

3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot

Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king

Posted 03/03/2019 03:13 AM   
[quote="DJ-RK"]Also, I found more games with the side bands (Anthem and Destiny 2), and I think I now understand what Dugom was trying to say earlier, because using the frustum cycle options the 2 stretch modes pushes the bands offscreen and the 2nd mode doesn't look too bad. I just found it conflicting that in Helifax's instructions (which Dugom had quoted and said I didn't read/follow) he says NOT to use the stretched frustum modes, and I was certain that I had read prior and followed Heli's instructions properly, because the bands are there in the unstretched mode. So a bit of confusion from all that, sorry again for getting defensive/uptight about it.[/quote]I may have been kinda rude, was'nt meant to be... But you've to reread that: [quote="Helifax"][color="orange"]Important: Adjust your in-game "Frustum" (CTRL+F11 by default) NOT TO STRETCH the image! By default the image is a bit stretched in CM (You can't see it since 100% NVidia separation is very low, but is very visible at higher depths). If you fail to do this, due to the stretching the result will be bad and can be headache inducing![/color][/quote]He says to use it, not NOT use it... English is not our first language so it may be not perfect, so you have to read: [quote="Helifax"]Important: Adjust your in-game "Frustum" (CTRL+F11 by default) [color="orange"]TO NOT[/color] STRETCH the image! By default the image is a bit stretched in CM (You can't see it since 100% NVidia separation is very low, but is very visible at higher depths). If you fail to do this, due to the stretching the result will be bad and can be headache inducing![/quote] BTW: I'm French. :) (So excuse my French !) .
DJ-RK said:Also, I found more games with the side bands (Anthem and Destiny 2), and I think I now understand what Dugom was trying to say earlier, because using the frustum cycle options the 2 stretch modes pushes the bands offscreen and the 2nd mode doesn't look too bad. I just found it conflicting that in Helifax's instructions (which Dugom had quoted and said I didn't read/follow) he says NOT to use the stretched frustum modes, and I was certain that I had read prior and followed Heli's instructions properly, because the bands are there in the unstretched mode. So a bit of confusion from all that, sorry again for getting defensive/uptight about it.
I may have been kinda rude, was'nt meant to be...

But you've to reread that:
Helifax said:Important:
Adjust your in-game "Frustum" (CTRL+F11 by default) NOT TO STRETCH the image! By default the image is a bit stretched in CM (You can't see it since 100% NVidia separation is very low, but is very visible at higher depths).
If you fail to do this, due to the stretching the result will be bad and can be headache inducing!
He says to use it, not NOT use it...

English is not our first language so it may be not perfect, so you have to read:

Helifax said:Important:
Adjust your in-game "Frustum" (CTRL+F11 by default)
TO NOT STRETCH the image! By default the image is a bit stretched in CM (You can't see it since 100% NVidia separation is very low, but is very visible at higher depths).
If you fail to do this, due to the stretching the result will be bad and can be headache inducing!


BTW: I'm French. :) (So excuse my French !)



.
Regarding the side bands: In some games where You need to use high separation values You just can't avoid a frustum setting that results in side bands as otherwise the complete image would be deformed. So what? In the beginning I just used a strip of black cardboard to cover this area. As the covered area just mirrors the image it doesn't contain any important information. Later I just learned to ignore it. Maybe there is a way to create black side bars via software? Some posts ago someone asked about a profile that causes the HUD to become 2D. When I tried CMu with F1 2017 (works great, BTW!) I was surprised to discover that it meanwhile has an own CM profile in the driver. In contrary to the AC:Unity profile I used before this profile managed to separate the HUD and presents it in 2D. The relevant value is [b]2DDHUDSettings=0x10000106 [/b] This value is used for: The Crew, F1 2017, F1 2015, Elite Dangerous, Obduction, Metal Gear Solid V: The Phantom Pain, Street Fighter V, Need for Speed, Hellblade: Senua's Sacrifice, Mirror's Edge: Catalyst I tried it with other games but so far it only worked with Destiny 2. Unfortunately also the cross hairs will become 2D then so I stayed with the old setting.
Regarding the side bands: In some games where You need to use high separation values You just can't avoid a frustum setting that results in side bands as otherwise the complete image would be deformed. So what? In the beginning I just used a strip of black cardboard to cover this area. As the covered area just mirrors the image it doesn't contain any important information. Later I just learned to ignore it. Maybe there is a way to create black side bars via software?

Some posts ago someone asked about a profile that causes the HUD to become 2D. When I tried CMu with F1 2017 (works great, BTW!) I was surprised to discover that it meanwhile has an own CM profile in the driver. In contrary to the AC:Unity profile I used before this profile managed to separate the HUD and presents it in 2D. The relevant value is
2DDHUDSettings=0x10000106

This value is used for: The Crew, F1 2017, F1 2015, Elite Dangerous, Obduction, Metal Gear Solid V: The Phantom Pain, Street Fighter V, Need for Speed, Hellblade: Senua's Sacrifice, Mirror's Edge: Catalyst
I tried it with other games but so far it only worked with Destiny 2. Unfortunately also the cross hairs will become 2D then so I stayed with the old setting.

My original display name is 3d4dd - for some reason Nvidia changed it..?!

Posted 03/03/2019 07:54 AM   
Yes, the side bands are a product of CM. You are effectively pushing the whole image in depth. To get a proper image the, the game should render more outside the bezels. As a result you have 2 options: 1 - Break the 16:9 AR by stretching it side to side. 2 - Preserve 16:9 AR, but introduce the bands to the sides (which basically is a copy of the edge of the Framebuffer, but scaled to -1 on the X axis). Like DJ-ARK said, this is down to preference, but I still think everyone should avoid the default mode, where the center of the image is 16:9 AR and the sides is stretched - this breaks the separation across the image and initially I couldn't figure why my eyes hurt and everything looked wrong :)) Until I realised what was actually wrong! Sadly, I didn't find a setting in the Profile to change the CM frustum! (We don't want to change the regular Stereo Frustum). For 2DDHUDSettings=0x10000106, the most significant bit represents the NVIDIA rating. 1 = Excelent. As a result 2DDHUDSettings=0x00000106 would give you the same result but with a rating of 0 = 3D Vision Ready :) This flag works in some games but not all of them.
Yes, the side bands are a product of CM. You are effectively pushing the whole image in depth. To get a proper image the, the game should render more outside the bezels.

As a result you have 2 options:
1 - Break the 16:9 AR by stretching it side to side.
2 - Preserve 16:9 AR, but introduce the bands to the sides (which basically is a copy of the edge of the Framebuffer, but scaled to -1 on the X axis).

Like DJ-ARK said, this is down to preference, but I still think everyone should avoid the default mode, where the center of the image is 16:9 AR and the sides is stretched - this breaks the separation across the image and initially I couldn't figure why my eyes hurt and everything looked wrong :)) Until I realised what was actually wrong!
Sadly, I didn't find a setting in the Profile to change the CM frustum! (We don't want to change the regular Stereo Frustum).


For
2DDHUDSettings=0x10000106, the most significant bit represents the NVIDIA rating. 1 = Excelent.
As a result 2DDHUDSettings=0x00000106 would give you the same result but with a rating of 0 = 3D Vision Ready :)

This flag works in some games but not all of them.

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)

Posted 03/03/2019 11:49 AM   
[quote="Dugom"] Hope it's helps. [/quote] Yes, it does. Ive get the tadaaaaa sound :) Further question will follow. For example: [quote="Helifax"]I don't understand why people are still using Nvidia Inspector to change profiles. [/quote] I thought that the Inspector and Helifax' tool are two different things. thx
Dugom said:


Hope it's helps.



Yes, it does. Ive get the tadaaaaa sound :)

Further question will follow. For example:

Helifax said:I don't understand why people are still using Nvidia Inspector to change profiles.


I thought that the Inspector and Helifax' tool are two different things.

thx

Posted 03/03/2019 01:13 PM   
  20 / 25    
Scroll To Top