
It's paper mario on linux, it works almost exactly as intended.
So sometimes pressing a button on the keyboard or moving the mouse swaps you from gamepad to m+kb controls, the only way to go back however is to completely relaunch for some reason.
Launching with wineD3D is required; if you don't, the game will crash on startup. The game performs exactly as it should with it.
PROTON_USE_WINED3D=1 %command%

Did a full playthrough with nearly zero issues, only problem was with a single NPC's voice
Vi's sister's voice would frequently glitch and produce a very harsh noise
Full playthrough with no issues

No issues, everything runs great. You might even get more if you lower to 30 and 6 or 5 watts but I didn't bother.
Dropped it to 40 frames and 8 watts

The Game used to Run, suddenly it doesn't.
PROTON_LOG=1 %command%
At first I thought that it was because the mesa package was flagged. I did an update today and the issue is still there.

A flawless experience.
There's not much to say here, as the experience is essentially flawless and performance is great. I played through the entire game with a DS4 controller, and that got picked up by the game with no problems whatsoever.
I played this on my laptop, but this is probably a fantastic game to play on your Steam Deck, since it's tailor made for controllers and performance rather well.
Vi, Lief, and Kabbu
mangohud %command%
On Steam Deck, it occasionally drops your button inputs. (This hasn't happened for any other game, so I'm reasonably certain this game is the problem).
Perfectly playable, the dropped inputs only really interfere with 1 or 2 parts of the game, but you can still 100% it despite that.
Played this on a long train ride, not a single issue over several hours of playtime.
It just works.
yup, lookin good
i had to downgrade my version of proton to an older version i only tested 4.11 and my controller started working
If your graphics card does not support vulkan, use PROTON_USE_WINED3D=1 %command%
as launch options as my previous report suggested.
Game doesn't launch/open without putting "PROTON_USE_WINED3D=1 %command%" in the launch options. May need to open winecfg and change windows version to Windows 10, then add built-in d3d12 through the libraries menu, but not sure if this is correlated - try this if it still doesn't launch. Everything works perfectly otherwise - including cloud saves.
Not having this Option enabled immediately opens what appears to be a crash handler
Works out of the box without any modifications needed.
#Works out of the box with any >5.0 Proton base or Glorious Eggroll
Experienced weird graphics a few days ago but an update of mesa-drivers solved it.