Future of 3D Vision Support (Official announcement from NVIDIA)
  31 / 42    
[quote="Kitessencial"]Update: I tried installing the 3D Vision driver from an earlier version (425.31), and the installation succeeded, but it showed an error message after that, saying that there was a version mismatch between the graphics driver and the 3D vision driver. Playing with it a little bit, I could pinpoint that the files "nvSCPAPI.dll" and "nvSCPAPI64.dll", located in "C:\Program Files (x86)\NVIDIA Corporation\3D Vision" are responsible for verifying the driver version. I then installed driver 425.31, uninstalled the 3D Vision driver that came with it, and installed the one from 419.67. The same version mismatch error appeared, but when I replaced the aforementioned files from version 425.31, 3D vision started working. So, I'm basically running version 199.67 of 3D Vision on driver 425.31. If Nvidia didn't change another thing in their drivers, other than the just removal of the 3D Vision Drivers, then it could be possible to change those 2 .dll files to match the newer 430.39 driver. Although I think that's unlikely to be true, since that would make the removal of 3D Vision support an arbitrary thing from Nvidia, with no benefits for them, I'm still trying to test that possibility.[/quote] This is great news! Can you test some 3D games ranging from DX9 to DX11, maybe some of the newer RTX titles too like Shadow of Tomb Raider to see if fixes and 3D works as it's supposed to. I'm still confident that we might find ways to install old 3D drivers on newer graphics drivers, until newer Windows feature updates and driver updates make it incompatible. The most crucial thing is to find a way to install 3D drivers on newer generation RTX 3080 cards when they show up.
Kitessencial said:Update: I tried installing the 3D Vision driver from an earlier version (425.31), and the installation succeeded, but it showed an error message after that, saying that there was a version mismatch between the graphics driver and the 3D vision driver.
Playing with it a little bit, I could pinpoint that the files "nvSCPAPI.dll" and "nvSCPAPI64.dll", located in "C:\Program Files (x86)\NVIDIA Corporation\3D Vision" are responsible for verifying the driver version.
I then installed driver 425.31, uninstalled the 3D Vision driver that came with it, and installed the one from 419.67. The same version mismatch error appeared, but when I replaced the aforementioned files from version 425.31, 3D vision started working. So, I'm basically running version 199.67 of 3D Vision on driver 425.31.
If Nvidia didn't change another thing in their drivers, other than the just removal of the 3D Vision Drivers, then it could be possible to change those 2 .dll files to match the newer 430.39 driver.
Although I think that's unlikely to be true, since that would make the removal of 3D Vision support an arbitrary thing from Nvidia, with no benefits for them, I'm still trying to test that possibility.


This is great news! Can you test some 3D games ranging from DX9 to DX11, maybe some of the newer RTX titles too like Shadow of Tomb Raider to see if fixes and 3D works as it's supposed to.

I'm still confident that we might find ways to install old 3D drivers on newer graphics drivers, until newer Windows feature updates and driver updates make it incompatible. The most crucial thing is to find a way to install 3D drivers on newer generation RTX 3080 cards when they show up.

