Suggested driver to use?
  4 / 8    
Figured I'd bump this thread, as a lot of people may not know about it, and can add some bacground. [b]Of note, I also have discovered that 350.12 breaks our Mordor fix. The UI is damaged by having no text in the Sauron's Army screen, and also makes the aiming cursor flicker and part of the time the last change QTE circles are missing. This makes it unplayable.[/b] Driver 347.52 works fine here: [img]http://sg.bo3b.net/mordor/ShadowOfMordor31_85.jps[/img] Driver 350.12 is broken: [img]http://sg.bo3b.net/mordor/ShadowOfMordor33_85.jps[/img]
Figured I'd bump this thread, as a lot of people may not know about it, and can add some bacground.


Of note, I also have discovered that 350.12 breaks our Mordor fix. The UI is damaged by having no text in the Sauron's Army screen, and also makes the aiming cursor flicker and part of the time the last change QTE circles are missing. This makes it unplayable.


Driver 347.52 works fine here:

Image


Driver 350.12 is broken:

Image

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

#46
Posted 05/09/2015 04:22 AM   
Driver 352.86 seems to be pretty bad. I get crashes about every 15 minutes in GTA5, and Witcher3 seems to crash at load often. It also seems to cause serious stutter in GTA5 if I play simply in 2D. Anyone having any luck with it?
Driver 352.86 seems to be pretty bad. I get crashes about every 15 minutes in GTA5, and Witcher3 seems to crash at load often. It also seems to cause serious stutter in GTA5 if I play simply in 2D.

Anyone having any luck with 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

#47
Posted 05/24/2015 07:43 AM   
I concur re 3252.86 and GTA5 but add it allows grasses to render correctly. p.s. I would say I look for this thread twice each month. This is such a useful thread for boards like ours which rely on threads like this one for reference; it should be stickied iyam.
I concur re 3252.86 and GTA5 but add it allows grasses to render correctly.

p.s.
I would say I look for this thread twice each month. This is such a useful thread for boards like ours which rely on threads like this one for reference; it should be stickied iyam.

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

#48
Posted 05/24/2015 12:54 PM   
Hi, i always follow this thread too ;). I saw that helifax made a feedback about the driver 353.06. Maybe this one erase the previous problems about Mordor, Da:i, Gta 5 and Witcher 3? I ask this because as you told, it seems that new products are locked to only the last drivers who support them i'm right? So i have to check if they are not too much broken to profit your wonderful work.
Hi,
i always follow this thread too ;).

I saw that helifax made a feedback about the driver 353.06.

Maybe this one erase the previous problems about Mordor, Da:i, Gta 5 and Witcher 3?

I ask this because as you told, it seems that new products are locked to only the last drivers who support them i'm right?
So i have to check if they are not too much broken to profit your wonderful work.

#49
Posted 06/01/2015 09:15 AM   
353.06 GTA5 works with grasses on and doesn't crash on my rig. MP3 profile.
353.06

GTA5 works with grasses on and doesn't crash on my rig. MP3 profile.

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

#50
Posted 06/01/2015 07:17 PM   
353.06 kills 3D in Far Cry 4 - game goes mono (shifted perspective from one eye) as soon as it loads.
353.06 kills 3D in Far Cry 4 - game goes mono (shifted perspective from one eye) as soon as it loads.

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#51
Posted 06/04/2015 01:22 AM   
What about 353.30? No improvement?
What about 353.30?
No improvement?

#52
Posted 06/23/2015 04:09 AM   
[quote=""]What about 353.30? No improvement?[/quote] Don't know about FC4, but this driver doesn't work at all with GTA5, and 3D randomly drops out to the same bad 3D in Mordor. Reminds me of the WatchDogs dropouts. I'd avoid this one. It seems like a general rule of thumb is that we should avoid game specific drivers as being seriously buggy and rushed.
said:What about 353.30?
No improvement?

Don't know about FC4, but this driver doesn't work at all with GTA5, and 3D randomly drops out to the same bad 3D in Mordor. Reminds me of the WatchDogs dropouts. I'd avoid this one.

It seems like a general rule of thumb is that we should avoid game specific drivers as being seriously buggy and rushed.

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

