PlayableShow Details
Playable
Used a DualShock 4. Steam Input was required to make it work. After launching I had to manually select all controller binds.
Playing with VSync disabled makes the game very unstable (some levels always crash at the same point with VSync disabled, many levels unbeatable on very high framerates etc.)
I was able to 100% the game.
Tried launching it with Proton Experimental first but got a black screen. Then tried with Proton 8.0 and it launched perfectly. Plays great
please see this comment https://www.reddit.com/r/SteamDeck/comments/yr1j5k/comment/kpnnsiz/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Game is unplayable without tinkering because proton forgets to install direct X , and you have to install it manually. Other than that, runs fine.
Runs great after changing the version, first tried with other launch options but they changed the gpu it runned on without them it's fixed
Without changing versions you get the error "Your video card doesn't meet game requirements Pixel Shaders v1.1 or higher required"
if i can fix the issue with the gpu, yes but otherwise no because you see the screen like updating half on top and half on the bottom(30fps)
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
i think its using my intel graphics instead of the nvidia one
limit framerate & refresh rate
Flawless (Linux Mint, default Steam proton (8.0-3 or Experimental))
Xbox Series controller works flawlessly too.
Local co-op untested.
PROTON_LOG=1 PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1 %command%
Starting the game initially led to a grey intro screen. From there the first level could be launched by pressing Enter twice, but the characters would be invisible and all the textures would be messed up.
According to reports on the "LEGO Batman: The Videogame" page, this was due to a Vulkan problem, except the VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json given solution was not working for me.
Then I tried to switch from Vulkan to WineD3D as indicated by TCperry1 on this page (PROTON_USE_WINED3D=1), but it was still not working.
I activated Proton logs with PROTON_LOG=1, and I took a look to the log file (mine was in ~/snap/steam/common/).
Looking through the logs, I saw this error message repeated multiple times: err:d3dcompiler:compile_shader HLSL shader parsing failed.
After a little searching, I found this fix using winetricks: WINEPREFIX="/path/to/steamapps/compatdata/32330/pfx" winetricks d3dx9 d3dx9_43 d3dcompiler_43
If the winetricks command does not work, try the following:
- Remove the
/path/to/steamapps/compatdata/32330/pfx/directory (wine prefix created by proton). - Launch the game from steam again to re-create a clean version of this prefix.
- Use the winetricks command.
- Launch the game once again.
More recent versions of proton may work (I didn't try).
First level bugs out somtimes if vsync not enabled
Grey corrupted graphics on main menu. Cannot navigate. Unplayable.
Recommended settings: In-game vsync on, Deck FPS limit off
Limited the framerate to 48 FPS
Menu says "Quit to Windows" and the game is in english, while my system language is german, but I did not bother to try to change that.
Game is working great! Controller support is also great! (Uses XBOX prompts.)
The game says "Quit to Windows", but really should say "Quit to Desktop".
The game is fairly easy to get up and running with just a few tweaks. The performance is really great from my experience.
The music plays for a few seconds then loops back to the beginning.
Surprisingly the only LEGO game where I haven't been affected by the W + A + Jump issue, all the keybinds work for me. Pretty solid.
Audio loops the first second. Put "PROTON_NO_ESYNC=1 %command%" in the command line to solve.
Fullscreen improperly set to the non-default window, adjust and reverse the aspect ratio to fix.
Ensure Vsync is enabled. This isn't a proton-specific issue but many physics like stairs and walking speed completely break with it off.
Por fin he podido instalar no solo 1 mando, sino 2. Que bien!!!! He jugado con mi hija durante 1 hora.
Se arregla con las notas de los demás usuarios
Funciona, pero no detecta los mandos, lo quería para jugar con mi hija, y así no me sirve.
Escribir este comando para que el sonido funcione bien: PROTON_NO_ESYNC=1 %command%
No me detecta ningún mando
Proton 5 DID NOT WORK. I had to force it to downgrade to 3.7-8, although I haven't tested which specific version breaks.
Initially my controller would be picked up as the first and second player, but installing a better controller driver (xow, I think) and rebooting resolved this.
Can't start the game
When I click the Play button the game seems to start then immediately stop.
Disable Esync to fix audio looping issues.
Just need to disable Esync to get a perfect experience playing. DualShock 3 controller works fine (not recognized by default).
PROTON_NO_ESYNC=1 %command% to stop audio looping
Unknown(> 10 hours with Proton)Works flawless after some configuration (not out of the box): -> no sound: set launch options: PROTON_NO_ESYNC=1 %command% -> sticky feet (player fails to jump on some occasions): within game: options, graphic options, vert. synch: ON -> X-Box controller: not automatically detected, configure manually (use keyboard to select function to configure)
Unknown(> 10 hours with Proton)UnknownI´m the Ubuntu Guy I just wanted to say that in the prefix a controller (js or event) must turn off because otherwise the controller is recognized as a player 1 and 2
UnknownUnknownPlayed first level. Plays as well as any other LEGO game, Steam Controller works great but doesn't prevent screen from sleeping - have to disable screen sleep manually or bump mouse occasionally to prevent display sleep.
UnknownUnknownFix the sound loop with the startup parameters "PROTON_NO_ESYNC=1 %command%"
Unknown
