3D stereoscopic Options are not avialable after Update to Windows 10 17.9
3 / 3
@everyone:
These bugs need to be reported. There is no one else who is going to do it.
It's [i]everyone's[/i] job to report bugs. It's not a community if people don't put in some legwork to help report, test, and fix things.
Always report bugs that impact you to NVidia. Take the time. Contribute. Even if they get multiple bug reports, that is far, far superior to none. And makes it more important, and probably gets it fixed faster because they have more data.
Here is the reporting link:
[url]https://nvidia.custhelp.com/app/answers/detail/a_id/4512/kw/report%20bug[/url]
@everyone:
These bugs need to be reported. There is no one else who is going to do it.
It's everyone's job to report bugs. It's not a community if people don't put in some legwork to help report, test, and fix things.
Always report bugs that impact you to NVidia. Take the time. Contribute. Even if they get multiple bug reports, that is far, far superior to none. And makes it more important, and probably gets it fixed faster because they have more data.
Uhh bo3b? The first way that page lists for reporting bugs is to post something in the forums. We've had three active threads on this issue, including one where an NVIDIA person acknowledged that a bug had been submitted. Will hassling a live chat person about it actually help more?
So anyway, I finally took the plunge. Ouch. Nasty. I doubt I could have gotten through this without all the fixes posted in the threads here and there's no way in Hades a typical user is going to be able to handle this.
I've got a PG278QR Asus monitor so I knew I was in for trouble. I set the monitor to 120Hz in the Change Resolution section of the NVIDIA control panel. My drivers were from December, I think, so not the most up to date but pretty close. 3D Vision was disabled.
The Fall Creator's update went through without a hitch. The aftermath was a bit messy - broken file associations being the most annoying. (I still haven't convinced Windows that my copy of Bitdefender doesn't have the firewall option.) I actually didn't bother using 3D Vision for a few days afterward.
When I tried to enable 3D Vision, my system went crazy - blanking the screen in and out - until it finally displayed the 3D Vision Setup Wizard but the only option there was Discover Mode. That's also what was displaying in the "Stereoscopic 3D display type" section of the control panel. I tried turning off G-SYNC in the control panel and rebooting but it didn't help. Then I downloaded the latest drivers and installed those. There was a surprise waiting there: the driver for the emitter was no longer installed!
Well that explains a lot. So I updated the driver and rebooted. Now the display type lists as Asus 3D/G-SYNC LCD and... the Wizard still displays just the Discovery mode option!? So I finally used the Advanced VConfig program to set the registry option to say I had already run the wizard and also merged in my own registry settings to set the hotkeys I like. This made it so I was finally able to enable 3D Vision.
It worked, too. Prey worked great and even Dead or Alive managed to kick into 3D Vision without crashing. But the PhereoImageViewer did something strange: it turned on 3D Vision but actually displayed my images in side by side mode, just like it does when I have 3D Vision disabled. The fix for that was to go into the exe properties and disable the full screen optimization. (Reading in this topic, that probably would have fixed the setup wizard, too.)
Uhh bo3b? The first way that page lists for reporting bugs is to post something in the forums. We've had three active threads on this issue, including one where an NVIDIA person acknowledged that a bug had been submitted. Will hassling a live chat person about it actually help more?
So anyway, I finally took the plunge. Ouch. Nasty. I doubt I could have gotten through this without all the fixes posted in the threads here and there's no way in Hades a typical user is going to be able to handle this.
I've got a PG278QR Asus monitor so I knew I was in for trouble. I set the monitor to 120Hz in the Change Resolution section of the NVIDIA control panel. My drivers were from December, I think, so not the most up to date but pretty close. 3D Vision was disabled.
The Fall Creator's update went through without a hitch. The aftermath was a bit messy - broken file associations being the most annoying. (I still haven't convinced Windows that my copy of Bitdefender doesn't have the firewall option.) I actually didn't bother using 3D Vision for a few days afterward.
When I tried to enable 3D Vision, my system went crazy - blanking the screen in and out - until it finally displayed the 3D Vision Setup Wizard but the only option there was Discover Mode. That's also what was displaying in the "Stereoscopic 3D display type" section of the control panel. I tried turning off G-SYNC in the control panel and rebooting but it didn't help. Then I downloaded the latest drivers and installed those. There was a surprise waiting there: the driver for the emitter was no longer installed!
Well that explains a lot. So I updated the driver and rebooted. Now the display type lists as Asus 3D/G-SYNC LCD and... the Wizard still displays just the Discovery mode option!? So I finally used the Advanced VConfig program to set the registry option to say I had already run the wizard and also merged in my own registry settings to set the hotkeys I like. This made it so I was finally able to enable 3D Vision.
It worked, too. Prey worked great and even Dead or Alive managed to kick into 3D Vision without crashing. But the PhereoImageViewer did something strange: it turned on 3D Vision but actually displayed my images in side by side mode, just like it does when I have 3D Vision disabled. The fix for that was to go into the exe properties and disable the full screen optimization. (Reading in this topic, that probably would have fixed the setup wizard, too.)
The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering.
[quote="bo3b"]@everyone:
These bugs need to be reported. There is no one else who is going to do it.
It's [i]everyone's[/i] job to report bugs. It's not a community if people don't put in some legwork to help report, test, and fix things.
Always report bugs that impact you to NVidia. Take the time. Contribute. Even if they get multiple bug reports, that is far, far superior to none. And makes it more important, and probably gets it fixed faster because they have more data.
Here is the reporting link:
[url]https://nvidia.custhelp.com/app/answers/detail/a_id/4512/kw/report%20bug[/url][/quote]
Helifax and I can confirm this, as well as others here that take the necessary action.
[quote="Zloth"]Uhh bo3b? The first way that page lists for reporting bugs is to post something in the forums. We've had three active threads on this issue, including one where an NVIDIA person acknowledged that a bug had been submitted. Will hassling a live chat person about it actually help more?[/quote]
There are numerous ways to go about reporting the issue. Post in the driver feedback thread, file a driver bug report, file a driver regression support, contact live chat support, contact phone support.
The biggest thing, is that they "must" be able to duplicate the problem. Give them as much info as possible, even minute details that might seem unimportant. Do not think that because your having a problem, everyone is. It could be specific to hardware or software that's on your system and not related to Nvidia's drivers.
bo3b said:@everyone:
These bugs need to be reported. There is no one else who is going to do it.
It's everyone's job to report bugs. It's not a community if people don't put in some legwork to help report, test, and fix things.
Always report bugs that impact you to NVidia. Take the time. Contribute. Even if they get multiple bug reports, that is far, far superior to none. And makes it more important, and probably gets it fixed faster because they have more data.
Helifax and I can confirm this, as well as others here that take the necessary action.
Zloth said:Uhh bo3b? The first way that page lists for reporting bugs is to post something in the forums. We've had three active threads on this issue, including one where an NVIDIA person acknowledged that a bug had been submitted. Will hassling a live chat person about it actually help more?
There are numerous ways to go about reporting the issue. Post in the driver feedback thread, file a driver bug report, file a driver regression support, contact live chat support, contact phone support.
The biggest thing, is that they "must" be able to duplicate the problem. Give them as much info as possible, even minute details that might seem unimportant. Do not think that because your having a problem, everyone is. It could be specific to hardware or software that's on your system and not related to Nvidia's drivers.
Latest driver
https://forums.geforce.com/default/topic/1035590/geforce-drivers/official-390-77-game-ready-whql-display-driver-feedback-thread-released-1-29-18-/
[quote="ManuelGuzmanNV"]Our new GeForce Game Ready 390.77 WHQL drivers provides the optimal gaming experience for Kingdom Come: Deliverance, War Thunder, Black Desert Online, and Metal Gear Survive
[url]https://www.geforce.com/whats-new/articles/kingdom-come-deliverance-game-ready-driver[/url]
To download and install, simply fire up GeForce Experience and click the "Drivers" tab.
[u][b]Providing Feedback:[/b][/u]
This is a peer to peer support forum. While we try to read every end user feedback, we are unable to provide support to each and every user through the forums. If you require a response to a support inquiry, please visit the NVIDIA Support website where our Live Chat NVIDIA Customer Care team is available 24/7 (English only):
[url]http://www.nvidia.com/support[/url]
To report a software issue, please fill out the NVIDIA driver feedback form. This will help us collect the specific information needed to reproduce your issue and prioritize driver fixes:
[url]http://surveys.nvidia.com/index.jsp?pi=6e7ea6bb4a02641fa8f07694a40f8ac6[/url]
You are also welcome to discuss driver issues or leave suggestions in this thread however please keep comments family friendly. Any personal attacks towards other forum users or obscene language will be deleted. You are free to disagree with others. If you believe you have been insulted by another user, please report post to a Mod but do not retaliate.
Most software issues are specific to a users system configuration. If you seek assistance from other users on this board, we suggest providing as much information as possible including:
[.]System information[/.]
[.]Regression information. Does your issue occur with the last driver?[/.]
[.]For corruption/display issues, please include screenshots showing the in game graphics settings used and any NVIDIA Control Panel settings that you have changed from the default settings[/.]
[.]Is your screen flashing/losing signal? Most monitors ship with inexpensive video cables. If you are pushing the limits of cable technology (eg 4K resolution, high refresh rate, etc.) and you are experiencing flashing/loss of signal, consider swapping your video cable for a VESA complaint cable rated for your display. We also recommend keeping your video cable to around 6 feet.[/.]
[.]For stability issues, if your graphics card is factory/manually overclocked, does the issue go away if you lower your clock speeds to NVIDIA reference clock speeds[/.]
No trolling or posts aimed at baiting users into an argument with you. Users who violate this rule repeatedly will be permanently banned.[/quote]
[quote="ManuelGuzmanNV"][u]Issues and Updates:[/u]
-On some systems running multiple monitors, PC may TDR on cold boot. No problem with warm boot.
-After PC is left on for extended period of time, HDCP may be lost cause HTC Vive/Oculus Rift to launch to a black screen. Rebooting PC resolves issue.
-NieR:Automata randomly freezes with white screen
-Content type from NVIDIA Control Panel reset on reboot - [u][b]Fixed in next driver[/b][/u]
-Gears of War 4 may randomly crash
-Doom (OpenGL) may crash on launch if HDR is enabled in Windows
-Rise of the Tomb Raider displays partial flickering in DX12 mode
-NvfbcPluginWindow preventing Windows from shutting down if PC is left on for extended period of time
-Alt Tabbing in some windowed games w/ G-sync enabled may cause the FPS to change when you alt-tab back into the game
-Call of Duty WWII flickers after driver update
-Random TDR while using Firefox on Pascal GPUs
[u][b]Release Notes:[/b]
[/u]
[url]https://us.download.nvidia.com/Windows/390.77/390.77-win10-win8-win7-desktop-release-notes.pdf[/url][/quote]
One thing that "very few" people ever do, is read driver notes for known issues.
ManuelGuzmanNV said:Our new GeForce Game Ready 390.77 WHQL drivers provides the optimal gaming experience for Kingdom Come: Deliverance, War Thunder, Black Desert Online, and Metal Gear Survive
To download and install, simply fire up GeForce Experience and click the "Drivers" tab.
Providing Feedback:
This is a peer to peer support forum. While we try to read every end user feedback, we are unable to provide support to each and every user through the forums. If you require a response to a support inquiry, please visit the NVIDIA Support website where our Live Chat NVIDIA Customer Care team is available 24/7 (English only):
To report a software issue, please fill out the NVIDIA driver feedback form. This will help us collect the specific information needed to reproduce your issue and prioritize driver fixes:
You are also welcome to discuss driver issues or leave suggestions in this thread however please keep comments family friendly. Any personal attacks towards other forum users or obscene language will be deleted. You are free to disagree with others. If you believe you have been insulted by another user, please report post to a Mod but do not retaliate.
Most software issues are specific to a users system configuration. If you seek assistance from other users on this board, we suggest providing as much information as possible including:
System information
Regression information. Does your issue occur with the last driver?
For corruption/display issues, please include screenshots showing the in game graphics settings used and any NVIDIA Control Panel settings that you have changed from the default settings
Is your screen flashing/losing signal? Most monitors ship with inexpensive video cables. If you are pushing the limits of cable technology (eg 4K resolution, high refresh rate, etc.) and you are experiencing flashing/loss of signal, consider swapping your video cable for a VESA complaint cable rated for your display. We also recommend keeping your video cable to around 6 feet.
For stability issues, if your graphics card is factory/manually overclocked, does the issue go away if you lower your clock speeds to NVIDIA reference clock speeds
No trolling or posts aimed at baiting users into an argument with you. Users who violate this rule repeatedly will be permanently banned.
ManuelGuzmanNV said:Issues and Updates:
-On some systems running multiple monitors, PC may TDR on cold boot. No problem with warm boot.
-After PC is left on for extended period of time, HDCP may be lost cause HTC Vive/Oculus Rift to launch to a black screen. Rebooting PC resolves issue.
-NieR:Automata randomly freezes with white screen
-Content type from NVIDIA Control Panel reset on reboot - Fixed in next driver
-Gears of War 4 may randomly crash
-Doom (OpenGL) may crash on launch if HDR is enabled in Windows
-Rise of the Tomb Raider displays partial flickering in DX12 mode
-NvfbcPluginWindow preventing Windows from shutting down if PC is left on for extended period of time
-Alt Tabbing in some windowed games w/ G-sync enabled may cause the FPS to change when you alt-tab back into the game
-Call of Duty WWII flickers after driver update
-Random TDR while using Firefox on Pascal GPUs
If something was working on a previous driver, but isn't now, that's considered driver regression.
This is one of the easiest bugs for them to fix, provided that they can duplicate and confirm the issue.
They will try to use the same or as close to the same hardware to induce the issue. So please, try to go overboard with details.
And many thanks to those that do properly report bugs/driver issues/ feature requests.
Note: It is a good idea to post here first, to see if others are having the issue.
I was having problems with no 3d option showing up in windows settings system. The fix was to create another windows user account, set it as administrator and reinstall the drivers from this account. The upgrade to CFU had messed up permissions on my user account, causing the 3d driver to fail to install.
I was having problems with no 3d option showing up in windows settings system. The fix was to create another windows user account, set it as administrator and reinstall the drivers from this account. The upgrade to CFU had messed up permissions on my user account, causing the 3d driver to fail to install.
I have this issue now. I always had "enabling" 3D stereoscopic in settings of my monitors and had no desire to play with my old 3Dvision glasses. But since WOW BfA coming out I get them from a shelf and suddenly this settings are gone from windows. What do I do? I have freshly reinstalled windows and clean install of latest Nvidia driver.
Can I turn this on by using cmd or something?
Edit: I managed to install 3Dvision driver separately from Geforce experience and it's working. But since my monitor isn't officially 3DVision ready (Acer Predator), it's working not as intended and all stuff is wrong.
I have this issue now. I always had "enabling" 3D stereoscopic in settings of my monitors and had no desire to play with my old 3Dvision glasses. But since WOW BfA coming out I get them from a shelf and suddenly this settings are gone from windows. What do I do? I have freshly reinstalled windows and clean install of latest Nvidia driver.
Can I turn this on by using cmd or something?
Edit: I managed to install 3Dvision driver separately from Geforce experience and it's working. But since my monitor isn't officially 3DVision ready (Acer Predator), it's working not as intended and all stuff is wrong.
Guys I think I must have finally gotten hold of the update that everyone's complaining about. I've had nothing but problems this week with things suddenly breaking, including the Nvidia drivers.
Reading this thread helped with one game - Subnautica, which previously wouldn't launch without crashing. By going into the properties of the executable and selecting "disable fullscreen optimizations" it started just fine. - I'll update the Subnautica thread accordingly.
I've discovered however, that Arkham Asylum (yeah the oldest one) will not run in stereo 3D without the dreaded red message either inside the game or outside of it. What I mean is that I get two potential results:
1) It runs okay in-game but as soon as I exit I get the red message in desktop mode and it won't disappear until I disable 3D Vision from the NV control panel. - OR -
2) I get the red message inside AND outside the game when attempting to run the 3D Vision fix with the game - it's tied to the d3d9.dll associated with the fix.
Either way it's not working normally.. any ideas?
Guys I think I must have finally gotten hold of the update that everyone's complaining about. I've had nothing but problems this week with things suddenly breaking, including the Nvidia drivers.
Reading this thread helped with one game - Subnautica, which previously wouldn't launch without crashing. By going into the properties of the executable and selecting "disable fullscreen optimizations" it started just fine. - I'll update the Subnautica thread accordingly.
I've discovered however, that Arkham Asylum (yeah the oldest one) will not run in stereo 3D without the dreaded red message either inside the game or outside of it. What I mean is that I get two potential results:
1) It runs okay in-game but as soon as I exit I get the red message in desktop mode and it won't disappear until I disable 3D Vision from the NV control panel. - OR -
2) I get the red message inside AND outside the game when attempting to run the 3D Vision fix with the game - it's tied to the d3d9.dll associated with the fix.
Either way it's not working normally.. any ideas?
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64
These bugs need to be reported. There is no one else who is going to do it.
It's everyone's job to report bugs. It's not a community if people don't put in some legwork to help report, test, and fix things.
Always report bugs that impact you to NVidia. Take the time. Contribute. Even if they get multiple bug reports, that is far, far superior to none. And makes it more important, and probably gets it fixed faster because they have more data.
Here is the reporting link:
https://nvidia.custhelp.com/app/answers/detail/a_id/4512/kw/report%20bug
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
So anyway, I finally took the plunge. Ouch. Nasty. I doubt I could have gotten through this without all the fixes posted in the threads here and there's no way in Hades a typical user is going to be able to handle this.
I've got a PG278QR Asus monitor so I knew I was in for trouble. I set the monitor to 120Hz in the Change Resolution section of the NVIDIA control panel. My drivers were from December, I think, so not the most up to date but pretty close. 3D Vision was disabled.
The Fall Creator's update went through without a hitch. The aftermath was a bit messy - broken file associations being the most annoying. (I still haven't convinced Windows that my copy of Bitdefender doesn't have the firewall option.) I actually didn't bother using 3D Vision for a few days afterward.
When I tried to enable 3D Vision, my system went crazy - blanking the screen in and out - until it finally displayed the 3D Vision Setup Wizard but the only option there was Discover Mode. That's also what was displaying in the "Stereoscopic 3D display type" section of the control panel. I tried turning off G-SYNC in the control panel and rebooting but it didn't help. Then I downloaded the latest drivers and installed those. There was a surprise waiting there: the driver for the emitter was no longer installed!
Well that explains a lot. So I updated the driver and rebooted. Now the display type lists as Asus 3D/G-SYNC LCD and... the Wizard still displays just the Discovery mode option!? So I finally used the Advanced VConfig program to set the registry option to say I had already run the wizard and also merged in my own registry settings to set the hotkeys I like. This made it so I was finally able to enable 3D Vision.
It worked, too. Prey worked great and even Dead or Alive managed to kick into 3D Vision without crashing. But the PhereoImageViewer did something strange: it turned on 3D Vision but actually displayed my images in side by side mode, just like it does when I have 3D Vision disabled. The fix for that was to go into the exe properties and disable the full screen optimization. (Reading in this topic, that probably would have fixed the setup wizard, too.)
The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering.
-- Doctor Who, "Face of Evil"
Helifax and I can confirm this, as well as others here that take the necessary action.
There are numerous ways to go about reporting the issue. Post in the driver feedback thread, file a driver bug report, file a driver regression support, contact live chat support, contact phone support.
The biggest thing, is that they "must" be able to duplicate the problem. Give them as much info as possible, even minute details that might seem unimportant. Do not think that because your having a problem, everyone is. It could be specific to hardware or software that's on your system and not related to Nvidia's drivers.
https://forums.geforce.com/default/topic/1035590/geforce-drivers/official-390-77-game-ready-whql-display-driver-feedback-thread-released-1-29-18-/
One thing that "very few" people ever do, is read driver notes for known issues.
This is one of the easiest bugs for them to fix, provided that they can duplicate and confirm the issue.
They will try to use the same or as close to the same hardware to induce the issue. So please, try to go overboard with details.
And many thanks to those that do properly report bugs/driver issues/ feature requests.
Note: It is a good idea to post here first, to see if others are having the issue.
Can I turn this on by using cmd or something?
Edit: I managed to install 3Dvision driver separately from Geforce experience and it's working. But since my monitor isn't officially 3DVision ready (Acer Predator), it's working not as intended and all stuff is wrong.
Reading this thread helped with one game - Subnautica, which previously wouldn't launch without crashing. By going into the properties of the executable and selecting "disable fullscreen optimizations" it started just fine. - I'll update the Subnautica thread accordingly.
I've discovered however, that Arkham Asylum (yeah the oldest one) will not run in stereo 3D without the dreaded red message either inside the game or outside of it. What I mean is that I get two potential results:
1) It runs okay in-game but as soon as I exit I get the red message in desktop mode and it won't disappear until I disable 3D Vision from the NV control panel. - OR -
2) I get the red message inside AND outside the game when attempting to run the 3D Vision fix with the game - it's tied to the d3d9.dll associated with the fix.
Either way it's not working normally.. any ideas?
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64