Hmm, sounds like Destructoid found a bad memory leak there (16GB system RAM, 4GB VRAM = this was not a case of the game wanting more RAM from normal operation - I am a programmer) or something else odd (symptoms could easily be something else going wrong but it doesn't sound like the executable working "normally", whatever caused it to break). It's certainly not universal as DF did their tests on a few different rigs and didn't walk into similar issues.
The inconsistent FPS issues and being settings-agnostic does unfortunately remind me of Just Cause 3. That game worked find for some people, and terribly for other (with basically no consistent way to guess which camp you're in other than run it and see - at least from my pool of friends and range of hardware/configurations). A game which got reclassified by nVidia from their first comment on recommended specs to the final ones they advised post-release, and was shown in radically better state (at events) pre-release. So here's the conspiracy theory: the beta version nVidia tested and was at shows didn't have the final DRM (Denuvo). No intrusive hooks to protect the encrypted binary existed in those versions.
A quick note of clarification: Denuvo is the anti-tamper system. It works on top of DRM (the thing that makes sure you have the rights to run the software). Basically traditional DRM (like the options available to any Steam-powered game) is wrapping the actual game with more code that firsts checks you have a token that allows you to run the game, then run (the token can be generated at install time, so you have to be online to install a game, or at run-time, so you have to be online to play a game - the latter is what many publishers moved away from). Cracking is making it so that check is skipped by modifying the executable (and basically removing that check). What Denuvo does is ensure that tampered executables don't work. So it is more than a check you run and then forget, it has to be constantly there, making sure this doesn't leak the unencrypted binary. I suspect it messes with program execution to do so and make it so hard to crack.
So this Tomb Raider also has Denuvo. And is also showing this incredibly inconsistent performance (which doesn't appear to be related to GPU load) or specific areas. When I looked at Just Cause 3 it actually looked like the GPU side was basically soft-crashing and being recovered (the GPU stalled and the VRAM load was completely flushed and reloaded when the fps cratered and then returned but lower than before the stall).
What if something in the Denuvo layer isn't well tested (note that it will be a different version every game to make cracking harder and they probably don't submit it to GPU makers) and on some machine configurations causes a memory leak and/or a GPU driver soft-crash? We'll never see this software working without the Denuvo, unless crackers do finally manage to extract an unencrypted binary (which they will strip the DRM from to enable piracy). Makes me interested in seeing that crack, if it does get completed (own JC3 on Steam, linked to my profile, 50+ hours played and completed, definitely not a pirate pretending to want cracks under the mask of a "valid" reason). Way sooner than the "in 10 years" discussed on the most recent Bombcast.
Edit: Why hasn't this busted all Denuvo encrypted games to not work with drivers/PC properly? Maybe something in the mastering tools used by Squidix or the specific branch/version of it they purchased/are using is breaking. I guess we'll know more in 24 hours if the same group who found JC3 broken find this one is busted too in the same way (but that Destructoid report is outlining basically exactly how JC3 shipped broken).
Log in to comment