Posted 04/24/2019 04:45 AM   
[quote="Captain0007"][quote="Kitessencial"]Update: I tried installing the 3D Vision driver from an earlier version (425.31), and the installation succeeded, but it showed an error message after that, saying that there was a version mismatch between the graphics driver and the 3D vision driver. Playing with it a little bit, I could pinpoint that the files "nvSCPAPI.dll" and "nvSCPAPI64.dll", located in "C:\Program Files (x86)\NVIDIA Corporation\3D Vision" are responsible for verifying the driver version. I then installed driver 425.31, uninstalled the 3D Vision driver that came with it, and installed the one from 419.67. The same version mismatch error appeared, but when I replaced the aforementioned files from version 425.31, 3D vision started working. So, I'm basically running version 199.67 of 3D Vision on driver 425.31. If Nvidia didn't change another thing in their drivers, other than the just removal of the 3D Vision Drivers, then it could be possible to change those 2 .dll files to match the newer 430.39 driver. Although I think that's unlikely to be true, since that would make the removal of 3D Vision support an arbitrary thing from Nvidia, with no benefits for them, I'm still trying to test that possibility.[/quote] This is great news! Can you test some 3D games ranging from DX9 to DX11, maybe some of the newer RTX titles too like Shadow of Tomb Raider to see if fixes and 3D works as it's supposed to. I'm still confident that we might find ways to install old 3D drivers on newer graphics drivers, until newer Windows feature updates and driver updates make it incompatible. The most crucial thing is to find a way to install 3D drivers on newer generation RTX 3080 cards when they show up. [/quote] Testing a bit more, by just editing the .dlls and changing their version number do match the ones of other .dlls in "C:\Program Files\NVIDIA Corporation", I could get the 419.67 to work on the 425.31 driver. The same trick, however, does NOT apply for the newest driver. This weekend I can test how stable and how well 3D vision works when the versions don't match.
Captain0007 said:
Kitessencial said:Update: I tried installing the 3D Vision driver from an earlier version (425.31), and the installation succeeded, but it showed an error message after that, saying that there was a version mismatch between the graphics driver and the 3D vision driver.
Playing with it a little bit, I could pinpoint that the files "nvSCPAPI.dll" and "nvSCPAPI64.dll", located in "C:\Program Files (x86)\NVIDIA Corporation\3D Vision" are responsible for verifying the driver version.
I then installed driver 425.31, uninstalled the 3D Vision driver that came with it, and installed the one from 419.67. The same version mismatch error appeared, but when I replaced the aforementioned files from version 425.31, 3D vision started working. So, I'm basically running version 199.67 of 3D Vision on driver 425.31.
If Nvidia didn't change another thing in their drivers, other than the just removal of the 3D Vision Drivers, then it could be possible to change those 2 .dll files to match the newer 430.39 driver.
Although I think that's unlikely to be true, since that would make the removal of 3D Vision support an arbitrary thing from Nvidia, with no benefits for them, I'm still trying to test that possibility.


This is great news! Can you test some 3D games ranging from DX9 to DX11, maybe some of the newer RTX titles too like Shadow of Tomb Raider to see if fixes and 3D works as it's supposed to.

I'm still confident that we might find ways to install old 3D drivers on newer graphics drivers, until newer Windows feature updates and driver updates make it incompatible. The most crucial thing is to find a way to install 3D drivers on newer generation RTX 3080 cards when they show up.


Testing a bit more, by just editing the .dlls and changing their version number do match the ones of other .dlls in "C:\Program Files\NVIDIA Corporation", I could get the 419.67 to work on the 425.31 driver. The same trick, however, does NOT apply for the newest driver.
This weekend I can test how stable and how well 3D vision works when the versions don't match.

Posted 04/24/2019 04:50 AM   
Thanks for taking the time to test this possibility. Have you tried installing the older 3D drivers on 430.39 with this trick yet, and it didn't work at all? Or you haven't tried the newer driver yet, and so far testing two of the older versions mismatching one another?
Thanks for taking the time to test this possibility. Have you tried installing the older 3D drivers on 430.39 with this trick yet, and it didn't work at all? Or you haven't tried the newer driver yet, and so far testing two of the older versions mismatching one another?

Posted 04/24/2019 05:13 AM   
[quote="Kitessencial"][quote="Captain0007"][quote="Kitessencial"]Update: I tried installing the 3D Vision driver from an earlier version (425.31), and the installation succeeded, but it showed an error message after that, saying that there was a version mismatch between the graphics driver and the 3D vision driver. Playing with it a little bit, I could pinpoint that the files "nvSCPAPI.dll" and "nvSCPAPI64.dll", located in "C:\Program Files (x86)\NVIDIA Corporation\3D Vision" are responsible for verifying the driver version. I then installed driver 425.31, uninstalled the 3D Vision driver that came with it, and installed the one from 419.67. The same version mismatch error appeared, but when I replaced the aforementioned files from version 425.31, 3D vision started working. So, I'm basically running version 199.67 of 3D Vision on driver 425.31. If Nvidia didn't change another thing in their drivers, other than the just removal of the 3D Vision Drivers, then it could be possible to change those 2 .dll files to match the newer 430.39 driver. Although I think that's unlikely to be true, since that would make the removal of 3D Vision support an arbitrary thing from Nvidia, with no benefits for them, I'm still trying to test that possibility.[/quote] This is great news! Can you test some 3D games ranging from DX9 to DX11, maybe some of the newer RTX titles too like Shadow of Tomb Raider to see if fixes and 3D works as it's supposed to. I'm still confident that we might find ways to install old 3D drivers on newer graphics drivers, until newer Windows feature updates and driver updates make it incompatible. The most crucial thing is to find a way to install 3D drivers on newer generation RTX 3080 cards when they show up. [/quote] Testing a bit more, by just editing the .dlls and changing their version number do match the ones of other .dlls in "C:\Program Files\NVIDIA Corporation", I could get the 419.67 to work on the 425.31 driver. The same trick, however, does NOT apply for the newest driver. This weekend I can test how stable and how well 3D vision works when the versions don't match.[/quote] What exactly is the error you got when you changed the dll version number to 430.39? It sounds like interfaces required are missing from the actual display driver. In which case there is no hope of reviving it. You may as well stay at 425.31 until no longer possible.
Kitessencial said:
Captain0007 said:
Kitessencial said:Update: I tried installing the 3D Vision driver from an earlier version (425.31), and the installation succeeded, but it showed an error message after that, saying that there was a version mismatch between the graphics driver and the 3D vision driver.
Playing with it a little bit, I could pinpoint that the files "nvSCPAPI.dll" and "nvSCPAPI64.dll", located in "C:\Program Files (x86)\NVIDIA Corporation\3D Vision" are responsible for verifying the driver version.
I then installed driver 425.31, uninstalled the 3D Vision driver that came with it, and installed the one from 419.67. The same version mismatch error appeared, but when I replaced the aforementioned files from version 425.31, 3D vision started working. So, I'm basically running version 199.67 of 3D Vision on driver 425.31.
If Nvidia didn't change another thing in their drivers, other than the just removal of the 3D Vision Drivers, then it could be possible to change those 2 .dll files to match the newer 430.39 driver.
Although I think that's unlikely to be true, since that would make the removal of 3D Vision support an arbitrary thing from Nvidia, with no benefits for them, I'm still trying to test that possibility.


