MHzBurglar
Published
Forcing the game to use the latest experimental build of Proton allows the opening FMV to work correctly.
In addition to some minor modifications to the back buttons and touchpads in the Steam controller config, I also changed some button assignments in the game's built-in control configuration on the settings menu.
My cloud saves briefly stopped syncing; my Steam Deck had no save data and the game said it was storing 0 kb on the cloud. I don't know if this was Proton's fault or not.
Loading my save from my desktop PC (where it was still safe and sound), saving the game to "update" the save data, and exiting the game forced it to re-sync to the cloud.
Shadows seem to greatly affect framerate.
If the shadow quality is set to low and shadow distance to near, the game will consistently get about ~57-60 fps at 1280x720, even with all other settings maxed out (texture quality on high, LOD set to far, AA and AF enabled, etc.)
Increasing shadow quality or distance to medium will immediately cause the framerate to drop to about 35fps, and worse if set to high.
The game runs well on Proton Stable 7.0-2, but the FMV videos will not play. The latest experimental build of Proton fixes the FMV issues.
Regardless of the Proton version, be sure to set shadow quality to "low" and shadow distance to "near", as shadows seem to tank the framerate. All other settings can be maxed out at 1280x720 (the game does not support 1280x800.)
export WINEDLLOVERRIDES="winhttp=n,b"; %command%
The game works flawlessly out-of-the-box.
If you want to use Memoria or other mods, you need to add the following launch option (exactly as written) in Steam in order for the mods to work correctly:
export WINEDLLOVERRIDES="winhttp=n,b"; %command%
Adding this will enable Memoria to correctly locate the folders where the extracted/modded assets are stored within the WINE prefix.
(proton 7.0.3) Title screen and File select screen work; game crashes to a black screen afterward
The game crashes to a black screen after the file select screen if the Steam Deck is running in its default 'Game Mode'. The game seems to work correctly if the Steam Deck is booted to 'Desktop Mode' and the game is launched through the 'desktop' Steam client.
The game runs perfectly on the Steam Deck with the default Proton version/settings. Just install and play!
The crash occurs on the "Planet Bomber..." cutscene and the game crashed before the cutscene could be skipped. I did not have the opportunity to test battle mode or a story mode save file last the beginning of the game.
Other users have suggested adding the launch option PROTON_USE_WIND3D=1 %command%, but that did not appear to affect anything with the latest version of the game (v2.2) and Proton 7.x.
I tried using Proton 7.0-2 official, Proton Experimental, Proton 6.3-8, and GE Proton 7-17, but the game crashed at the same spot every time.
The Windows build of the game will have no video and corrupted audio unless additional packages are installed into the prefix via ProtonTricks.
Install ProtonTricks in Desktop mode, and run the following command from the terminal:
protontricks 40800 d3dcompiler_47 xact
The Steam Deck plays the native Linux version of Super Meat Boy by default. While this version is "deck certified" and runs perfectly, it is an extremely outdated version of the game. It is the same 2010-release build as the "OG Beta" build on Windows, rather than the newer 2015 revision of the game.
In order to play the Windows version of the 2015 build on Proton, you need to force the game to use Proton Experimental or Proton 7.0-2, and make sure that you install D3Dcompiler_47 and XACT (XAudio) into the Proton Prefix usinf ProtonTricks. If these packages are not installed, the game will have no video, and the audio will corrupt/freeze the game once it gets to the title screen. With these packages installed, the game works flawlessly under Proton.
The native Linux build is completely broken on SteamOS 3.x due to a ton of missing libraries/dependencies. Unfortunately, the Steam Deck will try to install/run the native Linux version by default, and the game will not launch.
Forcing the game to install/run the Windows build through Proton works flawlessly out-of-the-box.
