OUps sorry .. try again now are fixedPicardon wrote:
Thank you for the reply and your help but the links don't work.
(Please delete your quote with wrong links to avoid confusions to other users)

OUps sorry .. try again now are fixedPicardon wrote:
Thank you for the reply and your help but the links don't work.
Isaacvigo wrote:Picardon wrote: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 !!
Are u sure posted the right modified ones? ... when i tried them , it post: version mismatch errorRAGEdemon wrote: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...
Code: Select all
regini.exe s3dtoggle.txt
@Echo Off
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /enable
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
Code: Select all
regini.exe s3dtoggle.txt
@echo off
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /disable
Im still having mismatch issue, no matter wich folder i chooseRAGEdemon wrote:
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.
...
The only think affected is chrome to me... it stays about 2 seconds in white window before it apears .RAGEdemon wrote:
Are you gents also getting Windows OS slowdowns when opening items/programs or navigating folders?
Maybe that's just me...
Isaacvigo wrote:Finally . i was installing and unninstaling StereoscopicDriver a few times, at fourth or fifth time it works (no mismatch)
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.Robert256 wrote: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
I´m afraid Nvidia wants sell VR not 3Dvision.Isaacvigo wrote: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.
Awesome Robert256, much appreciated 8)Robert256 wrote: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 1809Robert256 wrote: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
Robert256 wrote: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
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.subwoofa wrote: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.
https://www.mtbs3d.com/phpbb/viewtopic. ... 05&t=23703dlrjajdlfo wrote: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?
edwardsean wrote: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!
I'm working on a universal patch, it seems ready for Win10. If you want, you can try it here:tuff253 wrote: 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.