Stuttering/low FPS in 3dvision with only certain games
  5 / 6    
As expected Nvidia support decided the drivers are not the issue using the logic that since the stuttering happens on all the drivers that will run on the 1060. The issue MUST not be my system and not them. They are now saying the issue must be my card and I need to run a stress test on it for an hour. I disagree about the stuttering being caused by my card as my card in 3d mode runs at a constant 99% when running the latest Deus Ex and does not exhibit crashes or stuttering.
As expected Nvidia support decided the drivers are not the issue using the logic that since the stuttering happens on all the drivers that will run on the 1060. The issue MUST not be my system and not them.

They are now saying the issue must be my card and I need to run a stress test on it for an hour.

I disagree about the stuttering being caused by my card as my card in 3d mode runs at a constant 99% when running the latest Deus Ex and does not exhibit crashes or stuttering.

AMD FX-8350 4GHz
Gigabyte 990FXA-UD3 Rev 4.0
G-Skill PC3-10700- 16GB
Gigabyte Windforce GTX 1060 OC 6GB - 417.01
Creative Soundblaster Z
ViewSonic VX2268WM Black 22" 1680x1050 5ms 120Hz 3Dvision
Windows 10 x64 1709

#61
Posted 09/09/2016 10:40 PM   
Based on the comment from masterotaku [url]https://forums.geforce.com/default/topic/936450/3d-vision/gtx1080-reviews-out-/post/4971691/#4971691[/url] It seems like the Pascal series cards have some sort of problem. He tested it on Windows 7, which takes out that variable, and still gets stutter as well, with a 1080. I'm running the newest driver on Windows 7, and do not get stutter with a GTX 970. Something about the new generation cards, or the way driver interacts with them is introducing this problem. NVidia should be able to reproduce this problem pretty easily. Once they get that far in your support request, make sure they try it.
Based on the comment from masterotaku https://forums.geforce.com/default/topic/936450/3d-vision/gtx1080-reviews-out-/post/4971691/#4971691

It seems like the Pascal series cards have some sort of problem. He tested it on Windows 7, which takes out that variable, and still gets stutter as well, with a 1080.

I'm running the newest driver on Windows 7, and do not get stutter with a GTX 970.

Something about the new generation cards, or the way driver interacts with them is introducing this problem.


NVidia should be able to reproduce this problem pretty easily. Once they get that far in your support request, make sure they try it.

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

#62
Posted 09/10/2016 02:05 AM   
My stutter issues in the games I listed are now gone. [url]https://forums.geforce.com/default/topic/966422/3d-vision/3d-vision-cpu-bottelneck-gathering-information-thread-/post/4982099/#4982099[/url]

AMD FX-8350 4GHz
Gigabyte 990FXA-UD3 Rev 4.0
G-Skill PC3-10700- 16GB
Gigabyte Windforce GTX 1060 OC 6GB - 417.01
Creative Soundblaster Z
ViewSonic VX2268WM Black 22" 1680x1050 5ms 120Hz 3Dvision
Windows 10 x64 1709

#63
Posted 09/23/2016 03:50 AM   
OK, now we have an answer for this problem. Let's followup here so we can all learn new tricks. First off- the answer is, it's a driver bug. [size="L"]If you use the latest driver 372.90, the problem is fixed.[/size] It's also worth noting that this new driver fixes the stutter I see in Just Cause 3. JC3 is now actually playable in 3D. The interesting part here is our line of thinking about the problem. We thought it might be related to the Pascal series cards, and now we know that's not true. That was false correlation, because the only drivers you could run with new cards were broken ones. Next in line of bad analysis- AMD CPUs. It was a notable difference between all our systems, and AMD chips are relatively rare for 3D Vision, but it didn't have anything to do with the problem. Next up- single core performance. Not related to this problem. It seems fairly clear at this point that the problem was actually a mutex/multithreading bug in the driver when 3D Vision is enabled. Next up was Win10. We thought it might be related, and particularly the Anniversary, but the OS is not a problem. Problem happened and was fixed on Win7, same on Win10. Next was the suspected 3-core limit in 3D. Not the case here. These are always hard to tease out, but it's worth noting that it's not related to this hard stutter. Those were not terrible guesses, but it's worth remembering the end result when we have such a clear answer.
OK, now we have an answer for this problem. Let's followup here so we can all learn new tricks.

