


Steam overlay is borked
Works great NATIVELY; but running with proton means you HAVE to use Vulkan or you'll get graphical glitches and very dim lighting. Native doesn't have those issues Couldn't get proton to run with vulkan on my end though
Game would drop frames about every 45 seconds only while docked.
Click on the game, then the cog to open up properties, go to betas and select sdl3 testing. you can launch the game and play docked without any issue now, enjoy.
Runs natively and without issues

Works Perfectly.
Celeste is peak gaming :3
Had some stuttering problems running native, swapped to proton and they were fixed, then swapped back and for some reason they were gone :D

in addition to a perfect full screen, the window leaks over to another monitor

Some very light tinkering (opening the game properties in Steam and selecting the SDL3 beta build of the game) required for the game to launch on some systems, at least for as long as the SDL3 build isn't the default one. It is likely to become the default in the future, fixing this issue.

everest is installed
KDE PLasma has a strange issue using pure vanilla with a gap at the bottom where the taskbar would be
patch the binary using execstack -s path/to/celeste/binary
execstack is an AUR package

Latest GCC update on arch broke the executable, need to install execstack from aur and run execstack -s Celeste.bin.x86_64 and execstack -s Celeste.bin.x86 in game folder

Works out of the box
No tinkering necessary

Native not working, using proton.

Works great
Use proton to fix steam overlay

performs basically identically to the windows version, weird keyboard controls and all! :)
ran using steam via crostini (so in a VM) as chromeOS flex does not support the native app

game works great natively
black bars appear after alt+tabbing the game on wayland. alt+tabbing couple of times or tourning fullscreen off and on fixes the issue
10/10

Game is currently broken for me, used to work on that system.
Tried running the game both natively and with Proton.
Running sway. Native crashed on launch without ever bringing up a game window and opens a text editor with crash logs. The logs seem unhelpful to the user. Proton opened a fullscreen white window that froze my desktop for a few seconds, then turned black and nothing else happened, no sound playing, no game, etc.

Native support and works right out of the box.
Celeste works right out of the box because it has native support. I am able to play with my controller. The PICO-8/Classic version works. In a worse scenario, you can run the Windows version with Proton or Wine, but I haven't dealt with that issue.
Runs natively and smoothly

Funciona perfecto y sin inconvenientes

Works flawlessly
If you're on Wayland, the game runs under Xwayland. Works great regardless.

Excellent platformer with a stellar Linux port
The way my Xbox controller's joystick was bound to the 8 possible dashing directions felt off. May just be how the game is though

works very well, out of the box!!
Works right out of the box.

I played it with a leverless controller and it worked perfectly fine.

Ran perfectly fine.
Zero issues.

Steam overlays didn't work when running natively. They showed up as empty gray boxes. Switched to proton and it worked.

Great game and great native experience
Worked amazingly well on native. Had no problems. Controller detection was flawless and installing mods through everest worked as well.

Runs perfectly with no tweaks required.
I also ran this on a Thinkpad X200 (upgraded with nearly-dead SATA 2.5" SSD and 8GB of RAM from an old MacBook) running OpenSUSE Tumbleweed and it worked near-perfectly there (OpenGL 2.1 is old) - only issues on that device were that parts of the menu felt like they had lower framerates (probably due to the graphical effects the menu uses since this did not persist into gameplay) and also that the steam client is very resource-intensive, especially when its main window is being rendered (electron app moment).

FNA3D_FORCE_DRIVER=OpenGL %command%
Epic Game Store version of game, installed onto steam deck via Junk Store.
To echo a previous user, without the above launch command the non-UI colors are completely wrong. With the launch command it works perfectly.
Add this launch command BEFORE the existing one (from the Junk Store install), separated by a space.

/gldevice:Vulkan
I used Standard-Settings in Steam. I have to set "/gldevice:Vulkan" as Start-Parameter, otherwise it's unreliable if the Game starts. If the Game starts without this Parameter, then it mostly runs fine, except for Chapter 5 (Mirror-Temple) where a graphical Glitch occured. I didn't test the Steam-Overlay without that Parameter tho.
For some unknown reason, the Game won't start the Native Linux-Version for me anymore. But in Proton and with the given Start-Parameter, everything runs.

/gldevice:Vulkan
Steam Overlay doesn't display correctly when it's not specified that the game should use Vulkan, at least when using wayland.

Runs perfectly!!
Really happy its native so performance is perfect and is made for linux overall.

Lighting glitch in Chapter 5 at Proton 8.0.5, Heavy graphical artifact at Proton 9.0-2, could be fixed by switching into Native version
Activating Steam Input.
On Native version, can be happen minor several performance drop at specific chapter.
Maybe Nvidia GPU Driver issue, considering most of other player and Steam Deck have no issue. F- you Nvidia.

I tried useing it through proton and got a major grafical bug where the screen showed up red, but it started working properly once i swiched to the native version.
graphical errors runing through proton
the comunity mod loder works great just if you use arch you have to download olympus witch works really well
works as if it was native

Requires launching the right executable file from the game files instead of launching it through Steam because the .sh file is broken.
Needed to launch the right executable file from the game's directory instead of launching it through Steam because the .sh file assumes im on the wrong architecture
lighting is broken on proton, also the .sh file actually did work one time idk why doe lul