Nvidia App performance issue gets 'fixed' with release 11.0.1 — but all it has done is turn off Game Filters by default
Brushing problems under the carpet rather than fixing them.
The Nvidia App has been updated with a new release, from version 10.0.x to 11.0.1. The significant change here is that users should not experience the disappointing gaming performance loss (up to 15%) witnessed by those who installed prior releases. However, rather than fix the underlying bug, Nvidia seems to have swept it under the carpet, as 11.0.1's only flagged change is that the "Game Filter now defaults to off."
We wrote about this option-toggle fix (which is more like a workaround) shortly after tech forums and social media began to erupt with complaints over the performance-sapping Nvidia App. The app moved out of beta a few weeks ago and replaced the (also) unloved GeForce Experience accessory app in the 566.14 drivers release. The beta testing period wasn't enough to catch the gaming performance impacts. If only the test team had included an avid Assassin's Creed Mirage player.
So, if you already have a previous version of the Nvidia App, primarily the prior 10.0.3 release, perhaps it isn't worth grabbing this new one. If you have already implemented the toggle workaround to preserve your GeForce fps, why not skip the 11.0.1 update to save a few bytes of data transfer (147mb) and reduce your carbon footprint?
For those who missed our previous story, in which we explained how to restore your graphics card performance, all you have to do is visit "Settings > Features > Overlay > Game Filters and Photo Mode" in the Nvidia App and click the toggle (to off). The Nvidia App 11.0.1 already has this toggle turned to the off position for you.
Previous releases of the Nvidia App have been stuffed with many more impactful optimizations, updates, and changes but only warranted a 0.0.1 increment in the version number. Perhaps Nvidia has updated something in 11.0.1 that it hasn't told us about, or the devs are already enjoying the Christmas spirit and wanted to celebrate with a major version increment.
You can grab the latest Nvidia App version, 11.0.1, directly from Nvidia here, where you should also find any subsequent updates.
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
Mark Tyson is a news editor at Tom's Hardware. He enjoys covering the full breadth of PC tech; from business and semiconductor design to products approaching the edge of reason.
-
hotaru251 "there is no problem in ba sing se"Reply
if you can't use filters should of just removed em until an actual fix is done no just disable em by default :| -
txfeinbergs I have no idea what this article is even talking about. 11.0.1 has been available since 11/6. There is nothing new here.Reply -
ekio If they could make the UI readable, that would be nice too.Reply
They went all in for the new d4rk g4m3r style, but I find the settings very hard to read.
Compared to Intel GPU graphics command center, that is clean and well-made, this is awful. -
HyperMatrix “save a few bytes of data transfer (147mb) and reduce your carbon footprint?”Reply
You can’t be serious….reading this article uses more electricity than downloading a 147MB application. -
SirStephenH Sweeping the problem under the rug?Reply
Nvidia is doing what you should want every company to do with software. They're releasing an update with a workaround for a problem while they continue working on a proper fix. It's best not to leave issues hanging when there's something quick and simple that will at least reduce the issue's occurrence. -
SirStephenH
You can use the filters and it doesn't break anything if you use them, it just drops your performance by up to 15% if you have the overlay enabled, whether you enable filters or not. In cases like these where an optional component causes performance loss but doesn't break anything, it's better to give people the choice of whether they want to use it or not.hotaru251 said:"there is no problem in ba sing se"
if you can't use filters should of just removed em until an actual fix is done no just disable em by default :|