protonscr

Sonic Forces

protonopen appid 637100Game compatibility - UnofficialRegression
ValveSoftware/Proton#3571 · opened 2020-02-26 by Ruedii · updated 2024-07-13 · 4 comments · github · game page · search this game
RRuedii 2020-02-26 github

Whitelist Request

  • Name of the game to be whitelisted: Sonic Forces
  • Steam AppID of the game:637100

System Information

I confirm:

  • [X] that pressing the Play button in the Steam client is sufficient.
  • [] that runtime config options are necessary to run the game.
  • [X] that no workarounds other than PROTON_* env variables are necessary.

Issues

  • [X] I haven't experienced any issues.
  • [X] There are no issues left open for this game.
  • [X] Although I consider the gaming experience equal to Windows there are remaining issues:
  1. Minor performance hickups. (Might be E-Sync related?)
  2. Alt-Tab can't switch out of game. (Possibly Window Manager related)
Kkisak-valve maintainer 2024-07-09 github

Sonic Forces (637100)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7882.
@d-anez3 posted on 2024-07-09T20:16:35:

Compatibility Report

  • Name of the game with compatibility issues: Sonic Forces
  • Steam AppID of the game: 637100

System Information

  • GPU: AMD Custom GPU 0405 (vangogh, LLVM 14.0.6, DRM 3.45, 5.13.0-valve36-1-neptune)
  • Video driver version: 4.6 (Compatibility Profile) Mesa 22.2.0 (git-17e5312102)
  • Kernel version: 5.13.0-valve36-1-neptune
  • Link to full system information report as Gist: unavailable, Deck is on RMA :(
  • Proton version: Experimental, 8.0-5

I confirm:

  • [✔️ ] that I haven't found an existing compatibility report for this game.
  • [✔️ ] that I have checked whether there are updates for my system available.

Symptoms

Sometime in between Proton 8 and 9, controller support for Sonic Forces broke, necessitating a switch back to Proton 8.0-5 to rectify the issue. The 2 latest reports on ProtonDB have the same issue, one on another Deck and the other on Linux Mint.

Reproduction

  • Launch the game with Proton Experimental with a controller connected, and test any inputs on the title screen. Inputs should not be recognized, even though they should be (the game doesn't need a manual switch to controller vs. keyboard input).
  • Switch to Proton 8.0-5, launch the game with a controller, and test any inputs on the title screen. Inputs should be properly recognized now.
Kkisak-valve maintainer 2024-07-09 github

Hello @d-anez3, when you get a chance, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

Wwaspennator 2024-07-09 github

steam-637100.log
I can also confirm on my oled deck with Proton Experimental, none of my inputs work to get past the title screen, despite being deck verified.

RRuedii 2024-07-13 github

There have been recent changes in the steam input stack.  I suspect that is the issue.

It would be nice if there was a stack for "Legacy" games on all platforms. It seems to hit harder on steam deck because it is hard to configure.

The legacy stack should just connect the new stack as a controller to the old API.  It should be missing a lot of the new features in the new stack, but it should make configurations from the new stack work on games using the old API.

The old API was very limited in how the game saw it.  The new one is a much more complete stack and can be seen and modified by games that are written for it.

Proton versions

Launch options

Upstream links