#53
Posted 06/23/2015 08:39 AM   
This should definitely be a sticky I cannot believe how awesome you are Bo3b for keeping this up to date! (and for all the other reasons, of course :-) ) If possible, maybe make the "Terrible, do not use" text appear as red colour, to quickly know what drivers we can dismiss. And maybe if it's worth it, colour in green the best driver for a certain card or game. It's so stupid lately, depending what driver you use you will be locked out of the fixes for certain games. Thanks again for your great efforts to add some method to the nVidia madness of late.
This should definitely be a sticky
I cannot believe how awesome you are Bo3b for keeping this up to date! (and for all the other reasons, of course :-) )
If possible, maybe make the "Terrible, do not use" text appear as red colour, to quickly know what drivers we can dismiss. And maybe if it's worth it, colour in green the best driver for a certain card or game.
It's so stupid lately, depending what driver you use you will be locked out of the fixes for certain games.
Thanks again for your great efforts to add some method to the nVidia madness of late.

#54
Posted 06/23/2015 10:16 AM   
Hey Bo3b, I see you've started collecting the profiles from each driver. Here's a few more: http://darkstarsword.net/profiles/
Hey Bo3b, I see you've started collecting the profiles from each driver. Here's a few more:
http://darkstarsword.net/profiles/

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#55
Posted 06/23/2015 12:11 PM   
[quote=""]Hey Bo3b, I see you've started collecting the profiles from each driver. Here's a few more: http://darkstarsword.net/profiles/[/quote] Thanks man! I've added those links to the first post. As we fill in more I'll update the post. For people following along, the idea here is that we have a completely clean, untouched, set of profiles for a given driver release. We can then copy/paste specific profiles out of those releases for any experiments or use newer profiles in older drivers. [quote=""]This should definitely be a sticky I cannot believe how awesome you are Bo3b for keeping this up to date! (and for all the other reasons, of course :-) ) If possible, maybe make the "Terrible, do not use" text appear as red colour, to quickly know what drivers we can dismiss. And maybe if it's worth it, colour in green the best driver for a certain card or game. It's so stupid lately, depending what driver you use you will be locked out of the fixes for certain games. Thanks again for your great efforts to add some method to the nVidia madness of late.[/quote] Thanks Zappologist. It's all about the maintenance. :-> For coloring the text, I can't say with enough assurance that a given driver is bad or not. I was hoping that people would chime in and add their experiences with drivers, but that hasn't happened, so this data is primarily my solo experience, and thus prone to revision and less confidence in the notes. Not completely useless, but take my driver comments with a grain of salt, as it's all different setups and hardware and limited data.
said:Hey Bo3b, I see you've started collecting the profiles from each driver. Here's a few more:

http://darkstarsword.net/profiles/


Thanks man! I've added those links to the first post. As we fill in more I'll update the post.

For people following along, the idea here is that we have a completely clean, untouched, set of profiles for a given driver release. We can then copy/paste specific profiles out of those releases for any experiments or use newer profiles in older drivers.


said:This should definitely be a sticky
I cannot believe how awesome you are Bo3b for keeping this up to date! (and for all the other reasons, of course :-) )
If possible, maybe make the "Terrible, do not use" text appear as red colour, to quickly know what drivers we can dismiss. And maybe if it's worth it, colour in green the best driver for a certain card or game.
It's so stupid lately, depending what driver you use you will be locked out of the fixes for certain games.
Thanks again for your great efforts to add some method to the nVidia madness of late.

Thanks Zappologist. It's all about the maintenance. :->

For coloring the text, I can't say with enough assurance that a given driver is bad or not. I was hoping that people would chime in and add their experiences with drivers, but that hasn't happened, so this data is primarily my solo experience, and thus prone to revision and less confidence in the notes.

Not completely useless, but take my driver comments with a grain of salt, as it's all different setups and hardware and limited data.

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

