[Guide] Win 10 v1903+, gfx driver v430.39+ 3DV Fix

Post by **schwing** » Fri Nov 22, 2019 3:22 pm

skyrimer wrote: I changed refresh rate on nvidia inspector to
"use the 3d application setting" and that fixed the message on all the games I've tested for now (vampyr, shadow of the tomb raider, aragami).

I'll add it to the Known Issues section, but I'm going to suggest that they try changing the global profile first. That should help make a blanket change unless it's overriden by a game.

Post by **skyrimer** » Fri Nov 22, 2019 5:12 pm

Thanks I'll try that schwing.

I'm getting some weird issues on 441.20. Aragami only boots in 3d if lauched with 3d fix manager, but it has terrible ghosting now and it wasn't that bad the first time. Also Shadow of the Tomb Raider and Dishonored 2 have awful ghosting, even the 3d vision demo, however Vampyr seems to work fine. I'm using ASUS PG278Q, which sometimes could get stuck on gsync mode and give terrible ghosting, but it barely happened before, but now I can't get it working properly. I've tried everything I can think of like switching gsync on/off, changing refresh rate, turning on/off computer or monitor, but the ghosting is still there.

EDIT: Went back to 425 drivers and the horrible ghosting is still there, idk what's going on now.

Post by **skyrimer** » Sat Nov 23, 2019 2:27 am

Tried Life is Strange and Bloodstained, same result, every single game has become a ghosting mess and they were perfect before on PG278Q , even in 425.31. Tried in another computer and same result, so it looks like something related to the monitor, the thing is that it worked fine until the driver upgrade.

Post by **schwing** » Sat Nov 23, 2019 4:35 am

Try DDU if you haven't already. Otherwise idk.

Post by **skyrimer** » Sat Nov 23, 2019 8:28 am

Tried DDU into 425.36 and also DDU into 441.20, in both cases still unbearable ghosting, right now 3d is broken for me, I'll buy a new DisplayPort cable and hopefully that's the issue, but either it was just a coincidence that it broke exactly in this moment or something in this process has damaged the cable/screen, i don't know.

Post by **the_jaguar** » Mon Nov 25, 2019 10:44 pm

A lot of us 3D MVC movie fans have been stuck with 425.31 since that's the last version that supports 3D MVC. It would be incredibly helpful if you could look into enabling support for 3D MVC - thanks!

Post by **daz7887** » Wed Nov 27, 2019 12:03 pm

Hi, I am using the 441.20 Nvidia driver and Windows 10 v1909 (which is reported above to be working with this fix) but I cannot follow the guide. There is no folder that starts with nv_dispi... or nvmdi... in C:\Windows\System32\DriverStore\FileRepository. I searched the FileRepository folder and it does have a subfolder that contains DLLs with the same names as the fixed ones, but that subfolder is called nv_desktop_ref4i.inf_amd64_80c89c29607d7829. The mention of AMD makes me doubt that it's the right folder (since I don't have an AMD GPU or CPU), but I tried replacing the DLLs in there anyway. Unfortunately, as I expected, this didn't fix the problem.

3D Vision hasn't worked for me since I reinstalled Windows recently due to a boot problem. I have the 3D Vision driver installed with 3D Fix Manager. I can turn on 3D with the fix manager or the official setup wizard, but it never activates after that, not even for the official 3D test application, which has always worked for me before.

Thank you to anyone who can offer advice.

Post by **Robert256** » Wed Nov 27, 2019 4:02 pm

skyrimer wrote:Tried DDU into 425.36 and also DDU into 441.20, in both cases still unbearable ghosting, right now 3d is broken for me, I'll buy a new DisplayPort cable and hopefully that's the issue, but either it was just a coincidence that it broke exactly in this moment or something in this process has damaged the cable/screen, i don't know.

I had these problems before, and could fix them by using another USB port for the IR emitter.

Post by **schwing** » Wed Nov 27, 2019 7:15 pm

@daz7887 Try the hex edit option. If it works, I'll update the guide to suggest that.

Post by **bORNcRUEL** » Thu Nov 28, 2019 1:08 am

@Schwing - Can't thank you enough for posting this guide and letting us enable 3D in latest nvidia drivers. My config:

Driver: 441.41
System: 1909 Win 10
G CArd: Asus 1080TI
Display: BenQ HT3550

