That‘s certainly something they‘re gonna want to fix. I hope DF and GN pick up on this, seems like free views and I‘d love to hear what they‘ve got to say on the matter.

Edit: Also wondering if it‘s the app or if the performance hit disappears when you disable the overlay. Only flew over the article to see what games are affected how badly so mb if that’s mentioned.

Edit 2:

HUB‘s Tim tested it and found that it‘s the overlay or rather the game filter portion of the overlay causing the performance hit. You can disable this part of the overlay in the app‘s settings, or disable the overlay altogether.

He also found that this feature wasn’t impacting performance on GeForce Experience, so it’s very likely a bug that’s gonna be fixed.

To clarify: Using game filters actively can have an impact on either, but right now even when not actively using them, they cause a performance hit just by the functionality being enabled; a bug.

The only outlier where just having the app installed hit performance was the Harry Potter game.

[+] eramseth@lemmy.world -8 points 1 day ago (1 children)

Yeah they didn't test that. Nor did they test having the app installed but not running. Crummy article tbh.

[–] ArbiterXero@lemmy.world 13 points 1 day ago (1 children)

Disagree, and i don’t think it’s the point.

As an average user, why am I paying a performance hit for nvidia’s own “recommended parameters”

That’s trash and a terrible experience, and they should be called out for it.

[–] eramseth@lemmy.world 2 points 21 hours ago (1 children)

I don't think you're understanding. The testing they did was presumably fine and the performance hit is probably unacceptable. But mentioning but not testing the scenarios of

app installed but not running
app installed and running but overlay turned off

Is kinda mailing it in.

[–] ArbiterXero@lemmy.world 2 points 20 hours ago

I’ll give you that, yep, sure.

But that doesn’t invalidate the data they did get, it’s just not a full picture.