Interesting, is that why my apps are scaled to a lot larger than they were on previous drivers, even though the Windows scaling is set to the same value?
That could very well be the case.
I suppose they won't ever actually SAY what the exact difficulty was - they'll just address it and move on pretending it never happened. Standard Operating Procedure, no?
:catwink:
Thanks for the link, my updater still shows 347.52 as the latest driver. Hope it works, those crashes are a huge pain. My fps didn't change btw.
Well. I suppose technically the 347.52 is the latest driver in terms of development. As for stability and actual release date, it's the tweaked version of the 345.20. Their updater software looks at the numerical build number rather than the release date.
In reality, the 345.20 is a Band-Aid release to appease the masses whose display hardware dislikes some of the "enhancements" the newer drivers can push out of their GPUs.
Honestly? It's a pretty decent compromise if your monitor has a 60Hz or less refresh and/or more than a 5ms response time or doesn't handle scaling well.
The 347.52 is listed as WHQL certified, sure - but have you read the specs for the hardware it's certified on? I have some pretty amazing hardware straight from Badassdom Central and that list makes me drool...
:catlol:
