How to remove 3D Vision Discovery without removing 3D Vision? :(
  3 / 3    
try this (don't know exact translation for the options) go to NVCP go to screen set color settings in point 2 as "use Nvidia settings" instead of "other apps control color settings" this got me a solution mabye
try this (don't know exact translation for the options)
go to NVCP
go to screen
set color settings in point 2 as "use Nvidia settings" instead of "other apps control color settings"
this got me a solution mabye

#31
Posted 10/04/2015 09:54 AM   
It was not... I'm going crazy. I have to boot and reboot to be able to change to 3dvision. At the first boot I can't even select 3dvision :(
It was not...
I'm going crazy.
I have to boot and reboot to be able to change to 3dvision. At the first boot I can't even select 3dvision :(

#32
Posted 10/24/2015 11:13 AM   
Same problem here. Using GTX670 on 2 screens with Windows extend screen, non Surround. Every time when I restart the PC the stupid 3D Vision Discover is chosen by default taking the control of what is displayed on screen (red/cyan instead of 3DVision). Using Windows 10 Pro x64. Nvidia Driver 358.87 Is there any way to block or delete or delete this "feature" (FOR CHRIST SAKE and for continuing to be one NVidia customer) ? Thank you.
Same problem here. Using GTX670 on 2 screens with Windows extend screen, non Surround.
Every time when I restart the PC the stupid 3D Vision Discover is chosen by default taking the control of what is displayed on screen (red/cyan instead of 3DVision).

Using Windows 10 Pro x64. Nvidia Driver 358.87

Is there any way to block or delete or delete this "feature" (FOR CHRIST SAKE and for continuing to be one NVidia customer) ?

Thank you.

#33
Posted 11/08/2015 03:11 AM   
Same problem here! I run 3 Asus-monitors in 3D vision surround. Very often after booting the PC the 3D-device is automatically set to "3D vision Discover" instead of "ASUS 120 Hz 3D-LCD". Even if I change it to "ASUS" it stays as "Discover"!! My only chance is to reboot the PC and try this again. Come on Nividia-support, can you please at least answer to your customers problems?? Even if the answer is "No, you can't disable 3D-vision-Discover without disabling 3D-vision and all you can do is to reboot your PC and hope that you can get rid of the wrong settings!" but it would at least be an answer in this official forum!!
Same problem here! I run 3 Asus-monitors in 3D vision surround. Very often after booting the PC the 3D-device is automatically set to "3D vision Discover" instead of "ASUS 120 Hz 3D-LCD". Even if I change it to "ASUS" it stays as "Discover"!! My only chance is to reboot the PC and try this again.
Come on Nividia-support, can you please at least answer to your customers problems?? Even if the answer is "No, you can't disable 3D-vision-Discover without disabling 3D-vision and all you can do is to reboot your PC and hope that you can get rid of the wrong settings!" but it would at least be an answer in this official forum!!

Win 8.1 pro 64 bit, Gigabyte Z87X-D3H - i7-4770K@3.5 - 32 GB, 2x Geforce TITAN SLI (EVGA), 3x ASUS 3D-Vision-Monitors

#34
Posted 01/04/2016 06:17 PM   
Guys, if you are running in 144hz, try running in 120hz. I haven't had the 3d discover issue for weeks now. The issue stopping also coincided with 361.43 for me.
Guys, if you are running in 144hz, try running in 120hz. I haven't had the 3d discover issue for weeks now. The issue stopping also coincided with 361.43 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

#35
Posted 01/04/2016 06:47 PM   
Hmm, I tried running in 144Hz for a couple of days to see if it would happen again, and it hasn't. It may actually have been fixed once and for all? I had this problem constantly from my first day of installation to about 3 weeks ago, and not once since 361.43. I did do a clean install of Windows 10 around that time too though. Is anyone else still getting it with that driver?
Hmm, I tried running in 144Hz for a couple of days to see if it would happen again, and it hasn't. It may actually have been fixed once and for all? I had this problem constantly from my first day of installation to about 3 weeks ago, and not once since 361.43. I did do a clean install of Windows 10 around that time too though. Is anyone else still getting it with that driver?

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

#36
Posted 01/05/2016 03:52 PM   
This problem is hit and miss for everyone, there seems to be different causes for it. Some have never resolved it as far as I know. For some re-plugging the USB connection from 2.0 to 3.0 does the trick (seems to be newer boards) others plugging from 3.0 to 2.0 does the trick. For some, they seem to be able to use any USB port. For others, they must use a port directly off of the motherboard (Nvidia recommends this) Then there are others that solved the problem by updating drivers for their motherboards USB, chipsets, bios, etc.. But the main culprit seems to be Nvidia's drivers. There is a huge thread on this buried somewhere in the forums, plus many others. My personal experience has been related exclusively to a few drivers. The most recent was 358.50, it was the worst of the offenders that I had experienced to date. 359.00 and 361.43 have been trouble free for me. I thought you might be on to something with that 144Hz thing because I have always kept mine at 120. Thus it could explain why others were having problems when I wasn't. It's really hard to say what causes this for any given person at any given time.
This problem is hit and miss for everyone, there seems to be different causes for it. Some have never resolved it as far as I know.

For some re-plugging the USB connection from 2.0 to 3.0 does the trick (seems to be newer boards) others plugging from 3.0 to 2.0 does the trick. For some, they seem to be able to use any USB port. For others, they must use a port directly off of the motherboard (Nvidia recommends this)

Then there are others that solved the problem by updating drivers for their motherboards USB, chipsets, bios, etc..

But the main culprit seems to be Nvidia's drivers.

There is a huge thread on this buried somewhere in the forums, plus many others.

My personal experience has been related exclusively to a few drivers. The most recent was 358.50, it was the worst of the offenders that I had experienced to date. 359.00 and 361.43 have been trouble free for me.

I thought you might be on to something with that 144Hz thing because I have always kept mine at 120. Thus it could explain why others were having problems when I wasn't.

It's really hard to say what causes this for any given person at any given time.

#37
Posted 01/05/2016 06:50 PM   
There also was one poster that said that if he wiggled the cable connection at emitter, it would cause it.
There also was one poster that said that if he wiggled the cable connection at emitter, it would cause it.

#38
Posted 01/05/2016 06:53 PM   
This seems to be one of those little details (bugs) left in pourpose to make consumers think that Nvidia workers could do better the job easily if they wanted (basic psychological trick). Of course they are aware about this, long time ago, even before you first experienced the problem. Maybe if you pray enough they will fix the problem pressing the enter key, but I doubt it. 800€ the cost of a Nvidia card, and nobody can press a key..., this is ridiculous. When my 660TI dies I will buy a console.
This seems to be one of those little details (bugs) left in pourpose to make consumers think that Nvidia workers could do better the job easily if they wanted (basic psychological trick). Of course they are aware about this, long time ago, even before you first experienced the problem. Maybe if you pray enough they will fix the problem pressing the enter key, but I doubt it. 800€ the cost of a Nvidia card, and nobody can press a key..., this is ridiculous. When my 660TI dies I will buy a console.

- 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)

#39
Posted 01/05/2016 08:08 PM   
FOR FUCK SAKE, i have this problem for years. There is literally no solution. Every time i restart the PC the first thing that i do is switch the stupid discovery thing back to my Asus 120hz 3D LCD. I swear, i don't even know why i take so much abuse from NVIDEA. I was loyal since 3d Vision even started, for 8 years i play games everyday with 3D Vision 2 glasses, i kept upgrading my NVIDEA card to keep up with all the new games and the insane requirement in 3D, and i never felt so abandoned in my life. I don't even feel excited about the upcoming VR because i know it's just another thing NVIDEA will let die from the very start. ZERO SUPPORT.
FOR FUCK SAKE, i have this problem for years. There is literally no solution. Every time i restart the PC the first thing that i do is switch the stupid discovery thing back to my Asus 120hz 3D LCD.

I swear, i don't even know why i take so much abuse from NVIDEA. I was loyal since 3d Vision even started, for 8 years i play games everyday with 3D Vision 2 glasses, i kept upgrading my NVIDEA card to keep up with all the new games and the insane requirement in 3D, and i never felt so abandoned in my life. I don't even feel excited about the upcoming VR because i know it's just another thing NVIDEA will let die from the very start. ZERO SUPPORT.

i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD

#40
Posted 01/06/2016 04:26 PM   
[quote="Payne-TK"]FOR FUCK SAKE, i have this problem for years. There is literally no solution. Every time i restart the PC the first thing that i do is switch the stupid discovery thing back to my Asus 120hz 3D LCD. I swear, i don't even know why i take so much abuse from NVIDEA. I was loyal since 3d Vision even started, for 8 years i play games everyday with 3D Vision 2 glasses, i kept upgrading my NVIDEA card to keep up with all the new games and the insane requirement in 3D, and i never felt so abandoned in my life. I don't even feel excited about the upcoming VR because i know it's just another thing NVIDEA will let die from the very start. ZERO SUPPORT.[/quote] It's not actually Nvidia's fault that 3D is dying. As we can see from this board, every game requires a bespoke fix essentially, and all that is up to the developer as far as Nvidia is able to support it. Have you tried switching USB ports for your emitter/updating chipset drivers? The problem seems to be with the driver booting up before the emitter is detected/initialized. If not you can always try to make a batch file or something that will reenable it automatically.
Payne-TK said:FOR FUCK SAKE, i have this problem for years. There is literally no solution. Every time i restart the PC the first thing that i do is switch the stupid discovery thing back to my Asus 120hz 3D LCD.

I swear, i don't even know why i take so much abuse from NVIDEA. I was loyal since 3d Vision even started, for 8 years i play games everyday with 3D Vision 2 glasses, i kept upgrading my NVIDEA card to keep up with all the new games and the insane requirement in 3D, and i never felt so abandoned in my life. I don't even feel excited about the upcoming VR because i know it's just another thing NVIDEA will let die from the very start. ZERO SUPPORT.


It's not actually Nvidia's fault that 3D is dying. As we can see from this board, every game requires a bespoke fix essentially, and all that is up to the developer as far as Nvidia is able to support it.

Have you tried switching USB ports for your emitter/updating chipset drivers? The problem seems to be with the driver booting up before the emitter is detected/initialized. If not you can always try to make a batch file or something that will reenable it automatically.

#41
Posted 01/06/2016 11:03 PM   
I can't do the USB trick. I am using 3D Vision 2 glasses, the emitter is directly incorporated in the monitor. It is something that the new nvidea drivers broke since who knows what version and they never bothered to fix it. I tried all the tricks with color settings etc. and it's all placebo. It only works for some because of RNG (there are times when windows starts normal so a few successive random occurrences may lead you to think you cured it)
I can't do the USB trick. I am using 3D Vision 2 glasses, the emitter is directly incorporated in the monitor. It is something that the new nvidea drivers broke since who knows what version and they never bothered to fix it.

I tried all the tricks with color settings etc. and it's all placebo. It only works for some because of RNG (there are times when windows starts normal so a few successive random occurrences may lead you to think you cured it)

i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD

#42
Posted 01/07/2016 01:17 PM   
Why don't you guys use the [url=https://forums.geforce.com/default/topic/544995/3d-vision/handy-batch-file-to-fix-3d-settings/1/]bo3b's batch file[/url] Thre is also another user [color="green"]lgp1985[/color] who even created a service for windows to auto enable 3DVision on startup, you can fint it [url=https://3dvisionready.codeplex.com/]here[/url]
Why don't you guys use the bo3b's batch file

Thre is also another user lgp1985 who even created a service for windows to auto enable 3DVision on startup, you can fint it here

Ryzen 1700X 3.9GHz | Asrock X370 Taichi | 16GB G.Skill
GTX 1080 Ti SLI | 850W EVGA P2 | Win7x64
Asus VG278HR | Panasonic TX-58EX750B 4K Active 3D

#43
Posted 01/08/2016 08:53 PM   
OMG ..the new Nvidea GeForce Experience Update fixed the problem for me. It no longer switches to Discovery Glasses on restart. I don't know if they fixed it intentional or by mistake, but it works. FAITH RESTORED
OMG ..the new Nvidea GeForce Experience Update fixed the problem for me. It no longer switches to Discovery Glasses on restart. I don't know if they fixed it intentional or by mistake, but it works.

FAITH RESTORED

i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD

#44
Posted 01/10/2016 08:23 AM   
  3 / 3    
Scroll To Top