The 40fps ceiling on The Blood of Dawnwalker isn't a marketing footnote; it's a deliberate systems engineering decision that reveals how modern console titles negotiate silicon budgets, thermal envelopes. And immovable ship dates. When Eurogamer confirmed that the game will cap at 40 frames per second on PlayStation 5 - PS5 Pro. And Xbox Series X/S at launch, the immediate reaction focused on disappointment. But for senior engineers, the real story is the architecture and economics behind that number.
This article reframes the launch spec through a software engineering lens. We will look at frame-time budgets - display synchronization, GPU and CPU bottlenecks - temporal reconstruction. And the platform certification constraints that push teams to ship with a sub-60fps target. Whether you build games, distributed systems, or latency-sensitive applications, the tradeoffs here are familiar: you can't improve everything, so you pick the constraints you can live with.
Why Frame Rate Targets Are Architecture Decisions
Frame rate is often treated as a quality setting. But in production it's a non-functional requirement baked into the architecture from pre-production. A 60fps target means every frame must render, simulate,, and and present within 1667 milliseconds. A 30fps target doubles that budget to 33, while 3 ms. A 40fps target sits at 25 ms, but each of these numbers cascades through the engine: draw-call limits, physics tick rates, AI update frequency, audio buffer sizes, and network interpolation windows all shift.
In production environments, I have seen teams lock frame-rate targets before finalizing art direction because the target dictates which rendering features can survive. Real-time global illumination, dense crowd simulation, high-resolution shadow cascades,, and and ray-traced reflections all consume millisecondsIf the art vision requires those features, the engineering team has to find the frame rate that can absorb them that's exactly what appears to have happened with The Blood of Dawnwalker: the visual target and the console silicon target converged at 40fps.
Understanding the 40fps Console Target
Forty frames per second is an unusual number for console games. But it isn't arbitrary. It represents a middle ground between the cinematic smoothness of 30fps and the responsiveness of 60fps, while also aligning cleanly with 120Hz display refresh rates. On a 120Hz panel, 40fps maps to three refresh cycles per frame. Which produces consistent pacing without the judder you get from fitting 30fps into a 60Hz signal.
From a software engineering standpoint, the 25-millisecond frame budget gives developers roughly 50% more compute time per frame than 60fps. While still feeling noticeably more responsive than 30fps. That extra headroom can preserve higher-resolution textures, denser geometry, or more expensive lighting passes. And it also provides margin for worst-case scenesAs anyone who has profiled a AAA title knows, average frame time is meaningless; the 99th percentile is what ships.
Frame Pacing and Player Perception
Raw frame rate numbers can mislead. A locked 30fps game with perfect frame pacing often feels better than a variable 45fps game with erratic delivery. Frame pacing is the consistency with which frames arrive on screen. And it's governed by the scheduler, the swap chain. And the display's refresh timing. In console engines, this is usually handled by platform-specific presentation APIs such as DXGI on Xbox or the PS5's native presentation layer.
Forty frames per second on a fixed 120Hz display simplifies pacing math. Each rendered frame occupies three refresh intervals. So the player sees one new image every 25 milliseconds with minimal variance. Compare that to a 60fps-capable game that occasionally dips to 50fps on a 60Hz screen: the inconsistent cadence is more distracting than the lower average. For The Blood of Dawnwalker, capping at 40fps may be a quality-of-experience choice as much as a performance compromise.
GPU Bound vs CPU Bound Bottlenecks
Modern console titles are usually GPU-bound at higher resolutions. But CPU bottlenecks remain common in open-world or simulation-heavy games. The PS5 and Xbox Series X both use AMD Zen 2-based CPUs with eight cores, while the Series S runs a lower-clocked variant. If a game's world streaming, physics, animation. Or AI systems saturate those cores, the GPU can't help. No amount of dynamic resolution scaling will unlock 60fps if the simulation thread is the blocker.
This distinction matters for predicting post-launch patches. GPU-bound performance issues are sometimes addressable through shader optimization, draw-call batching, reduced LOD distances. Or upscalers like AMD FSR. CPU-bound issues are harder because they often require fundamental changes to game logic, threading,, and or data structuresIf The Blood of Dawnwalker is CPU-bound in dense areas, a 60fps mode may not arrive until the team rewrites significant systems render pipeline architecture
Temporal Reconstruction and Upscaling Tradeoffs
Most current-generation console games rely on temporal reconstruction or machine-learning upscaling to hit their performance targets. Technologies like Unreal Engine 5's Temporal Super Resolution, AMD FidelityFX Super Resolution. And NVIDIA DLSS reconstruct a higher-resolution image from lower-resolution render targets. These techniques can buy back 30% to 50% of GPU time, but they introduce motion artifacts, ghosting, and latency that must be tuned.
The choice to ship at 40fps rather than a reconstructed 60fps suggests the team either prioritized image fidelity over frame rate or found that the upscaling artifacts were unacceptable for this title's visual style. In production, these decisions are usually data-driven: A/B testing on reference displays, objective metrics like PSNR. And subjective review by the art director. A cap isn't always a failure to improve; sometimes it's the outcome of an optimization process that concluded 40fps native delivered the best product.
VRR, HDMI 2. 1. And Display Synchronization
Variable Refresh Rate is the hidden enabler of non-standard frame rates. HDMI 2. 1 introduced support for VRR. And both the PS5 and Xbox Series X/S add it. VRR allows the display to adjust its refresh interval to match the game's output, reducing screen tearing and stutter when frame times fluctuate. At 40fps on a VRR-capable 120Hz display, the panel can present frames at consistent 25ms intervals without the fixed-refresh compromises.
This technical reality is why 40fps modes have become more common this generation. Developers can target an intermediate frame rate without worrying about the harsh 60Hz cadence that made 30fps feel juddery on older displays. The HDMI 2. 1 specification effectively expanded the design space for console software engineers, and 40fps is one of the results. If you're debugging frame delivery, tools like Microsoft PIX and RenderDoc can visualize exactly how frames align with VRR windows.
Performance Budgeting in Game Engines
AAA game development treats performance like a budget. Every subsystem is allocated a number of milliseconds per frame: 2 ms for culling, 3 ms for shadow rendering, 4 ms for lighting, 1. 5 ms for physics, and so on. These budgets are enforced through automated profiling in continuous integration. Tools like Unreal Insights, Microsoft PIX, RAD Telemetry. And Superluminal capture timing data from devkits and flag regressions.
When a project nears certification, the team enters triage. Features that exceed budget are cut, simplified, or moved to post-launch updates. The decision to cap at 40fps likely came from this process: the team identified that the game couldn't reliably hit 60fps within quality targets before the launch window. And 30fps felt too sluggish for the combat or traversal loop. Forty frames per second was the feasible compromise that preserved the approved visual bar game performance optimization
Platform Certification and Launch Constraints
Console platform holders enforce technical certification requirements-Sony's TRC and Microsoft's XR-that cover crash rates, loading times - save behavior. And performance stability. A game does not need to hit 60fps to pass certification, but it must avoid severe frame drops, hard locks, and broken presentation. In practice, this means a stable 40fps mode is preferable to an unstable 60fps mode that would fail certification or generate refund requests.
Launch windows are also constrained by physical manufacturing, marketing spend. And contractual obligations. A studio can't delay indefinitely to chase a 60fps mode if the publisher has committed to a retail date. This is where software engineering meets project management: the team ships the best-performing stable build, then continues optimization in patches. Day-one patches, weekly hotfixes. And seasonal updates are the modern equivalent of continuous deployment for boxed software.
Lessons for Application Performance Engineering
The same principles apply outside gaming. In distributed systems, we set latency service-level objectives and make tradeoffs between consistency, availability. And cost. When a service cannot meet its latency SLO under peak load, we implement load shedding, circuit breakers, or graceful degradation rather than crashing. A 40fps cap is the rendering equivalent of a circuit breaker: it bounds the worst-case experience so the system remains stable.
Observability is the common thread. Game teams use profilers, frame-time histograms, and telemetry dashboards just as SaaS teams use Prometheus, Grafana, and distributed tracing. The lesson for senior engineers is that performance targets are negotiated, not discovered. You build telemetry, measure percentiles - understand bottlenecks. And then choose the target that satisfies users without breaking the schedule. The final number is rarely the theoretical maximum; it's the operational maximum.
Frequently Asked Questions
Why did the developers choose 40fps instead of 30fps or 60fps?
Forty frames per second offers a middle ground. It provides a 25-millisecond frame budget, which is more generous than 16. 67 ms at 60fps, while feeling noticeably smoother than 30fps. It also aligns cleanly with 120Hz displays, producing consistent frame pacing and making VRR synchronization easier.
Could a 60fps mode be added after launch?
It is possible but depends on the bottleneck. GPU-bound issues can sometimes be resolved through shader optimization, reduced rendering load,, and or upscalingCPU-bound issues in simulation, AI. Or world streaming are harder to fix without re-architecting systems. The studio has stated no 60fps mode is currently planned, suggesting the gap may be structural.
Do I need a 120Hz TV to benefit from 40fps?
A 120Hz display is ideal because 40fps divides evenly into 120Hz, giving consistent three-refresh-cycle pacing. On a standard 60Hz display, 40fps doesn't divide evenly, which can introduce judder unless Variable Refresh Rate is supported and enabled on both the console and display.
What engine is The Blood of Dawnwalker built on?
Developer Rebel Wolves hasn't publicly confirmed the engine in all detail. Though the game is built on Unreal Engine 5. UE5's Nanite virtualized geometry and Lumen global illumination are demanding features that make 60fps targets challenging on current console hardware without aggressive optimization or upscaling.
How common is a 40fps launch target in console gaming?
Forty frames per second has become more common this generation, especially for visually ambitious titles targeting quality modes on 120Hz displays. Games like Ratchet & Clank: Rift Apart and Horizon Forbidden West have offered 40fps quality modes it's a pragmatic engineering choice rather than an industry standard.
Conclusion: Performance Is Always a Negotiation
The Blood of Dawnwalker launching at 40fps on PS5, PS5 Pro. And Xbox Series X/S isn't evidence of a broken engine or poor optimization it's evidence of a team making a disciplined engineering tradeoff under real constraints, and they chose stability, visual fidelity,And a consistent cadence over a 60fps target that might have required unacceptable compromises or an extended delay.
For engineers building any real-time system, the lesson is the same: performance targets aren't ideals to be chased forever. They are contracts between the system - the user, and the business. Instrument your pipeline, measure your percentiles, understand your bottlenecks. And ship the configuration that best satisfies all three. If you want to explore how we approach performance architecture, observability. And platform engineering, contact our team or read more about console certification processes on our blog.
What do you think?
Is a stable, visually rich 40fps launch preferable to an unstable 60fps mode that might fail certification or require visual cuts players would notice?
How should platform holders evolve certification requirements to balance innovation in rendering with consumer expectations for higher frame rates?
What telemetry and observability practices from game engine profiling could most improve how your team sets and enforces latency SLOs?
.
Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today →