Compatibility Report

Using the instructions from https://github.com/ValveSoftware/Proton/issues/1235#issuecomment-418589364, I managed to disable my controller and am now able to user my controller (an 8Bitdo SF30 Pro).

My user.reg ended up looking like this

~/.steam/steam/steamapps/compatdata/323460/pfx/user.reg

[Software\\Wine\\DirectInput\\Joysticks] 1547525979
#time=1d4ac898845fe2c
"8Bitdo SF30 Pro"="disabled"
"8Bitdo SF30 Pro (event)"="disabled"
"8Bitdo SF30 Pro (js)"="disabled"

Proton 4.11 controller not detected if plug in during intro movie.
If controller connected before run game, detected as Gamepad 5 and direction is stuck
Simply controller doesn't work at all on Proton 4.11

With Proton 4.2.9 and 4.11.3 the F310 seems to be fine even when plugged in and starting the game.

I used the PS4 controller Bluetooth connection which doesn't work with Proton 4.11 but works with 3.16. They have said the Proton 4 directly access the controller where the older version is emulation. I believe this change has caused this compatibility issue

I used the PS4 controller Bluetooth connection which doesn't work with Proton 4.11 but works with 3.16. They have said the Proton 4 directly access the controller where the older version is emulation. I believe this change has caused this compatibility issue

Ahh that explains it. Sorry to hear they messed up the bluetooth connection :(

Game seems to work well on deck, but for some reason there's a weird graphical quirk halfway through the game, playing on Overkill mode, went through most of the game until you got into the part where you go into space and while some of the meteorites are showing up, some of them are just mostly invisible, making it harder to guess where the hell they are. Apparently this was happening briefly with the Mikado Remix version too and it got patched. Easiest way to replicate it is to play through overkill mode on practice difficulty (Turns off all enemy bullets), then just breeze through the game until you get to the space sections, then as soon as you beat special mission 2 (Destroy asteroids), intentionally game over to unlock the stages for future testing. It's more easily noticeable on special mission 2 where you have to destroy as many asteroids as possible.

Edit: I also tried forcing WineD3D to see if it would change anything and certain asteroids still showed up as invisible, dunno if this is a proton issue, a deck issue, a mesa issue, or something else.

steam-323460.log

How it looks on deck:

How it should look from my W11 laptop running this game:

Checking out protondb, seems like the issue happens on intel chips too, judging from one review mentioning the issue 4 years ago, dunno if the reviewer was using proton 4.0 or 5.0, but they were apparently using mesa version "3.0 Mesa 19.1.4" taken from the report

I'm assuming the issue is still present since the issue report on the mesa github is still open.

Updated to steamos stable with latest mesa drivers, can confirm the invisible meteorite issue is still present

Also present on oled deck, sharing link to mesa issue report since I probably should have done it sooner.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/9167

Report seems to also mention some stuff going on with intel iris so I dunno if this is both an amd and an intel issue too.

Updated to latest version of stable steamos and it looks to me like the meteors are finally rendering.

Updated to latest version of stable steamos and it looks to me like the meteors are finally rendering.

Yes, can also confirm. I've closed the mesa bug report :)