First off- the answer is, it's a driver bug. If you use the latest driver 372.90, the problem is fixed.

It's also worth noting that this new driver fixes the stutter I see in Just Cause 3. JC3 is now actually playable in 3D.


The interesting part here is our line of thinking about the problem. We thought it might be related to the Pascal series cards, and now we know that's not true. That was false correlation, because the only drivers you could run with new cards were broken ones.

Next in line of bad analysis- AMD CPUs. It was a notable difference between all our systems, and AMD chips are relatively rare for 3D Vision, but it didn't have anything to do with the problem.

Next up- single core performance. Not related to this problem. It seems fairly clear at this point that the problem was actually a mutex/multithreading bug in the driver when 3D Vision is enabled.

Next up was Win10. We thought it might be related, and particularly the Anniversary, but the OS is not a problem. Problem happened and was fixed on Win7, same on Win10.

Next was the suspected 3-core limit in 3D. Not the case here. These are always hard to tease out, but it's worth noting that it's not related to this hard stutter.


Those were not terrible guesses, but it's worth remembering the end result when we have such a clear answer.

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

#64
Posted 09/24/2016 11:15 PM   
Well said. Wonder when this bug was introduced, and why everyone did not notice it? Maybe the better your CPU the more likely the issue was hidden? Also it is apparent Nvidia fixed this issue, but it was not listed in the Driver Release notes as a fixed issue. Did they fix it accidentally? Anyway no matter why or what I am glad it is fixed and for now this driver is my 3dVision 'gold standard' that all other drivers will be judged upon.
Well said. Wonder when this bug was introduced, and why everyone did not notice it? Maybe the better your CPU the more likely the issue was hidden? Also it is apparent Nvidia fixed this issue, but it was not listed in the Driver Release notes as a fixed issue. Did they fix it accidentally?

Anyway no matter why or what I am glad it is fixed and for now this driver is my 3dVision 'gold standard' that all other drivers will be judged upon.

AMD FX-8350 4GHz
Gigabyte 990FXA-UD3 Rev 4.0
G-Skill PC3-10700- 16GB
Gigabyte Windforce GTX 1060 OC 6GB - 417.01
Creative Soundblaster Z
ViewSonic VX2268WM Black 22" 1680x1050 5ms 120Hz 3Dvision
Windows 10 x64 1709

#65
Posted 09/24/2016 11:36 PM   
I wonder how long this bug has been around for. I remember this hard stutter all the way back on core 2 duo with a GF4 Ti4600 in games such as Need for Speed underground, especially on the drift courses. It was fixed after a CPU / GFX card upgrade, and at the time I assumed it was just the CPU/GPU not being powerful enough. Hopefully it won't rear its ugly head again!
I wonder how long this bug has been around for. I remember this hard stutter all the way back on core 2 duo with a GF4 Ti4600 in games such as Need for Speed underground, especially on the drift courses.

It was fixed after a CPU / GFX card upgrade, and at the time I assumed it was just the CPU/GPU not being powerful enough.

Hopefully it won't rear its ugly head again!

Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.

