The survival horror game, Resident Evil 4, developed by Capcom, is available for PS4, PS5, Xbox Series X/S and PC, as the game has a strong protection system in the PC version.

This excellent title is a remake of the original hit game from 2005. The game includes new graphical updates and gameplay mechanics, but retains many of the core elements that made the original game so popular, making it an enjoyable experience for critics, fans of the original game, and new players alike.

When Resident Evil 4 Remake was released on PC via Steam, it was confirmed on the store page that it contains the controversial DRM: Denuvo Anti-tamper protection system, which left players across the platform concerned about how it would affect the game's performance on computers, as has happened with many Capcom titles in the past.

While the game's reviews seem to be great and almost perfect from players on the Steam store, many of them have complained that the game's performance issues appear on default settings on devices that should be able to handle the full version of the game as opposed to the beta version, where one reviewer said via the game's page:

The test worked fine with the correct settings, without any issues. However, the full version has performance issues, caused by Denuvo, as usual.

Another player talking about this issue he's having:

Denuvo again!, I can't even start the game, the demo played well, but I can't play the full game well.

In any case, it's usually a major problem for owners of low-end to mid-range computers, as it directly impacts performance and even leads to a drop in average frame rates. Of course, this issue doesn't apply to all games that use this protection system.

The Denuvo protection system has suffered significantly with Intel Alder Lake PC processors, with issues arising related to the recognition of hybrid architecture programs, as well as the emergence of digital rights management tools in games running on active cores as a separate system, which could cause the game to suddenly close or even prevent it from running in the first place, but Intel resolved this issue several years ago.

Copy the article link The link has been copied