A forum for discussing and organizing recreational softball and baseball games and leagues in the greater Halifax area.
Time for another before/after performance comparison, just for an ignorant Denuvo salestwat to say: "Nuh-Uh"
-
Somehow the same logic is not applied when people talk about Linux. It's always the developers fault if something doesn't work on it, such as multiplayer games, standard engineering softwares, or even computer accessories.But it is. There's nothing Linux devs can do if game/anticheat devs block Linux.
-
Somehow the same logic is not applied when people talk about Linux. It's always the developers fault if something doesn't work on it, such as multiplayer games, standard engineering softwares, or even computer accessories.Because those developers are not actually trying to get it to work in Linux, they are trying to get it to work in Windows. Game developers that are licensing denuvo probably are trying to get their game with denuvo. Linux intended software does not have the performance issues denuvo has.
-
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.So you admit games simply run better without it.
-
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."It's not that it adds overhead on top, it's just that it adds to the top some head over.
-
So you admit games simply run better without it.
-
"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 is 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'.
-
If very many developers integrating Denuvo are making errors with it, it's because of Denuvo. Their documentation is insufficient or their interface is poorly designed or something. Or maybe their code really is just shit. Most likely some combination of factors. Regardless, I'm not letting them off the hook; this is still their fault as much as it is that of the companies choosing to use it.
-
You must not get my point. What I’m saying is that is 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.
-
They’re just providing a service. We should mostly blame the editors/devs that are making the choice of including it. I hate the tool but idc about the companyJust to be clear, I wasn't making a moral argument in my previous comment, only a technical one. If their software causes slowdowns in many real-world cases, I blame them for it, not just the people who are using it.
-
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.
alright then