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

[Isaacvigo]

Thank you for the reply and your help but the links don't work.

OUps sorry .. try again now are fixed

(Please delete your quote with wrong links to avoid confusions to other users)

[kakashisensei]

What if I can't find the numbers in the dll file with the hex editor? 83 F8 07 0F 8F 97 01 00 00 can't be found. 441.87 driver.

use this modified dlls pack ( http://www.mediafire.com/file/r2zvd47m8 ... n.zip/file )
With 441.87 oficial standart drivers ( https://www.nvidia.es/download/driverRe ... /156327/es )

1- change the extension of the dll modified by dl_ ( nvwgf2um.dl_ & nvwgf2umx.dl_ )
2- Unzip the official driver package with 7z
3- Replace the original dl_ with the dl_ that you have renamed in the corresponding folder
4- Install those drivers from the uncompresed folder with setup.exe
5- Complete 3d drivers with 3d fix manager
U are ready!!

it goes flawless with not anticheat messages at all !!
Doesnt need to change permissions at all
No need to found neither modiffies any archives in your system disk
Im happy to make this discovering and share it

Making this way the driver stays "signed" and causes not isssues at all

********** *********

try this way !!

Just tried this method and it works for me, same as manually using Schwing's hex edit method. I'm using win 10 1909 latest.

But steamVR is still not working with 3d vision enabled. It just fails to start. Can't use virtual desktop, helix vision, or anything that relies on steamVR to play 3d vision games in a VR desktop. Anyone else experiencing this? Have to fall back to 425.31 driver... smh

[subwoofa]

Windows 1909 nVidia 441
Use 7z tool for unzip.

1. Download http://www.guru3d.com/files-details/dis ... nload.html
2. Run DDU in safe mode and restart
3. Download http://www.mediafire.com/file/r2zvd47m8 ... n.zip/file (411.87_3dvision)
4. Extract 411.87_3dvision with 7z
5. Change the extensions from "dll" to "dl_" for these files in the extracted directory: ( nvwgf2um.dl_ & nvwgf2umx.dl_ )
6. Download https://www.nvidia.com/download/driverR ... /156327/en (NON-DCH!)
7. Extract downloaded blahblahblah-whql.zip with 7z
8. Replace the whql extracted driver files in Display.Driver folder with your re-extensioned dl_ files from the 411.87_3dvision folder
9. Install the modified uncompressed driver from you whql folder with setup.exe
10. 3D Fix Manager won't install your driver ( it's a cool tool, install it anyway later )
11. LOSTi time: https://losti.s3.amazonaws.com/3D_Drive ... _LOSTI.zip
12. Extract with 7z, rename the extracted folder to LOSTI or something simple
13. Windows 7/8: http://de.download.nvidia.com/Windows/4 ... l-whql.exe
    Windows 10: http://de.download.nvidia.com/Windows/4 ... l-whql.exe
14. Copy the 425 download.exe to the LOSTI folder
15. Plug in all your 3DVision stuff, you're about to set it up
16. Run/Double-click 3D_driver_Changer.cmd in the LOSTI folder
17. Follow the instructions. Read them carefully. Press 'y' when appropriate. If you have to press 'n' I can't help you.
18. While following the instructions, the 3D Vision driver installer dialog will run. Do your best to make it happy.
19. 3D Vision setup will run. You plugged in everything, right? You know the drill.
20. It works (for me. Good luck.)

[dlrjajdlfo]

441.87 and 442.19 work fine on Windows 1909 in the above way, but no longer on 442.50.

[RAGEdemon]

442.50 WHQL (non DCH) seems to be "working" on 1909, however my system has severe slowdown with these drivers + 3DV in the windows OS environment - e.g. it takes 5 seconds for Chrome to open instead of 0.5s; takes 5 seconds to get into nVidia control panel instead of usual ~1s etc.

When 3DV is disabled via NV control panel, performance immediately returns to normal fast snappyness.

Strange behaviour...

Anyway, here are my edited .dll files...

[schwing]

[Deleted]

[Isaacvigo]

442.50 WHQL (non DCH) seems to be "working" on 1909, however my system has severe slowdown with these drivers + 3DV in the windows OS environment - e.g. it takes 5 seconds for Chrome to open instead of 0.5s; takes 5 seconds to get into nVidia control panel instead of usual ~1s etc.

When 3DV is disabled via NV control panel, performance immediately returns to normal fast snappyness.

Strange behaviour...

Anyway, here are my edited .dll files...

Are u sure posted the right modified ones? ... when i tried them , it post: version mismatch error

[Losti]

The isntallation for 3D Vision dont work anymore since 442.50, you have to go with 442.19 as latest driver you are able to install 3D. ==> I am on Win 10 1809

If anyone are able to install 3D with 442.50 just let me know

[Dark_saiyens]

If it doesn't work any more with 442.50 it gonna be very annoying in few months...
fu** you Nvidia

[RAGEdemon]

Tested and working on Losti's Universal Unreal Engine MechWarrior 5 fix and GTA5.

I have done some investigating and can confirm that it does work with 442.50 with the dlls in my above post - however there are additional steps:

Thanks to schwing for his instructions: the dlls are hex edited with the values he provided.

After you have replaced the DLLs from safe mode and booted into Windows, the additional steps are:

1. Install the 3DV driver in the folder: \fix_manager_1.74\Drivers\StereoscopicDriver\Win10\NV3DVision\setup.exe

NOT: \fix_manager_1.74\Drivers\StereoscopicDriver\Win10\3DVision.exe <-- this will give a driver mismatch error.

2. At this point, you will then see that the drivers are installed and the 3DV tab appears in the nvidia control panel, however you cannot enable them without an error dialogue.

To fix this, enable 3DV via registry. This is my script:

Batch file to enable:

Code: Select all

regini.exe s3dtoggle.txt
@Echo Off
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /enable

s3dtoggle.txt contents: <-- This is my custom settings file - edit/remove personalised values as necessary

Code: Select all

\Registry\Machine\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D
MonitorSizeOverride = REG_DWORD 0x0000000F
StereoVisionConfirmed = REG_DWORD 0x00000001
StereoDefaultOn = REG_DWORD 0x00000000
StereoViewerType = REG_DWORD 0x00000001
ToggleLaserSight = REG_DWORD 0x00000248
LaserSightIndex = REG_DWORD 0x00000009
LaserSightFile = REG_SZ DLL:9
StereoSeparation = REG_DWORD 0x00000064
StereoAdvancedHKConfig = REG_DWORD 0x00000001
SnapShotQuality = REG_DWORD 0x0000005A

Batch file to disable 3DV driver:

Code: Select all

regini.exe s3dtoggle.txt
@echo off
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /disable

regini.exe can be downloaded from the internet.

=================

Caveats:
1. Slow Windows OS - opening programs, exploring folders, etc.
2. Editing nvstres.dll / nvstres64.dll to disable the red message no longer works - how is this even possible?

But it seems to be working with games otherwise, e.g. MW5 and GTA5 tested so far (only games I currently have installed).

I'd love to hear some insight from our Sages - I might have done something wrong of course, or my extra steps were useless in some manner...

[Losti]

HM, this is nothing special than the hex edited files but its not working. But after some things in 3DFM and the registry things i now got 3dv in 442.50 .... hm .... but i dnot know how i have done this, this is what i need to track down. Its also not working propperly because of some errors starting the wizzard. But no more Version missmatch... HM...... let me invesigate this

[RAGEdemon]

Thank you Losti

Please let me know if I can be of any service...

[Isaacvigo]

After you have replaced the DLLs from safe mode and booted into Windows, the additional steps are:

1. Install the 3DV driver in the folder: \fix_manager_1.74\Drivers\StereoscopicDriver\Win10\NV3DVision\setup.exe

NOT: \fix_manager_1.74\Drivers\StereoscopicDriver\Win10\3DVision.exe <-- this will give a driver mismatch error.

2. At this point, you will then see that the drivers are installed and the 3DV tab appears in the nvidia control panel, however you cannot enable them without an error dialogue.

...

Im still having mismatch issue, no matter wich folder i choose

[Losti]

I am working on a solution that i have found, i am working on the cmd script for you!

//ETA: 30.02.2020

[Isaacvigo]

Finally . i was installing and unninstaling StereoscopicDriver a few times, at fourth or fifth time it works (no mismatch)

[Losti]

//skipped

[RAGEdemon]

Great news guys; and thank you Losti!

Are you gents also getting Windows OS slowdowns when opening items/programs or navigating folders?

Maybe that's just me...

[Isaacvigo]

Are you gents also getting Windows OS slowdowns when opening items/programs or navigating folders?

Maybe that's just me...

The only think affected is chrome to me... it stays about 2 seconds in white window before it apears .
Alll the other thinks i feel them even better than before. folders etc..

[Losti]

Hm, i will currently skip this here. There are some things of instability and so on. I suggest use 442.19 as latest driver and inport profiles from 442.50

Finally . i was installing and unninstaling StereoscopicDriver a few times, at fourth or fifth time it works (no mismatch)

Are you able to run the wizzard?

[Robert256]

Hi guys,

I just updated the installation files for the 442.50 driver. It works fine on Win10 1909.

You can download it here:
https://imaging3d.com/3DVision_442.50_Win10_64bit.zip

See the instructions in the readme.txt file.

Best regards, Robert

[Losti]

Hi guys,

I just updated the installation files for the 442.50 driver. It works fine on Win10 1909.

You can download it here:
https://imaging3d.com/3DVision_442.50_Win10_64bit.zip

See the instructions in the readme.txt file.

Best regards, Robert

OK this is stupid, i have done all the things again and again and again and run into problems. Also follow your way thats the same i do, except the modded driver files need for win 19XX.
AND IT WORKS!!!

I came from DDU with 425.31 (Note: Using DDU as in your readme without 425.31 installation AFTER DDU will NOT install the controller driver BUT: If you do not want to install 425.31 after DDU and directly got o 442.50, we can start 3DFM and let it install the controller driver separately)

I am on Win 1809

Its really strange because everything you have done there (except the hexy modded driver files) weill be done by 3DFM and/or my tool. So whats the difference????

So there are 2 things to track down, why the things NOW working!!

1. ONLY change the driver tags for the NvSCPAPI.dll and NvSCPAPI64.dll as i have done in the manual way of my tutorial, NOT change the others (my tool will change all the versions for the 3DV files
2. We need the HexEdited files

So ill investigate this !!!

GREAT THING !!!! THANK YOU!!

Everything is like it was before.... WOOOW i am so curiouse about the final solution and the issue that causes the version missmatch before since 442.50 using my tool

Hope its option 1 because than i can update the tool. If its uption 2, than we need HexEditor thing every update..... Ill inform you later !!!

[Losti]

The answer is NOT 1 and NOT 2.

The answer is: ONLY CHANGE DRIVER VERSION ANF FILE VERSION TAGS for the NvSCPAPI.dll and NvSCPAPI64.dll. Any changes on the version, EVEN if i change it to 425.31 will cause the troubles. So i dont know why but the driver seems NOW check file modifications, or the version change tool will make faults. However, seems that if we only change the tags for this 3 files the things are working again!!

Ill update my driver tool and check the things for 1809 / 1903 again.

[Isaacvigo]

I still don't understand why Nvidia insists on complicating our lives to we can use our 3D pyramid ...
I imagine that the next step they will take will be to encrypt the installer dll so that we cannot enter our modified driver files.
Either way, I think we are doing very well and we will be able to have the package of 3D drivers ready to face the news.
Congratulations for the great work.

[vidalsh68]

I still don't understand why Nvidia insists on complicating our lives to we can use our 3D pyramid ...
I imagine that the next step they will take will be to encrypt the installer dll so that we cannot enter our modified driver files.
Either way, I think we are doing very well and we will be able to have the package of 3D drivers ready to face the news.
Congratulations for the great work.

I´m afraid Nvidia wants sell VR not 3Dvision.

[Losti]

Some things has been changed, so i have updated the Driver tool from here: https://www.mtbs3d.com/phpBB/viewtopic. ... 05&t=23277

OK seems we are back to buissines, THANK YOU VERY MUCH Robert256 for your post (https://www.mtbs3d.com/phpBB/viewtopic. ... 32#p168132) that let me find out the things that went wrong with 442.50 !!!

Not to cause extense traffic for Bo3B i have uploaded the new tool @ my webspace, please get this there!!!

http://web396.inetseite.de/3D_Driver_To ... _LOSTI.zip

The tool is working as usual! I also have added some hints für Win 10 1903 (or later) users to direct to this thread and also added a hint for SUPER CARD users.

Win 10 1809 users (or versions before):
- install 3D-Driver and 3D-Vision by the use of this tool

Win 10 1903 (or later) users:
- install 3D-Driver and 3D-Vision by the use of this tool
- follow this guide to get this finally working: https://www.mtbs3d.com/phpBB/viewtopic. ... 05&t=23352
- for Driver 442.50 you can also use this files and the guidiance (in the readme of the archive) from here: https://www.mtbs3d.com/phpBB/viewtopic. ... 32#p168132

SUPER CARD USERS users:
- install 3D-Driver and 3D-Vision by the use of this tool, and skipp the part of the 425.31 installation described there (because you cant install it with a super card)
- install and start 3D-Fix manager
- enable 3D with the slider in the upper right corner
- this will ask you to install the 3D-Vision controller driver, just install it and restart, than you have 3D-Vision with the latest driver @ your SUPER card without the 425.31 step thats not possible for you!





INFO:

Not to getting lost, its also uploaded @ the amazon saw service

(https://losti.s3.amazonaws.com/3D_Drive ... _LOSTI.zip)

I also have updated the 3D_Driver_Tool_V1.10_by_LOSTI.zip there that is the same version like 1.20 now, only in case the current existing tutorials will not be updated.

[Chtiblue]

Hi guys,

I just updated the installation files for the 442.50 driver. It works fine on Win10 1909.

You can download it here:
https://imaging3d.com/3DVision_442.50_Win10_64bit.zip

See the instructions in the readme.txt file.

Best regards, Robert

Awesome Robert256, much appreciated 8)

[skyrimer]

Hi guys,

I just updated the installation files for the 442.50 driver. It works fine on Win10 1909.

You can download it here:
https://imaging3d.com/3DVision_442.50_Win10_64bit.zip

See the instructions in the readme.txt file.

Best regards, Robert

HUGE thanks for this, it's so easy to update the drivers like this, I didn't even DDU and worked like a charm, tried 3 games and all worked great, thanks a lot Robert256 for this amazing pack. Tested on Windows 10 1809

[tuff253]

Do the front page steps need updating to support the latest drivers?

[necrovamp]

Thank you so much, I was having major trouble with the fix setup and permissions hex edit, and I dont even know where I ended up.
But I eventually got to a page that said version mismatch.

i ran DDU again , and followed ur instructions, 100% perfect install, thank you!!!!

Hi guys,

I just updated the installation files for the 442.50 driver. It works fine on Win10 1909.

You can download it here:
https://imaging3d.com/3DVision_442.50_Win10_64bit.zip

See the instructions in the readme.txt file.

Best regards, Robert

[Scarhead]

Thanks to Schwing, Losti and robert for the nvidia driver 3DVision patch.

You guys are great!

[subwoofa]

I really don't want to do this again. I've got this working for 1909/441 and I hope I don't need to ever download another version of anything ever again.

[Robert256]

I really don't want to do this again. I've got this working for 1909/441 and I hope I don't need to ever download another version of anything ever again.

No worries, that's why I'm working on a universal patch, almost done. It will be as easy as downloading the right driver and run the patcher to install it.

[dlrjajdlfo]

I am using hp reverb.
On 441,87 and 442,19 everything worked perfectly just by copying two dll files and installing 3dfix manager with 3d vision driver install automatically
And I played a game.
Yes It was all I have to do
But at 442.50 , the wmr portal and 3D vision collide again,
It is no longer possible to run 3d vision and VR simultaneously.
so I have to change the 0x709D3AD2 value to 0x00000004 and after then i have to change all games to 0x00000008.
To be honest, this problem occurs with all drivers except 441.87 and 442.19.

Does anyone know why this happen?

[Losti]

I am using hp reverb.
On 441,87 and 442,19 everything worked perfectly just by copying two dll files and installing 3dfix manager with 3d vision driver install automatically
And I played a game.
Yes It was all I have to do
But at 442.50 , the wmr portal and 3D vision collide again,
It is no longer possible to run 3d vision and VR simultaneously.
so I have to change the 0x709D3AD2 value to 0x00000004 and after then i have to change all games to 0x00000008.
To be honest, this problem occurs with all drivers except 441.87 and 442.19.

Does anyone know why this happen?

https://www.mtbs3d.com/phpbb/viewtopic. ... 05&t=23703

[dlrjajdlfo]

https://www.mtbs3d.com/phpbb/viewtopic. ... 05&t=23703

Even if I did what you said, the results are the same.
I wonder how 441.87 and 442.19 did not cause this error.

So I think I'll have to use 442.19 until the gtx 3000 series card comes out,


I pondered again.
This is not a problem with the 3dvision installation process.
When I use only 3dvision without VR it works fine perfectly
Also, after when I uncheck 3d vision, VR works fine.

So I think this problem is due to something in the NVIDIA driver file that interferes with VR access.

I think it's right that bo3b solves it, rather than seeing it as Losti your problem.
Because this is a problem in Helixvision.

[oneofthe8devilz]

I just used Losti's tool to migrate from: Windows 10 LTSC (18.09) + NVIDIA GEFORCE 2060 RTX + "NVIDIA GEFORCE DRIVER 425.31" to "NVIDIA GEFORCE DRIVER 442.50" and I must say it went smooth as butter with everything seeming to work flawlessly so far in the 3DV/VR division...

Amazing Job Guys !

[edwardsean]

Thanks so much guys! The directions here worked like a charm with 442.50.

What I’m wondering about though is what happens after 442.40 with the next update. Can we use these same directions or are they specific to this driver?

Is this the new procedure going forward, at least until Nivida makes another change?

Maybe the process can be updated in 3D Fix Manager?

Thanks!

[tuff253]

Thanks so much guys! The directions here worked like a charm with 442.50.

What I’m wondering about though is what happens after 442.40 with the next update. Can we use these same directions or are they specific to this driver?

Is this the new procedure going forward, at least until Nivida makes another change?

Maybe the process can be updated in 3D Fix Manager?

Thanks!

Did you use the front page steps for driver 442.40 or did you run steps from some of the posts above in addition to the front page steps? I have yet to even try getting 3D to work on my PC using any of these steps but I think it is starting to get complex especially if the front page steps don't work with the current driver release.

[edwardsean]

I ran the front page steps first. However, even using the standard Nvidia driver update it did not work. I was using 3D Fix Manager to install the 3D Vision drivers and they would not install correctly.

The method in the posts above worked for me flawlessly.

I did the optional DDU step just in case.

Good luck!

[Robert256]

Did you use the front page steps for driver 442.40 or did you run steps from some of the posts above in addition to the front page steps? I have yet to even try getting 3D to work on my PC using any of these steps but I think it is starting to get complex especially if the front page steps don't work with the current driver release.

I'm working on a universal patch, it seems ready for Win10. If you want, you can try it here:

- Download https://www.imaging3d.com/BringBack3DV.zip and copy the contents from this archive to c:\temp
- Download the new Standard(not DCH!) NVidia driver installer and also save it in c:\temp (see the download link in the readme.txt)
- Disconnect from internet. Optionally you can uninstall the current driver with DDU.
- Run BringBack3DV.exe. It will patch the driver and add 3D Vision, just see the onscreen instructions to install everything. May take a few minutes!
- Reconnect to internet.

Cheers!

Robert256