This is great news! Can you test some 3D games ranging from DX9 to DX11, maybe some of the newer RTX titles too like Shadow of Tomb Raider to see if fixes and 3D works as it's supposed to.

I'm still confident that we might find ways to install old 3D drivers on newer graphics drivers, until newer Windows feature updates and driver updates make it incompatible. The most crucial thing is to find a way to install 3D drivers on newer generation RTX 3080 cards when they show up.


Testing a bit more, by just editing the .dlls and changing their version number do match the ones of other .dlls in "C:\Program Files\NVIDIA Corporation", I could get the 419.67 to work on the 425.31 driver. The same trick, however, does NOT apply for the newest driver.
This weekend I can test how stable and how well 3D vision works when the versions don't match.


What exactly is the error you got when you changed the dll version number to 430.39? It sounds like interfaces required are missing from the actual display driver. In which case there is no hope of reviving it. You may as well stay at 425.31 until no longer possible.

There are 10 types of people in the world. Those who understand binary and those who don't.

Independent Software/Game Developer

ASUS ROG RealBench Developer.

Posted 04/24/2019 10:52 AM   
Those of us with new/emerging HMDs like Pimax 8K are probably going to have to create dual boot setups, with frozen OS and NVidia driver in 3D Vision setup, and the latest OS and driver updates for HMD setup. I do not know how long Windows 10 will let an OS version remain fixed before forcing an update, however. It also sounds like there may be a performance difference if Creator Ready drivers are used for future 3DMigoto updates, versus Game Ready drivers, especially for newer games.
Those of us with new/emerging HMDs like Pimax 8K are probably going to have to create dual boot setups, with frozen OS and NVidia driver in 3D Vision setup, and the latest OS and driver updates for HMD setup. I do not know how long Windows 10 will let an OS version remain fixed before forcing an update, however. It also sounds like there may be a performance difference if Creator Ready drivers are used for future 3DMigoto updates, versus Game Ready drivers, especially for newer games.

Posted 04/24/2019 02:41 PM   
[quote="Kitessencial"] So, I'm basically running version 199.67 of 3D Vision on driver 425.31.[/quote] They are in the same driver branch, so that is probably why they work without too much fuss. GL on finding a way to hack 430 and on, I hope you or someone finds a way. I know that I fired up Mass Effect Andromeda recently and it crashed until I switched to a newer driver. So I can only imagine that we'll run into newer games that do the same and will simply not launch at all with drivers 418-425. Maybe not even in 2D
Kitessencial said: So, I'm basically running version 199.67 of 3D Vision on driver 425.31.


They are in the same driver branch, so that is probably why they work without too much fuss.

GL on finding a way to hack 430 and on, I hope you or someone finds a way.

I know that I fired up Mass Effect Andromeda recently and it crashed until I switched to a newer driver. So I can only imagine that we'll run into newer games that do the same and will simply not launch at all with drivers 418-425. Maybe not even in 2D

