Facepalm
Published
gamemoderun %command%
Works perfectly. Just make sure you have Proton's EasyAntiCheat Runtime installed. It should be in your library.
The only reason I use gamemoderun is since I have a script configured for it to toggle FreeSync on or off. It should not be necessary otherwise. Launching the game the first time triggers a really long shader compilation step before the game launches (like 20 minutes). You can skip it, but after waiting for that I had literally zero shader hitches or similar, even without downloading the shader cache from reddit.
Works perfectly
Works flawlessly, even trans-atlantic.
With the AMDVLK drivers the game stuttered a lot with DX12, but not with DX11. But DX11 had rendering artifacts instead. After switching to the RADV drivers the game works flawlessly in DX12 mode.
FNA3D_FORCE_DRIVER=OpenGL %command%
I own Celeste on a non-steam platform, so I added it as a non-steam game. Without the launch command the non-UI colors were completely wrong. With the launch command it works perfectly.
Some insane crackling when certain sounds play. However, I managed to fix it entirely by applying the same fix as is often recommended on Windows for this game: Switching the rate of the audio output to 96,000 Hz.
Huge pain to figure out how to do these days (varies per distro/version), but I've had absolutely zero audio problems since.
The game closed immediately until I disabled by second monitor.
Works great
The first session I crashed after every single mission, without fail. Since then I've been disabling my second monitor and it has not happened again. Not sure if that was what fixed it, but worth trying if you also crash after completing missions.
The game didn't launch at all in proton 5.13, but works perfectly in 6.3.
Crashes somewhat often
The game works, but crashes often enough that it's not an overly enjoyable experience.
The game window appears completely black on launch, and has to be force killed.
Perf is a bit rough but otherwise seems to work fine
Changing the resolution scale slider causes some artifacts that may or may not persist after closing the settings screen.
Performance is tolerable, but just barely.
Not sure why everyone else with AMD cards are having issues. For me it works just fine with RADV. I don't have AMDVLK installed at all (32-bit or 64-bit) however, maybe that's the difference? My specs on the right are up-to-date. I did have one issue where the game refused to launch and nothing showed up after clicking play. I managed to resolve it by deleting the game's compatdata folder. Hasn't happened again but maybe it will. Steam has also started verifying files twice as I've exited the game. Not sure what's caused it.
Seems to work well
No tinkering needed as of Proton 8. I did have a crash or two, but my brother playing in Windows did as well, so it's probably beta stability issues rather than Proton ones.
Needs some manual cfg file changes, runs excellent after that. Screenshot capturing does not work.
SDL_VIDEODRIVER= %command%
Despite running in Proton, the game attempts to use the wayland SDL backend since my SDL_VIDEODRIVER environment variable is set to wayland. Which obviously doesn't work since it's a Windows executable. So I had to tweak the command line to unset that variable.
Works great
If your computer can handle it, do yourself a favor and disable FSR2. Even when set to prefer Quality, the game looks so much worse than when disabled. Especially people's faces/hair.
SDL_VIDEODRIVER= %command%
Since this game uses SDL but does not support wayland, I had to update the launch command to unset the environment variable that makes SDL use wayland. Without that it didn't work either natively or through proton.
Works perfectly after the first 5-10 min.
Some stuttering in the first cutscene, and while side scrolling for the first 5-10 min. Smooth as butter after that.
Runs great so far
The game generally runs superbly. In the mall with Junpei early in the game however (maybe 20-30 min in), the frame rate dropped quite significantly. But I've only seen it in that one place, and I don't know if it will still be bad once the game opens up a bit. It was such a short scene that it's barely worth mentioning, but it did happen nonetheless.
I've only played one hour so far, but it has run great in that one hour with a generally rock solid 120 FPS (frame cap).
Mostly runs fine
FPS drops very noticeably around story islands, from 120140 to 6070.
Won't launch without proton experimental
The game crashed when the co-op partner joined.
Fails to launch
Despite the other reports, changing the launch command did not cause the game to work for me. Regardless of proton version.
Works perfectly
Works perfectly in co-op, did not try competitive.
As of Proton 8, this works for me out of the box. It did not in Proton 7. I played through the entire campaign in co-op without problems.
Works perfectly
On the Steam Deck I had the same issue others are having, with movies showing as static colored textures instead. Even with Proton Experimental. On my PC everything works perfectly - including said movies - without any tinkering. Just using Proton 7.0-2.
No online
Requires dotnet48, which doesn't work with proton 5.13 or above. After selecting proton 5.9 and installing dotnet48 vcrun2015 faudio d3dcompiler_47 with protontricks the game launches, but online multiplayer doesn't work at all.
The game often insists on starting on my second monitor and is impossible to move to my primary monitor, it just moves back. I have to switch to windowed mode and then fullscreen it with my window manager instead when that happens. Other times it will start but only let my cursor reach a quarter of the window. When that happens it can be unborked by some combination of pressing Alt+Enter a few times, resizing the window, and fullscreening it in the window manager. But once it's sorted it's fine for the rest of that session.
Proton 7.0.2 had frequent irregular frame pacing. Switching to experimental made it go away.
Works perfectly
I've played through this game twice, and not had a single problem. Even with mods installed.
Runs really poorly
The game runs extremely poorly. Not sure if it's due to Proton or if the game is just that unoptimized, but some areas run as low as 15 FPS. Which seems really absurd for this level of graphics on this hardware. Other games run fine though, so it's not impossible that it's the game.
I can't recommend playing it like this, regardless of whether it's due to the game or due to Proton.
You could probably save some battery with some tweaking, since it's not a very graphically demanding game.
No issues with proton 8
I was completely unable to even launch the native version. It just closed immediately. After setting it to use Proton instead it ran fine.
Two or three times during the playthrough I got stuck on a loading screen, with no way out but to kill the game and restart it. Each time it had saved during the loading screen however, and I loaded back in on the other side of it. Not a huge deal, just a minor annoyance.
Works fine
After playing for a few hours some sound effects can get up to a few seconds out of sync. You demolish a building and don't hear the sound until way later. Not sure if it's a problem with the game.
I could not run the native version. It started, but no window appeared or anything. Possibly due to using wayland? But I've had no issues after switching Steam to using Proton instead.
I set the refresh rate to 40 Hz and enabled half rate saving to save on battery. Neither option really matters much visually for this game, but extended my battery life to 6-7 hours of active play.
Can't connect to the voice chat server. We used discord instead.
Crashes as soon as you pick a table. Steam reviews suggest it's an issue with AMD cards on Windows too and that the developers haven't been rushing to get it fixed (it's been broken for months).
gamemoderun %command%
I've played this for ~90 hrs, exclusively on Linux, and almost all of it in online multiplayer. The only reason I run it through gamemoderun is since I have gamemode configured to turn adaptive sync on/off. Works perfectly without it as well.
