Playing Lego Batman: The Legacy of the Dark Knight on Steam Deck – My Honest Performance Review

There is always a special kind of thrill when a highly anticipated game drops into advanced access. Recently, I got my hands on Lego Batman: The Legacy of the Dark Knight, and I was immediately curious about one major thing: how does it run on our favorite portable handhelds? Surprisingly, the game snagged that coveted Steam Deck Verified status well ahead of its official release. Naturally, as someone who loves pushing portable hardware to its limits, I had to put it through its paces to see if it actually deserves that green checkmark.

Spoiler alert: I actually think it does deserve it this time around. However, if you are planning to dive into Gotham’s blocky underworld, you should know that the default settings are a little bit strange, and the overall performance can be wildly inconsistent. Let me walk you through my personal experience, the technical quirks I encountered, and the absolute best settings to get this game running smoothly.

The Out-of-the-Box Experience

When you first boot up Lego Batman: The Legacy of the Dark Knight, you will notice that the game defaults to an unlimited frame rate with AMD’s FSR (FidelityFX Super Resolution) set to Balanced, and pretty much all the graphical sliders pushed down to Low. Honestly, this is exactly what you would expect for a demanding Unreal Engine 5 title in 2026. Modern gaming engines are incredibly heavy, and portable devices have to work incredibly hard to keep up with the complex lighting and geometry.

Now, I know there are plenty of gamers out there who will immediately start tweaking, screaming about lossless scaling, various upscalers, and a whole bunch of other technical jargon. But let me save you some time: you really do not need to overcomplicate things with this specific title. The out-of-the-box settings are a decent starting point, but trying to heavily modify them beyond a few key tweaks will not yield the massive performance boosts you might be hoping for.

The Frame Rate Capping Disaster

Here is where things get genuinely bizarre. My first instinct, like many handheld gamers trying to save precious battery life, was to cap the frame rate. Usually, locking a game to 30 FPS or 40 FPS provides a much smoother, more consistent experience on a portable device, while keeping temperatures and battery drain in check. In this game, however, capping the frame rate actually causes significantly more problems than it solves.

While capping it does save a tiny bit of battery in certain quiet, indoor scenarios, the overall way this game manages power is baffling. How Lego Batman manages to still chew through all your available wattage, even with a strict frame rate cap, is completely beyond me. Ah, the efficiencies of Unreal Engine 5 at its finest, right? You just have to laugh at the irony of a game running at 30 FPS but drawing the power of a much higher frame rate.

If you do decide to cap the frame rate, it absolutely ruins the performance. This becomes painfully obvious the moment you hop into a Bat-vehicle and start driving around the open city. With a 30 FPS cap engaged, the gameplay becomes incredibly stuttery. I watched my performance overlay in real-time, and the power draw was a complete rollercoaster. In some quiet areas, the wattage would drop as low as 6 watts. But the second I started driving through the streets, it would violently spike back up to 19 or 20 watts—again, all while locked at a measly 30 FPS. It is absolutely insane and makes for a frustratingly jarring experience that pulls you right out of the immersion.

My Recommended Settings for the Best Experience

Since capping the frame rate is essentially a trap, what should you do? After hours of tinkering and exploring the city, I found the sweet spot. First and foremost, leave that frame rate unlimited. If the game is going to demand maximum wattage and drain your battery anyway, you might as well get the extra frames to show for it. It makes the combat and traversal feel much more responsive.

Secondly, let us talk about upscaling. Out of the box, FSR on Balanced is fine, but I found it to be a little too fuzzy for my liking. It takes away from the crisp, vibrant, plastic aesthetic that makes Lego games so visually charming. Instead, I highly recommend switching the upscaler to Intel XeSS and setting it to Quality mode. When I made this switch, the game instantly looked noticeably better. We lose that annoying fuzziness, the edges of the Lego bricks become sharper, and the best part? We maintain the exact same performance level.

If you prefer AMD’s FSR, it is still a decent fallback, but based on my extensive testing, XeSS Quality is the clear winner here. Any other aggressive upscaling methods just do not make a huge difference, so keep it simple and stick to XeSS.

Final Thoughts and Expected Performance

So, what can you actually expect when running my recommended setup of XeSS Quality, Low graphics settings, and an unlimited frame rate? In my playthrough, I consistently hit between 40 and 60 frames per second. The exact number really depends on what specific area of Gotham you are exploring and how much of the map the game is trying to load in at any given time. Indoor levels tend to hover closer to that 60 FPS mark, while tearing down the streets in the Batmobile will drop you closer to 40 FPS.

Despite the weird power management and the stuttering issues associated with frame caps, Lego Batman: The Legacy of the Dark Knight is a remarkably fun experience on a portable setup. Navigating its quirks just takes a little bit of patience and the right settings tweaks. I am having an absolute blast exploring the city, and once you get past the initial setup, the classic, addictive gameplay loop shines through brilliantly.

Whether you are jumping in right now during advanced access or waiting for a future sale, I hope these insights help you get the most out of your crime-fighting adventure. Happy gaming, and remember: sometimes, it is best to just let the frame rate fly and enjoy the ride!