Steam Deck · Guides

LEGO Batman: Legacy of the Dark Knight on Steam Deck: Verified, but Target 30 FPS

Summary

Treat LEGO Batman: Legacy of the Dark Knight as a 30 FPS Steam Deck game. Start with Low settings, FSR Balanced, Frame Generation off, and a 30 FPS cap; test open-world Gotham, where traversal and combat are heavier.

Published Updated 15 sourcesBy John Hentrich

Quick verdict

Target 30 FPS on Steam Deck. Low settings, FSR Balanced, Frame Generation off, and a 30 FPS cap are a reasonable starting point from the published tests and owner reports below. Expect dips in Gotham, especially while driving, gliding, fighting, or playing co-op.

This is a source-based recommendation, not our own benchmark or a promise of a locked frame rate. If you need consistent 60 FPS, the available Deck evidence does not support buying it for that target.

Keep the default Verified runtime to start; SteamDB's compatibility record identifies Proton 10.0-4. Use the following as a tuning baseline, not a single configuration tested by every source.

SettingStarting point
SteamOS frame cap / refresh30 FPS / 60 Hz
TDP and CPU/GPU clocksAuto
Resolution1280x800
Graphics presetLow
UpscalingFSR Balanced
Frame GenerationOff
Material QualityLow
Distance Field Ambient OcclusionOff
Motion blurOff or Low, to preference

Fullscreen or Borderless can be tested if one behaves poorly. HDR is optional: early hands-on coverage found no major performance hit, but that was not a full-game test.

Test a busy Gotham traversal route before raising quality. FSR Performance is a softer-image option to test if Balanced struggles; FSR Quality may suit lighter story missions, with less headroom outdoors. Neither change guarantees steady frame times.

Keep Frame Generation off for the initial test. Owners disagree about its usefulness, with some reporting smoother play and others reporting delay or motion artifacts.

What Valve confirms

Steam's compatibility metadata, mirrored through SteamDB, marks the game Verified with a May 12, 2026 test timestamp. The checklist covers working default controls, matching Deck button icons, legible text, and a performant default graphics configuration. It does not promise 60 FPS.

Valve flags an external-controller caveat: on Deck or SteamOS, the game may not default to a connected Bluetooth or USB pad. Switch the active controller through the Quick Access Menu if needed.

SteamDB detects FSR, XeSS, DLSS, Frame Generation, and NVIDIA Reflex support. These are game-wide features, not confirmation that every option applies to Deck. The minimum PC target is Low / 1080p / 30 FPS with Balanced FSR or XeSS and Frame Generation; the recommended target is Medium / 1440p / 60 FPS with Quality upscaling and Frame Generation. Those desktop targets are not Deck benchmarks.

Published Deck tests

SteamDeckHQ's launch-week hands-on found contained story levels smoother than open-world Gotham, which generally ran at 30 FPS or higher in its opening-hours test. Defaults were mostly Low with upscaling. The site also reported 16:10 support without black bars and no apparent HDR performance penalty. Later areas were outside that test's scope.

TwistedVoxel's May 21 guide used 1280x800, V-Sync off, an unlimited in-game FPS limit, FSR Balanced, and Low lighting, shadows, textures, reflections, post-processing, and population. Material Quality was Low and Distance Field Ambient Occlusion was off. It reported mostly above 30 FPS, with occasional dips into the high 20s. Our suggested 30 FPS cap is an editorial tuning choice, not the outlet's in-game limit.

TechRadar played on PC and handheld, including Deck, and needed substantial settings cuts. It also reported wall glitches and overworld bugs, but supplied no Deck FPS figures.

PC Gamer described settings cuts and severe boss-QTE slowdowns on desktop. Its review header lists Deck Verified, but its performance findings are not a Deck test.

Why owner experiences differ

The reports below cover different settings and areas, often without identifying LCD or OLED hardware. They should not be averaged into one benchmark.

  • In a detailed r/SteamDeck thread, one owner reported 30 FPS with FSR Balanced and Frame Generation; another disliked the delay and motion. A third reported roughly 40–50 FPS at medium settings outside combat, with combat dips. Co-op and the first area drew additional complaints.
  • A separate help thread described about 30 FPS in enclosed levels at Low, with driving and gliding struggling outdoors.
  • A Steam Community discussion included a positive opening-hours report and a different owner's 30 FPS profile: 1280x800, no upscaling or Frame Generation, Epic Textures and LEGO Mesh, Low Material Quality, and Near view / streaming distance.
  • A negative Steam thread reported 20–30 FPS at Low with FSR, poor image quality, and no benefit from Lossless Scaling. A reply disagreed. Neither account establishes a universal baseline.

Why keep Material Quality low?

A Steam Community post reported a desktop gain from around 40 FPS to 60+ when lowering Material Quality below Epic. That is not a measured Deck gain. Low is nevertheless a sensible starting point because both TwistedVoxel's Deck test and the community 30 FPS profile used it.

Launch problems and runtime changes

Black screen after changing graphics settings: a Reddit thread describes successful first launches followed by black screens after FSR changes and enabling Frame Generation. One commenter reported success with Proton Experimental. Treat that as an unconfirmed workaround, not a general fix.

Before changing Proton, close the game and back up local saves; cloud support alone does not prove they have synced. If you test Experimental, change only that setting, record the result, and avoid cycling through versions.

CodeFusion / Denuvo errors: SteamDB identifies Denuvo Anti-Tamper, and a Deck launch-error report shows a CodeFusion error without a confirmed fix. Keep the exact error for support rather than assuming it is another Proton problem.

Battery, briefly

The cited tests provide no reliable battery figure. If you lower TDP manually, do it gradually and retest Gotham traversal for stutter.