Game is really unstable on Proton. Usually it hangs before I can even reach the main menu. Disabling esync seems to improve it ever so slightly. It's a gamble whether I can make it in-game or not, and if I do there are some pretty obvious graphical and performance issues. Still, it does sort of work which is promising.
I've tested it with wine-staging-3.19 (with esync enabled) and DXVK git, and no crashes there, and none of the graphical glitches that are evident with Proton (black squares). I'm not sure if the performance is worse or not with Proton as I haven't been able to get in game recently at all there, but I suspect part of it is just shader and state caches being built.
EDIT: Bug also exists with Proton 3.7.8
On Vega 56/64 the game has another issue:



Play button in the Steam client is sufficient.PROTON_NO_ESYNC=1 %command% launch option within the Steam client.@NTMan, does that launch option help the game on your system?
@NTMan, does that launch option help the game on your system?
Unfortunately it doesn't helps on my setup.
Log with enabled PROTON_NO_ESYNC=1 option: steam-847370.log
Sunset Overdrive appears to work properly with Proton 4.11-1 (no need to disable esync).
Play button in the Steam client is sufficient.Hello, is anyone seeing an issue with this game and Proton 4.11 that would block it from being whitelisted?
@kisak-valve Game still randomly GPU hangs with a Vega 56 and LLVM (as well as ACO). It's hard to debug because it looks to be random, and only happens every hour or so. Another GPU hang was fixed with ACO, but this one looks to be different as it occurs with both compilers.
@kisak-valve I disagree for whitelisting this game because the game doesn't see XBOX Elite Controller, but works well with Dualshock 4 controller.
@aqxa1 Does the game still hang with recent LLVM/Mesa?
@hakzsam I don't have my Vega card currently installed, but I don't remember it hanging last time I played it with that GPU (but that is just from memory).
The game runs but after 15 minutes voices and music sometimes cut out. A restart of the game gets it back. This happens both during gameplay and cutscenes.
here is my log file
steam-847370.log
if i have a new booted pc i can play 1 hour without any problems after that i get the same error.
someone on a forum posted this
"I found a solution on the official forums. I guess I had to change my sound setting from HDMI 7.1 uncompressed to stereo uncompressed in the console's Display and Sound menu. If anyone has the same problem, that worked perfectly."
i don't know how can i do this
DualSense controller doesn't work with Steam Input on this game, and also I'm getting an error that the save files were corrupted on first boot before any save files should have existed.
I think the game can be re-evaluated by now.
Just marathoned halfway through it in the last 2 days with Proton on the Steam Deck (Maxed Out, 30 FPS), and never had an issue with it, fully OOTB aside from a few native bugs already present on Windows.
Just two pieces of advice:
proton 4.11x1 2019-08proton 4.11-1x1 2019-08proton 3.7x1 2018-11PROTON_NO_ESYNC=1`x1 2019-01PROTON_NO_ESYNC=1x1 2018-12PROTON_NO_ESYNC=1 %command%x1 2018-12
Compatibility Report
System Information
I confirm:
[x] that I haven't found an existing compatibility report for this game.
[x] that I have checked whether there are updates for my system available.
steam-847370.log
Symptoms
Consistent application exits during launch process.
Reproduction
Libraryusing the Steam client and press thePlaybutton