Devices > Video Cards, Monitors, Televisions, and Projectors
NVIDIA stops support for 3D from 430 driver
RoderickGI:
When you first posted this I updated to Version 425.31 of the nVidia drivers, which were a bit hard to find if I remember correctly, as I was being directed to the 418 all the time. The nVidia pages on it weren't much help, I have to say.
Anyway, I found madVR and/or the TV weren't switching to frame pack 3D automatically, as they had been doing before, so I tried side-by-side and found that worked okay. Also tried top-bottom which was okay. But both required manual switching of the TV.
I still haven't gone back and gotten frame pack 3D to work automatically as it used to on earlier driver, but now using 425.31. Do you have that working tij? Or am I going to have to go back to 418?
tij:
--- Quote from: RoderickGI on August 25, 2019, 07:35:55 pm ---When you first posted this I updated to Version 425.31 of the nVidia drivers, which were a bit hard to find if I remember correctly, as I was being directed to the 418 all the time. The nVidia pages on it weren't much help, I have to say.
Anyway, I found madVR and/or the TV weren't switching to frame pack 3D automatically, as they had been doing before, so I tried side-by-side and found that worked okay. Also tried top-bottom which was okay. But both required manual switching of the TV.
I still haven't gone back and gotten frame pack 3D to work automatically as it used to on earlier driver, but now using 425.31. Do you have that working tij? Or am I going to have to go back to 418?
--- End quote ---
I am on 425.31 … frame packing switching still work (in NVidia control panel there should be setting for Stereoscopic 3D … if that's there 3D should work)
RoderickGI:
Yep, that's there.
When I turned that on things didn't work correctly. I can't remember if it was previously turned on, or if it was off and madVR turned it on as required. I think the latter.
I'll have to test and play around with settings again. Or find the thread that went through it all.
tij:
If you turning it on Desktop to see it in 3D … Destop resolution must be 1080p23 for 3D to kick in
When you mess with Top/Bottom (don't do Side by Side or overlaid MC OSD will be garbage), you probably mess up some setting for 3D in madVR
Things to check for framepack:
in [devices]
[properties] 3D should be "auto"
[display modes] should be only "1080p23"
in [rendering]
[stereo 3D]
[when playing 2d content] … "disable OS sterei 3D..."
[when playing 3d content] … "enable"
[restore os stereo 3d...] … ticked
TheShoe:
Heads up for Windows 10 Pro users:
For over a year Windows 10 update never insisted I update the nVidia display driver. Today it did and I could not prevent it from doing so if I were to continue to use Windows update (since you can't select which updates to install). By default, I have Win10 Pro configured to not install updates until I decide to do so (I think in latest Windows Fall update, this is now also limited across all versions).
I let it update expecting to have to roll back the nVidia display driver. Sure enough 3D is removed and you get MVC rendering as SBS. Fine but for now I am not going that route. So I re-installed the last nVidia driver with 3D Vision support and am back to "normal".
I did find that with Windows 10 Pro you can change the system policy template for windows update to prevent driver updates. Will see if that works, though now I expect I will not see potentially other critical updates. Tend to like complete control over driver updates in any case.
Instructions here:
https://www.groovypost.com/howto/disable-automatic-hardware-driver-updates-on-windows-10/
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version