Now about the issue i am facing:
I mostly use Stereoscopic 3D for watching movies (as PC gives the best experience through Powerdvd), but with your solution, even though I was able to get 3D integrated and activated successfully in 441.41 drivers, I am not able to get same experience as 425.31 while watching movies. There is too much cross talk. Multiple attempts at calibrating through drivers, powerdvd and the display (BenQ HT3550) didn't help either.

Is there a setting anywhere (like 3D Fix Manager or else) which I can change to remove cross talk while watching movies. Generally, this is resolved by switching left and right signals on glasses in other cases, but here even that is not helping. Could it be the that this fix is not meant for watching 3D movies?

Any help will be greatly appreciated. Thanks in advance.

Post by **schwing** » Thu Nov 28, 2019 1:22 am

I don't use 3D movie software so I haven't looked at if it works for me. My testing has been all 3D gaming so far. I will add this to the Known Issues section and see if it happens when I can.

Post by **bORNcRUEL** » Thu Nov 28, 2019 1:34 am

schwing wrote:I don't use 3D movie software so I haven't looked at if it works for me. My testing has been all 3D gaming so far. I will add this to the Known Issues section and see if it happens when I can.

Thanks for recording this... Will look forward...

Post by **bORNcRUEL** » Thu Nov 28, 2019 1:36 am

the_jaguar wrote:A lot of us 3D MVC movie fans have been stuck with 425.31 since that's the last version that supports 3D MVC. It would be incredibly helpful if you could look into enabling support for 3D MVC - thanks!

Does this apply to 3D movies that we watch through powerdvd as well? Just wondering as I am getting too much cross talk while watching 3d movies after applying this fix.
Thanks.

Post by **daz7887** » Thu Nov 28, 2019 5:20 am

schwing wrote:@daz7887 Try the hex edit option. If it works, I'll update the guide to suggest that.

The hex edit option tells me to go to the same folder as the first option, but my problem is that folder doesn't even exist. There is another folder containing two DLL files with the correct names – should I assume those are the files I'm looking for?

Post by **the_jaguar** » Thu Nov 28, 2019 10:12 am

bORNcRUEL wrote:
the_jaguar wrote:A lot of us 3D MVC movie fans have been stuck with 425.31 since that's the last version that supports 3D MVC. It would be incredibly helpful if you could look into enabling support for 3D MVC - thanks!
Does this apply to 3D movies that we watch through powerdvd as well? Just wondering as I am getting too much cross talk while watching 3d movies after applying this fix.
Thanks.

Yep, same as stereoscopic 3D. Even after using 3Dfixmanager, none of us are not able to watch 3D movies (using madVR) and MPC (BE or HC) or Kodi.

Post by **the_jaguar** » Thu Nov 28, 2019 10:13 am

schwing wrote:I don't use 3D movie software so I haven't looked at if it works for me. My testing has been all 3D gaming so far. I will add this to the Known Issues section and see if it happens when I can.

Thanks for the update. Many of us 3D fans would be extremely grateful to you if you could look into this when you get a chance.

Post by **Chtiblue** » Fri Nov 29, 2019 2:04 pm

bORNcRUEL wrote:
the_jaguar wrote:A lot of us 3D MVC movie fans have been stuck with 425.31 since that's the last version that supports 3D MVC. It would be incredibly helpful if you could look into enabling support for 3D MVC - thanks!
Does this apply to 3D movies that we watch through powerdvd as well? Just wondering as I am getting too much cross talk while watching 3d movies after applying this fix.
Thanks.

No problem here when watching 3D movies with PowerDVD

Post by **bORNcRUEL** » Sat Nov 30, 2019 11:39 am

Chtiblue wrote:
bORNcRUEL wrote:
the_jaguar wrote:A lot of us 3D MVC movie fans have been stuck with 425.31 since that's the last version that supports 3D MVC. It would be incredibly helpful if you could look into enabling support for 3D MVC - thanks!
Does this apply to 3D movies that we watch through powerdvd as well? Just wondering as I am getting too much cross talk while watching 3d movies after applying this fix.
Thanks.
No problem here when watching 3D movies with PowerDVD

wow! good for you... can you pls share details of your current setup? driver version, os version, display type, etc? i am assuming that you are not getting any cross talk while watching (which is kinda encouraging). pls also share if you have made any changes in 3dfixmanager... thanks

Post by **Robert256** » Tue Dec 03, 2019 3:02 pm

I'm also watching 3D movies without problems (no crosstalk). I use stereoscopic player, with the patched 441.20 drivers.
A few years ago I had crosstalk, which severely depended on which USB port I plugged in the IR emitter (and what other devices were plugged in in the same USB card).
Updating the drivers had no effect on this timing issue.
Maybe for people having severe crosstalk, this utility could help: https://www.nvidia.com/en-us/geforce/fo ... s-timings/

