Eyes reversing?
  2 / 2    
[quote="Pirateguybrush"]The weird thing is though, the problem seems to happen at the same time as framerate issues. I also see poor framerates on whichever game is having the issue. Did you have that too?[/quote] Sorry, I posted something then never reported back. But no I did not have performance issues, just dodgy eye reversal. It sounds like you are going to a huge amount of effort re-installing windows and so on, but I am convinced that the monitor emitter is just flawed, or at least the way it has to connect to the computer is flawed. With the standalone emitter its a USB cable plugged in, with the monitor the signal is going through the DVI cable to the monitor, then through whatever channels in the monitor to its own emitter, so that be more prone to timing and sync issues. I don't know for sure, but I do know that the standalone emitter never has this problem, but my built in emitter always has it. If you can pick up a cheap 3DV-1 set on eBay with an emitter, that will solve your problems, but of course you will need to spend money...
Pirateguybrush said:The weird thing is though, the problem seems to happen at the same time as framerate issues. I also see poor framerates on whichever game is having the issue. Did you have that too?

Sorry, I posted something then never reported back. But no I did not have performance issues, just dodgy eye reversal. It sounds like you are going to a huge amount of effort re-installing windows and so on, but I am convinced that the monitor emitter is just flawed, or at least the way it has to connect to the computer is flawed. With the standalone emitter its a USB cable plugged in, with the monitor the signal is going through the DVI cable to the monitor, then through whatever channels in the monitor to its own emitter, so that be more prone to timing and sync issues. I don't know for sure, but I do know that the standalone emitter never has this problem, but my built in emitter always has it. If you can pick up a cheap 3DV-1 set on eBay with an emitter, that will solve your problems, but of course you will need to spend money...

Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278

#16
Posted 01/05/2014 12:01 PM   
I reinstalled windows 8.1 with literally nothing but graphics drivers and Steam, not even chipset drivers - and it still didn't work (though it did the very first time, subsequent attempts saw severe framerate issues in 2d/3d/sli/single and the eye swapping issue). Other things tried include: Testing each card individually in different slots Dropping to one stick of ram in different slots Installing 8.1 with nothing but graphics drivers Installing 8.1 with nothing but sats preinstall drivers and graphics drivers Installing 8.1 with all drivers Crying Weeping Windows Updates Sobbing Changing BIOS settings at random (and also the bios defaults) Updating BIOS Disconnecting all peripherals and unnecessary hard drives But after installing Win8, things seem to be ok so far, both in terms of 3d and framerates. I'm still getting everything set back up, but it's working for now.
I reinstalled windows 8.1 with literally nothing but graphics drivers and Steam, not even chipset drivers - and it still didn't work (though it did the very first time, subsequent attempts saw severe framerate issues in 2d/3d/sli/single and the eye swapping issue). Other things tried include:
Testing each card individually in different slots
Dropping to one stick of ram in different slots
Installing 8.1 with nothing but graphics drivers
Installing 8.1 with nothing but sats preinstall drivers and graphics drivers
Installing 8.1 with all drivers
Crying
Weeping
Windows Updates
Sobbing
Changing BIOS settings at random (and also the bios defaults)
Updating BIOS
Disconnecting all peripherals and unnecessary hard drives

But after installing Win8, things seem to be ok so far, both in terms of 3d and framerates. I'm still getting everything set back up, but it's working for now.

#17
Posted 01/06/2014 05:23 AM   
In the meantime I installed Windows 7: no problems, latest nvidia non-beta drivers 331.82 (latest beta drivers make no difference). So I doubt it is defective hardware. I reinstalled Windows 8.1 then: this time I sticked to the graphics drivers provided by Windows Update (326.60) and additionally installed PhysX-9.13.0725 manually (latest separate install package from nvidia) because it doesn't get installed via Windows Update. Result: I did test it now almost a day and no problems any more since then. My guess is it has something to do with the combination Windows 8.1 and the latest nvidia drivers.
In the meantime I installed Windows 7: no problems, latest nvidia non-beta drivers 331.82 (latest beta drivers make no difference). So I doubt it is defective hardware.