Posted 04/24/2019 03:16 PM   
@cameramanbrayton Provided you were not a spammer, to get your hidden post to show, you need to see this thread. [url]https://forums.geforce.com/default/topic/845400/forum-feedback/post-here-if-your-posts-amp-replies-are-hidden/[/url]
@cameramanbrayton

Provided you were not a spammer, to get your hidden post to show, you need to see this thread.

https://forums.geforce.com/default/topic/845400/forum-feedback/post-here-if-your-posts-amp-replies-are-hidden/

Posted 04/24/2019 03:54 PM   
[quote="Nodens"]What exactly is the error you got when you changed the dll version number to 430.39? It sounds like interfaces required are missing from the actual display driver. In which case there is no hope of reviving it. You may as well stay at 425.31 until no longer possible.[/quote] The error I was getting was that the driver version and 3D vision version didn't match each other. The same error that happened initially when I tried installing 3D Vision on a different version. About the interfaces not existing anymore on the newer release, I agree that this is most likely the situation, I'm just testing to make sure. Wouldn't make sense for them to still be there, but doesn't hurt to try I guess.
Nodens said:What exactly is the error you got when you changed the dll version number to 430.39? It sounds like interfaces required are missing from the actual display driver. In which case there is no hope of reviving it. You may as well stay at 425.31 until no longer possible.


The error I was getting was that the driver version and 3D vision version didn't match each other. The same error that happened initially when I tried installing 3D Vision on a different version.
About the interfaces not existing anymore on the newer release, I agree that this is most likely the situation, I'm just testing to make sure. Wouldn't make sense for them to still be there, but doesn't hurt to try I guess.

Posted 04/24/2019 08:43 PM   
Hello. Completely new here. Read all of the 457 more or less disappointing comments. Since years I'm using my Nvision set with an Asus 120hz monitor and an outdated GTX650 (I'm outdated myself). Since I'm not a gamer but a dedicated 3D movie watcher I guess I'll stick with the 419.67 version (which has the 3D driver) and make up an environment with Win 1809 and some update-stopping-software so that I always get back via system restore. Til a real solution pops up...
Hello. Completely new here. Read all of the 457 more or less disappointing comments. Since years I'm using my Nvision set with an Asus 120hz monitor and an outdated GTX650 (I'm outdated myself). Since I'm not a gamer but a dedicated 3D movie watcher I guess I'll stick with the 419.67 version (which has the 3D driver) and make up an environment with Win 1809 and some update-stopping-software so that I always get back via system restore. Til a real solution pops up...

Posted 04/24/2019 10:41 PM   
When they announced driver won't be included in future packages, I thought graphics driver would update/install and just that the 3D Vision driver would always remain untouched. When the setup start, usually we can manually select what to install and not. I don't see why the 3D Vision would be removed when updating.
When they announced driver won't be included in future packages, I thought graphics driver would update/install and just that the 3D Vision driver would always remain untouched. When the setup start, usually we can manually select what to install and not. I don't see why the 3D Vision would be removed when updating.

3D Vision must live! NVIDIA, don't let us down!

Posted 04/24/2019 10:48 PM   
Too bad gaming wasn't 100% on Linux with the open source driver ;(
Too bad gaming wasn't 100% on Linux with the open source driver ;(

I'm ishiki, forum screwed up my name.

9900K @5.0 GHZ, 16GBDDR4@4233MHZ, 2080 Ti

Posted 04/25/2019 05:35 AM   
[quote="Kitessencial"] The error I was getting was that the driver version and 3D vision version didn't match each other. The same error that happened initially when I tried installing 3D Vision on a different version. About the interfaces not existing anymore on the newer release, I agree that this is most likely the situation, I'm just testing to make sure. Wouldn't make sense for them to still be there, but doesn't hurt to try I guess.[/quote] For clarification, you got the version mismatch error although you had edited the dll libraries' version number to 430.39? If yes, then can you tell me how you changed the dll version number? I think I need to find some time this week to do some reverse engineering on these libraries and see what's actually going on. If it's the version mismatch error indeed it's possibly still doable. [quote="limextree"] Too bad gaming wasn't 100% on Linux with the open source driver ;( [/quote] Well unfortunately nouveau does not support 3d vision (or any sort of 3d stereo) in the driver. And even if it did, nouveau's performance is abysmal. Anyone sane installs the nvidia driver instead, on linux, unless they have issues with the licensing (which is the main reason nouveau exists as most distros can not bundle the nvidia driver due to licensing reasons).
Kitessencial said:
The error I was getting was that the driver version and 3D vision version didn't match each other. The same error that happened initially when I tried installing 3D Vision on a different version.
About the interfaces not existing anymore on the newer release, I agree that this is most likely the situation, I'm just testing to make sure. Wouldn't make sense for them to still be there, but doesn't hurt to try I guess.