Post by **edwardsean** » Wed Dec 04, 2019 6:22 am

Does this Fix also work on Windows 10 - 1909 or should I stick with 1903?

Post by **schwing** » Wed Dec 04, 2019 10:57 am

1909 has not introduced any differences that I can see. It works fine for me. That's why I put a + for it in the topic title since I'm confident it will keep working.

Post by **bORNcRUEL** » Wed Dec 04, 2019 11:48 pm

Robert256 wrote:I'm also watching 3D movies without problems (no crosstalk). I use stereoscopic player, with the patched 441.20 drivers.
A few years ago I had crosstalk, which severely depended on which USB port I plugged in the IR emitter (and what other devices were plugged in in the same USB card).
Updating the drivers had no effect on this timing issue.
Maybe for people having severe crosstalk, this utility could help: https://www.nvidia.com/en-us/geforce/fo ... s-timings/

Thanks for sharing your experience. From what i have heard here, and other discussions over internet, seems like this issue is more prevalent with users using 3D display through 3D play software, instead of nvidia 3d vision kit. In my case also, I am using 3D projector with 3D glasses that came with it. May be users like yourself who are using ir emitter kit by nvidia are not facing the same problem. Reason why I am certain that this driver related is because all the crosstalk goes away the moment I switch to 425.31 driver version. Hopefully someone will come out with the solution soon for this.

Post by **Necropants** » Sun Dec 08, 2019 4:22 pm

Is this whats happening? I have been reluctant to pull the trigger to try this out myself due to the different experiences reported in this thread.
Is it working for everyone thats using a standard 3dvision monitor with Usb emitter?

Post by **skyrimer** » Mon Dec 09, 2019 5:33 pm

I'm using 441.20 and windows 10 1809 and it's working fine for me, at least with Vampyr and SOTTR on Asus PG278QR, i haven't tried any other games since I updated.

If you're going to try it check robert256 repack here: https://www.imaging3d.com/3DVision_441. ... _64bit.zip , check the readme in the zip.

Extremely easy and painless install.

Post by **edwardsean** » Thu Dec 12, 2019 2:59 pm

Thanks for Schwing for this guid and this thread. I'm on 1909 and got 3DVsion working for a while and it was so good to have real 3D back!

After Nvidia support was withdrawn I tried to convince myself to live with 2D, but a few hours back in 3D and I just couldn't believe how good it was and how much I missed it. I can't believe this technology had to be sidelined.

Unfortunately, I updated Nvidia driver and now I'm having trouble getting 3D back even if I roll back the Nvidia driver. I'm trying to troubleshoot but one issue I'm having is that I now have 4 folders of nv_dispi... followed by different alphanumeric sequences. So, I don't know which folder to access to do the Hex edit. It seems like each folder has a copy of the nvwgf2um.dll, nvwgf2umx.dll files.

Any ideas of what to try?

Post by **schwing** » Thu Dec 12, 2019 3:11 pm

Use DDU to start over. If the option in DDU to disable driver updates prevents Windows Update from installing a crappy driver before you, then use that. Otherwise disconnect from the internet before DDU restarts. You'll lose all of those Nvidia-related folders. Then install the gfx driver again. Now you should have nv_dispi.inf.... Otherwise go from top to bottom, sorted in Date Modified descending order, until one of the folders has those files. Hex edit them, as the guide's files are not frequently updated.

Edit: the guide's files have been updated.

Post by **edwardsean** » Thu Dec 12, 2019 7:57 pm

Thanks Schwing!

I started over with DDU. I'm back to one nv_dispi.inf... file. So, I can do the hex edit.

The problem is that I still can't get Win10 1909 + Nvidia 441.66 (or older) to accept the 3DVision driver. 3DVision Fix Manager goes through the install procedure, but fails in the end with an error that says there is a "mismatch" with my graphics driver.

Has anyone encountered this and found a way around?

Post by **schwing** » Thu Dec 12, 2019 9:28 pm

You're installing a DCH graphics driver. There's information in the guide I updated recently for getting DCH to work. Or you can manually install a Standard driver, but you have to use DDU again if you do that.

Post by **Porlonus** » Fri Dec 13, 2019 9:36 am

