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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
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.
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