UnsupportedShow Details
Unknown
Works perfectly out of the box!
No tinkering needed, runs smoothly and without any lags, actually more stable than on Windows.
The game is really fun. There are loads of items to find and it's really cool being in a fully lego world.
It's hard to see what the characters want sometimes as they only show icons and not text and the icon is quite small. It really helps looking up the quests and characters on fandom wiki for more info.
Sometimes the lighting seems to flash on the terrain. But otherwise it's been running fine.
Works pretty well out of the box, just did some tweaks to improve battery life and solve a mild flickering issue
The game can reach 90 FPS, but depending on the world/zone it will drop to the mid 40s. I prefer to set the TDP at 8W and cap the frame rate at 45; this way battery life is pretty decent, the frame rate is more stable and the game still feels pretty smooth.
Video settings:
- Texture Quality: High
Effects settings:
- FSAA: On
- Shadow Quality: Low --- Note: if shadow quality is set higher than "Low" there is pretty noticeable flickering.
- Depth of Field: Off
- Motion Blur: Off
- Ambient Occlusion: On
Landscape settings (only available when in-game):
- Landscape Draw Distance: Higher
- Landscape Transparency: On
- Landscape Stud Quality: Very High
- Landscape Shadows: On
Runs great
No problems in multiplayer. I hosted a Server and a friend was able to join from his Windows PC
No issues
Works fine out of the box
Given the massive bug, you would have to be fine with regular restarts. You can do it but life's too short. You'll play other games instead.
Performance is great for some time, if you fiddle with the detail levels. 30 fps on Steam Deck is fine for this game. Problem kicks in after a while playing, especially if you are in a world with lots of 'biomes', or environments. It happens even quicker, it seems, if you're flying around fast. However you play though eventually everything will suddenly slow to a crawl. Textures start to pop in very severely. The game will then become unplayable until you exit and reload. When this state occurs, there doesn't seem to be excessive load on any CPU cores or excessive gpu usage. The ram and vram usage seems fine. This happens on an internal 512gig SSD with lots of free space so it isn't a storage issue. This game has always had these tendencies on Windows, but was eventually made to work by the devs before it was abandoned. On Steam OS the problem is far worse and remains to this day, it seems.
Every positive reporter here hasn't played it for very long on the Steam Deck before posting I have to assume, as it doesn't take too much play to trigger the enviable massive slowdown bug. If you can find a tweak to solve this, please publish here. Shame, because the game runs well, until it hits the wall and tanks. Note that I have put huge hours into this game on desktop PC via Windows (privacy settings mask that on here) and have it almost 100% complete but cannot do the same on the Steam Deck despite this looking promising when it is first run. The devs are long gone, so only community tweaking can save this game now. Any takers?
sometimes a slight crack in the narrator
Runs flawlessly out of the box
Initially I experienced a few performance hiccups in larger worlds, resolved by switching from DirectX-11 to 9 in game's settings - not necessary but recommended if your GPU is struggling
The game ran absolutely fine. I'd even say better then under Windows.
Crashed once after an hour of playtime. Might be unrelated though.
In order to fix the keyboard not recognized after opening the menu or pressing alt+tab, you need to disable steam overlay.
In order to make the keyboard work, all you need to do is disable steam overlay after that it will work as it should.
It doesn't boot with 5.13-1
To fix the keyboard not recognized after opening the menu, run the command: WINEPREFIX=$HOME/.steam/steam/steamapps/compatdata/332310/pfx/ winecfg, go to the Graphics section, enable Emulate a virtual desktop (and set the resolution to the real resolution of your normal screen).
Works perfectly out of the box, except a minor keyboard issue.
After opening the Esc-menu, the keyboard is no longer recognized. Controller works perfectly. (It's a good idea to play Lego games with controller anyways in general.)
game crashes quickly
the game crashes very early on on steam proton on linux
OOTB No issues.
Did not work with Steam controller but keyboard & mouse were fine.
Runs as good as native windows without DXVK or other tweaks.
Works perfectly fine out of the box on Proton with DXVK.
Runs perfectly out of the box. No issues
works but no tutorials are played ( chrash) , i think as m apu isnt fully supported its a matter of raw power...
Native-like, runs out of the box. No loading issues.
It starts, but exits without Wine D3d11. With it it works just fine using a Steam controller.
Better run in native than in steam runtime. Running in steam runtime is causing loading stuck when traveling between planets.
Game loads fine. The first planet is playable but when you take the rocket to the next planet it fails loading. Flying to the space endlessly
From a brief test, the graphics work fine with only occasional stuttering, but the audio is pretty broken -- background music plays fine, but sound effects don't play at all, and sound in some cutscenes is extremely quiet to the point of being inaudible.
since installed it again it works out of the box...no issues
Seems that nothing will happen when you start it out of the box, but after a few minutes (went away to cook coffee) it starts and is playable, also with 2players. After aprox. 1h no issues detected. Tested again: time between "startclick" and programstart again abou 15min. Next test wont work after 30min...could not reconstruct why or why not.