Hey, finally got some time again and tried that now, normal 441.66 with 1909 for a GTX980 and i5 3470s.
The 3D vision test works, but trying to start with the mod games would crash, resp. in a test with 3D deactivated 2/3 games would crash too, 1 would run rly slow.
I did recheck the mod (also correct position etc.). Btw. the folder with the files was named "nv_desktop_ref4i.inf_amd64..."
Simply placing back the original files at least in 2D, they would run again normally. (3D of course would crash or instead stay black)

Edit: okay I back on Win 10 Enterp. 1809 now, way more easy anyway. I just hope there will be solutions till 05.2021.

Post by **edwardsean** » Fri Dec 13, 2019 7:03 pm

Thanks Schwing! It was simple as DDU and I falling the standard drivers instead of DCH.
Now if only I can get Control not to crash in DX11.

Post by **Joker18** » Sun Dec 15, 2019 3:07 am

I just updated to 1909 trough https://www.microsoft.com/en-us/softwar ... /windows10
Windows did not reinstall nvidia drivers. I am on 441.12 with 3dvision working.
Driver version is standard.

Post by **Dark_saiyens** » Wed Dec 18, 2019 3:37 am

Hello!

I got motivated to update my graphic driver after changing my CPU/motherboard last week, having DCH drivers auto installed remplaced my 425 nvidia drivers and breaked the 3D Vision.
So for now i got 9700K + 2080 ti + Asus PG278QR + LG65C6V (haven't tried 3D vision yet on that screen, i would try it in few days after re installing jokerEDID)

I have followed LOSTI method and your fix in the first message.
I got huge issues because i had downloaded Nvidia drivers 441.66 DCH and i though it was the standard one... Anyway ! Make attention to NOT DOWNLOAD DCH drivers or it wouldn't works (from nvidia website you would download DCH....)
So i DDU in safe mod, reboot, use LOSTI method (warning, when u use LOSTI method by launching the .exe it erraze the 441.66 or any drivers u put in losti foldier and u have to put it again in the main foldier), then install "Install Take Ownership " (a bit boring to make it but when it is done u are happy) then use file replacement method from your first message here.

It works great ! I am in 441.66 and i can launch games in 3D Vision. No black screen in The witcher 3 like before.

1) I only got a huge issue with Subnautica. When i have launched it the first time after updated my drivers it was working, but all the times after i had an error message: "warning attempt to run in no stereoscopic mod blablabla" with double images in 3D but it looks like passive and not 3d vision sync. I think there is maybe a refresh problem (i am not stuck at 60hz in that game when i activate 3D with new drivers...) but i havent arrived to made it works after 2 hours... I have tried to reinstall the game, change DXini, refreshrate, compatibility from subnautica.exe etc
If i want that game works i have to be back to 425 drivers and i don't want. Any ideas there? Anyone tried to launch Subnautica after installing 1903/1909 ??
EDIT: It is same problem than skyrimer issue he mentionned with "GHOSTING" (= double image ) in 3D Vision + error compatibity message.
EDIT2: I HAVE UNPLUGED MY 3D Vision PYRAMID ON AN OTHER USB PORT AND IT WORKS AGAIN ! It was a sync prblm with new drivers ! Awesome !!

2) With 3D Fix manager in 1.74 we can't install Nvidia drivers on Windows 1903 or 1909 because of that version of windows and 3D fix doesn't want to update. Would it be possible to fix it with 1.75 ?
For downloading all 3D Fix manager version u can go here: http://fixmanager.rentus.de/download.php
Because i have seen some people it has fixed there problems when they made install with 3D Fix manager after Losti and your method. Thanks!

3) Any way to send money without having a Paypal account for helping 3D Fix Manager ? I don't want to make a Paypal account...

Post by **Dark_saiyens** » Wed Dec 18, 2019 4:36 am

skyrimer wrote:Thanks I'll try that schwing.

I'm getting some weird issues on 441.20. Aragami only boots in 3d if lauched with 3d fix manager, but it has terrible ghosting now and it wasn't that bad the first time. Also Shadow of the Tomb Raider and Dishonored 2 have awful ghosting, even the 3d vision demo, however Vampyr seems to work fine. I'm using ASUS PG278Q, which sometimes could get stuck on gsync mode and give terrible ghosting, but it barely happened before, but now I can't get it working properly. I've tried everything I can think of like switching gsync on/off, changing refresh rate, turning on/off computer or monitor, but the ghosting is still there.

EDIT: Went back to 425 drivers and the horrible ghosting is still there, idk what's going on now.

