AMD FSR 4.1 Upscaling + Frame Generation 4 Technology Lands on a Vulkan Engine for the First Time: DOOM: The Dark Ages Update 5 Goes Live
IT之家 November 17 news: DOOM: The Dark Ages released Update 5 yesterday (November 16), mainly adding AMD FSR Upscaling 4.1 super-resolution technology and Frame Generation 4 frame generation technology to the PC version of the game.
AMD executive Jack Huynh confirmed that the title has become the first Vulkan game to feature both technologies, meaning the previously announced compatibility support has officially landed in a game. IT之家 attaches the relevant screenshot below:

In plain terms, AMD's FSR Upscaling 4.1 super-resolution technology can be understood as "rendering at a lower resolution first, then reconstructing a clearer image," while Frame Generation 4 frame generation technology improves perceived smoothness by inserting extra frames. This update allows this game, which uses the Vulkan graphics API, to enable AMD's new-generation image processing technology on compatible hardware as well.
On compatibility, the official update notes also mention that Intel GPUs meeting the hardware and driver requirements can now enable FSR frame generation, but no specific models are listed. Beyond graphics features, Update 5 also adds Slaughter Mode, an endless survival mode, to the Revelations expansion, offering ever-escalating demon combat challenges, free of extra charge for owners of the related expansion, Premium Edition, or Premium Upgrade. In addition, the patch adjusts weapon balance and fixes issues such as weapons abnormally disappearing.
Related Articles
- A USB drive screen can also run DOOM, playable by just copying files
- Everything can run Doom: developer runs DOOM on a custom CPU built on GPT-5.6 Sol
- Running DOOM through 96 MB of text: rendering 1 frame takes about 180 seconds
- Hardcore stunting: a printer controller from forty years ago successfully runs DOOM
- This time it's serious: the original DOOM confirmed for the Evercade retro gaming platform
- DOOM crashes after running continuously for two years, caused by an integer overflow bug