I reinstalled Windows 8.1 then: this time I sticked to the graphics drivers provided by Windows Update (326.60) and additionally installed PhysX-9.13.0725 manually (latest separate install package from nvidia) because it doesn't get installed via Windows Update.

Result: I did test it now almost a day and no problems any more since then.

My guess is it has something to do with the combination Windows 8.1 and the latest nvidia drivers.

#18
Posted 01/06/2014 10:13 AM   
Hey all, in fact the new installation of my os (now i got Windows 8.0 and the newest nvidia drivers 332.21) clear this issue with my 3d Vision kit. Before that i also tried the newest nvidia driver on my windows 8.1 os. The eye reversing issue stiil occured. Now everthing works fine! especially call of duty ghosts is now playable:-)
Hey all, in fact the new installation of my os (now i got Windows 8.0 and the newest nvidia drivers 332.21) clear this issue with my 3d Vision kit. Before that i also tried the newest nvidia driver on my windows 8.1 os. The eye reversing issue stiil occured.

Now everthing works fine! especially call of duty ghosts is now playable:-)

#19
Posted 01/09/2014 10:32 PM   
Just out of curiosity, if this is happening to anyone ... could you go into your registry and check for the following Keys/Values, if they're present or not? Might just be a DLP/Checkerboard thing. [quote][HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D] "InterleavePattern0"=dword:aa55aa55 "InterleavePattern1"=dword:aa55aa55[/quote]At different times I've seen them [u]both[/u] set as either aa55aa55 or 55aa55aa, since I'm using DLP-Link glasses and have a reverse switch on them I would never actually know if it was reversed or not ... hell if I turn my head for a few seconds the glasses 'automatically' reverse on me.
Just out of curiosity, if this is happening to anyone ... could you go into your registry and check for the following Keys/Values, if they're present or not? Might just be a DLP/Checkerboard thing.

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D]
"InterleavePattern0"=dword:aa55aa55
"InterleavePattern1"=dword:aa55aa55
At different times I've seen them both set as either aa55aa55 or 55aa55aa, since I'm using DLP-Link glasses and have a reverse switch on them I would never actually know if it was reversed or not ... hell if I turn my head for a few seconds the glasses 'automatically' reverse on me.
#20
Posted 01/15/2014 05:22 PM   
I still have a backup of my 8.1 install, which I can boot to a VM and check that out for you. Just had a look, and I don't have those values appearing at all on either my current Win8 install, or my previous 8.1 install.
I still have a backup of my 8.1 install, which I can boot to a VM and check that out for you.

Just had a look, and I don't have those values appearing at all on either my current Win8 install, or my previous 8.1 install.

#21
Posted 01/15/2014 06:19 PM   
Thanks for checking that, I still am a little curious if adding them, and or reversing them would do anything. Like I said it might just be to do with checkerboard output but it'd be funny if worked. If anyone tries it I'd suggest at the very least logging off after the change to get everything to reload.
Thanks for checking that, I still am a little curious if adding them, and or reversing them would do anything. Like I said it might just be to do with checkerboard output but it'd be funny if worked. If anyone tries it I'd suggest at the very least logging off after the change to get everything to reload.
#22
Posted 01/24/2014 03:35 PM   
Have you tried updating your usb driver for the emittor in windowsupdate ? (maybe you probably did..) That worked for me ,if i've got problems with the emittor/glasses reversing.
Have you tried updating your usb driver for the emittor in windowsupdate ? (maybe you probably did..)
That worked for me ,if i've got problems with the emittor/glasses reversing.

Intel I7 3820 3.8 Ghz,MSI MS7760 Motherboard, 6GB )2x MSI GTX670 (SLI),OCZ Vertex 230Gb SSD,OCZ Agility 120Gb SSD, Asus 3D VG278HR ,Optoma HD67 3D DLP Beamer with 95inch 2.5 gain screen.

#23
Posted 01/25/2014 12:11 PM   
Emitter is built into the monitor and doesn't require drivers.
Emitter is built into the monitor and doesn't require drivers.

