Removing Denuvo Lifts Mirage Minimum FPS from 51 to 90 in Community Test [2026]

By Indie Kings | September 20, 2026

Updated September 20, 2026: Removing Denuvo and VMProtect from Assassin's Creed Mirage version 1.1.1 lifted minimum FPS from 51 to 90, a 76 percent gain, per benchmark results relayed by GameGPU. Average FPS rose 14 percent from 162 to 186 on an i7 13700K with RTX 5080, while 1 percent lows jumped from 93 to 128.

Assassins Creed Mirage benchmark comparing Denuvo protected versus DRM-free frame rates

Image: Mirage benchmark scene used for the Denuvo comparison. Credit: GameGPU.

What was tested on Mirage 1.1.1

Per GameGPU on September 19, 2026, testers compared Mirage 1.1.1 with Denuvo active against a version with DRM fully removed. Rig was an Intel i7 13700K, GeForce RTX 5080, 64GB RAM, and 4TB Samsung 990 Pro on Windows 11.

Measurements used the built-in benchmark at 1080p with standard graphics settings. That fixed scene makes averages and lows comparable across the two binaries.

GameGPU presents these as online comparative results, not a first-party Ubisoft test. Treat them as community benchmarks with a disclosed rig.

Results across average and lows

Per GameGPU, minimum FPS rose 76 percent from 51 to 90. The 1 percent low rose from 93 to 128 FPS and 0.1 percent low from 74 to 105 FPS.

Average FPS rose 14 percent from 162 to 186. Maximum was nearly flat at 232 versus 233, which shows the ceiling was GPU-bound while the floor was CPU and DRM-bound.

The pattern is smoothness, not peak speed. Rare-event stutters improved far more than the average.

Metric per GameGPU	With Denuvo	DRM-free	Gain
Minimum FPS	51	90	Plus 76 percent
1 percent low	93	128	Plus 38 percent
0.1 percent low	74	105	Plus 42 percent
Average FPS	162	186	Plus 14 percent
Maximum FPS	233	232	Flat

Why lows gain more than averages

Denuvo and VMProtect add background checks that fire during play. Per GameGPU, users note weaker CPUs would see an even bigger stability gap from that constant load.

Minimum and 0.1 percent lows capture those hitches. Averages smooth them out, which is why the average gained only 14 percent while minimums nearly doubled.

This matches prior DRM-compare history where lows move first. Frame pacing, not top speed, is where protection overhead shows.

Binary size after devirtualization

Per GameGPU, the original binary with Denuvo and VMProtect weighs 496 MB while the cleaned file is only 102 MB. Full devirtualization and protection removal account for that drop.

Size alone does not set FPS, but it signals how much wrapper code surrounded the game logic. Less resident protection means fewer checks per frame.

The 394 MB difference is specific to Mirage 1.1.1 packaging and will vary by title and protector version.

What it means for weaker CPUs

On a 13700K the floor still jumped 76 percent. Per GameGPU user notes, weaker processors should see a larger stability gap since background load eats a bigger share of fewer threads.

If you play Mirage on an older 6-core, prioritize patches and official builds. Do not seek unofficial DRM-free binaries, which carry malware and ban risks.

For buyers, the takeaway is to weigh 1 percent lows over averages when judging smoothness claims around protected launches.

Best metric here: Minimum and 0.1 percent low, not average.
Rig disclosed: 13700K plus RTX 5080 plus 64GB plus 990 Pro.
Safe path: Official patches only, no unofficial binaries.

FAQ

How much did minimum FPS improve?
From 51 to 90, plus 76 percent, per GameGPU relay of community benchmarks.

What about average FPS?
From 162 to 186, plus 14 percent, with maximum flat at 232 versus 233.

What rig was used?
Per GameGPU, i7 13700K, RTX 5080, 64GB RAM, Samsung 990 Pro 4TB, Windows 11, built-in benchmark at 1080p standard.

How big was the binary change?
Per GameGPU, 496 MB with Denuvo and VMProtect versus 102 MB cleaned.

Is this an official Ubisoft test?
No. These are online comparative results relayed by GameGPU, not first-party data.

Should I download a DRM-free exe?
No. Unofficial binaries risk malware and bans. Use official builds and judge by lows.

Bottom Line

On Mirage 1.1.1 the DRM-free binary nearly doubles minimum FPS and lifts 1 percent lows by 38 percent on a 13700K plus 5080. Averages move less, so read lows first when protection overhead is the question.