Every time I reboot settings default to 3D Vision Discover!
5 / 6
This only started happening to me in the last two or three driver releases (unfortunately I can't definitely remember which one), otherwise it was working fine for at least 3 years before then. My emitter definitely never turns off, it just seems like running a game in 3D Vision will cause it to revert to Discover on the next reboot. edit: I also went from 570 sli to 970 sli about the same time now that I think about it.
This only started happening to me in the last two or three driver releases (unfortunately I can't definitely remember which one), otherwise it was working fine for at least 3 years before then. My emitter definitely never turns off, it just seems like running a game in 3D Vision will cause it to revert to Discover on the next reboot. edit: I also went from 570 sli to 970 sli about the same time now that I think about it.
Hi
This has happened to me as long as I've used 3D vision, (over 2 years) I've never found a fix.
It has persisted through a number of drivers updates and two different versions of Windows.
I'm now running Windows 10 and still get the same thing.
I'm running a GTX 680 video card and an Asus 3D monitor.
I've gotten so that I just automatically go and change it every time I'm going to use 3D.
Mike
This has happened to me as long as I've used 3D vision, (over 2 years) I've never found a fix.
It has persisted through a number of drivers updates and two different versions of Windows.
I'm now running Windows 10 and still get the same thing.
I'm running a GTX 680 video card and an Asus 3D monitor.
I've gotten so that I just automatically go and change it every time I'm going to use 3D.
I have the same problem, Gtx 760, Windows 8.1, running with two monitors, an Asus 144hz and a samsung alt monitor, I have to manual set it back to Asus 120Hz 3D LCD from discovery everytime after windows 8.1 booted, very annoying.
I have the same problem, Gtx 760, Windows 8.1, running with two monitors, an Asus 144hz and a samsung alt monitor, I have to manual set it back to Asus 120Hz 3D LCD from discovery everytime after windows 8.1 booted, very annoying.
This happens for me when booting into my main Win 8.1 partition, but not when I boot into the Win 7 partition (ie. same hardware). The drivers in both are both the same too (353.38)... I'd always just assumed it was a Win 8.1 thing.
This happens for me when booting into my main Win 8.1 partition, but not when I boot into the Win 7 partition (ie. same hardware). The drivers in both are both the same too (353.38)... I'd always just assumed it was a Win 8.1 thing.
Gigabyte GTX 1080 G1 Gaming | 3 x Asus VG278HE | Intel i7 3930k | Asus Rampage IV Formula
maybe the problem has something to do with failure detecting 2nd monitor attached. I have an Acer h5360 as a 2nd monitor and when I unplug it I have no problems. Now with the last driver it is impossible even recongnize the brand of the pj until I select it into the Nvidia CP, and that is just a sign that Nvidia does not care about this kind of things..., so I would not be impressed if tomorrow I could not even play 3D with my pj unless stay stuck to obsolete Nvidia drivers.
maybe the problem has something to do with failure detecting 2nd monitor attached. I have an Acer h5360 as a 2nd monitor and when I unplug it I have no problems. Now with the last driver it is impossible even recongnize the brand of the pj until I select it into the Nvidia CP, and that is just a sign that Nvidia does not care about this kind of things..., so I would not be impressed if tomorrow I could not even play 3D with my pj unless stay stuck to obsolete Nvidia drivers.
I have the same sproblem since I have reinstalled my windows (3D Vision 1 emitter, one monitor). The only difference is that new system is on SSD and I have RAM Disk enabled now. It looks like USB problem, and it can happen even few minutes after boot, during the game.
I have the same sproblem since I have reinstalled my windows (3D Vision 1 emitter, one monitor). The only difference is that new system is on SSD and I have RAM Disk enabled now. It looks like USB problem, and it can happen even few minutes after boot, during the game.
Hi,
plug in you IR emitter to your USB 2.0 and [u]not USB 3.0[/u]. Then on startup the emitter is allways in the first range of initialization and the "discover" will not be enabled.
Regards Flixer
plug in you IR emitter to your USB 2.0 and not USB 3.0. Then on startup the emitter is allways in the first range of initialization and the "discover" will not be enabled.
I am having this problem as well - whenever I reboot, good 80% chance the display type will be reset to Discover. And my 3D doesn't work when it's set that way. I also went through the process of reinstalling the drivers several times trying to resolve the problem before I figured out what the issue was. I've gotten into the habit of fixing this setting every time I start up, but it's quite annoying to have to do so every time.
My motherboard has an option of "Full Initialization of USB devices during POST". Tried it. Thought it worked at first, but nope, still happening.
For the record, I've never had it reset prior to a reboot. Once it's set, it stays set until I power down/restart.
Unfortunately my only USB 2.0 ports are on top of my computer, none in the back. I don't like having stuff on top of the computer, so the 2.0 option, assuming it works, wouldn't be a permanent solution for me.
I am having this problem as well - whenever I reboot, good 80% chance the display type will be reset to Discover. And my 3D doesn't work when it's set that way. I also went through the process of reinstalling the drivers several times trying to resolve the problem before I figured out what the issue was. I've gotten into the habit of fixing this setting every time I start up, but it's quite annoying to have to do so every time.
My motherboard has an option of "Full Initialization of USB devices during POST". Tried it. Thought it worked at first, but nope, still happening.
For the record, I've never had it reset prior to a reboot. Once it's set, it stays set until I power down/restart.
Unfortunately my only USB 2.0 ports are on top of my computer, none in the back. I don't like having stuff on top of the computer, so the 2.0 option, assuming it works, wouldn't be a permanent solution for me.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
After having this work fine for me for the last 1.5 years, I'm now suddenly getting this all the time.
In my case, I've narrowed it down to turning off my projector.
When the projector is powered off, but not disabled in the control panel, it switches back to Discover. I think this might be different behavior for 350.12 driver too, because my habits haven't really changed, but the driver did.
So there are at least two ways to have this happen, if the monitor is somehow lost (can also happen at sleep), or if the USB ports are slow to recover.
Edit: Registry key that changes
Discover Mode: "StereoViewerType"=dword:80000001
Acer Mode: "StereoViewerType"=dword:00000001
I added that to my 3D settings batch file, and it worked to switch it from Discover to normal. So if you have this happening at boot time, this would fix it.
After having this work fine for me for the last 1.5 years, I'm now suddenly getting this all the time.
In my case, I've narrowed it down to turning off my projector.
When the projector is powered off, but not disabled in the control panel, it switches back to Discover. I think this might be different behavior for 350.12 driver too, because my habits haven't really changed, but the driver did.
So there are at least two ways to have this happen, if the monitor is somehow lost (can also happen at sleep), or if the USB ports are slow to recover.
I added that to my 3D settings batch file, and it worked to switch it from Discover to normal. So if you have this happening at boot time, this would fix it.
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
Hi bo3b,
can you upload your batch-file? It would be nice to see what you are loading on startup :)
Regards Flixer
[quote=""]After having this work fine for me for the last 1.5 years, I'm now suddenly getting this all the time.
In my case, I've narrowed it down to turning off my projector.
When the projector is powered off, but not disabled in the control panel, it switches back to Discover. I think this might be different behavior for 350.12 driver too, because my habits haven't really changed, but the driver did.
So there are at least two ways to have this happen, if the monitor is somehow lost (can also happen at sleep), or if the USB ports are slow to recover.
Edit: Registry key that changes
Discover Mode: "StereoViewerType"=dword:80000001
Acer Mode: "StereoViewerType"=dword:00000001
I added that to my 3D settings batch file, and it worked to switch it from Discover to normal. So if you have this happening at boot time, this would fix it.[/quote]
can you upload your batch-file? It would be nice to see what you are loading on startup :)
Regards Flixer
said:After having this work fine for me for the last 1.5 years, I'm now suddenly getting this all the time.
In my case, I've narrowed it down to turning off my projector.
When the projector is powered off, but not disabled in the control panel, it switches back to Discover. I think this might be different behavior for 350.12 driver too, because my habits haven't really changed, but the driver did.
So there are at least two ways to have this happen, if the monitor is somehow lost (can also happen at sleep), or if the USB ports are slow to recover.
I added that to my 3D settings batch file, and it worked to switch it from Discover to normal. So if you have this happening at boot time, this would fix it.
Thread about the batch file I made for changing these settings:
[url]https://forums.geforce.com/default/topic/544995/handy-batch-file-to-fix-3d-settings/[/url]
Edit to suit your needs. If you only want the Discover piece delete the other modifications. You can drop this into your startup folder, and it will run at every boot.
Edit to suit your needs. If you only want the Discover piece delete the other modifications. You can drop this into your startup folder, and it will run at every boot.
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
i7-6700k @ 4.5GHz, 2x 970 GTX SLI, 16GB DDR4 @ 3000mhz, MSI Gaming M7, Samsung 950 Pro m.2 SSD 512GB, 2x 1TB RAID 1, 850w EVGA, Corsair RGB 90 keyboard
This has happened to me as long as I've used 3D vision, (over 2 years) I've never found a fix.
It has persisted through a number of drivers updates and two different versions of Windows.
I'm now running Windows 10 and still get the same thing.
I'm running a GTX 680 video card and an Asus 3D monitor.
I've gotten so that I just automatically go and change it every time I'm going to use 3D.
Mike
It's extremely annoying.
Gigabyte GTX 1080 G1 Gaming | 3 x Asus VG278HE | Intel i7 3930k | Asus Rampage IV Formula
- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)
Same problem. Somewhat irritating.
Dear Nvidia guys, mind to pay some attention? ;)
Regards,
Alex
MSI Z97 GAMING 5
Intel Core i7 4790K
G.SKILL RipjawsX DDR3 2133MHz CL9 16GB
MSI GTX980 GAMING 4G
Windows 7
MOBO: GIGABYTE GA-M68MT-S2 CPU: AMD FX 4100 RAM: 8GB 1600HZ DDR3 HDD: 1TB WD (MASTER) 500GB WD (SLAVE) GRAPHICS: GTX750SC MONITOR: ASUS VG248QE 3D VISION KIT 2
plug in you IR emitter to your USB 2.0 and not USB 3.0. Then on startup the emitter is allways in the first range of initialization and the "discover" will not be enabled.
Regards Flixer
My motherboard has an option of "Full Initialization of USB devices during POST". Tried it. Thought it worked at first, but nope, still happening.
For the record, I've never had it reset prior to a reboot. Once it's set, it stays set until I power down/restart.
Unfortunately my only USB 2.0 ports are on top of my computer, none in the back. I don't like having stuff on top of the computer, so the 2.0 option, assuming it works, wouldn't be a permanent solution for me.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
In my case, I've narrowed it down to turning off my projector.
When the projector is powered off, but not disabled in the control panel, it switches back to Discover. I think this might be different behavior for 350.12 driver too, because my habits haven't really changed, but the driver did.
So there are at least two ways to have this happen, if the monitor is somehow lost (can also happen at sleep), or if the USB ports are slow to recover.
Edit: Registry key that changes
Discover Mode: "StereoViewerType"=dword:80000001
Acer Mode: "StereoViewerType"=dword:00000001
I added that to my 3D settings batch file, and it worked to switch it from Discover to normal. So if you have this happening at boot time, this would fix it.
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
Windows 10 64bit, AMD Ryzen 5 1600X, Nvidia GTX 780
Acer HN274H and Acer H5360
http://phereo.com/stepsbarto
can you upload your batch-file? It would be nice to see what you are loading on startup :)
Regards Flixer
https://forums.geforce.com/default/topic/544995/handy-batch-file-to-fix-3d-settings/
Edit to suit your needs. If you only want the Discover piece delete the other modifications. You can drop this into your startup folder, and it will run at every boot.
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