#66
Posted 09/25/2016 12:58 AM   
Not that anyone cares, but... The so-called "bug", I haven't encountered it ONCE. And I have tested on 5 Different machines.... 372.90 drivers WORK EXACTLY as the previous ones (on all 5 machines)... Point is... I am not sure WHAT WAS the exact cause of this problem! Sure, we can blame the driver. Is the easiest thing we can do (and what everyone has done so far). But, I am not so sure this issue was a "pure driver" of a much more "complicated" combination of events. Point is, I am not so sure we will not see this issue in the future... Something isn't exactly right here... (based on what everyone reported so far...) In any case, glad that it works for everyone now:) Just keeps your eyes "open" when it will "strike" again though...
Not that anyone cares, but... The so-called "bug", I haven't encountered it ONCE.
And I have tested on 5 Different machines.... 372.90 drivers WORK EXACTLY as the previous ones (on all 5 machines)...

Point is... I am not sure WHAT WAS the exact cause of this problem! Sure, we can blame the driver. Is the easiest thing we can do (and what everyone has done so far).

But, I am not so sure this issue was a "pure driver" of a much more "complicated" combination of events. Point is, I am not so sure we will not see this issue in the future... Something isn't exactly right here... (based on what everyone reported so far...)

In any case, glad that it works for everyone now:) Just keeps your eyes "open" when it will "strike" again though...

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)

#67
Posted 09/25/2016 01:36 AM   
Seems noone else has mentioned it here but the 3D Vision Driver has been updated to version 372.90. Looking at the release notes the 3D Vision Driver isn't even listed in the "Software Module Versions" section, maybe some late changes that didn't make the notes? @helifax: I actually read the signatures here more than any other forum! It helps to understand 3D performance and also helps me to dream/decide future upgrades :) Not that I expect you to type it all out again, most of the regulars/lurkers here should be familiar with your rig anyway!
Seems noone else has mentioned it here but the 3D Vision Driver has been updated to version 372.90.

Looking at the release notes the 3D Vision Driver isn't even listed in the "Software Module Versions" section, maybe some late changes that didn't make the notes?

@helifax: I actually read the signatures here more than any other forum! It helps to understand 3D performance and also helps me to dream/decide future upgrades :) Not that I expect you to type it all out again, most of the regulars/lurkers here should be familiar with your rig anyway!

OS & Driver: Win 10 w/417.35
CPU & GPU: i7 4790k, Gigabyte 980Ti G1 Gaming
MB & RAM: Asrock Z97 Extreme4, GSkill Trident 16Gb DDR3 2400Mhz
Audio: Realtek HD, Steinberg UR44
Display: Acer XB271HUA w/3D Vision 2 Kit

#68
Posted 09/25/2016 03:43 AM   
Yep, 372.90 is a massive improvement on smoothness on both my gtx 980 and gtx 1080 using win 7 and win 10. i7 2600k cpu. Fallout 4, just cause 3, Rise of the tomb raider, batman arkham games saw massive boost for me. All those had bad stuttering which is now fixed.
Yep, 372.90 is a massive improvement on smoothness on both my gtx 980 and gtx 1080 using win 7 and win 10. i7 2600k cpu. Fallout 4, just cause 3, Rise of the tomb raider, batman arkham games saw massive boost for me. All those had bad stuttering which is now fixed.