In fact it is NOT GHOSTING issue. It is due to 3d vision problems after updating after 425 drivers. I got same issue in Subnautica after fix it (cf my post just up that one).
It looks like it tried to launch 3D vision but it fails and it looks like passive 3D lol...
I got same problem by launching Black mesa, it fixes it by reinstalling 3D Drivers in 425 and relaunch the game (u can change resolution for applying new settings and launch it in a good way)

Now we need to understand why we got that " GHOSTING" problem with all new drivers for lots of games...

Robert256 wrote:
skyrimer wrote:Tried DDU into 425.36 and also DDU into 441.20, in both cases still unbearable ghosting, right now 3d is broken for me, I'll buy a new DisplayPort cable and hopefully that's the issue, but either it was just a coincidence that it broke exactly in this moment or something in this process has damaged the cable/screen, i don't know.
I had these problems before, and could fix them by using another USB port for the IR emitter.

Thanks, so maybe our "ghosting" problem come from our USB, it could explain why it was working for me the first time and not after and it looked like sync issue with my "error compatibility etc"

I would try it tonight !

EDIT: I HAVE UNPLUGED MY 3D Vision PYRAMID ON AN OTHER USB PORT AND IT WORKS AGAIN ! It was a sync prblm with new drivers ! Awesome !!

Post by **tadpole** » Thu Dec 19, 2019 10:19 am

Dark_saiyens wrote:maybe our "ghosting" problem come from our USB

If it helps, I'm using a passive 3D setup and don't get any ghosting using the newer drivers.

Post by **Dark_saiyens** » Fri Dec 20, 2019 4:02 am

schwing wrote:    I'm happy to announce a fix for Windows 10 1903 3D Vision for 430.39+ gfx drivers! The fix below is not the final version, and we need feedback
to know it works. If you are on 1903 and try this out, then please leave some feedback using the feedback suggestions below as a guide. If you are
not on 1903, then think about whether you want to update, as it's the first fix we've found. Please keep the fix on this forum, and all support
requests in this thread, by PM, or the 3DV Discord. Thank you very much for your patience.

    Here are the fix steps, and pick option 1 or 2:

Before you start:

Install Take Ownership from the "one-click registry" option at the bottom, extract it with 7-Zip, and double-click the "Add" .reg file.
Confirm that the menu option appears when right-clicking a folder and a file. It doesn't work on a folder if you're inside it.

Or: JurandyRafael suggested NTFSAccess, which avoids adding to the right-click menu and is a more traditional method.

Restart in Safe Mode

Option 1: file replacement (easier method, but 441.66 is required)

Download a 7z file containing two 441.66 DLL's for Standard or DCH depending on what gfx driver you have installed.

Go to C:\Windows\System32\DriverStore\FileRepository and find the nv_dispi... (or: nvmdi...) by sorting by Date Modified descending
If you can't find the folder, look for one that has the DLL's.

Right-click the folder and choose Take Ownership. In my testing, doing this on just the DLL's to replace was not sufficient.

Go into the folder, back up the DLL's you are replacing, and replace them with the downloaded ones.
If the folder was some other name and option 1 doesn't work, then revert using your backup files and try option 2.

Option 2: hex edit (manual method, probably any future driver)

Go to the same folder as in option 1. Back up the DLL you are hex editing, right-click it, then choose Take Ownership.

Open a hex editor as admin (I use HxD), go to the same folder, and hex edit the DLL as below.

Explaining the step below: open the DLL, copy the bytes on the left in the step below, and paste them in a Find window (CTRL+F). Choose the
    Hex-Values (or Bytes) option before pressing Find. You'll arrive at the first byte, which is 83. Pressing Find again should show some error or
    do nothing. Replace by copy-pasting (HxD: CTRL+B) the bytes on the right. To prevent typos, don't type them manually. Before you replace,
    make sure the cursor is on the left side of 83, and that the hex editor says "Overwrite" on the bottom (toggled with the INSERT key).

For nvwgf2um.dll   (32-bit games): replace 83 F8 07 0F 87 D3 01 00 00 FF 24 85 with B0 08 EB 0C

For nvwgf2umx.dll (64-bit games): replace 83 F8 07 0F 8F 97 01 00 00                with B0 08 EB 05

Save your changes (and ignore any access errors).

Final steps:

Restart your computer.

The 3D Vision driver can be installed before or after this guide with 3D Fix Manager or the Losti method.
You may have to restart the computer, but usually stereo works after the installation finishes.

If you have a DCH gfx driver, then follow this post to get DCH working. You may experience slow app startups while stereo is enabled. This
    doesn't happen for Standard gfx drivers.

