Open zany130 opened 1 year ago
I didn't get into gameplay because I was trying to solve the input issue, but also realized that the game doesn't progress past the intro on proton 8 works on 7 though, so there is a proton 8 regression @kisak-valve steam-740130.zip
Hello @zany130, please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
how can i paste the information into a gist though? the old way of going into help system information and then pressing ctrl+a
and then ctrl+c
doesn't work (the information doesn't seem to be copyable cant even highlight it with the mouse) that's why I uploaded an inxi instead
EDIT: noticed if I click system information and then click where it says runtime system information. there a box at the bottom to copy everything into the clipboard
updated OP with the new gist
I didn't get into gameplay because I was trying to solve the input issue, but also realized that the game doesn't progress past the intro on proton 8 works on 7 though, so there is a proton 8 regression @kisak-valve steam-740130.zip
@zany130 We cannot reproduce this. Could you give some more details? Does the failure happen when launching a new game? At what point does the game fail - during the video before gameplay starts? Also - could you please retest on 7.0-6 and make sure that the game is still playable on your setup there?
The game hangs after starting a new game or loading a game file. Unfortunately for some reason, the hang is not consistent making determining what's going on difficult, but it might not be a proton regression as it still sometimes happens to me on proton 7.0-6.
Sometimes the game is able to load a save/start a new game just fine, but other times it will just black screen and hang indefinitely, eventually causing 100% CPU utilization and system freeze.
at first, I thought it was a proton regression as I was getting the issue with proton 8 and not with 7. I switched back to 8 and ran into the issue again so I thought it was a regression.
Then I thought it was a mangohud issue as I was able seemingly to reproduce the issue with mangohud but not without until I eventually was able to reproduce with mangohud enabled.
I haven't been able to pinpoint what exactly is causing this so I mainly just play this game on my Steam deck which works with no issues.
EDIT: I also tried completely uninstalling the game (making sure all game files, compact data, and shaders) are completely gone and then reinstalling and playing with proton 7.0-6 (with no launch arguments like mangohud or anything else) and was still able to occasionally reproduce the crash so not sure what is going on.
I'm seeing some texture or shader corruption recently - proton version doesn't seem to help. It was working a month back so I'm not sure if its a new game version or a driver version: ^ small white bars over the top of character textures
Proton version or game settings doesn't seem to make a difference (Experimental, 7.0-6, 8-3, GE).
FWIW game otherwise runs flawlessly and I don't see the same issue on Deck - may be a mesa/radv issue on RDNA3 but I figured I would report here as well.
Replying to https://github.com/ValveSoftware/Proton/issues/6747#issuecomment-1556303950
Seems like even if I am able to progress past the title screen and load a game file it will still randomly cause 100%cpu usage and freeze my pc
with the last thing in the log being 8349.300:012c:0198:err:sync:RtlpWaitForCriticalSection section 000000006FB79BA0 (null) wait timed out in thread 0198, blocked by 019c, retrying (60 sec)
@Shearerbeard Thank you for the report. This appears to have been a mesa issue that have already been fixed again on latest main.
@zany130 I have tried loading into a save game a whole bunch of times on my desktop but have been unable to reproduce so far. Tested with Proton 8.0-2, kernel 6.3.6, AMD 7900XTX with mesa 23.0.3 and a AMD 7950x
Since Friday night, I been able to run the game using the Zen kernel. Maybe a bug in the tkg kernel. I could of sworn I tried the vanilla arch kernel but I will try it again as well
@Shearerbeard Thank you for the report. This appears to have been a mesa issue that have already been fixed again on latest main.
@zany130 I have tried loading into a save game a whole bunch of times on my desktop but have been unable to reproduce so far. Tested with Proton 8.0-2, kernel 6.3.6, AMD 7900XTX with mesa 23.0.3 and a AMD 7950x
I can confirm with the most recent mesa-vulkan-23.2.0-git.20230610.1555f41.fc37 the issue is fixed
My issue only happens when using the tkg kernel built with the BMQ schedular. any kernel using cfs (stock arch and zen) works fine. I don't know if other schedulers have this issue but it seems like its, not a proton issue so I guess this can be closed?
With the latest version of Proton Experimental which is based on Wine 9.0, it has broken the compatibility of the controllers, I tried with my XONE and Switch controller, even using Steam Input and it simply does not work, it is particularly with this game, I tried in another game and yes It runs fine..
With Proton 8.0-5 the controls work without problem with this game.
Hello @Alejandro9509, 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.)
Compatibility Report
System Information
EDIT: new gist : https://gist.github.com/zany130/771908d6758bb450f3e2c36085d32d0c
I confirm:
steam-740130.log
Symptoms
steam input remapping is being ignored
Reproduction