3D emitter turns off ?
  3 / 3    
[quote="Kaimastah"]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 :)[/quote] Oh... Yeah... 3D Vision is always ON in NVPanel and the emitter never goes "dark". If for some reason you set 3D Vision to OFF in Nvpanel, the emitter goes dark and later on you set 3D Vision to ON in Npanel you need to "manually" replug it for the OS to autodetect it. When is "dark" it doesn't exist, from the software point of view. So, yeah all the crashes that people have can come from here:) I thought everyone was having 3D Vision as always ON in Nvpanel and had issues of the emitter turning off after some time...
Kaimastah said: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 :)


Oh...
Yeah... 3D Vision is always ON in NVPanel and the emitter never goes "dark".
If for some reason you set 3D Vision to OFF in Nvpanel, the emitter goes dark and later on you set 3D Vision to ON in Npanel you need to "manually" replug it for the OS to autodetect it.
When is "dark" it doesn't exist, from the software point of view.

So, yeah all the crashes that people have can come from here:)

I thought everyone was having 3D Vision as always ON in Nvpanel and had issues of the emitter turning off after some time...

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#31
Posted 12/16/2016 10:40 PM   
Well I'm not sure when this thing was implemented but in the past I could always turn off 3D vision in the CP without the emitter going off. This was maybe 2 years ago, not really sure. But I've always done that since enabling 3D vision has an impact on 2D performance.
Well I'm not sure when this thing was implemented but in the past I could always turn off 3D vision in the CP without the emitter going off. This was maybe 2 years ago, not really sure. But I've always done that since enabling 3D vision has an impact on 2D performance.

#32
Posted 12/16/2016 10:46 PM   
[quote="Kaimastah"]Well I'm not sure when this thing was implemented but in the past I could always turn off 3D vision in the CP without the emitter going off. This was maybe 2 years ago, not really sure. But I've always done that since enabling 3D vision has an impact on 2D performance.[/quote] That was on Windows 7. Windows 8/8.1/10 has this issue. Is not a driver problem but rather an OS design problem. The OS decides to suspend/unplug different devices. Don't know if Nvidia can do anything about it (except keeping the service ON even if 3D Vision is disabled). But, I think just re-plugging the 3D Vision emitter is the easiest fix. One problem I have related to Win10, is that even if 3D Vision is set to ON in NVPanel, sometimes on BOOT my emitter is dark. (Just on cold-boot, not restart). So... I guess, yeah Win10 FTW... /not :) Edit: On my Laptop, where the emitter is embedded, I don't have this problem (Win 10 as well). Only when the emitter is connected on USB on my desktop. so clearly an OS problem :( Power savings do help when 3D Vision is ON and emitter plugged. Without disabling "power savings" or what is called, the emitter will turn dark even if 3D Vision is ON... :(
Kaimastah said:Well I'm not sure when this thing was implemented but in the past I could always turn off 3D vision in the CP without the emitter going off. This was maybe 2 years ago, not really sure. But I've always done that since enabling 3D vision has an impact on 2D performance.


That was on Windows 7.

Windows 8/8.1/10 has this issue. Is not a driver problem but rather an OS design problem. The OS decides to suspend/unplug different devices. Don't know if Nvidia can do anything about it (except keeping the service ON even if 3D Vision is disabled).



But, I think just re-plugging the 3D Vision emitter is the easiest fix. One problem I have related to Win10, is that even if 3D Vision is set to ON in NVPanel, sometimes on BOOT my emitter is dark. (Just on cold-boot, not restart). So... I guess, yeah Win10 FTW... /not :)

Edit:
On my Laptop, where the emitter is embedded, I don't have this problem (Win 10 as well). Only when the emitter is connected on USB on my desktop. so clearly an OS problem :(

Power savings do help when 3D Vision is ON and emitter plugged. Without disabling "power savings" or what is called, the emitter will turn dark even if 3D Vision is ON... :(

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#33
Posted 12/16/2016 10:54 PM   
I guess that makes a lot of sense. The thing is that this wasn't always happening on Windows 8. Only until a specific update or maybe somewhere along the way because I've been on Win 8 since it was released and this was not an issue for a long time. But one day my PC began to BSOD after not playing in 3D for a few weeks or months (actually I totally had the emitter unplugged for a long time in that period) and only after a while I noticed that the emitter was going off. This was really surprising for me because I had not seen the emitter going off like ever. In any case I feel like a dumbass for not realizing this sooner lol. Also it's pretty funny that you knew this the whole time lol.
I guess that makes a lot of sense. The thing is that this wasn't always happening on Windows 8. Only until a specific update or maybe somewhere along the way because I've been on Win 8 since it was released and this was not an issue for a long time. But one day my PC began to BSOD after not playing in 3D for a few weeks or months (actually I totally had the emitter unplugged for a long time in that period) and only after a while I noticed that the emitter was going off. This was really surprising for me because I had not seen the emitter going off like ever.

In any case I feel like a dumbass for not realizing this sooner lol.
Also it's pretty funny that you knew this the whole time lol.

#34
Posted 12/16/2016 11:21 PM   
[quote="Kaimastah"]I guess that makes a lot of sense. The thing is that this wasn't always happening on Windows 8. Only until a specific update or maybe somewhere along the way because I've been on Win 8 since it was released and this was not an issue for a long time. But one day my PC began to BSOD after not playing in 3D for a few weeks or months (actually I totally had the emitter unplugged for a long time in that period) and only after a while I noticed that the emitter was going off. This was really surprising for me because I had not seen the emitter going off like ever. In any case I feel like a dumbass for not realizing this sooner lol. Also it's pretty funny that you knew this the whole time lol.[/quote] Yeah:( I didn't realise that 3D Vision was turned Off in Nvpanel and later turned on;) I would have said it from the beginning;) I know is a pain. That's why normally for me is always ON:))
Kaimastah said:I guess that makes a lot of sense. The thing is that this wasn't always happening on Windows 8. Only until a specific update or maybe somewhere along the way because I've been on Win 8 since it was released and this was not an issue for a long time. But one day my PC began to BSOD after not playing in 3D for a few weeks or months (actually I totally had the emitter unplugged for a long time in that period) and only after a while I noticed that the emitter was going off. This was really surprising for me because I had not seen the emitter going off like ever.

In any case I feel like a dumbass for not realizing this sooner lol.
Also it's pretty funny that you knew this the whole time lol.


Yeah:( I didn't realise that 3D Vision was turned Off in Nvpanel and later turned on;) I would have said it from the beginning;) I know is a pain. That's why normally for me is always ON:))

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#35
Posted 12/17/2016 11:35 AM   
Well since I've discovered this only last night after months and countless hours of trying to make the emitter always be on even with 3D turned off (rofl), it seems that Power Savings did not affect the emitter for at least a few hours. But today after I woke up I noticed the emitter was off again even with 3D turned on and I suspect this happened because Windows went in Standby mode so yeah I think you're right about the Power Saving thing. I'm gonna have to test this again with Power Saving off meh lol. Anywho I'm really glad I finally sorted this thing out. Thanks again Helifax for helping out :D
Well since I've discovered this only last night after months and countless hours of trying to make the emitter always be on even with 3D turned off (rofl), it seems that Power Savings did not affect the emitter for at least a few hours. But today after I woke up I noticed the emitter was off again even with 3D turned on and I suspect this happened because Windows went in Standby mode so yeah I think you're right about the Power Saving thing. I'm gonna have to test this again with Power Saving off meh lol.

Anywho I'm really glad I finally sorted this thing out. Thanks again Helifax for helping out :D

#36
Posted 12/17/2016 12:35 PM   
Well Glad I found this thread and realize now it cant really be corrected, was wondering why the dang thing kept turning off on me last night after a short time of being plugged in, not the end of the world but a PITA. On a side note and why I'm posting, you can reinitialize the emitter by just calling up Devices and printers.
Well Glad I found this thread and realize now it cant really be corrected, was wondering why the dang thing kept turning off on me last night after a short time of being plugged in, not the end of the world but a PITA. On a side note and why I'm posting, you can reinitialize the emitter by just calling up Devices and printers.

#37
Posted 03/09/2017 06:40 PM   
  3 / 3    
Scroll To Top