#56
Posted 06/24/2015 01:50 AM   
@bo3b Not that it matters to anyone else, but I've been using Win 8 and not 8.1 all this time, so you might want to amend that little detail. I had asked my vendor to update it to 8.1 prior to purchase. Apparently they'd only changed the interface to resemble Win 7 and that was it, and I'd never thought to check. So there you go. Also, one thing I should make very clear, is that I've [u]never[/u] updated either Win 7 or Win 8 on my rig since I've bought it. It might be important not to overlook this fact, when it comes to benchmark testing. All of my games run perfectly well in SLI on both systems. My reasoning is that if no games work on a newly installed OS, prior to updating Windows, then fair enough, then there's nothing to lose by updating everything to the absolute hilt. But why, I ask myself, introduce voluminous amounts of unknown variables if they're not needed, or might only make things worse? Simplicity is what I've always aimed for, making it that much easier for me to determine as to what newly introduced variable might be causing trouble and hopefully correct it there and then. I'm just wondering if this explains as to why you're not getting SLI functionality on GTA V, and why you are not able to match my results at present.
@bo3b

Not that it matters to anyone else, but I've been using Win 8 and not 8.1 all this time, so you might want to amend that little detail. I had asked my vendor to update it to 8.1 prior to purchase. Apparently they'd only changed the interface to resemble Win 7 and that was it, and I'd never thought to check. So there you go. Also, one thing I should make very clear, is that I've never updated either Win 7 or Win 8 on my rig since I've bought it. It might be important not to overlook this fact, when it comes to benchmark testing. All of my games run perfectly well in SLI on both systems. My reasoning is that if no games work on a newly installed OS, prior to updating Windows, then fair enough, then there's nothing to lose by updating everything to the absolute hilt. But why, I ask myself, introduce voluminous amounts of unknown variables if they're not needed, or might only make things worse? Simplicity is what I've always aimed for, making it that much easier for me to determine as to what newly introduced variable might be causing trouble and hopefully correct it there and then. I'm just wondering if this explains as to why you're not getting SLI functionality on GTA V, and why you are not able to match my results at present.

Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82, DX11.0

#57
Posted 06/24/2015 03:58 AM   
[quote=""]@bo3b Not that it matters to anyone else, but I've been using Win 8 and not 8.1 all this time, so you might want to amend that little detail. I had asked my vendor to update it to 8.1 prior to purchase. Apparently they'd only changed the interface to resemble Win 7 and that was it, and I'd never thought to check. So there you go. Also, one thing I should make very clear, is that I've [u]never[/u] updated either Win 7 or Win 8 on my rig since I've bought it. It might be important not to overlook this fact, when it comes to benchmark testing. All of my games run perfectly well in SLI on both systems. My reasoning is that if no games work on a newly installed OS, prior to updating Windows, then fair enough, then there's nothing to lose by updating everything to the absolute hilt. But why, I ask myself, introduce voluminous amounts of unknown variables if they're not needed, or might only make things worse? Simplicity is what I've always aimed for, making it that much easier for me to determine as to what newly introduced variable might be causing trouble and hopefully correct it there and then. I'm just wondering if this explains as to why you're not getting SLI functionality on GTA V, and why you are not able to match my results at present. [/quote] OK, thanks, I've updated the post there. That actually makes a bit more sense, because Win8 is running essentially the same DXGI and D3D11 as Win7, and I could never explain why your "8.1" was working better. 8.1 introduced all sorts of new problems including weird bugs and a new DXGI. As far as running patch-free- I understand your motivation and agree with part of it. The only problem with that idea is that you are running a system that hasn't actually been tested by anyone. When NVidia does QA, they are for sure going to use fully patched systems, so your setup will be an outlier. Not saying that's necessarily wrong, if it's not broken, and you get the results you want, that's the end goal. In terms of variables, the patches actually reduce the number of variables, because you'll more closely match what everyone mostly uses and more importantly what the game devs and NVidia use for QA. Given that their QA for PC Gaming seems to be genuinely awful, it's not clear if that's actually a disadvantage. :->
said:@bo3b

Not that it matters to anyone else, but I've been using Win 8 and not 8.1 all this time, so you might want to amend that little detail. I had asked my vendor to update it to 8.1 prior to purchase. Apparently they'd only changed the interface to resemble Win 7 and that was it, and I'd never thought to check. So there you go. Also, one thing I should make very clear, is that I've never updated either Win 7 or Win 8 on my rig since I've bought it. It might be important not to overlook this fact, when it comes to benchmark testing. All of my games run perfectly well in SLI on both systems. My reasoning is that if no games work on a newly installed OS, prior to updating Windows, then fair enough, then there's nothing to lose by updating everything to the absolute hilt. But why, I ask myself, introduce voluminous amounts of unknown variables if they're not needed, or might only make things worse? Simplicity is what I've always aimed for, making it that much easier for me to determine as to what newly introduced variable might be causing trouble and hopefully correct it there and then. I'm just wondering if this explains as to why you're not getting SLI functionality on GTA V, and why you are not able to match my results at present.