#24
Posted 01/27/2014 12:11 PM   
Hm, so I'm now getting a similar issue while testing Windows 10. Doesn't bode well. The framerates are fine, but the eye swapping thing is still happening. It only swaps for a second, then reverts to normal. This is on a single 970, driver 347.25, with a reasonably clean Windows install. The problem presents in Defence Grid 2, Walking Dead Season 2, Outlast, AC4 (that's all I've tested so far). I can't trigger it in Arkham City. I've only noticed this on my monitor (VH278H), but not my projector (W1070). My Windows 8 install doesn't have this issue. I might need to enlist a couple of people to test this, if you have the time. We can't stay on Win7/8 forever, and we're going to need to bring this to nVidia's attention if it turns out it's an issue for everyone. You can download the Windows 10 technical preview at the link below. Please install it to a spare hard drive (if you have one around), install the latest drivers, and test it out. I'm keen to know if this is just my bad luck, or something bigger. http://windows.microsoft.com/en-au/windows/preview-iso EDIT: Disabling the onboard Intel graphics driver (that I wasn't using) might have fixed the issue. I'm going to have to test further. More data would still be very useful.
Hm, so I'm now getting a similar issue while testing Windows 10. Doesn't bode well. The framerates are fine, but the eye swapping thing is still happening. It only swaps for a second, then reverts to normal. This is on a single 970, driver 347.25, with a reasonably clean Windows install.

The problem presents in Defence Grid 2, Walking Dead Season 2, Outlast, AC4 (that's all I've tested so far). I can't trigger it in Arkham City. I've only noticed this on my monitor (VH278H), but not my projector (W1070). My Windows 8 install doesn't have this issue.

I might need to enlist a couple of people to test this, if you have the time. We can't stay on Win7/8 forever, and we're going to need to bring this to nVidia's attention if it turns out it's an issue for everyone.

You can download the Windows 10 technical preview at the link below. Please install it to a spare hard drive (if you have one around), install the latest drivers, and test it out. I'm keen to know if this is just my bad luck, or something bigger.

http://windows.microsoft.com/en-au/windows/preview-iso

