Time for another before/after performance comparison, just for an ignorant Denuvo salestwat to say: "Nuh-Uh"
this post was submitted on 04 Mar 2025
1 points (100.0% liked)
Games
18005 readers
929 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 2 years ago
MODERATORS
Denuvo itself, if correctly implemented, has minimal impact. The thing is most games call it too often or wrongly implements it, which slow things down considerably.
Yes, I think you’re right. Games perform better when they call Denuvo less frequently. Therefore, for optimal performance, games should call Denuvo 0 times.
For sure 😂
That may be the case, but doesn't change the fact, that games run better without Denuvo.
It also doesn't change the fact that the activation limit is stupid as hell when you are using Linux and every Proton change counts as a new activation.
As far as I know Denuvo also hinders the development of native Linux builds of games.
And if you see video games as art, Denuvo actively stands in the way of preservation.
Obviously it is anti-consumer as you can't do backups, need constant internet convection, if any part of the chain breaks you are screwed out of your game, it hinders mod developers and so on.
"It's not that it adds overhead on top, it's just that it adds to the top some head over.
You must not get my point. What I’m saying is that if Denuvo is implemented properly, we shouldn’t see a difference that’s more than like 3%. If it’s more, then it’s called too often and thus a bad implementation from the devs.
When comparison videos are shared, it’s often on games with bad implementations. You can also find some comparisons that don’t affect performance as much. In the end it’s the Denuvo implementation that’s slowing down, and that’s on the dev, not the company making unoptimized code.
I’m not denying that it impacts performance: it does, but not as much as you might believe if properly implemented, which if not, is not Denuvo's (the company) fault, but rather the devs'.
I get you, but I think at a certain point if we're relying on it being properly implemented and a large group isn't then I'd say we're back on denuvo as the party at fault for not addressing it and preventing it.
It sucks, but we have to expect and plan for when people are stupid to a point because that is always going to be a key source of failure.
That’s an opinion :) alright then