FOR NVIDIA SUPPORT: 3D VISION FLICKERING ISSUE Please help us fix this problem.
11 / 16
By the way, I can offer a counter example that it works well for me in a number of different setups.
I've used a straight CRT setup, where I can run the monitor at 85Hz, 100Hz, or 120Hz without trouble. I do very occasionally see the flicker when running at 120Hz, but never at lower frequencies.
I also tried out and returned the Viewsonic Vx2265wm (too small). It ran at 120Hz there without trouble, but also very occasional flickers.
I've used the kit for almost a year now, and it works pretty well for me, over two different motherboards, two different CPUs (one dual, one quad), multiple nVidia versions, switching from Raptors to SSD, and either single or SLI which I have now. I've even used it through TH2G with three surround CRTs all in Stereo, at 85Hz. (Fun! /alien.gif' class='bbc_emoticon' alt=':alien:' /> )
It seems clear that 3d Vision is on the outside edge of performance that can be achieved through the USB.
It looks to me that the crux of people's problems are that their systems are delaying USB events. Every frame requires a USB event to be sent, to tell the emitter to send the signal to the glasses. If you delay that event, or drop some, it will cause flicker.
This suggests that the glasses plus emitter combo is susceptible to problems in the software, or other devices that use USB bandwidth.
This is also why lowering the frequency to 100Hz often works, because it lowers the demands on the timing.
My best suggestion is to plug your emitter into a motherboard connection, but make sure that the emitter is the *only* item for that hub. If you plug in a mouse, or a hard drive, or something else to that hub, you might very well get USB stalls that cause flicker.
Look in Device Manager, and make sure your emitter is the sole item for that motherboard hub.
If you have other software on the system that turns off interrupts for any length of time, you can also expect USB stalls, and thus flicker. I know this can be very difficult to determine, so a good experiment would be to make a new bootable partition and install a clean OS upon that partition with nothing except your nVidia drivers, and your motherboard drivers. There is a lot of poorly written software in the world.
You can easily make a new partition in either Vista or 7 by using the Disk Management and shrinking a current volume.
By the way, I can offer a counter example that it works well for me in a number of different setups.
I've used a straight CRT setup, where I can run the monitor at 85Hz, 100Hz, or 120Hz without trouble. I do very occasionally see the flicker when running at 120Hz, but never at lower frequencies.
I also tried out and returned the Viewsonic Vx2265wm (too small). It ran at 120Hz there without trouble, but also very occasional flickers.
I've used the kit for almost a year now, and it works pretty well for me, over two different motherboards, two different CPUs (one dual, one quad), multiple nVidia versions, switching from Raptors to SSD, and either single or SLI which I have now. I've even used it through TH2G with three surround CRTs all in Stereo, at 85Hz. (Fun! /alien.gif' class='bbc_emoticon' alt=':alien:' /> )
It seems clear that 3d Vision is on the outside edge of performance that can be achieved through the USB.
It looks to me that the crux of people's problems are that their systems are delaying USB events. Every frame requires a USB event to be sent, to tell the emitter to send the signal to the glasses. If you delay that event, or drop some, it will cause flicker.
This suggests that the glasses plus emitter combo is susceptible to problems in the software, or other devices that use USB bandwidth.
This is also why lowering the frequency to 100Hz often works, because it lowers the demands on the timing.
My best suggestion is to plug your emitter into a motherboard connection, but make sure that the emitter is the *only* item for that hub. If you plug in a mouse, or a hard drive, or something else to that hub, you might very well get USB stalls that cause flicker.
Look in Device Manager, and make sure your emitter is the sole item for that motherboard hub.
If you have other software on the system that turns off interrupts for any length of time, you can also expect USB stalls, and thus flicker. I know this can be very difficult to determine, so a good experiment would be to make a new bootable partition and install a clean OS upon that partition with nothing except your nVidia drivers, and your motherboard drivers. There is a lot of poorly written software in the world.
You can easily make a new partition in either Vista or 7 by using the Disk Management and shrinking a current volume.
Good luck, and let us know what you find out.
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
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia![/quote]
Jrox thats EXACTLY what's happening, everytime I move my mouse the glasses flicker like crazy. I'm going to try and change the IRQs and see if that make the difference.
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
Jrox thats EXACTLY what's happening, everytime I move my mouse the glasses flicker like crazy. I'm going to try and change the IRQs and see if that make the difference.
[quote name='TrekCZ' post='1032805' date='Apr 2 2010, 07:43 PM']Unfortunatelly there is no easy way to change IRQ in windows Vista and greater and usually motherboards do not such a tweaking.
You may want to try your IR emmiter and mouse in various usb ports.[/quote]
I've disabled all peripheral, except "pci express root" which are on the same IRQ, no change for me :(
[quote name='TrekCZ' post='1032805' date='Apr 2 2010, 07:43 PM']Unfortunatelly there is no easy way to change IRQ in windows Vista and greater and usually motherboards do not such a tweaking.
You may want to try your IR emmiter and mouse in various usb ports.
I've disabled all peripheral, except "pci express root" which are on the same IRQ, no change for me :(
Run System Information - msinfo32 and take a look what is on the same IRQ with ir emmiter.
You can also take a look in bios if there are some options - consult manual (e.g. try to enable/disable HPET if you have it there ...)
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia![/quote]
My system also seems to have devices sharing the port my GFX card uses (port 16) - can I literally select the components sharing the same port as the entry for the gfx card and select a vacant IRQ number?
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
My system also seems to have devices sharing the port my GFX card uses (port 16) - can I literally select the components sharing the same port as the entry for the gfx card and select a vacant IRQ number?
Lord, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.
-------------------
Vitals: Windows 7 64bit, i5 2500 @ 4.4ghz, SLI GTX670, 8GB, Viewsonic VX2268WM
Take a look at msinfo what is on the same irq as usb - I have nic - make sure you have the latest drivers for all devices on that irq, it is common that manufacturers provide crap drivers for their devices ruining whole system, I have nvidia motherboard so everything is excellent as usual. Make sure you have high precision timer there.
Take a look in device manager for usb root serving your IR emmiter. Make sure everything is ok there and that you have certified PSU capable of powering your usb devices in a certified way.
Also I forgot, run DPC latency checker [url="http://www.thesycon.de/deu/latency_check.shtml"]http://www.thesycon.de/deu/latency_check.shtml[/url] couple of minutes and there should be always reported
[i]This machine should be able to handle real-time streaming of audio and/or video data without drop-outs.[/i]
Take a look at msinfo what is on the same irq as usb - I have nic - make sure you have the latest drivers for all devices on that irq, it is common that manufacturers provide crap drivers for their devices ruining whole system, I have nvidia motherboard so everything is excellent as usual. Make sure you have high precision timer there.
Take a look in device manager for usb root serving your IR emmiter. Make sure everything is ok there and that you have certified PSU capable of powering your usb devices in a certified way.
I may have found my problem...I am just unsure as how to fix it. Windows has been giving me a lot of the "your device could run faster if you plugged it into a USB 2.0 port" Yes...my USB ports are 2.0 high speed. I checked device manager to make sure, all 4 root hubs I looked at were running high speed. Open LFD, play a little while, flicker starts, quit game....now my nvidia stereo controller (it even switched hubs to sit with my mouse?) is on a hub that is running "full speed" that before when I had checked it was high speed. 2 hubs downgraded themselves to full speed....wtf? If anyone has an answer to that, I'll love you forever lol.
I may have found my problem...I am just unsure as how to fix it. Windows has been giving me a lot of the "your device could run faster if you plugged it into a USB 2.0 port" Yes...my USB ports are 2.0 high speed. I checked device manager to make sure, all 4 root hubs I looked at were running high speed. Open LFD, play a little while, flicker starts, quit game....now my nvidia stereo controller (it even switched hubs to sit with my mouse?) is on a hub that is running "full speed" that before when I had checked it was high speed. 2 hubs downgraded themselves to full speed....wtf? If anyone has an answer to that, I'll love you forever lol.
Here's my experience
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does
[quote name='Faust' post='1045700' date='Apr 27 2010, 12:32 AM']Here's my experience
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does[/quote]
I'd like to add to this. I bought an Acer GD235HZ monitor and ran the setup for the first time last night. Everything worked like a charm. I played Bad Company 2 and even 3 games of DotA without a single problem. Then, in the middle of another DotA game my PC crashed and I rebooted. Since then I have severe flickering when trying to run DotA, so much so that I cannot use 3D anymore in DotA or ANY other game. When I run the "launch test application" in the Nvidia Control Panel it DOESN'T FLICKER!! ?? But here comes another interesting thing, when I view, for example, the Batman Arkham Asylum Power Pack, I can view the images in 3D without flickering, until I move my mouse OR press buttons on my keyboard. If I don't touch my mouse or keyboard, I have no flickering. Unfortunately when it comes to games it flickers constantly...
So I know for a fact it's NOT a faulty IR transmitter or faulty glasses because they DO work in some cases like the Spinning Nvidia logo test application. This HAS to be a very big driver problem.
I'm running Windows 7 Ultimate 64bit edition. 2xGTX280's in SLi with a 9800GT for PhysX. I've tried disabling everything such as PhysX and SLi, no difference. I've tried EVERYTHING recommended on this board. My mouse is a Razer Mamba and my Keyboard is a MS Reclusa. If that helps. All drivers are 100% up to date.
[quote name='Faust' post='1045700' date='Apr 27 2010, 12:32 AM']Here's my experience
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does
I'd like to add to this. I bought an Acer GD235HZ monitor and ran the setup for the first time last night. Everything worked like a charm. I played Bad Company 2 and even 3 games of DotA without a single problem. Then, in the middle of another DotA game my PC crashed and I rebooted. Since then I have severe flickering when trying to run DotA, so much so that I cannot use 3D anymore in DotA or ANY other game. When I run the "launch test application" in the Nvidia Control Panel it DOESN'T FLICKER!! ?? But here comes another interesting thing, when I view, for example, the Batman Arkham Asylum Power Pack, I can view the images in 3D without flickering, until I move my mouse OR press buttons on my keyboard. If I don't touch my mouse or keyboard, I have no flickering. Unfortunately when it comes to games it flickers constantly...
So I know for a fact it's NOT a faulty IR transmitter or faulty glasses because they DO work in some cases like the Spinning Nvidia logo test application. This HAS to be a very big driver problem.
I'm running Windows 7 Ultimate 64bit edition. 2xGTX280's in SLi with a 9800GT for PhysX. I've tried disabling everything such as PhysX and SLi, no difference. I've tried EVERYTHING recommended on this board. My mouse is a Razer Mamba and my Keyboard is a MS Reclusa. If that helps. All drivers are 100% up to date.
I fixed all my fickering issues by unplugging my Internet TV Box ( Freebox HD in France), the interferences without using the remote controller were permanent, and in M&B and the demo Medusa caused me many blinking and desynchronizations.
So, for thoose who have a TV near their computers : Just switch off completly all your devices attached to your TV and try again the 3D Vision.
Now I can play Mount and Blade (my favourite game and the best game in 3D) without flickering issues.
I fixed all my fickering issues by unplugging my Internet TV Box ( Freebox HD in France), the interferences without using the remote controller were permanent, and in M&B and the demo Medusa caused me many blinking and desynchronizations.
So, for thoose who have a TV near their computers : Just switch off completly all your devices attached to your TV and try again the 3D Vision.
Now I can play Mount and Blade (my favourite game and the best game in 3D) without flickering issues.
I've used a straight CRT setup, where I can run the monitor at 85Hz, 100Hz, or 120Hz without trouble. I do very occasionally see the flicker when running at 120Hz, but never at lower frequencies.
I also tried out and returned the Viewsonic Vx2265wm (too small). It ran at 120Hz there without trouble, but also very occasional flickers.
I've used the kit for almost a year now, and it works pretty well for me, over two different motherboards, two different CPUs (one dual, one quad), multiple nVidia versions, switching from Raptors to SSD, and either single or SLI which I have now. I've even used it through TH2G with three surround CRTs all in Stereo, at 85Hz. (Fun!
It seems clear that 3d Vision is on the outside edge of performance that can be achieved through the USB.
It looks to me that the crux of people's problems are that their systems are delaying USB events. Every frame requires a USB event to be sent, to tell the emitter to send the signal to the glasses. If you delay that event, or drop some, it will cause flicker.
This suggests that the glasses plus emitter combo is susceptible to problems in the software, or other devices that use USB bandwidth.
This is also why lowering the frequency to 100Hz often works, because it lowers the demands on the timing.
My best suggestion is to plug your emitter into a motherboard connection, but make sure that the emitter is the *only* item for that hub. If you plug in a mouse, or a hard drive, or something else to that hub, you might very well get USB stalls that cause flicker.
Look in Device Manager, and make sure your emitter is the sole item for that motherboard hub.
If you have other software on the system that turns off interrupts for any length of time, you can also expect USB stalls, and thus flicker. I know this can be very difficult to determine, so a good experiment would be to make a new bootable partition and install a clean OS upon that partition with nothing except your nVidia drivers, and your motherboard drivers. There is a lot of poorly written software in the world.
You can easily make a new partition in either Vista or 7 by using the Disk Management and shrinking a current volume.
Good luck, and let us know what you find out.
I've used a straight CRT setup, where I can run the monitor at 85Hz, 100Hz, or 120Hz without trouble. I do very occasionally see the flicker when running at 120Hz, but never at lower frequencies.
I also tried out and returned the Viewsonic Vx2265wm (too small). It ran at 120Hz there without trouble, but also very occasional flickers.
I've used the kit for almost a year now, and it works pretty well for me, over two different motherboards, two different CPUs (one dual, one quad), multiple nVidia versions, switching from Raptors to SSD, and either single or SLI which I have now. I've even used it through TH2G with three surround CRTs all in Stereo, at 85Hz. (Fun!
It seems clear that 3d Vision is on the outside edge of performance that can be achieved through the USB.
It looks to me that the crux of people's problems are that their systems are delaying USB events. Every frame requires a USB event to be sent, to tell the emitter to send the signal to the glasses. If you delay that event, or drop some, it will cause flicker.
This suggests that the glasses plus emitter combo is susceptible to problems in the software, or other devices that use USB bandwidth.
This is also why lowering the frequency to 100Hz often works, because it lowers the demands on the timing.
My best suggestion is to plug your emitter into a motherboard connection, but make sure that the emitter is the *only* item for that hub. If you plug in a mouse, or a hard drive, or something else to that hub, you might very well get USB stalls that cause flicker.
Look in Device Manager, and make sure your emitter is the sole item for that motherboard hub.
If you have other software on the system that turns off interrupts for any length of time, you can also expect USB stalls, and thus flicker. I know this can be very difficult to determine, so a good experiment would be to make a new bootable partition and install a clean OS upon that partition with nothing except your nVidia drivers, and your motherboard drivers. There is a lot of poorly written software in the world.
You can easily make a new partition in either Vista or 7 by using the Disk Management and shrinking a current volume.
Good luck, and let us know what you find out.
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
I get no flickering with Samsung so I thought I fixed this flickering issue but ....
I get flickering with Acer H5630??? No matter what cable I use....
This doesn't explain one of the theory about USB emitter being bull crap..... becuase it is completely depends on display now. I m confused again.
I get no flickering with Samsung so I thought I fixed this flickering issue but ....
I get flickering with Acer H5630??? No matter what cable I use....
This doesn't explain one of the theory about USB emitter being bull crap..... becuase it is completely depends on display now. I m confused again.
[url="http://www.overclock.net/faqs/73418-how-improve-mouse-response-accuracy-changing.html"]http://www.overclock.net/faqs/73418-how-im...y-changing.html[/url]
http://www.overclock.net/faqs/73418-how-im...y-changing.html
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia![/quote]
Jrox thats EXACTLY what's happening, everytime I move my mouse the glasses flicker like crazy. I'm going to try and change the IRQs and see if that make the difference.
All the best m8
Dave
just wanted to throw this out there, I am probably one of the more experienced 3d system users. (beein gaming in 3d since 2002)
over the years i've fixed this issue several times, although not always with the same solution. Here's some tips to maybe point some of you in the right direction. This pertains most likely to those of you who experience flicker constantly with the glasses, not just some games or software. If your problem is persists only part of the time, this may not help.
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
For those of you who do not know, an IRQ is basically a reserved "pipeline" for communications to the system. These pipelines basically "listen" for updated instructions from the hardware. For instance, when you press a key on your keyboard, you're sending an interrupt message to the CPU, which either overides, or is overidden by other instructions depending on what's happening with the machine at that moment. There's more to it than that, but that's the basic idea.
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
Jrox thats EXACTLY what's happening, everytime I move my mouse the glasses flicker like crazy. I'm going to try and change the IRQs and see if that make the difference.
All the best m8
Dave
You may want to try your IR emmiter and mouse in various usb ports.
You may want to try your IR emmiter and mouse in various usb ports.
You may want to try your IR emmiter and mouse in various usb ports.[/quote]
I've disabled all peripheral, except "pci express root" which are on the same IRQ, no change for me :(
[img]http://quake.fr/tmp/peripheral.jpg[/img]
You may want to try your IR emmiter and mouse in various usb ports.
I've disabled all peripheral, except "pci express root" which are on the same IRQ, no change for me :(
You can also take a look in bios if there are some options - consult manual (e.g. try to enable/disable HPET if you have it there ...)
You can also take a look in bios if there are some options - consult manual (e.g. try to enable/disable HPET if you have it there ...)
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia![/quote]
My system also seems to have devices sharing the port my GFX card uses (port 16) - can I literally select the components sharing the same port as the entry for the gfx card and select a vacant IRQ number?
Anyway, over the years I've discovered something in particular these glasses absolutely do not like. That's IRQ CONFLICTS, ESPECIALLY ones involved with the graphics processor!
Now, when certain IRQ channels are shared with your graphics card, they can cause unwanted interruptions, or pauses, which in turn knocks the glasses out of sync, and causes them to momentarily pause or 'flicker".
On my systems over the years, I've noticed that whenever I had hardware sharing the same IRQ with my gpu, it would cause flicker. It was always either my sound card, (which caused permanent, uncontrollable flicker) or my wireless mouse which would would be on the same IRQ as my video card. (this caused flicker ONLY when moving or clicking the mouse.)
Anyway, I hope this my give someone out there a helping hand in the right direction. I'm bummed to see people are still dealing with this crap, even after all these years. Shame on you, Nvidia!
My system also seems to have devices sharing the port my GFX card uses (port 16) - can I literally select the components sharing the same port as the entry for the gfx card and select a vacant IRQ number?
Lord, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.
-------------------
Vitals: Windows 7 64bit, i5 2500 @ 4.4ghz, SLI GTX670, 8GB, Viewsonic VX2268WM
Handy Driver Discussion
Helix Mod - community fixes
Bo3b's Shaderhacker School - How to fix 3D in games
3dsolutionsgaming.com - videos, reviews and 3D fixes
[img]http://img256.imageshack.us/img256/4079/59256822.jpg[/img]
Take a look in device manager for usb root serving your IR emmiter. Make sure everything is ok there and that you have certified PSU capable of powering your usb devices in a certified way.
[img]http://img253.imageshack.us/img253/5042/42890948.jpg[/img]
Also I forgot, run DPC latency checker [url="http://www.thesycon.de/deu/latency_check.shtml"]http://www.thesycon.de/deu/latency_check.shtml[/url] couple of minutes and there should be always reported
[i]This machine should be able to handle real-time streaming of audio and/or video data without drop-outs.[/i]
Take a look in device manager for usb root serving your IR emmiter. Make sure everything is ok there and that you have certified PSU capable of powering your usb devices in a certified way.
Also I forgot, run DPC latency checker http://www.thesycon.de/deu/latency_check.shtml couple of minutes and there should be always reported
This machine should be able to handle real-time streaming of audio and/or video data without drop-outs.
hope this helps
hope this helps
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does
�Case: Cooler Master HAF 932
�OS: Win7 64 bit
�MBR: EVGA x58 Classified
�CPU: CoreI7 920 @ 4.2 ghz, 1.38V
�RAM: 3x 2Gb OCZ Reaper 1900 mhz
�GPU: PNY 480 GTX
�PSU: Koolance 1700W watercooled PSU
�HDD:OCZ Colossus 120 GB SSD
�MON: Samsung24" Syncmaster 245B
�MON2: Acer H5360 3D projector
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does[/quote]
I'd like to add to this. I bought an Acer GD235HZ monitor and ran the setup for the first time last night. Everything worked like a charm. I played Bad Company 2 and even 3 games of DotA without a single problem. Then, in the middle of another DotA game my PC crashed and I rebooted. Since then I have severe flickering when trying to run DotA, so much so that I cannot use 3D anymore in DotA or ANY other game. When I run the "launch test application" in the Nvidia Control Panel it DOESN'T FLICKER!! ?? But here comes another interesting thing, when I view, for example, the Batman Arkham Asylum Power Pack, I can view the images in 3D without flickering, until I move my mouse OR press buttons on my keyboard. If I don't touch my mouse or keyboard, I have no flickering. Unfortunately when it comes to games it flickers constantly...
So I know for a fact it's NOT a faulty IR transmitter or faulty glasses because they DO work in some cases like the Spinning Nvidia logo test application. This HAS to be a very big driver problem.
I'm running Windows 7 Ultimate 64bit edition. 2xGTX280's in SLi with a 9800GT for PhysX. I've tried disabling everything such as PhysX and SLi, no difference. I've tried EVERYTHING recommended on this board. My mouse is a Razer Mamba and my Keyboard is a MS Reclusa. If that helps. All drivers are 100% up to date.
I have a 295, if I disable SLI it works fine so far. Otherwise I get the blinking every 10-30 seconds on every game.
Im using x58 classified and Ive tried a different set before with one pair of glasses and the samsung monitor. Sold it because of blinking issues
Back then i was on windows vista 64 bit. Now Im on win7 64 bit, new set with 2 pair of glasses.
I have noticed too, just like some other user, the 'blinking' is at both glasses at the very same time. Im using 2 pair of glasses with an acer h5380 projector now.
If theres an out of sync for a second it occurs at both glasses.
Nvidia should fix this, cause Im sure potential buyers are reading this and are turned off by the high amount of complainers here in this thread ^^.
For me it makes no sense of course to not use SLI on a $500,- card, not using half of it :S
So I'll sell it and buy a 480 gtx and see what that does
I'd like to add to this. I bought an Acer GD235HZ monitor and ran the setup for the first time last night. Everything worked like a charm. I played Bad Company 2 and even 3 games of DotA without a single problem. Then, in the middle of another DotA game my PC crashed and I rebooted. Since then I have severe flickering when trying to run DotA, so much so that I cannot use 3D anymore in DotA or ANY other game. When I run the "launch test application" in the Nvidia Control Panel it DOESN'T FLICKER!! ?? But here comes another interesting thing, when I view, for example, the Batman Arkham Asylum Power Pack, I can view the images in 3D without flickering, until I move my mouse OR press buttons on my keyboard. If I don't touch my mouse or keyboard, I have no flickering. Unfortunately when it comes to games it flickers constantly...
So I know for a fact it's NOT a faulty IR transmitter or faulty glasses because they DO work in some cases like the Spinning Nvidia logo test application. This HAS to be a very big driver problem.
I'm running Windows 7 Ultimate 64bit edition. 2xGTX280's in SLi with a 9800GT for PhysX. I've tried disabling everything such as PhysX and SLi, no difference. I've tried EVERYTHING recommended on this board. My mouse is a Razer Mamba and my Keyboard is a MS Reclusa. If that helps. All drivers are 100% up to date.
So, for thoose who have a TV near their computers : Just switch off completly all your devices attached to your TV and try again the 3D Vision.
Now I can play Mount and Blade (my favourite game and the best game in 3D) without flickering issues.
So, for thoose who have a TV near their computers : Just switch off completly all your devices attached to your TV and try again the 3D Vision.
Now I can play Mount and Blade (my favourite game and the best game in 3D) without flickering issues.