Unknown
Forced Proton usage
Native build did not detect controller - force running with Proton got it working
Le jeu fonctionne sans aucun problème
- GPU 800MHz
- CPU 7W
It seems like my previous issues were hardware-related; for some reason this game was particularly good at crashing my old Deck. After RMA replacement, it is working fine so far.
If vsync is disabled and the Deck's 60 FPS cap is enabled, the game will run at 60 FPS but not smooth at all - feels more like a stuttery 30. Either the Deck's FPS cap needs to be disabled or vsync needs to be enabled for proper performance.
Frequently hangs. Took 3 tries to get past the first level then it hung in the 2nd.
Native wouldn't recognize my Xbox Series X controller, even when disabling Steam Input. Proton (I used 7.0-2 and 3.7-8, both work the same) picks up my controller immediately, and offers identical performance.
If you use a keyboard, the native version should be fine.
6.15-GE-1 GloriousEggroll
The game has a permanent micro ghosting issue that I wasn't able to fix with proton options. Tried forced triple buffering, zero latency and vsync. It's present in Windows as well. I believe it's due to game being too zoomed in but not sure.
Controllers don't work in native Linux but with Proton work as expected, at least with DS4.
Entirely playable, unless you're using bluetooth headphones.
There was a significant audio delay (couple hundred ms) when using bluetooth headphones (tested with 2 different headphones). A bummer given this is a rhythm-based game. No delay when playing over the speakers or wired headphones. I don't think this is an issue with Proton, since the native Linux version also has this problem, as well as the Windows version running natively (on Windows).
Tested using a Dualshock 3 controller -- input & vibrations work flawlessly, though obviously the game displays xbox buttons.
