• Gimpydude@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    35
    ·
    2 years ago

    Specifically, he wanted to see if he could prove that Denuvo kills performance as much as many people believe.

    This can be done without cracking it. There have been several games that have removed this DRM, as well as some who have added it post-publication. Benchmarks between versions should highlight the performance issues.

    Also, fuck Denuvo.

  • William@lemmy.world
    link
    fedilink
    English
    arrow-up
    30
    ·
    2 years ago

    "He discovered that the amount of Denuvo code executed in-game is quite infrequent, with calls occurring once every few seconds, or during level loads. This suggests that Denuvo is not killing performance, contrary to popular belief. "

    No, it might suggest that this version of Denuvo and the way that this developer implemented it might not be affecting performance.

    However, “every few seconds” is actually quite a lot, and if it causes a stutter each time, it’s brutal on perceived framerate. So no, it doesn’t actually suggest that Denuvo isn’t killing performance. It’s actually making it pretty obvious that it can easily affect performance.

  • Hal-5700X@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    2 years ago

    A DRM developer says DRM protection does not hamper gaming performance. Okay, nothing weird here.

  • nanoUFO@sh.itjust.worksOPM
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 years ago

    Fuck denuvo, the only good thing about denuvo is that eventually the devs get tired of paying for it.

  • mindbleach@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    15
    ·
    2 years ago

    Denuvo is a cache defeat mechanism. Of course it kills performance. If CPUs still worked like 386s and 68000s, then having eight copies of every function and bouncing merrily between them would make no difference. But modern processors are only fast because they spend negligible time waiting for RAM to get its act together. Every squandered microsecond is a thousand cycles burned.