#69
Posted 09/25/2016 10:53 AM   
Yesssss!!! Batman Arkham Origins runs perfectly with the new drivers. No more fps drops or stuttering when flying around.
Yesssss!!! Batman Arkham Origins runs perfectly with the new drivers. No more fps drops or stuttering when flying around.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#70
Posted 09/25/2016 10:56 AM   
[quote="helifax"]Not that anyone cares, but... The so-called "bug", I haven't encountered it ONCE. And I have tested on 5 Different machines.... 372.90 drivers WORK EXACTLY as the previous ones (on all 5 machines)... Point is... I am not sure WHAT WAS the exact cause of this problem! Sure, we can blame the driver. Is the easiest thing we can do (and what everyone has done so far). But, I am not so sure this issue was a "pure driver" of a much more "complicated" combination of events. Point is, I am not so sure we will not see this issue in the future... Something isn't exactly right here... (based on what everyone reported so far...) In any case, glad that it works for everyone now:) Just keeps your eyes "open" when it will "strike" again though...[/quote] I care. I like to have as much information as possible. Especially high quality tests like you make. However, it's important to remember that each of our personal experiences cannot be applied to everyone else. There is just far too much variance in hardware and software to make generalized conclusions. It's really interesting that you have not run into these problems, whereas numerous other people, including myself, have. The fact that you do not see the bug does not mean it does not exist. I'm not making up false reports or chasing non-existent problems. I can say with complete confidence that this fixed the stuttering in Just Cause 3, for my system. Like you, I do strict tests, changing only a single parameter at a time to clarify. The only change I made was to DDU install the new driver, and ran the exact same scenario. I've taken to putting my test cases on alternate boot partitions, so literally nothing else changes outside of my tests. I'm not simply "blaming the driver", I proved it with a clean experiment. Given that other people are reporting improvements as well, we can clearly conclude that the new driver fixes [i]something [/i]related to a stutter bug. @terintamel's experiment is not as good, because he changed multiple parameters at a time. It would be super helpful, if he can downgrade the driver and test if the bug comes back, as that would give the extremely strong A:B:A test that proves it. It is also worth noting that the driver [i]does not[/i] fix the Far Cry 3 stuttering that I see. 3D enabled causes stuttering when running through the jungle, and 3D disabled is perfectly smooth. So... it does not fix all stuttering. Please let me be clear- I am not trying to give you a hard time, and I am not trying to pick another fight. I, like you, just want the facts.
helifax said:Not that anyone cares, but... The so-called "bug", I haven't encountered it ONCE.
And I have tested on 5 Different machines.... 372.90 drivers WORK EXACTLY as the previous ones (on all 5 machines)...

Point is... I am not sure WHAT WAS the exact cause of this problem! Sure, we can blame the driver. Is the easiest thing we can do (and what everyone has done so far).

But, I am not so sure this issue was a "pure driver" of a much more "complicated" combination of events. Point is, I am not so sure we will not see this issue in the future... Something isn't exactly right here... (based on what everyone reported so far...)

In any case, glad that it works for everyone now:) Just keeps your eyes "open" when it will "strike" again though...

I care. I like to have as much information as possible. Especially high quality tests like you make.

However, it's important to remember that each of our personal experiences cannot be applied to everyone else. There is just far too much variance in hardware and software to make generalized conclusions.

It's really interesting that you have not run into these problems, whereas numerous other people, including myself, have. The fact that you do not see the bug does not mean it does not exist. I'm not making up false reports or chasing non-existent problems.


I can say with complete confidence that this fixed the stuttering in Just Cause 3, for my system. Like you, I do strict tests, changing only a single parameter at a time to clarify. The only change I made was to DDU install the new driver, and ran the exact same scenario.

I've taken to putting my test cases on alternate boot partitions, so literally nothing else changes outside of my tests. I'm not simply "blaming the driver", I proved it with a clean experiment.

Given that other people are reporting improvements as well, we can clearly conclude that the new driver fixes something related to a stutter bug.


@terintamel's experiment is not as good, because he changed multiple parameters at a time. It would be super helpful, if he can downgrade the driver and test if the bug comes back, as that would give the extremely strong A:B:A test that proves it.


It is also worth noting that the driver does not fix the Far Cry 3 stuttering that I see. 3D enabled causes stuttering when running through the jungle, and 3D disabled is perfectly smooth. So... it does not fix all stuttering.


Please let me be clear- I am not trying to give you a hard time, and I am not trying to pick another fight. I, like you, just want the facts.

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

#71
Posted 09/25/2016 11:08 PM   
@bo3b - If I get a chance to image my system I will try a downgrade. Just slightly afraid to potentially mess up something that is working for me. I can say with 100% certainty that ALL my stuttering is gone in the games that stuttered before;Far Cry 3 included. I am literally shocked at how well those games are running now.
@bo3b - If I get a chance to image my system I will try a downgrade. Just slightly afraid to potentially mess up something that is working for me.