For clarification, you got the version mismatch error although you had edited the dll libraries' version number to 430.39? If yes, then can you tell me how you changed the dll version number?
I think I need to find some time this week to do some reverse engineering on these libraries and see what's actually going on. If it's the version mismatch error indeed it's possibly still doable.

limextree said:
Too bad gaming wasn't 100% on Linux with the open source driver ;(


Well unfortunately nouveau does not support 3d vision (or any sort of 3d stereo) in the driver. And even if it did, nouveau's performance is abysmal. Anyone sane installs the nvidia driver instead, on linux, unless they have issues with the licensing (which is the main reason nouveau exists as most distros can not bundle the nvidia driver due to licensing reasons).

There are 10 types of people in the world. Those who understand binary and those who don't.

Independent Software/Game Developer

ASUS ROG RealBench Developer.

Posted 04/25/2019 02:48 PM   
Perhaps Process Explorer or something similar. I wonder if the 3D Vision drivers can be hacked into a stand alone version and then used with an injector. Ultimately, Nvidia should just Open Source their Stereoscopic drivers
Perhaps Process Explorer or something similar.

I wonder if the 3D Vision drivers can be hacked into a stand alone version and then used with an injector.

Ultimately, Nvidia should just Open Source their Stereoscopic drivers

Posted 04/25/2019 03:05 PM   
[quote="Rhialto"]When they announced driver won't be included in future packages, I thought graphics driver would update/install and just that the 3D Vision driver would always remain untouched. When the setup start, usually we can manually select what to install and not. I don't see why the 3D Vision would be removed when updating.[/quote] i just saw this problem, i updated drivers to 430.39-desktop-win10-64bit-international-whql and it removed me 3DVision modules. i reinstalled 425.31-desktop-win10-64bit-international-whql but even with personalized installation, i couldn't unselect already installed 430.39 driver in order it doesn't change. So the reinstallation downgraded to 425.31 . grrrrrrrrrrrrr so i'm angry because we are forced to keep 425.31 if we want to keep 3DVision ??? someone has a solution ? thank you
Rhialto said:When they announced driver won't be included in future packages, I thought graphics driver would update/install and just that the 3D Vision driver would always remain untouched. When the setup start, usually we can manually select what to install and not. I don't see why the 3D Vision would be removed when updating.


i just saw this problem, i updated drivers to 430.39-desktop-win10-64bit-international-whql
and it removed me 3DVision modules.

i reinstalled 425.31-desktop-win10-64bit-international-whql but even with personalized installation, i couldn't unselect already installed 430.39 driver in order it doesn't change. So the reinstallation downgraded to 425.31 . grrrrrrrrrrrrr

so i'm angry because we are forced to keep 425.31 if we want to keep 3DVision ???

someone has a solution ? thank you

Corei7 4790K 32GB / 2xSLI: Titan X Pascal 3DSurr 7680x1440 +FSIM cockpit :D

My Hardcore gamer rig : http://forum.hardware.fr/configuration.php?config=hardwarefr.inc&pseudo=greatxerox
SETUP Video 20190623 : https://vimeo.com/343968979
Pictures : http://www.casimages.com/u/greatxerox/369138
Best site Emulation on the net : http://www.emu-france.com/

Posted 04/25/2019 04:47 PM   
My solution is to immediately create a dual boot setup, freezing Windows 10 OS (as much as possible, with help from Falcon Northwest) with 425.31 driver on one boot disk (with backup), and latest OS/NVidia drivers on another boot disk - for my VR headsets. VR environments like SteamVR are very likely to require the latest drivers and OS updates...
My solution is to immediately create a dual boot setup, freezing Windows 10 OS (as much as possible, with help from Falcon Northwest) with 425.31 driver on one boot disk (with backup), and latest OS/NVidia drivers on another boot disk - for my VR headsets. VR environments like SteamVR are very likely to require the latest drivers and OS updates...

Posted 04/25/2019 05:44 PM   
  31 / 42    
Scroll To Top