UnsupportedShow Details
Unknown
Controller problems seem to be tied to game engine (Construct, more particularly to NW.js powering it). In my case it doesn't help, that the controller itself is a generic off-brand (although it worked flawlessly in every (aside from one, and also using the web technology) other game otherwise).
Text in the game was mostly invisible (including options menu), presumably due to a missing font.
Did a vim search and replace in package.nw/language_en.json
1,%s/"text": "\([^"]*\)/"text": "[font=Commodore Rounded v1.2]\1[\/font]/g
Then searched for " and fixed those three lines up manually. This makes most of the game text visible, mostly just numbers being invisible afterwards.
Missing font means even after manual hacking of the localization file, numbers remain invisible.
Default install linux-native was even worse, failed to render the window at all. Tried multiple versions of proton which all worked except the missing font.
Text not displaying makes it hard to tell what's happening and all the options unusable.
Tried Proton GE and Proton not-GE. Tried the Linux native version.
Most of where there should be text showed no text; the main menu worked (because the text there is made of images), but all the options menus are blank. One line of dialogue in-game worked (where it was intentionally unreadable gibberish characters) but then it went blank from there, except for one word a couple of minutes in.
Running in Linux-native mode the window didn't work at all. All versions of Proton seemed okay apart from the missing text.
Couldn't try it in not-full-screen to see if that would improve the text behavior, because I couldn't find the invisible option for not-full-screen!
gamemoderun %command% --ozone-platform=wayland --disable-gpu-memory-buffer-video-frames
The demo don't work at all on my gnome 46/wayland session.
Retail game works, but had multiple crashes the first couple of minutes untill i saw that it is a nxjs game which runs in an embeded "chromium" sortof.
The game worked perfectly for me from start to last boss with the tinker launch commands that forces it to run under wayland
the --disable-gpu-memory-buffer-video-frames might not be neccesary, but it helps getting rid of some spamming log messages.
Since it's basically chromium, one could probably tinker with more chromium flags.
Game crashed both randomly and also during transitions between levels.
Also transition between levels feels slower than it should be.
