Hello,
Today i experienced this issue also.
I have the latest NVidia drivers and the emittor LED flickers after a while and then goes off.
Can't turn it on also, i have to disconnect the cable and reconnect it again.
I have a clean install of Windows 8.1 with no other apps installed.
Why are there so much problems with games and NVidia 3D?
We paid big bucks for 3D hardware and everytime it gives problems.
I don't understand why making a new windows while the older ones works good.
I switched to Win 8 because they said it works better with 3D, well i found out that this isn't true.
Can i have my money back? no offcourse not, but for a year now i did not play games in 3D with satisfactory with a lot of complains to people like HelixMod guys that don't deserve complains. They try the best they can but everytime something else screws up to play games in 3D.
I don't have Oracle Virtual box installed on my pc, i don't have anything else other then Win 8 installed on this pc and the game i wanted to play in 3D.
Hope there is someone that knows what is happening here. In future i'll be more carefull and keep my wallet closed, for example: Oculus Rift and Vive i don't buy because of these problems.
A new pc also not because the apps coming out these days are crap as hell. Why keep changing things while they worked before?
Today i experienced this issue also.
I have the latest NVidia drivers and the emittor LED flickers after a while and then goes off.
Can't turn it on also, i have to disconnect the cable and reconnect it again.
I have a clean install of Windows 8.1 with no other apps installed.
Why are there so much problems with games and NVidia 3D?
We paid big bucks for 3D hardware and everytime it gives problems.
I don't understand why making a new windows while the older ones works good.
I switched to Win 8 because they said it works better with 3D, well i found out that this isn't true.
Can i have my money back? no offcourse not, but for a year now i did not play games in 3D with satisfactory with a lot of complains to people like HelixMod guys that don't deserve complains. They try the best they can but everytime something else screws up to play games in 3D.
I don't have Oracle Virtual box installed on my pc, i don't have anything else other then Win 8 installed on this pc and the game i wanted to play in 3D.
Hope there is someone that knows what is happening here. In future i'll be more carefull and keep my wallet closed, for example: Oculus Rift and Vive i don't buy because of these problems.
A new pc also not because the apps coming out these days are crap as hell. Why keep changing things while they worked before?
After my install of Windows 10 I have started experiencing this problem as well. It has taken me a while to notice because I haven't tried gaming in 3D much at all since the new install. But I noticed the last few days that after my PC runs a while my emitter shuts off. Reconnecting the cable wakes it up again, but I have been too busy with other things to verify if it would shut off during a gaming session.
After my install of Windows 10 I have started experiencing this problem as well. It has taken me a while to notice because I haven't tried gaming in 3D much at all since the new install. But I noticed the last few days that after my PC runs a while my emitter shuts off. Reconnecting the cable wakes it up again, but I have been too busy with other things to verify if it would shut off during a gaming session.
|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
You can try the suggestion by this poster, it fixed the issue for him.
[url]https://forums.geforce.com/default/topic/818046/fix-for-3d-emitter-not-loading-on-boot-and-always-reverting-to-3d-vision-discovery-/#4483230[/url]
Actually installing the latest driver update corrected the problem. Only thing is, a game I was getting great performance in has reverted to sucky performance... so pick your poison I guess. I'm going to try to go back to 368.22 or whatever the previous update was and see if the emitter thing was just a quirky install.
Actually installing the latest driver update corrected the problem. Only thing is, a game I was getting great performance in has reverted to sucky performance... so pick your poison I guess. I'm going to try to go back to 368.22 or whatever the previous update was and see if the emitter thing was just a quirky install.
|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
Same behaviour here after switching to windows 10. In win7 all worked like a charm.
even more. I am suffering constant hangs every time I activate or deactivate 3d vision. I opened this topic:
https://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10/
I just got the 3d vision 2 glasses kit, I had 3d vision 1 years ago. The emitter shuts off after I am in windows for a while, requiring me to plug in the usb cable in the emitter to get the light green. I don't know what to do, is the emitter faulty?
I just got the 3d vision 2 glasses kit, I had 3d vision 1 years ago. The emitter shuts off after I am in windows for a while, requiring me to plug in the usb cable in the emitter to get the light green. I don't know what to do, is the emitter faulty?
There's several other threads related to this Windows 8.1/10 Power Saving issue which sometimes causes BSODs and system hangs. You're certainly not the only one experiencing this. You can find some workarounds in those threads.
There's several other threads related to this Windows 8.1/10 Power Saving issue which sometimes causes BSODs and system hangs. You're certainly not the only one experiencing this. You can find some workarounds in those threads.
I have all power saving, like for the computer and monitor, turned off. Do you mean power saving for usb? How do I turn that off? The emitter hasn't shut off during 3d games or blu ray 3d's yet, it always seems to shut off when I am in the desktop doing other things.
I have all power saving, like for the computer and monitor, turned off. Do you mean power saving for usb? How do I turn that off? The emitter hasn't shut off during 3d games or blu ray 3d's yet, it always seems to shut off when I am in the desktop doing other things.
A common suggestion is to disable USB Selective Suspend in the Advanced Power Settings in Control Panel but unfortunately that didn't work for anyone afaik. That's why I said you should check other threads related to this. Most of them are about crashes and syshangs. This is a good start:
http://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10
Guys I don't believe any of those old threads will help Windows 10 users.. I had the same issue when I was on windows 10 and tried all those old suggestions none worked..
I don't remember what exactly was the issue but never found a fix.. The only thing you can do is unplug the emitter and back in.. this only happens when not ingame..
When ingame it works fine it is just when you sit at desktop browsing internet or something the emitter just turns off.. Even if you turn off the slect suspend as that does nothing..
Something needs to be fixed either in Win 10 or NVidia drivers in win 10..
Guys I don't believe any of those old threads will help Windows 10 users.. I had the same issue when I was on windows 10 and tried all those old suggestions none worked..
I don't remember what exactly was the issue but never found a fix.. The only thing you can do is unplug the emitter and back in.. this only happens when not ingame..
When ingame it works fine it is just when you sit at desktop browsing internet or something the emitter just turns off.. Even if you turn off the slect suspend as that does nothing..
Something needs to be fixed either in Win 10 or NVidia drivers in win 10..
This issue also happens in the latest Windows 8.1 as I have personally experienced it. Also you don't need to replug the emitter. I have posted in other threads that a simple workaround is to manually re-detect your devices by starting a program called HWINFO64 which will turn the emitter on again. This works for me 100% of the time and I've had no issues since.
You just have to remember that a crash or syshang may occur when:
- Emitter off + starting 3D vision in a game or movie;
- Emitter off + 3D vision Enabled in the nVidia CP while casually browsing in Chrome or Mozilla Firefox;
- Emitter off + Enabling/Disabling 3D vision in the nVidia CP.
This issue also happens in the latest Windows 8.1 as I have personally experienced it. Also you don't need to replug the emitter. I have posted in other threads that a simple workaround is to manually re-detect your devices by starting a program called HWINFO64 which will turn the emitter on again. This works for me 100% of the time and I've had no issues since.
You just have to remember that a crash or syshang may occur when:
- Emitter off + starting 3D vision in a game or movie;
- Emitter off + 3D vision Enabled in the nVidia CP while casually browsing in Chrome or Mozilla Firefox;
- Emitter off + Enabling/Disabling 3D vision in the nVidia CP.
[quote="The_Nephilim"]Well redetecting as you call it is basically the same as just unplugging and replugging it in..[/quote]
The main difference being that it's not being physically handled, thus eliminating the chance of damaging the emitter itself. Since, 99.9% of the time it seems to be software related. I've only seen one poster mention that he could wiggle the connection an initiate a failure. In his case a replacement solved the issue.
The_Nephilim said:Well redetecting as you call it is basically the same as just unplugging and replugging it in..
The main difference being that it's not being physically handled, thus eliminating the chance of damaging the emitter itself. Since, 99.9% of the time it seems to be software related. I've only seen one poster mention that he could wiggle the connection an initiate a failure. In his case a replacement solved the issue.
After much testing and lots of headaches I have finally concluded why the emitter turns off. Although I'm not 100% sure I would much appreciate if you guys can further test my findings:
- Power Saving options in Windows have absolutely NO EFFECT on the emitter;
- The emitter is solely controlled by an nVidia service;
- The emitter will always turn itself off after a certain period of time if you Disable 3D vision in the nVidia Control Panel;
- The emitter will always remain ON if you have Enabled 3D vision in the nVidia CP, although you will still have to manually turn it on by re-plugging it or by re-detecting it (for which I use HWINFO64) if it was off beforehand.
This pretty much explains why some people haven't seen the emitter go off if they've always had 3D vision enabled in the nVidia CP.
Furthermore, this means that everyone experiencing system crashes or hangs when starting a game in 3D due to the emitter being off, would have to either manually turn on the emitter, which is a pain as many of you have probably noticed, or always enable 3D vision and use the Advanced 3D Configuration Tool to disable the "3D mode always enabled" option and manually toggle 3D with the shortcut. This will of course have an impact on 2D performance but it is nothing compared to those BSODs, at least for me.
I would also very much like to thank nVidia for really testing the crap out of this before making such a huge change.
If you guys can test this and post your results here for future reference that would be really swell :)
After much testing and lots of headaches I have finally concluded why the emitter turns off. Although I'm not 100% sure I would much appreciate if you guys can further test my findings:
- Power Saving options in Windows have absolutely NO EFFECT on the emitter;
- The emitter is solely controlled by an nVidia service;
- The emitter will always turn itself off after a certain period of time if you Disable 3D vision in the nVidia Control Panel;
- The emitter will always remain ON if you have Enabled 3D vision in the nVidia CP, although you will still have to manually turn it on by re-plugging it or by re-detecting it (for which I use HWINFO64) if it was off beforehand.
This pretty much explains why some people haven't seen the emitter go off if they've always had 3D vision enabled in the nVidia CP.
Furthermore, this means that everyone experiencing system crashes or hangs when starting a game in 3D due to the emitter being off, would have to either manually turn on the emitter, which is a pain as many of you have probably noticed, or always enable 3D vision and use the Advanced 3D Configuration Tool to disable the "3D mode always enabled" option and manually toggle 3D with the shortcut. This will of course have an impact on 2D performance but it is nothing compared to those BSODs, at least for me.
I would also very much like to thank nVidia for really testing the crap out of this before making such a huge change.
If you guys can test this and post your results here for future reference that would be really swell :)
Today i experienced this issue also.
I have the latest NVidia drivers and the emittor LED flickers after a while and then goes off.
Can't turn it on also, i have to disconnect the cable and reconnect it again.
I have a clean install of Windows 8.1 with no other apps installed.
Why are there so much problems with games and NVidia 3D?
We paid big bucks for 3D hardware and everytime it gives problems.
I don't understand why making a new windows while the older ones works good.
I switched to Win 8 because they said it works better with 3D, well i found out that this isn't true.
Can i have my money back? no offcourse not, but for a year now i did not play games in 3D with satisfactory with a lot of complains to people like HelixMod guys that don't deserve complains. They try the best they can but everytime something else screws up to play games in 3D.
I don't have Oracle Virtual box installed on my pc, i don't have anything else other then Win 8 installed on this pc and the game i wanted to play in 3D.
Hope there is someone that knows what is happening here. In future i'll be more carefull and keep my wallet closed, for example: Oculus Rift and Vive i don't buy because of these problems.
A new pc also not because the apps coming out these days are crap as hell. Why keep changing things while they worked before?
|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
https://forums.geforce.com/default/topic/818046/fix-for-3d-emitter-not-loading-on-boot-and-always-reverting-to-3d-vision-discovery-/#4483230
|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
even more. I am suffering constant hangs every time I activate or deactivate 3d vision. I opened this topic:
https://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10/
http://forums.geforce.com/default/topic/971868/3d-vision/pc-crash-everytime-i-enable-3d-vision-with-windows-10
I don't remember what exactly was the issue but never found a fix.. The only thing you can do is unplug the emitter and back in.. this only happens when not ingame..
When ingame it works fine it is just when you sit at desktop browsing internet or something the emitter just turns off.. Even if you turn off the slect suspend as that does nothing..
Something needs to be fixed either in Win 10 or NVidia drivers in win 10..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
You just have to remember that a crash or syshang may occur when:
- Emitter off + starting 3D vision in a game or movie;
- Emitter off + 3D vision Enabled in the nVidia CP while casually browsing in Chrome or Mozilla Firefox;
- Emitter off + Enabling/Disabling 3D vision in the nVidia CP.
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
The main difference being that it's not being physically handled, thus eliminating the chance of damaging the emitter itself. Since, 99.9% of the time it seems to be software related. I've only seen one poster mention that he could wiggle the connection an initiate a failure. In his case a replacement solved the issue.
- Power Saving options in Windows have absolutely NO EFFECT on the emitter;
- The emitter is solely controlled by an nVidia service;
- The emitter will always turn itself off after a certain period of time if you Disable 3D vision in the nVidia Control Panel;
- The emitter will always remain ON if you have Enabled 3D vision in the nVidia CP, although you will still have to manually turn it on by re-plugging it or by re-detecting it (for which I use HWINFO64) if it was off beforehand.
This pretty much explains why some people haven't seen the emitter go off if they've always had 3D vision enabled in the nVidia CP.
Furthermore, this means that everyone experiencing system crashes or hangs when starting a game in 3D due to the emitter being off, would have to either manually turn on the emitter, which is a pain as many of you have probably noticed, or always enable 3D vision and use the Advanced 3D Configuration Tool to disable the "3D mode always enabled" option and manually toggle 3D with the shortcut. This will of course have an impact on 2D performance but it is nothing compared to those BSODs, at least for me.
I would also very much like to thank nVidia for really testing the crap out of this before making such a huge change.
If you guys can test this and post your results here for future reference that would be really swell :)