I can say with 100% certainty that ALL my stuttering is gone in the games that stuttered before;Far Cry 3 included.

I am literally shocked at how well those games are running now.

AMD FX-8350 4GHz
Gigabyte 990FXA-UD3 Rev 4.0
G-Skill PC3-10700- 16GB
Gigabyte Windforce GTX 1060 OC 6GB - 417.01
Creative Soundblaster Z
ViewSonic VX2268WM Black 22" 1680x1050 5ms 120Hz 3Dvision
Windows 10 x64 1709

#72
Posted 09/25/2016 11:26 PM   
I haven't done as much precise testing, but this driver definitely improved stuttering issues for me. The only variable I recall changing is driver version 368.69->372.90. I've seen improvements in Fallout 4 and Assassin's Creed Rogue (before this driver fix, I was seriously considering playing these on console due to the bad stutter on my PC). There is also Rise of the Tomb Raider, Lords of the Fallen, and Batman Arkham Knight which had stutter issues, but I haven't gotten around to testing those yet.
I haven't done as much precise testing, but this driver definitely improved stuttering issues for me. The only variable I recall changing is driver version 368.69->372.90.
I've seen improvements in Fallout 4 and Assassin's Creed Rogue (before this driver fix, I was seriously considering playing these on console due to the bad stutter on my PC).

There is also Rise of the Tomb Raider, Lords of the Fallen, and Batman Arkham Knight which had stutter issues, but I haven't gotten around to testing those yet.

i7-4770k @ 4.3GHz
EVGA GTX 1080Ti
16GB 2400MHz DDR3
1TB SanDisk SSD
2TB 7200RPM HDD
Windows 10 x64

#73
Posted 09/25/2016 11:57 PM   
Thanks bo3b for the very good explanation;) Sometimes I lose myself in details and can't make an explanation that everyone agrees/understands:) You pretty much nailed there;) Because, I didn't see the issue "doesn't mean" is not there. I agree! Then again, I 99% of the time RUN Surround (this is both WINDOWS and games. Actually Surround is 10001% always enabled in Windows. Based on past experience, Surround behaves like a hybrid between Single Screen + SLI and Single Screen + Single GPU. It has a thing of "it's own". But I also do a lot of test on my Laptop(s) with a single GPU + Single screen. I also disable Surround and run Single Screen + SLI as well for test. Just nothing I use daily though.) Also, it would be awesome if no-one ever experienced this sort of problem:) I just wanted to put in a "reminder" that if we see something like this again, maybe is the Nvidia drivers or maybe not;) (Like you and I know, software is darn complicated especially when you run "Windows 10" as your OS, with all it's updates and "breakable things"....)
Thanks bo3b for the very good explanation;) Sometimes I lose myself in details and can't make an explanation that everyone agrees/understands:)

You pretty much nailed there;)

Because, I didn't see the issue "doesn't mean" is not there. I agree! Then again, I 99% of the time RUN Surround (this is both WINDOWS and games. Actually Surround is 10001% always enabled in Windows. Based on past experience, Surround behaves like a hybrid between Single Screen + SLI and Single Screen + Single GPU. It has a thing of "it's own". But I also do a lot of test on my Laptop(s) with a single GPU + Single screen. I also disable Surround and run Single Screen + SLI as well for test. Just nothing I use daily though.)

Also, it would be awesome if no-one ever experienced this sort of problem:) I just wanted to put in a "reminder" that if we see something like this again, maybe is the Nvidia drivers or maybe not;) (Like you and I know, software is darn complicated especially when you run "Windows 10" as your OS, with all it's updates and "breakable things"....)

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)

