Assassin’s Creed Mirage on iPad Pro M5: what a real-world test reveals about performance, settings, and stutter
A new hands-on test puts Assassin’s Creed Mirage through its paces on Apple’s latest iPad Pro with the M5 chip, and the results are a reality check for anyone hoping for console-like performance. While the game can look sharp and holds a steady 30 frames per second, persistent shader compilation stutter, a hard 30 FPS cap, and aggressive internal resolution scaling limit the experience across Apple’s M-series lineup.
Here’s what the tester found
– Graphics options allow resolution scaling up to 100% and presets up to High. The game is locked to 30 FPS.
– On the M5 iPad Pro at 100% resolution and High settings, the frame rate stayed at 30 FPS, but gameplay frequently stuttered and froze thanks to shaders compiling on the fly. The experience was described as awful despite the stable frame counter.
– The game targets a resolution of 2420 × 1362 but actually renders internally at 1210 × 682 because a fixed 50% internal scaling is always active. You can’t disable or change this background scaler, so even when you select the iPad’s native resolution, the engine still renders at a much lower internal resolution.
– GPU frame times hovered around 20 ms throughout. Since 60 FPS requires about 16.7 ms per frame, the current performance headroom suggests that even if the 30 FPS cap were lifted, the game would still struggle to reach 60 FPS.
– Reducing the visible resolution scale to 50% effectively rendered at 1210 × 834 and, after MetalFX upscaling, roughly 606 × 340 internally. Even then, frame times stayed around 20 ms, indicating the bottleneck isn’t solved by cutting resolution alone.
How the M5 compares to M4 and M1
– Visual parity between M4 and M5: There’s no noticeable image quality improvement for Mirage when moving from the M4 to the M5 iPad Pro. Both devices are locked to 30 FPS and both suffer from similar shader compilation stutters.
– Slight GPU timing gains on M5: A closer look at Apple’s Metal HUD showed the M5’s GPU frame times were 5–10 ms lower than on the M4. That’s a meaningful architectural gain on paper, but it doesn’t translate into a smoother experience because of the game’s cap, internal scaling behavior, and shader-related hitches.
– M1 trails behind: On the M1 iPad Pro, maintaining a consistent 30 FPS requires dropping to a much lower resolution, and the hit to image quality is obvious. Among the three, the M1 is the least ideal device for this title.
Why the experience feels choppy despite 30 FPS
Shader compilation stutter is the main culprit. As the game encounters new effects and materials, it compiles shaders during gameplay, causing sudden spikes and micro-freezes. Those hitches are disruptive enough that a locked 30 FPS doesn’t feel smooth. Pair that with fixed 50% internal scaling and consistently high GPU frame times, and you have a title that simply isn’t taking full advantage of Apple’s latest mobile silicon—yet.
What needs to change
The test points to one clear conclusion: Assassin’s Creed Mirage needs significant optimization on iPadOS to fully utilize the M-series chips. Improvements could include:
– Precompiled or cached shaders to eliminate in-game compilation stutter
– More flexible internal resolution controls, with the option to disable the forced 50% scaler
– Better frame pacing and the possibility of a 60 FPS mode if performance budgets allow
Other games tested
In the same session, Hitman: World of Assassination and Divinity: Original Sin 2 were also evaluated. While details weren’t the focus of this test summary, the standout takeaway is that Mirage, specifically, faces the heaviest constraints right now due to its rendering pipeline and optimization state.
Bottom line for gamers
– Expect a capped 30 FPS across M1, M4, and M5 iPad Pro models in Assassin’s Creed Mirage.
– Even on M5, stutters from shader compilation can make gameplay feel rough despite a steady frame counter.
– Lowering the resolution scale doesn’t fix the core issues, which stem from the game’s internal scaling and optimization rather than raw GPU power.
– Without updates from the developer, a true 60 FPS experience on current iPad Pro hardware looks unlikely.
If you’re considering an iPad Pro for AAA gaming and Mirage is high on your playlist, the M5 does offer slightly better GPU timings than the M4, but the overall experience is currently limited by the game itself. For now, this is a showcase of how much optimization matters—even when the hardware is more than capable on paper.
