Elta: Defy All Gods Runs at 40 FPS on Steam Deck — Barely

The performance numbers in this Elta: Defy All Gods demo preview tell a more interesting story than the combat does. Low preset. Roughly 60% resolution scale. A 40 FPS cap applied in SteamOS. That isn’t a game running comfortably on Valve’s hardware — it’s a game that’s been negotiated down to fit, and every one of those dials is a decision someone at the studio made about what the deck can survive. For a demo launching October 1, that profile is the thing handheld players should actually read, not the slow-motion finishers.

The combat itself is legitimately the hook. The preview describes shader-driven slo-mo finishers, an Arkham-style flow of leaping between enemies, and a movement set with jump, double-jump, mid-air dash, dodge, and wall-run. That’s a generous, non-restrictive moveset — exactly what a 3D Metroidvania needs before it starts locking abilities behind progression. The weak spot is everything around it: no dialogue, a silent protagonist, and a story the demo barely gestures at. So you’re buying in on game feel, not narrative, at least for now.

Shader Compilation on Every New Area Is the Real Deck Killer

The demo reportedly holds 40 FPS at a 60% resolution scale, with heavy combat dipping into the mid-30s. That’s survivable — slow-mo finishers hide framerate dents better than most genres, and a 40 FPS target in SteamOS is a reasonable compromise on an 800p panel. The problem is what happens when you cross into a new zone: the game appears to compile shaders on entry, spiking CPU usage and cratering the framerate for a stretch.

On desktop that’s an annoyance. On a handheld it’s a structural issue. Shader compilation triggers at exactly the moments portable players hit hardest — resuming from suspend, fast-traveling after a short session, ducking back in on a commute. It also burns battery during a load that isn’t even gameplay. This isn’t a game that needs a re-optimization pass so much as a menu option: pre-compile shaders up front, or let the player eat one long hitch instead of a dozen short ones. It’s the same single-setting fix that made DragonSword: Awakening run smoothly on Deck.

A 15-Second Save Screen Punishes How Handheld Players Actually Play

The other friction point is the save. The demo’s saving screen reportedly runs 10-15 seconds — an eternity in 2026, when most games write state invisibly. Handheld play is built on interruption: five minutes before a train stop, ten before a meeting, a quick checkpoint dive before bed. A save that stalls the screen for fifteen seconds breaks that rhythm every single time, and it’s the kind of thing that compounds the more you play in short bursts rather than long sittings.

The same critique applies to the invisible walls fencing off ostensibly open levels. For a Metroidvania, exploration is the contract — arbitrary gating reads as a compromise when the whole pitch is a world you learn and re-traverse, the same promise Mariachi Legends is carrying into 2027. That’s a design call, not a Deck problem, but it nags harder on a portable screen where retreading the same corridor is what most sessions look like. My call: grab the demo when it drops October 1 and confirm the shader stutter and save times for yourself before committing. If both get addressed, this is a genuinely good Deck Metroidvania at 40 FPS. If they don’t, it’s a game you’ll want to play docked, not on the couch.