#74
Posted 09/26/2016 01:36 AM   
[quote="helifax"]Thanks bo3b for the very good explanation;) Sometimes I lose myself in details and can't make an explanation that everyone agrees/understands:) You pretty much nailed there;) Because, I didn't see the issue "doesn't mean" is not there. I agree! Then again, I 99% of the time RUN Surround (this is both WINDOWS and games. Actually Surround is 10001% always enabled in Windows. Based on past experience, Surround behaves like a hybrid between Single Screen + SLI and Single Screen + Single GPU. It has a thing of "it's own". But I also do a lot of test on my Laptop(s) with a single GPU + Single screen. I also disable Surround and run Single Screen + SLI as well for test. Just nothing I use daily though.) Also, it would be awesome if no-one ever experienced this sort of problem:) I just wanted to put in a "reminder" that if we see something like this again, maybe is the Nvidia drivers or maybe not;) (Like you and I know, software is darn complicated especially when you run "Windows 10" as your OS, with all it's updates and "breakable things"....)[/quote] Cool, sounds good. You had put "bug" in quotes, and I wanted to clarify that it was a genuine problem that I ran into, and also that my test case was as good as I can make it. The word "bug" is relatively vague, but in my judgment it was a bug that got fixed. I'm pretty stoked because now I can actually play JC3 whereas before it was DOA. It's weird that it fixed FarCry3 for terintamel, but not for me, and also weird that you never saw the problem, even on multiple systems. The complexity is really a drag. I like helping to make fixes, creating the tools, and fixing games, but I really don't like the QA involved in all the different configurations that everyone runs. QA is boring and not very interesting to me, but it's necessary to rule out various factors. This is the big reason I keep pushing people to just use Win7- it's more stable, less random bullshit changes from Microsoft to mess things up. And, doing QA for two OSes sucks. But of course, as you know, no one cares how hard it is, or how much time is wasted on QA for all these variants. After all, it's our time, not theirs. I'm not happy about it though.
helifax said:Thanks bo3b for the very good explanation;) Sometimes I lose myself in details and can't make an explanation that everyone agrees/understands:)

You pretty much nailed there;)

Because, I didn't see the issue "doesn't mean" is not there. I agree! Then again, I 99% of the time RUN Surround (this is both WINDOWS and games. Actually Surround is 10001% always enabled in Windows. Based on past experience, Surround behaves like a hybrid between Single Screen + SLI and Single Screen + Single GPU. It has a thing of "it's own". But I also do a lot of test on my Laptop(s) with a single GPU + Single screen. I also disable Surround and run Single Screen + SLI as well for test. Just nothing I use daily though.)

Also, it would be awesome if no-one ever experienced this sort of problem:) I just wanted to put in a "reminder" that if we see something like this again, maybe is the Nvidia drivers or maybe not;) (Like you and I know, software is darn complicated especially when you run "Windows 10" as your OS, with all it's updates and "breakable things"....)

Cool, sounds good. You had put "bug" in quotes, and I wanted to clarify that it was a genuine problem that I ran into, and also that my test case was as good as I can make it. The word "bug" is relatively vague, but in my judgment it was a bug that got fixed. I'm pretty stoked because now I can actually play JC3 whereas before it was DOA. It's weird that it fixed FarCry3 for terintamel, but not for me, and also weird that you never saw the problem, even on multiple systems.

The complexity is really a drag. I like helping to make fixes, creating the tools, and fixing games, but I really don't like the QA involved in all the different configurations that everyone runs. QA is boring and not very interesting to me, but it's necessary to rule out various factors.

This is the big reason I keep pushing people to just use Win7- it's more stable, less random bullshit changes from Microsoft to mess things up. And, doing QA for two OSes sucks. But of course, as you know, no one cares how hard it is, or how much time is wasted on QA for all these variants. After all, it's our time, not theirs. I'm not happy about it though.

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

#75
Posted 09/26/2016 03:27 AM   
  5 / 6    
Scroll To Top