• IcePee@lemmy.beru.co
      link
      fedilink
      English
      arrow-up
      26
      arrow-down
      1
      ·
      3 months ago

      While I’m no fan of the crippleware, I don’t think this product from them would effect your average gamer. It looks to be focused on beta testers and reviewers.

      But, knowing the human’s facility for laziness, odds on it will filter into general release.

  • DebatableRaccoon@lemmy.ca
    link
    fedilink
    English
    arrow-up
    77
    arrow-down
    1
    ·
    3 months ago

    Update: it causes even more hung processes while corpo shills and fanboys argue online that Denuvo has zero negative effect to infected games which is immediately disproven or ignored by those with brains.

  • TFO Winder@lemmy.ml
    link
    fedilink
    English
    arrow-up
    39
    ·
    3 months ago

    It’s a game of cat and mouse again.

    One leaker caught and account got banned … Another account created.

    • howrar@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 months ago

      I can’t say I know anything about how they choose their beta testers, but if I were to guess, there is probably some kind of vetting process that includes looking at how reputable you are. It would take a long time to build up that reputation.

    • bountygiver@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 months ago

      the leaker in question is about people like a qa tester or someone who got an early access review.

  • Willy@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    24
    ·
    3 months ago

    that’s an interesting idea. would they have to compile individual versions for the testers? will it work after final release and people stop having NDAs and can compare several copies with each other?

    • RecallMadness@lemmy.nz
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 months ago

      If I were building it, I’d do the watermarking on the individual assets & textures.

      Your asset pipeline would publish these to the solution, which would pack it up ready for distribution.

      Except, each beta tester logs into the game and the publishing system gives them a personalised set of assets with a unique noise filter thrown over the top.

      Mr leaky beta player publishes a video or screenshot of the gameplay, and then the studio can just reverse the noise algorithm to get their unique ID.

      Absolutely terrible for large scale content delivery. But for a small closed beta, probably not an issue.

      • maynarkh@feddit.nl
        link
        fedilink
        English
        arrow-up
        4
        ·
        3 months ago

        Wouldn’t capturing in high-res, then scaling down or compressing the picture/video defeat the noise filter? Or if you threw a bit of noise on it yourself?

        • suppenloeffel@feddit.de
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 months ago

          Steganography is a (fascinating) bitch. There are a lot of ways to hide a message in an image which is very resilient to manipulations like resizing, compression or even the loss of information by actually filming a screen versus taking a screen capture.

          If you adjust your approach to not rely on a single picture to reliably convey a short message, but part it out over tens or hundreds of frames in a video, it’s basically impossible to make sure that the message was erased without knowing the algorithms used or rendering the video unwatchable.

          It’s an awesome field and nothing new.

    • sus@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 months ago

      They could do it without recompilation, but something like changing the obfuscation and recompiling for every copy would likely make it much harder to get rid of the watermarks even if you can compare several different copies

      (though they could also have multiple watermarked sections so that any group of for example 3 copies would have some section that is identical, but still watermarked and would uniquely identify all three leakers. The amount of data you need the watermarks to contain goes up exponentially with the amount of distinct copies, but if you have say 1000 review copies and want to be resistant to 4 copies being “merged”, you only need to distinguish between 1000^4 combinations so you can theoretically get away with a watermark that only contains about 40 bits of data )

      • howrar@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        That’s ridiculously tiny, especially considering that the game itself is likely around 100GB. They could probably watermark every single copy that ever goes out.

  • JJLinux@lemmy.ml
    link
    fedilink
    English
    arrow-up
    12
    ·
    3 months ago

    Publishers don’t seem to understand that Denuvo is detrimental to them as much as for gamers. That crap regularly breaks games. Ask Bethesda, they should know.

  • KpochMX@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 months ago

    fighting piracy would be easier if they Develop a working and final build of the game - We are no paying full 70 usd price to be an Alpha tester

    instead of 70 usd make it 50 usd more people will have a second thought when pirating with a lower price Do not include core in-game function as DLC ( New Game Plus as dlc? )