OK, thanks, I've updated the post there. That actually makes a bit more sense, because Win8 is running essentially the same DXGI and D3D11 as Win7, and I could never explain why your "8.1" was working better. 8.1 introduced all sorts of new problems including weird bugs and a new DXGI.

As far as running patch-free- I understand your motivation and agree with part of it. The only problem with that idea is that you are running a system that hasn't actually been tested by anyone. When NVidia does QA, they are for sure going to use fully patched systems, so your setup will be an outlier.

Not saying that's necessarily wrong, if it's not broken, and you get the results you want, that's the end goal.

In terms of variables, the patches actually reduce the number of variables, because you'll more closely match what everyone mostly uses and more importantly what the game devs and NVidia use for QA. Given that their QA for PC Gaming seems to be genuinely awful, it's not clear if that's actually a disadvantage. :->

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

#58
Posted 06/24/2015 04:06 AM   
Point taken, but I'm sure you and I agree that ultimately we'd both rather not run our rigs in a manner deemed convenient for QA testers of dubious competence. I know that you appreciate that it's the end goal that counts. It's just that I've saved myself an awful lot of toing and froing by simply thinking laterally, since I'm not all that bright and yet still get the result that I'm after. If only you were running things bo3b. Anyhow, something to think about and thanks for amending.
Point taken, but I'm sure you and I agree that ultimately we'd both rather not run our rigs in a manner deemed convenient for QA testers of dubious competence. I know that you appreciate that it's the end goal that counts. It's just that I've saved myself an awful lot of toing and froing by simply thinking laterally, since I'm not all that bright and yet still get the result that I'm after.

If only you were running things bo3b. Anyhow, something to think about and thanks for amending.

Intel Core i7 4770k @ 4.4Ghz, 3x GTX Titan, 16GB Tactical Tracer LED, CPU/GPU Dual-Loop Water-Cooled - Driver 331.82, DX11.0

#59
Posted 06/24/2015 04:23 AM   
Thanks Bo3b for this awesome post. The state of these drivers for 3D is appalling. From what I see, I'll have to install a specific driver for each game I want to play. For example I read that 353.06 is good with witcher 3, but this one won't work with far cry 4. It almost doesn't seem possible that things are in such a sorry state. Doesn't seem very professional, but what can we do, I've seen the numbers that bo3d posted here and there isn't enough 3D players out there, I guess if they break our toy, well too bad... It won't really change their bottom line, since we already have our 3D vision kits and our glasses. Seems to be quite some work to play in 3D. And that's without all the work you put into each game. I watched a video yesterday from a racing channel about 3D vision 1 where they talked to that engineer from NVidia responsible for the compatibiliy ratings from NVidia. "And 3d is goin to be great, and it will be supported out of the box by so many games, and you have nothing to configure, it will configure itself..." Well... I guess ideas behind it were great, now for the implementation, I'm not too sure.
Thanks Bo3b for this awesome post.

The state of these drivers for 3D is appalling. From what I see, I'll have to install a specific driver for each game I want to play. For example I read that 353.06 is good with witcher 3, but this one won't work with far cry 4. It almost doesn't seem possible that things are in such a sorry state. Doesn't seem very professional, but what can we do, I've seen the numbers that bo3d posted here and there isn't enough 3D players out there, I guess if they break our toy, well too bad... It won't really change their bottom line, since we already have our 3D vision kits and our glasses.

Seems to be quite some work to play in 3D. And that's without all the work you put into each game.

I watched a video yesterday from a racing channel about 3D vision 1 where they talked to that engineer from NVidia responsible for the compatibiliy ratings from NVidia. "And 3d is goin to be great, and it will be supported out of the box by so many games, and you have nothing to configure, it will configure itself..."
Well... I guess ideas behind it were great, now for the implementation, I'm not too sure.

#60
Posted 06/24/2015 10:16 AM   
  4 / 8    
Scroll To Top