If you get a "driver mismatch" error, then you installed a DCH graphics driver

Test modern-looking games (DirectX 10+) or generally ones you know don't work without the fix.
Tomb Raider DX11 stereo works but DX12 stereo itself seems to be broken even in Win 10 1803.

To be safe, avoid launching games that have anti-cheat functionality, MMO's, or generally any game that has a ban feature.
There is no way of knowing if the fix triggers one until it does, except to revert the fix using your backup files.

At the minimum, we only expect feedback for games that have a 3Dmigoto fix applied anyway (typically offline single-player games).
    Feedback suggestions:

Games you tried                  (especially UE4 games)

What went wrong                (e.g. game startup broken, guide step undoable, etc.)

What works without the fix  (people have been reporting this phenomenon, probably their display of choice is why)

Gfx driver version you tried (430.39 or later only)

Your specs                          (e.g. i3/i7 CPU, GPU, etc.)

Attachments/links                (e.g. d3d11_log.txt after launching the game if d3dx.ini has calls = 1 and optionally debug = 1 under [Logging])

I have forgotten somethings....!
Thank you so much dude

It works great on all my games i have tested !

Post by **element** » Sat Dec 21, 2019 12:59 am

Hi, Thank you so much for this fix.

I run Windows 1909, Drivers 441.66 and RTX 2070 SUPER.

I tried a couple of games and its kind of a gamble if it works or not.

Works great on Bloodstained and NieR: Automata.

Doesn't work on Legacy of Kain: Defience. Boots in 2D.

And I was really looking forward for FFXIV, which booted in 3d and everything is working in 3d, even so I see stuff in 2d.
Its weird. My character and the background is 2d but some UI elements are 3D. And on the game's fix 3d screenshots the 3D looks really amazing.

I am planning on installing 1809 for dual boot and try these games there as well. Keep up the good work!

Post by **Isaacvigo** » Sun Dec 29, 2019 6:36 pm

Hello.
Thanks for the fix.
Actually im playing at 441.20 on w10 1909 in perfec 3d most of the times....
My issue is whith easy anticheat when i try to play "The Division 2 "...
Cant start because the new dlls are not allowed.
Do You know any way to skip this?

Post by **ziozeus** » Wed Jan 01, 2020 7:34 am

My happy report till now:

monitor ASUS VG278HR (with embedded emitter)
gtx_970 by DVI cable.

win10-1909
nvidia 441.66 non_DCH
DLL's Hex editing
3dvision driver installed with 3DFM

1) nvidia 3d setup went as usual
2) NVIDIA TEST drives the monitor to use the selected video refresh rate (one of the 3 selected, 100-110-120 MHz, for the test), monitor enters 3D mode but emitter does not activate and test image is 2D.
3) game1: Assetto Corsa Competizione now needs me to force refresh_rate=100 via d3dx.ini (I want play with 50fps for limited pc performance) otherwise will use 120MHz REGARDLESS of NVCP setting in the test wizard (I used to set 100MHz there)
4) game2: Assetto Corsa didn't work anymore, always started showing both left and right images statically one over another, monitor set at 144Mhz, no 3D emitter, no video in 3D mode, changing refresh rate behaviour with inspector leads to no results.
Anyhow, got it working by setting ALL these 3 in d3dx.ini:
refresh_rate=100 (or 110 or 120)
full_screen=1
force_stereo=1
5) game3: Richard Burns Rally (old DX9 game, no 3dfix needed) first attempt goes wrong (white screen), second is ok. This always happens when changing refreshrate via the 3D TEST page. Refresh changes accordingly.
6) stereoscopic player works for 3D films flawlessly

Thanks for the fix!!!

Post by **subwoofa** » Sun Jan 05, 2020 3:44 am

I tried following these instructions, but when I right-click display->Nvidia Control panel, there are no 3d Stereoscopic settings.

Are these fixes supposed to restore these settings? If I did followed the instructions correctly, and they were successful, am I supposed to see the usual 3d stereoscopic settings in the Nvidia Control Panel? Or do I have to test it on a game?

Post by **subwoofa** » Sun Jan 05, 2020 4:29 am

Also, is this legitimate:
https://www.nvidia.com/en-us/drivers/nv ... sb-driver/

I have a 3DVision-supported monitor, a 3DVision2 USB emitter, and the 3DVision2 glasses. I had hoped that if I just installed this 3dvisioncontrollerdriver.exe I would get my 3d back but there is still no option on the Nvidia Controller.

Do you have any suggestions? Is it obvious that I did something wrong?
Thanks!