EDIT: Disabling the onboard Intel graphics driver (that I wasn't using) might have fixed the issue. I'm going to have to test further. More data would still be very useful.

#25
Posted 02/19/2015 06:56 PM   
[quote="Pirateguybrush"]Hm, so I'm now getting a similar issue while testing Windows 10. Doesn't bode well. The framerates are fine, but the eye swapping thing is still happening. It only swaps for a second, then reverts to normal. This is on a single 970, driver 347.25, with a reasonably clean Windows install. I might need to enlist a couple of people to test this, if you have the time. We can't stay on Win7/8 forever, and we're going to need to bring this to nVidia's attention if it turns out it's an issue for everyone.[/quote] I think it's going to be a real crap-shoot as to whether 10 works well with 3D or not. Microsoft has changed the driver model again to v2.0 and they did an epically poor job on v1.3 with Win8.1. Odds are low. If you feel that responding to them, reporting bugs or otherwise doing some early testing will help, I'd say go for it. Normally I'm a genuine cynic when it comes to corporations listening to their customers. As near as I can tell it's just for warm fuzzy marketing and they could give a f* what we we say. I reported the bug with WDDM1.3 blowing everyone out of the water, and never received any response whatsoever. However, lame-ass Ballmer is out, Microsoft is running scared now, and making some really bold moves that suggest they actually are listening. Worth your time I expect. As far as staying on Win7, this decision is at least 1.5 years away. The Win10 has not even shipped yet, and you are concerned that we need to work on it? People should always work on the things they are most interested in, but for me I've got a list of 100 things that are more valuable to me that looking at beta or pre-release software. I have no intention of spending any time on Win10 bugs until probably the first service pack. But as I said before, whichever platform has the fewest time-wasters is the one I want to focus on.
Pirateguybrush said:Hm, so I'm now getting a similar issue while testing Windows 10. Doesn't bode well. The framerates are fine, but the eye swapping thing is still happening. It only swaps for a second, then reverts to normal. This is on a single 970, driver 347.25, with a reasonably clean Windows install.

I might need to enlist a couple of people to test this, if you have the time. We can't stay on Win7/8 forever, and we're going to need to bring this to nVidia's attention if it turns out it's an issue for everyone.

I think it's going to be a real crap-shoot as to whether 10 works well with 3D or not. Microsoft has changed the driver model again to v2.0 and they did an epically poor job on v1.3 with Win8.1. Odds are low.

If you feel that responding to them, reporting bugs or otherwise doing some early testing will help, I'd say go for it.

Normally I'm a genuine cynic when it comes to corporations listening to their customers. As near as I can tell it's just for warm fuzzy marketing and they could give a f* what we we say. I reported the bug with WDDM1.3 blowing everyone out of the water, and never received any response whatsoever.

However, lame-ass Ballmer is out, Microsoft is running scared now, and making some really bold moves that suggest they actually are listening. Worth your time I expect.


As far as staying on Win7, this decision is at least 1.5 years away. The Win10 has not even shipped yet, and you are concerned that we need to work on it?

People should always work on the things they are most interested in, but for me I've got a list of 100 things that are more valuable to me that looking at beta or pre-release software. I have no intention of spending any time on Win10 bugs until probably the first service pack.

But as I said before, whichever platform has the fewest time-wasters is the one I want to focus on.

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

#26
Posted 02/21/2015 04:21 AM   
My big concern is that Windows 7 is already out of mainstream support, and with DX12 on the way we're going to eventually be seeing DX12 exclusives. It's by no means an urgent problem, but the period of the technical preview may be the best window to contact MS/nVidia if we can provide useful information about problems. As it stands, I suspect I might have found a solution. But if we can get a few more people to test, that might be helpful.
My big concern is that Windows 7 is already out of mainstream support, and with DX12 on the way we're going to eventually be seeing DX12 exclusives. It's by no means an urgent problem, but the period of the technical preview may be the best window to contact MS/nVidia if we can provide useful information about problems.

As it stands, I suspect I might have found a solution. But if we can get a few more people to test, that might be helpful.

#27
Posted 02/21/2015 05:21 AM   
I agree with you that now is the time to ping them about problems as they are more likely to listen now than later. For DX12 exclusives, that isn't going to happen for at least two years, because DX12 has yet to ship, and no game developer could possibly justify being DX12 exclusive until the installed base trumps the older versions. Even if we have a mass migration to 10 because of the free upgrade, it will still be at least two years out. As an example of how slow this stuff moves, look at Oculus Rift. No game device ever had the hype-train that Rift has, and at present we have what, two, maybe three games with direct support? The real problem that is presently unknowable is how well does NVidia support it? Their track record is pretty bad, so I'm actually not expecting 3D Vision to run well on Win10 at all. I'm not at all worried about Win7 being out of mainstream support, because what does that actually mean for us? Had it made any difference whatsoever to be IN mainstream support?
I agree with you that now is the time to ping them about problems as they are more likely to listen now than later.

For DX12 exclusives, that isn't going to happen for at least two years, because DX12 has yet to ship, and no game developer could possibly justify being DX12 exclusive until the installed base trumps the older versions. Even if we have a mass migration to 10 because of the free upgrade, it will still be at least two years out.

As an example of how slow this stuff moves, look at Oculus Rift. No game device ever had the hype-train that Rift has, and at present we have what, two, maybe three games with direct support?


The real problem that is presently unknowable is how well does NVidia support it? Their track record is pretty bad, so I'm actually not expecting 3D Vision to run well on Win10 at all.

I'm not at all worried about Win7 being out of mainstream support, because what does that actually mean for us? Had it made any difference whatsoever to be IN mainstream support?

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

#28
Posted 02/21/2015 06:04 AM   
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
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

#29
Posted 05/22/2016 06:28 AM   
The emitter light never turned off for me. I suspect a faulty emitter in your case.
The emitter light never turned off for me. I suspect a faulty emitter in your case.

#30
Posted 05/22/2016 07:07 AM   
  2 / 2    
Scroll To Top