That's an interesting point. I am using MSAA in GTA5 and I am not sure what AA SF5 is using but I have all settings on max. hmm more tests....
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I have also encountered this issue in Rise of the Tomb Raider.
It is a severe version of the classical "screen tearing" syndrome, which in 2D never really bothered me much throughout the years, but in 3D it is devastating on the eyes. (As a little aside: even if I've been playing in 3D since 2011, with Asus VG278HR + SLI GTX580s, I've only noticed this effect when I've upgraded to SLI 980s last year. Before then, I had never used any form of v-sync while playing in 3D. After that moment, I had to always keep V-sync on Adaptive in the Panel)
Some details about the effect itself, in case other users want to confirm that it's a consistent behaviour:
1. The screen tearing only happens in certain games. Rise of the Tomb Raider confirmed issue. (No issue with Fallout NV, LEGO BAtman 2, Witcher 3)
2. The screen tearing only happens in the right eye. It happens even if panning the camera very slowly, not necessary to pan quickly, which is very strange because usually screen tearing happens due to the speed of image refresh being out of sync. Here even slow panning causes the tearing, as if the right eye has a hardcoded delay in processing certain image sectors. This is probably why no v-sync methods affect it, in-game or Panel.
3. It only happens in games using the Nvidia 3D renderer. For example, if you play ROTTR with the latest game patch, where the proprietary game renderer is used, the effect is not present.
4. The effect is only present in SLI. Switching to single card completely removes the effect.
5. The effect can be impacted by profile changes. For example, for Helifax' awesome ROTTR fix there is a profile change needed to make it work. If the second option (full profile change) is used, the effect is lessened. This may point to the fact that maybe not the code of the driver itself is busted, but maybe something in the SLI bits was updated incorrectly. This may explain why it happens only in certain games.
I have also encountered this issue in Rise of the Tomb Raider.
It is a severe version of the classical "screen tearing" syndrome, which in 2D never really bothered me much throughout the years, but in 3D it is devastating on the eyes. (As a little aside: even if I've been playing in 3D since 2011, with Asus VG278HR + SLI GTX580s, I've only noticed this effect when I've upgraded to SLI 980s last year. Before then, I had never used any form of v-sync while playing in 3D. After that moment, I had to always keep V-sync on Adaptive in the Panel)
Some details about the effect itself, in case other users want to confirm that it's a consistent behaviour:
1. The screen tearing only happens in certain games. Rise of the Tomb Raider confirmed issue. (No issue with Fallout NV, LEGO BAtman 2, Witcher 3)
2. The screen tearing only happens in the right eye. It happens even if panning the camera very slowly, not necessary to pan quickly, which is very strange because usually screen tearing happens due to the speed of image refresh being out of sync. Here even slow panning causes the tearing, as if the right eye has a hardcoded delay in processing certain image sectors. This is probably why no v-sync methods affect it, in-game or Panel.
3. It only happens in games using the Nvidia 3D renderer. For example, if you play ROTTR with the latest game patch, where the proprietary game renderer is used, the effect is not present.
4. The effect is only present in SLI. Switching to single card completely removes the effect.
5. The effect can be impacted by profile changes. For example, for Helifax' awesome ROTTR fix there is a profile change needed to make it work. If the second option (full profile change) is used, the effect is lessened. This may point to the fact that maybe not the code of the driver itself is busted, but maybe something in the SLI bits was updated incorrectly. This may explain why it happens only in certain games.
Nice work there.
Just to reiterate it happens in SF5 the worst I have ever seen, which has no SLI support at all, and no bits loaded, yet occurs with SLI on in the panel.
Nice work there.
Just to reiterate it happens in SF5 the worst I have ever seen, which has no SLI support at all, and no bits loaded, yet occurs with SLI on in the panel.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Maybe try this for Tomb Raider
[quote="Kingping1"][url]http://www.forum-3dcenter.org/vbulletin/showthread.php?p=10927377#post10927377[/url][/quote]
[url]https://forums.geforce.com/default/topic/911635/sli/rise-of-the-tomb-raider-sli-support/post/4792543/#4792543[/url]
Interesting...
So I see everyone here has a Maxwell based GPU.
This could explain why I don't see it on either of my PCs: my Surround which uses SLI is Kepler based, my other 2 Laptops (without SLI) are Kepler and Fermi based...
I don't know how to translate this...
Did you guys reported this to nvidia using the driver feedback form?
I think GTAV is the best example you can use for the reproduction scenario as it doesn't require any community fix/patch nor profile modification;)
Without having a Maxwell SLI system I can't really test or help you here:( I am still pondering if I should upgrade my 2x780Ti to 2x980Ti or wait for Pascals later this year (October/November most likely), but this is outside of this discussion;)
Interesting...
So I see everyone here has a Maxwell based GPU.
This could explain why I don't see it on either of my PCs: my Surround which uses SLI is Kepler based, my other 2 Laptops (without SLI) are Kepler and Fermi based...
I don't know how to translate this...
Did you guys reported this to nvidia using the driver feedback form?
I think GTAV is the best example you can use for the reproduction scenario as it doesn't require any community fix/patch nor profile modification;)
Without having a Maxwell SLI system I can't really test or help you here:( I am still pondering if I should upgrade my 2x780Ti to 2x980Ti or wait for Pascals later this year (October/November most likely), but this is outside of this discussion;)
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
This issue is really plaguing my gaming life horribly.
I just noticed it had happened before at least once, with an older series of drivers, in 2010
https://forums.geforce.com/default/topic/480592/3d-vision-sli-broken-in-260-xx-due-to-screen-tearing/
And Rowan mirrors my comments regarding the tearing in 3D, which cause not only image displacement (the actual "tearing") but also [u]depth[/u] displacement, which is murder on the eyes.
On recent drivers it's simply impossible to play games such as Fallout 4 or Tomb Raider. Even older/simpler games seem to be affected (State of Decay).
I'm trying to see if I find the oldest driver I can use to get rid of this, but it seems nowadays older drivers are less and less an option.
I'll share some info here, but if anyone can point me to Bo3b's driver thread (which should have been stickied from the start) I can post there as well. I's becoming extremely challenging to know what driver to use, and it's almost totally "on a game by game basis".
Fallout 4 does not seem to work on any driver older than 358.91. On this driver there is no tearing yet.
But of course I cannot play Rise of the Tomb Raider with the Helifax fix, I'm getting an error when importing SLI bits, probably because this driver did not contain any ROTTR info and simply adding the SLI bits is invalid. I should have created a custom profile or assigned the exe to another profile, but then it gets messy. Annoying, I wanted to play these two games back and forth for the moment, but maybe not possible.
If this does not get fixed, it will be a big issue.
Maybe Nvidia wants to kill SLI. If Pascal is powerful enough to go single card in 3D, and if VR does not support SLI, the future could well be single card.
But for the moment, I cannot believe that I have to contend with yet another 3D Vision frustration, just because I want to be entertained as befits a being with two eyes.
This issue is really plaguing my gaming life horribly.
I just noticed it had happened before at least once, with an older series of drivers, in 2010
https://forums.geforce.com/default/topic/480592/3d-vision-sli-broken-in-260-xx-due-to-screen-tearing/ And Rowan mirrors my comments regarding the tearing in 3D, which cause not only image displacement (the actual "tearing") but also depth displacement, which is murder on the eyes.
On recent drivers it's simply impossible to play games such as Fallout 4 or Tomb Raider. Even older/simpler games seem to be affected (State of Decay).
I'm trying to see if I find the oldest driver I can use to get rid of this, but it seems nowadays older drivers are less and less an option.
I'll share some info here, but if anyone can point me to Bo3b's driver thread (which should have been stickied from the start) I can post there as well. I's becoming extremely challenging to know what driver to use, and it's almost totally "on a game by game basis".
Fallout 4 does not seem to work on any driver older than 358.91. On this driver there is no tearing yet.
But of course I cannot play Rise of the Tomb Raider with the Helifax fix, I'm getting an error when importing SLI bits, probably because this driver did not contain any ROTTR info and simply adding the SLI bits is invalid. I should have created a custom profile or assigned the exe to another profile, but then it gets messy. Annoying, I wanted to play these two games back and forth for the moment, but maybe not possible.
If this does not get fixed, it will be a big issue.
Maybe Nvidia wants to kill SLI. If Pascal is powerful enough to go single card in 3D, and if VR does not support SLI, the future could well be single card.
But for the moment, I cannot believe that I have to contend with yet another 3D Vision frustration, just because I want to be entertained as befits a being with two eyes.
[quote="Zappologist"]I'll share some info here, but if anyone can point me to Bo3b's driver thread (which should have been stickied from the start)[/quote]
[url=https://forums.geforce.com/default/topic/777954/][color="orange"]Suggested driver to use?[/color][/url] by bo3b
@Zappologist:
Are you by any chance on Windows 7? In the Rise of Tomb Raider thread, Seregin said this issue went away when he was using Windows 10:
[quote="Seregin"]
Thank you very much, Helifax! Gonna try to "hunt" today :)
[b]UPDATE:[/b] Tried to run game under Windows 10 with latest driver, and I cannot reproduce tearing issue so far... Overall, does Windows 10 mature enough to ditch Windows 7 altogether in regard to 3D Vision gaming? I'm keeping it only because I've heard/read that 3D Vision gaming is usually broken under Windows 10...
Thanks! :)[/quote]
Can you try it on Windows 10? [s]If this is not an option for you I can try to "hack" 358.91 driver and see if I can't make ROTTR work on this driver;) (if the only thing it requires is a game profile that is;))[/s]
The game doesn't start, just hangs in a black windows even if I import the profiles in 358.91 :(
Are you by any chance on Windows 7? In the Rise of Tomb Raider thread, Seregin said this issue went away when he was using Windows 10:
Seregin said:
Thank you very much, Helifax! Gonna try to "hunt" today :)
UPDATE: Tried to run game under Windows 10 with latest driver, and I cannot reproduce tearing issue so far... Overall, does Windows 10 mature enough to ditch Windows 7 altogether in regard to 3D Vision gaming? I'm keeping it only because I've heard/read that 3D Vision gaming is usually broken under Windows 10...
Thanks! :)
Can you try it on Windows 10? If this is not an option for you I can try to "hack" 358.91 driver and see if I can't make ROTTR work on this driver;) (if the only thing it requires is a game profile that is;))
The game doesn't start, just hangs in a black windows even if I import the profiles in 358.91 :(
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
So, I ended up deciding to start from scratch with my PC and setup a dual Boot Windows 7 64x Windows 10 setup on my one SSD. Which ended up being an ordeal in itself. But I got there in the end.
(Interesting to note you don't actually really have to have a license for 10 or give up your windows 7 license if you do it this way. The only functionality you loose is the ability to customize the desktop colors and a small water mark on the lower right of the screen. Oh NOES!)
I can confirm this problem also occurs in windows 10 (in my SF5 benchmarks it also runs games slower and is more unstable.) although its not quite as pronounced. In windows 7 makes SF5 unplayable in SLI.
So now I am back in action I will try and take some videos but I will probably go for GTA5 since this game does not require a 3dvision fix or profile change.
I am using the latest driver in both OS
So, I ended up deciding to start from scratch with my PC and setup a dual Boot Windows 7 64x Windows 10 setup on my one SSD. Which ended up being an ordeal in itself. But I got there in the end.
(Interesting to note you don't actually really have to have a license for 10 or give up your windows 7 license if you do it this way. The only functionality you loose is the ability to customize the desktop colors and a small water mark on the lower right of the screen. Oh NOES!)
I can confirm this problem also occurs in windows 10 (in my SF5 benchmarks it also runs games slower and is more unstable.) although its not quite as pronounced. In windows 7 makes SF5 unplayable in SLI.
So now I am back in action I will try and take some videos but I will probably go for GTA5 since this game does not require a 3dvision fix or profile change.
I am using the latest driver in both OS
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Strange..
I have just upgraded my cards from 780TI (Kepler) to 980Ti (Maxwell) and I still can't see this issue....
But I haven't tried those specific games... maybe is tight only to them somehow?
Is this in Surround or a Single Screen? Or both? I haven't tried Single Screen but if it helps narrowing down the bug I can try to replicate it and at least we can fill a proper bug for it;)
Strange..
I have just upgraded my cards from 780TI (Kepler) to 980Ti (Maxwell) and I still can't see this issue....
But I haven't tried those specific games... maybe is tight only to them somehow?
Is this in Surround or a Single Screen? Or both? I haven't tried Single Screen but if it helps narrowing down the bug I can try to replicate it and at least we can fill a proper bug for it;)
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
As mentioned earlier in the thread, it doesn't occur in surround. I but I think this is a red herring because I think it's simply the frame rate does not run high enough for it to manifest. I can actually make the problem go away by forcing the refresh rate in game in gta down to 50hz.
I think it is game specific as well. I don't get it in all games. May even be only Dx11 ones, I don't think I have had the problem in a dx9 game yet.
As mentioned earlier in the thread, it doesn't occur in surround. I but I think this is a red herring because I think it's simply the frame rate does not run high enough for it to manifest. I can actually make the problem go away by forcing the refresh rate in game in gta down to 50hz.
I think it is game specific as well. I don't get it in all games. May even be only Dx11 ones, I don't think I have had the problem in a dx9 game yet.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I actually get screen tearing with 3D vision enabled on chrome browser. Like scrolling down.
Couldnt figure it out for the life of me then noticed if I turned off 3d vision it fixed.
I actually get screen tearing with 3D vision enabled on chrome browser. Like scrolling down.
Couldnt figure it out for the life of me then noticed if I turned off 3d vision it fixed.
Co-founder of helixmod.blog.com
If you like one of my helixmod patches and want to donate. Can send to me through paypal - eqzitara@yahoo.com
[quote="necropants"]As mentioned earlier in the thread, it doesn't occur in surround. I but I think this is a red herring because I think it's simply the frame rate does not run high enough for it to manifest. I can actually make the problem go away by forcing the refresh rate in game in gta down to 50hz.
I think it is game specific as well. I don't get it in all games. May even be only Dx11 ones, I don't think I have had the problem in a dx9 game yet.
[/quote]
I tried reducing 3D vision display frequency in (Nvidia panel 3D test section) to 110Hz, it seems to help a bit
necropants said:As mentioned earlier in the thread, it doesn't occur in surround. I but I think this is a red herring because I think it's simply the frame rate does not run high enough for it to manifest. I can actually make the problem go away by forcing the refresh rate in game in gta down to 50hz.
I think it is game specific as well. I don't get it in all games. May even be only Dx11 ones, I don't think I have had the problem in a dx9 game yet.
I tried reducing 3D vision display frequency in (Nvidia panel 3D test section) to 110Hz, it seems to help a bit
Latest 368.22 driver on win 7 was still giving me the same issue...upgrading to win 10 with the exact same driver version solved it for me! (Gtx 970 2x sli single screen)...hurray!
Latest 368.22 driver on win 7 was still giving me the same issue...upgrading to win 10 with the exact same driver version solved it for me! (Gtx 970 2x sli single screen)...hurray!
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I have the same issue in Rise of the Tomb Raider, did you found a solution?
It is a severe version of the classical "screen tearing" syndrome, which in 2D never really bothered me much throughout the years, but in 3D it is devastating on the eyes. (As a little aside: even if I've been playing in 3D since 2011, with Asus VG278HR + SLI GTX580s, I've only noticed this effect when I've upgraded to SLI 980s last year. Before then, I had never used any form of v-sync while playing in 3D. After that moment, I had to always keep V-sync on Adaptive in the Panel)
Some details about the effect itself, in case other users want to confirm that it's a consistent behaviour:
1. The screen tearing only happens in certain games. Rise of the Tomb Raider confirmed issue. (No issue with Fallout NV, LEGO BAtman 2, Witcher 3)
2. The screen tearing only happens in the right eye. It happens even if panning the camera very slowly, not necessary to pan quickly, which is very strange because usually screen tearing happens due to the speed of image refresh being out of sync. Here even slow panning causes the tearing, as if the right eye has a hardcoded delay in processing certain image sectors. This is probably why no v-sync methods affect it, in-game or Panel.
3. It only happens in games using the Nvidia 3D renderer. For example, if you play ROTTR with the latest game patch, where the proprietary game renderer is used, the effect is not present.
4. The effect is only present in SLI. Switching to single card completely removes the effect.
5. The effect can be impacted by profile changes. For example, for Helifax' awesome ROTTR fix there is a profile change needed to make it work. If the second option (full profile change) is used, the effect is lessened. This may point to the fact that maybe not the code of the driver itself is busted, but maybe something in the SLI bits was updated incorrectly. This may explain why it happens only in certain games.
Just to reiterate it happens in SF5 the worst I have ever seen, which has no SLI support at all, and no bits loaded, yet occurs with SLI on in the panel.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
https://forums.geforce.com/default/topic/911635/sli/rise-of-the-tomb-raider-sli-support/post/4792543/#4792543
So I see everyone here has a Maxwell based GPU.
This could explain why I don't see it on either of my PCs: my Surround which uses SLI is Kepler based, my other 2 Laptops (without SLI) are Kepler and Fermi based...
I don't know how to translate this...
Did you guys reported this to nvidia using the driver feedback form?
I think GTAV is the best example you can use for the reproduction scenario as it doesn't require any community fix/patch nor profile modification;)
Without having a Maxwell SLI system I can't really test or help you here:( I am still pondering if I should upgrade my 2x780Ti to 2x980Ti or wait for Pascals later this year (October/November most likely), but this is outside of this discussion;)
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)
I just noticed it had happened before at least once, with an older series of drivers, in 2010
https://forums.geforce.com/default/topic/480592/3d-vision-sli-broken-in-260-xx-due-to-screen-tearing/
And Rowan mirrors my comments regarding the tearing in 3D, which cause not only image displacement (the actual "tearing") but also depth displacement, which is murder on the eyes.
On recent drivers it's simply impossible to play games such as Fallout 4 or Tomb Raider. Even older/simpler games seem to be affected (State of Decay).
I'm trying to see if I find the oldest driver I can use to get rid of this, but it seems nowadays older drivers are less and less an option.
I'll share some info here, but if anyone can point me to Bo3b's driver thread (which should have been stickied from the start) I can post there as well. I's becoming extremely challenging to know what driver to use, and it's almost totally "on a game by game basis".
Fallout 4 does not seem to work on any driver older than 358.91. On this driver there is no tearing yet.
But of course I cannot play Rise of the Tomb Raider with the Helifax fix, I'm getting an error when importing SLI bits, probably because this driver did not contain any ROTTR info and simply adding the SLI bits is invalid. I should have created a custom profile or assigned the exe to another profile, but then it gets messy. Annoying, I wanted to play these two games back and forth for the moment, but maybe not possible.
If this does not get fixed, it will be a big issue.
Maybe Nvidia wants to kill SLI. If Pascal is powerful enough to go single card in 3D, and if VR does not support SLI, the future could well be single card.
But for the moment, I cannot believe that I have to contend with yet another 3D Vision frustration, just because I want to be entertained as befits a being with two eyes.
Suggested driver to use? by bo3b
Are you by any chance on Windows 7? In the Rise of Tomb Raider thread, Seregin said this issue went away when he was using Windows 10:
Can you try it on Windows 10?
If this is not an option for you I can try to "hack" 358.91 driver and see if I can't make ROTTR work on this driver;) (if the only thing it requires is a game profile that is;))The game doesn't start, just hangs in a black windows even if I import the profiles in 358.91 :(
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)
(Interesting to note you don't actually really have to have a license for 10 or give up your windows 7 license if you do it this way. The only functionality you loose is the ability to customize the desktop colors and a small water mark on the lower right of the screen. Oh NOES!)
I can confirm this problem also occurs in windows 10 (in my SF5 benchmarks it also runs games slower and is more unstable.) although its not quite as pronounced. In windows 7 makes SF5 unplayable in SLI.
So now I am back in action I will try and take some videos but I will probably go for GTA5 since this game does not require a 3dvision fix or profile change.
I am using the latest driver in both OS
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I have just upgraded my cards from 780TI (Kepler) to 980Ti (Maxwell) and I still can't see this issue....
But I haven't tried those specific games... maybe is tight only to them somehow?
Is this in Surround or a Single Screen? Or both? I haven't tried Single Screen but if it helps narrowing down the bug I can try to replicate it and at least we can fill a proper bug for it;)
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)
I think it is game specific as well. I don't get it in all games. May even be only Dx11 ones, I don't think I have had the problem in a dx9 game yet.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Couldnt figure it out for the life of me then noticed if I turned off 3d vision it fixed.
Co-founder of helixmod.blog.com
If you like one of my helixmod patches and want to donate. Can send to me through paypal - eqzitara@yahoo.com
I tried reducing 3D vision display frequency in (Nvidia panel 3D test section) to 110Hz, it seems to help a bit
DX58SO2 Intel Board | i7-970 | SLI 2x Gigabyte GTX 970 4GB stock OC @ 1033/1111 Mhz | 12GB Mem | Windows 10 64bit driver 368.22 | 3D Vision | PJ6221 Viewsonic Projector