Any idea why it is 345.20 when the one released on February 10th was 347.52? Is this just making an earlier version able to work with the 900 series?
Edit/addition: People on EVGA's forums think this might be some snafu by Nvidia - someone who tried it said his FPS took a big hit on the 345.20 driver over the 347.52 one.
Link: http://forums.evga.com/NVIDIA-34520-Drivers-m2300016.aspx
Actually, from the developer forums I could give you something of a painfully technical explanation about what they did, but basically it boils down to it being a Band-Aid release that enables some of the newer hardware features while avoiding the painful game and video application killing crashes that were being seen by a rather large pool of users when they would attempt to run in full screen mode. It has to do with the way the newer drivers handle scaling functions and high-res/high DPI display modes while still allowing all of that pretty hardware acceleration that the newer GPUs are capable of. Yes, it shows a performance hit compared to the 347.52 driver, but it's FAR less than the difference between running a windowed fullscreen session of a game like Inquisition compared to a true fullscreen session, and many people were finding that after updating to 347.52 windowed fullscreen was the only way their games and video applications would run. There are some major differences between the two in how they handle scaling on hi-res/high DPI displays, and DirectX 11 kept bombing out in fullscreen applications running under 347.52. The devs are hammering away at it though. Hopefully they'll figure out the problem soon and push out a new version.
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.
@PotentPotions wrote:Actually, from the developer forums I could give you something of a painfully technical explanation about what they did, but basically it boils down to it being a Band-Aid release that enables some of the newer hardware features while avoiding the painful game and video application killing crashes that were being seen by a rather large pool of users when they would attempt to run in full screen mode. It has to do with the way the newer drivers handle scaling functions and high-res/high DPI display modes while still allowing all of that pretty hardware acceleration that the newer GPUs are capable of. Yes, it shows a performance hit compared to the 347.52 driver, but it's FAR less than the difference between running a windowed fullscreen session of a game like Inquisition compared to a true fullscreen session, and many people were finding that after updating to 347.52 windowed fullscreen was the only way their games and video applications would run. There are some major differences between the two in how they handle scaling on hi-res/high DPI displays, and DirectX 11 kept bombing out in fullscreen applications running under 347.52. The devs are hammering away at it though. Hopefully they'll figure out the problem soon and push out a new version.
BTW, can you link us to the developer forums that you're talking about? I'd like to follow along
