Hi I have purchased the 3D vision 2 kit to go with iy VG248 Asus 3d ready monitor.
My issue is as follows,Ii have 2 monitors the one above and an LG 3d Passive D2342 using Zalman driver so Nvidia recognizes the #d ( it works fine in passive no issues) all running on Windows 7 GTX680 12g ram and I7 cpu OCZ SSD Vertex 4.
I need to unplug and re-plug the emitter every time I start my pc, this is frustrating and then set-up the Nvidia control panel back to Asus monitor if not if shows 3d device detect (or something similar).
Is there a fix or workaround ? i really do not want to have to purchase another Asus monitor since the LG works fine as a second monitor.
looking forward to some feed back or suggestions.
Thanks
Update Edit: Below is the link to the work around solution listed on Page 4 of this post,
Thanks to TsaebehT for his work and creating the detailled instructions for this.
[url]https://forums.geforce.com/default/topic/539264/3d-vision/emitter-disconneting-on-computer-boot/post/3792104/#3792104[/url]
Hi I have purchased the 3D vision 2 kit to go with iy VG248 Asus 3d ready monitor.
My issue is as follows,Ii have 2 monitors the one above and an LG 3d Passive D2342 using Zalman driver so Nvidia recognizes the #d ( it works fine in passive no issues) all running on Windows 7 GTX680 12g ram and I7 cpu OCZ SSD Vertex 4.
I need to unplug and re-plug the emitter every time I start my pc, this is frustrating and then set-up the Nvidia control panel back to Asus monitor if not if shows 3d device detect (or something similar).
Is there a fix or workaround ? i really do not want to have to purchase another Asus monitor since the LG works fine as a second monitor.
looking forward to some feed back or suggestions.
Thanks
Update Edit: Below is the link to the work around solution listed on Page 4 of this post,
Thanks to TsaebehT for his work and creating the detailled instructions for this.
I am running the latest 314.22, although i must admit i did not do a clean install, not sure if that would correct issue or not, just have so many adjustment done in control panel a clean boot will wipe those all away :-(
I am running the latest 314.22, although i must admit i did not do a clean install, not sure if that would correct issue or not, just have so many adjustment done in control panel a clean boot will wipe those all away :-(
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
I did a clean install of driver 314.22, did a shutdown, emitter turns on but as soon as windows boots it turns off and I get the " 3d Vision discover" under 3d in control panel.
Once I disconnect the emitter and reconnect everything is works fine.
I did a clean install of driver 314.22, did a shutdown, emitter turns on but as soon as windows boots it turns off and I get the " 3d Vision discover" under 3d in control panel.
Once I disconnect the emitter and reconnect everything is works fine.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
Hmmm... Seemed like the new driver was working for other people who have seen the problem.
Try another thing I suggested in that other thread.
Maybe try making the NVidia Stereoscopic service for the emitter an Automatic Delayed start in the Services panel.
That will change the timing of when it gets launched, and I think this problem stems from timing in general.
My emitter has been doing this, too. I haven't really looked into it, since it doesn't bother me that much; just unplug and re-plug. I assumed it was just a quirk of my motherboard's USB chip or something.
My emitter has been doing this, too. I haven't really looked into it, since it doesn't bother me that much; just unplug and re-plug. I assumed it was just a quirk of my motherboard's USB chip or something.
I tried changing it to delayed start and I get the following error:
The delayed auto-start flag could not be set. Error 87: The parameter is incorrect.
If it is something to do with the start order at boot up, maybe you could use CC Cleaner and under the advanced tab use the options to clear out the caches, then restart. Be sure to uncheck the boxes in CC Cleaner, you do not want to clear those all the time.
Assuming you are using an external emitter. An internal emitter is driven by monitor software I think.
http://www.piriform.com/ccleaner
If it is something to do with the start order at boot up, maybe you could use CC Cleaner and under the advanced tab use the options to clear out the caches, then restart. Be sure to uncheck the boxes in CC Cleaner, you do not want to clear those all the time.
Assuming you are using an external emitter. An internal emitter is driven by monitor software I think.
http://www.piriform.com/ccleaner
Yes i am using an external emitter, i will try changing to automatic delayed in services and see if that works. if someone else tried this please let me know here.
Thanks for your input
Yes i am using an external emitter, i will try changing to automatic delayed in services and see if that works. if someone else tried this please let me know here.
Thanks for your input
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
[quote="TaergEno"]I tried changing it to delayed start and I get the following error:
The delayed auto-start flag could not be set. Error 87: The parameter is incorrect.[/quote]
Yes, drag, looks like this is broken now. Doesn't work on any service.
Alternate solution for changing the timing is to run a 3rd party app like Startup Delayer:
[url]http://www.r2.com.au/page/products/show/startdelay[/url]
One other suggestion that worked for some other people was move the emitter to a different USB port (like front to back for example), and/or use a USB hub.
One other suggestion that worked for some other people was move the emitter to a different USB port (like front to back for example), and/or use a USB hub.
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
There was a user that posted within the last few months that had the same problem. He narrowed it down to the cable at the emitter end. He would put slight pressure/wiggle the cord and the emitter would engage. Perhaps you have the same issue.
There was a user that posted within the last few months that had the same problem. He narrowed it down to the cable at the emitter end. He would put slight pressure/wiggle the cord and the emitter would engage. Perhaps you have the same issue.
I would rule that one out, since i see the emitter turn on when i boot up, so i know it is getting juice (so too speak) but once windows is up the emitter turns off so i need to physically disconnect the cable from emitter and re-plug it in then "voilas" Houston we have a connection.
I will try plugging the emitter to my USB hub this might cause the needed delay in connection at boot up.
I would rule that one out, since i see the emitter turn on when i boot up, so i know it is getting juice (so too speak) but once windows is up the emitter turns off so i need to physically disconnect the cable from emitter and re-plug it in then "voilas" Houston we have a connection.
I will try plugging the emitter to my USB hub this might cause the needed delay in connection at boot up.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
I tried connecting the emitter to a USB hub and it works great, I reboot ( full shutdown) many time and every time the emitter connected. I guess the delay caused by the hub to connect to the pc permits the emitter to connect after everything is booted.
Thank for that ideal and suggestion , hope it works for others as well.
I tried connecting the emitter to a USB hub and it works great, I reboot ( full shutdown) many time and every time the emitter connected. I guess the delay caused by the hub to connect to the pc permits the emitter to connect after everything is booted.
Thank for that ideal and suggestion , hope it works for others as well.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
My issue is as follows,Ii have 2 monitors the one above and an LG 3d Passive D2342 using Zalman driver so Nvidia recognizes the #d ( it works fine in passive no issues) all running on Windows 7 GTX680 12g ram and I7 cpu OCZ SSD Vertex 4.
I need to unplug and re-plug the emitter every time I start my pc, this is frustrating and then set-up the Nvidia control panel back to Asus monitor if not if shows 3d device detect (or something similar).
Is there a fix or workaround ? i really do not want to have to purchase another Asus monitor since the LG works fine as a second monitor.
looking forward to some feed back or suggestions.
Thanks
Update Edit: Below is the link to the work around solution listed on Page 4 of this post,
Thanks to TsaebehT for his work and creating the detailled instructions for this.
https://forums.geforce.com/default/topic/539264/3d-vision/emitter-disconneting-on-computer-boot/post/3792104/#3792104
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
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
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
Once I disconnect the emitter and reconnect everything is works fine.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
Try another thing I suggested in that other thread.
Maybe try making the NVidia Stereoscopic service for the emitter an Automatic Delayed start in the Services panel.
That will change the timing of when it gets launched, and I think this problem stems from timing in general.
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
The delayed auto-start flag could not be set. Error 87: The parameter is incorrect.
Assuming you are using an external emitter. An internal emitter is driven by monitor software I think.
http://www.piriform.com/ccleaner
Thanks for your input
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
Yes, drag, looks like this is broken now. Doesn't work on any service.
Alternate solution for changing the timing is to run a 3rd party app like Startup Delayer:
http://www.r2.com.au/page/products/show/startdelay
One other suggestion that worked for some other people was move the emitter to a different USB port (like front to back for example), and/or use a USB hub.
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
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
I will try plugging the emitter to my USB hub this might cause the needed delay in connection at boot up.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.
Thank for that ideal and suggestion , hope it works for others as well.
Asus Rampage IV Formula X79 Mobo ,Windows 10 64 bit, GTX970 Strix, Corsair Vengeance 16g ram 1866, I7 3820 3.6G 10M R cpu, OCZ SSD Vertex 256g 4,Samsung SSD 840 Pro 256g , Nvidia 3d Vision 2, Asus VG248qe & LG2342 3D ready monitors, Corsair K95 rgb Keyboard, ASTRO 2013 ED. headphones & AMP, MMO Cyborg mouse.