search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.72k stars 1.03k forks source link

Street Fighter 6 (1364780) #6817

Open brndd opened 1 year ago

brndd commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1364780.log

Symptoms

Multiplayer matches have low and unstable FPS, ranging between about 30 and 45. Graphics settings did not appear to have any effect on this: the problem occurs even with the graphics turned as low as they will go.

Offline matches with the same characters on the same stages run at a stable 60 FPS, and the open beta of the game did not have this issue either.

Reproduction

  1. Join any online multiplayer match.
  2. Issue should occur every time.
brndd commented 1 year ago

After some debugging, I discovered the online stuttering seems to be caused by having CPU governor set to balanced rather than performance. Running the game with Feral Gamemode solves it.

J-Lowrance commented 1 year ago

I am having the same issue, though using the gamemoderun command or manually setting the governor for all of my cpus to performance does not solve the issue for me. System info - https://gist.github.com/J-Lowrance/56a84d3440ce8c4cd2bf345d9fc4a4d0

brndd commented 1 year ago

I see you also have a 12th gen Intel. One thing you could try is manually setting the processor affinity for the game to only run on the P-cores (should be the first 12 cores) rather than the E-cores.

New Intel CPUs have "performance" and "efficiency" cores, with the 12600k having 6 P-cores (which have hyperthreading, so there are 12 logical P-cores in total) and 4 E-cores (which do not have hyperthreading). I have heard that some games can get confused by them, though I haven't noticed such issues myself. Denuvo also didn't work on 12th gen Intel when the processors first came out but that should be fixed by now.

J-Lowrance commented 1 year ago

Tried setting the core affinity to only the p-cores (0-11 in my case), and still the same performance during online matches unfortunately.

blastermaster77 commented 1 year ago

I have a friend that has the game on steam deck and for some reason when he is offline (no internet) the game constantly crashes while playing, will be good to check that out.

brndd commented 1 year ago

@J-Lowrance do you have the input lag reduction option turned on in the game settings? That also causes performance issues for me, regardless of CPU governor.

RTbecard commented 1 year ago

Same issue with me on a i5-13600K. Manually setting the CPU governor to performance doesn't fix it for me.

appleforyou commented 1 year ago

Same problem here with the same graphics card. The problem seems to happen regardless of in-game settings for the most part. In addition to the framerate loss, it also causes inputs to be dropped in online matches, which is a severe problem (tested by cross-referencing a local recording with an external input viewer, and the in-game replay system which records the inputs received.)

This was with the schedutil cpu governor set system wide, and running with gamemode which "should" have set the cpu governor for the game to performance. It seems like that didn't have a complete effect, though. Setting the system-wide default cpu governor to performance in the kernel made the game fps higher, which helped to some extent, however it did not solve the problem. It brings the fps up from the 30s to the high 40s according to steam's in-game fps viewer. Still not as high as it should be, but noticeably less obstructive. I'm not sure to what extent the inputs still drop.

RTbecard commented 1 year ago

In case its relevant, the specs for my system which suffers from this issue:

CPU: Intel i5-13600K GPU: RTX 3070 Driver: Nvidia-driver-525 Kernel version: 6.2.6 Proton version: Proton Experimental & Proton GE 8-4 Distro: Pop!_OS 22.04

RTbecard commented 1 year ago

Okay, solved the issue on my machine. The problem was split lock protections (I had the same problem with God of War, although that was MUCH worse). Still not sure why this only shows up in online tho...

To diagnose the split lock issue, run the following command while the game is running and you should see a bunch of warning messages, like so:

$  sudo dmesg | grep split                 
[    0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
[41786.661399] x86/split lock detection: #AC: StreetFighter6./47861 took a split_lock trap at address: 0x16886c89a
[41788.750104] x86/split lock detection: #AC: StreetFighter6./47930 took a split_lock trap at address: 0x15f853006
[41789.268254] x86/split lock detection: #AC: StreetFighter6./47947 took a split_lock trap at address: 0x1684dde0a

The fix is simple, if you're running a Kernel >= 6.2, you can disable the split_lock protection during runtime with the following command. You can do this while the game is running, and you should see the problem immediately dissapear:

$ sudo sysctl kernel.split_lock_mitigate=0

You can also change a boot parameter to permanently disable split lock protections (see linked github issue below).

Heres a github issue and an article where I initially learned about this fix for god of war.

ByteDrummer commented 1 year ago

Thanks @RTbecard, that seems to fix it on my end.

Phantas0s commented 1 year ago

@RTbecard you saved me from so much frustration, you have no idea. I've now a solid 60FPS online, you get a kiss from Chun Li for that

My theory why it's only online: rollback netcode ask for much more from the CPU because it has to calculate the potential moves in advance, so higher CPU consumption (at least it's what I read, and it makes sense to me). Maybe it's when they abuse this split stuff...

jclc commented 1 year ago

A few minutes into World Tour starts to cause vertices to explode until the game crashes. Using Nvidia GTX 1660 Ti with driver version 525.116.04. Seems like many other Nvidia users are having the same issue on ProtonDB. I've tried both Proton experimental and GE 8.4

Looks like this is also affecting other RE Engine games like Monster Hunter Rise, albeit to a much lesser extent

drwhut commented 1 year ago

For me, when entering busy areas in the game (particularly in Metro City, another large spoiler-y World Tour location, and in populated Battle Hub lobbies), the game will often hit 100% GPU usage and the FPS will tank, after which there is a chance that the game will freeze. The frame rate also tends to tank when using the "Status" app on the in-game phone. I haven't noticed this happen in the smaller World Tour locations, in less-populated Battle Hub lobbies, or in Fighting Grounds.

I can confirm that I've also had vertex glitches, which have almost always coincided with the frame rate drops mentioned before, but for me this particular bug was rare during my play-through of World Tour.

This is with an RTX 2070 Super, running the 530.41.03 driver on Fedora 38. I have to use Proton Experimental in order to get past the opening splash screens.

mercifulboss commented 1 year ago

The game doesn't launch on an Nvidia2060 mobile. It gets stuck after the "Street Figther 6" splash screen and won't launch regardless of which proton version is used (tried Experimental, Hotfix and 8.4)

Also, i'm now getting a persistent error at launch: image

notpentadactyl commented 1 year ago

The game doesn't launch on an Nvidia2060 mobile. It gets stuck after the "Street Figther 6" splash screen and won't launch regardless of which proton version is used (tried Experimental, Hotfix and 8.4)

This should be fixed now on Proton Experimental with the [bleedige-edge] beta branch.

Please give it a try.

Also, i'm now getting a persistent error at launch: image

The message is from Denuvo DRM (Incorporates 3rd-party DRM: Denuvo Anti-tamper 5 different PC within a day machine activation limit).

After 24 hours you should be able to launch the game again.

mercifulboss commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6817#issuecomment-1611903327

You where right about the message coming from denuvo. I was able to launch the game again (finally) using Proton Experimental bleeding edge, but it remains stuck on this screen (same as yesterday), I left it for a while but it won't go pas this screen:

image

I have updated Proton Experimental before attempting to launch. Here is my driver information:

image

notpentadactyl commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6817#issuecomment-1612778095

When the game gets stuck: run sudo dmesg | tail and post the output. I wonder if you are getting a Xid error.

The fix in Proton Experimental [bleedige-edge] solved it on 3070 and 3080 at least...

mercifulboss commented 1 year ago

Here is the output of sudo dmesg | tail

[11290.053551] wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by c8:99:b2:dc:d7:88
[11323.575633] wlp0s20f3: disconnect from AP c8:99:b2:dc:d7:88 for new auth to c8:99:b2:dc:d7:87
[11323.695305] wlp0s20f3: authenticate with c8:99:b2:dc:d7:87
[11323.695336] wlp0s20f3: 80 MHz not supported, disabling VHT
[11323.700846] wlp0s20f3: send auth to c8:99:b2:dc:d7:87 (try 1/3)
[11323.758219] wlp0s20f3: authenticated
[11323.761474] wlp0s20f3: associate with c8:99:b2:dc:d7:87 (try 1/3)
[11323.782355] wlp0s20f3: RX ReassocResp from c8:99:b2:dc:d7:87 (capab=0x1c31 status=0 aid=10)
[11323.793282] wlp0s20f3: associated
[11323.924169] wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by c8:99:b2:dc:d7:87

Same output in better organized form:

image

Also, judging by the Protondb page (https://www.protondb.com/app/1364780) there are numerous reports of the game freezing and graphics degrading with time even in single player mode. Perhaps the issue that affects me, is the one that caused these freezes in the first place.

SuperBunChan commented 1 year ago

System Information

I confirm:

steam-1364780.log

Symptoms

Extreme lag/fps drop whenever 3D models are on the screen, 2D menus work fine.

Reproduction

Easy way to reproduce is to go into training mode.

n1000 commented 1 year ago

System Information

I confirm:

sf6-shader-lag-steam-1364780.log

Symptoms

Temporary game slowdown (drop to 0 framerate) occurs the first time a special move / animation with special effects is performed in game. The main game menu is also initially slow during its initial animation.

Reproduction

  1. Launch the game and enable shader cache warming in the options menu.
  2. Restart game and wait for shader cache warming to complete.
  3. Start a practice match as Ryu, try to throw a Hadouken. It works fine (no lag / stuttering).
  4. Exit the game and restart it.
  5. Start a practice match as Ryu, try to throw a Hadouken. At this point, there is significant lag and a frame rate drop to 0 during the first animation of the special move. Subsequent animations of the same special move work smoothly with no lag / stuttering.

Workaround

Using the launch command VKD3D_CONFIG=pipeline_library_app_cache %command% worked around this issue for me. After launching the game and allowing the shader warming to complete, the performance was consistently good even after relaunching the game multiple times.

kisak-valve commented 1 year ago

Street Fighter 6 (1364780) : "Generic Xbox Pad" freezes Challenge Screen for 60 seconds

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6916. @Dve89 posted on 2023-07-05T09:25:09:

Compatibility Report

System Information

I confirm:

Symptoms

When switching from Keyboard to Gamepad input, the video freezes when the Challenge Screen appears in online match making (sound clip: "Here comes a new challenger" and "Ranked Match" video).

After exactly 1 minute, the video continues, but game disconnects me from the match for inactivity.

When using "Generic Xbox Pad" (which is a Snackbox Micro), the bug appears as logged in this file: steam-1364780_bug.log

When using a keyboard, the bug does not appear, as logged here: steam-1364780_nobug.log

You can even reproduce the bug outside of real match making, but when previewing your Challenge Screen:

Fighting Ground -> Battle Settings (X) 
-> Character Tab -> Update Character Settings (Y) 
-> Customize Challenges Tab -> Full Screen Preview (Y)

The video clip does not fully play, because it stops mid-animation and I only see a few letters like: "R A N K E M T _ H ".

I have tried deleting the compatdata and the shader cache multiple times and rebuilt them, but that did not fix the problem.

The exact error message when the bug appears is the following:

21708.031:0140:023c:err:sync:RtlpWaitForCriticalSection section 0000020000197368 (null) wait timed out in thread 023c, blocked by 01e8, retrying (60 sec)

21709.472:0140:01cc:err:sync:RtlpWaitForCriticalSection section 0000000259D96140 "../src-wine/dlls/xinput1_3/main.c: controllers[0].crit" wait timed out in thread 01cc, blocked by 01e8, retrying (60 sec)

It times out the game for exactly 60 seconds: "blocked by 01e8, retrying (60 sec)" 0ef8 is the "Zeroplus Controller" (when Snackbox Micro is connected as Generic Xbox Pad)

edit:

The bug occurs when the arcade stick is being used in x-input mode (registered as "Generic Xbox Pad" 0c12:0ef8) and PS3-Mode (registered as "PS3 Controller" 054c:0268), but there are no problems in PS4-mode (registered as "Brook Univeral Fighting Board" 0c12:0ef7).

Reproduction

You need a keyboard and another peripheral in x-input mode, registered as "Generic Xbox Pad"
(in my case: Snackbox Micro 2022, 0c12:0ef8).

With the "Generic Xbox Pad", you trigger the bug like this:

Fighting Ground -> Battle Settings (X) 
-> Character Tab -> Update Character Settings (Y) 
-> Customize Challenges Tab -> Full Screen Preview (Y)

With keyboard input, the bug does not appear:

Fighting Ground -> Battle settings (R) 
-> Character Tab -> Update Character Settings (T) 
-> Customize Challenges Tab -> Full Screen Preview (T)

If you accept the match with your Keyboard and wait until the Challenge Screen is over, you can switch to Gamepad and continue to play without any error.

Metroxe commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6817#issuecomment-1595495268

$ sudo sysctl kernel.split_lock_mitigate=0
sysctl: cannot stat /proc/sys/kernel/split_lock_mitigate: No such file or directory

This unfortunately doesn't run on my Ubuntu Machine. The game runs 60FPS perfectly everywhere, except when an online match starts, even the win/lose animation and the intro anitmations are at 60FPS, but as soon as gameplay is starts in an online match, it locks to ~30 FPS.

Metroxe commented 1 year ago

I ended up having to add split_lock_detect=off to my GRUB config in order to resolve the split lock issue. Here are instructions for anyone else having this issue.

  1. Open the GRUB configuration file. You'll need to use sudo to get the necessary permissions:

    sudo nano /etc/default/grub

  2. Find the line that begins with GRUB_CMDLINE_LINUX_DEFAULT. This line contains the boot parameters that are applied each time your system boots.

    It might look something like this:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  3. Add split_lock_detect=off to the end of the parameters, inside the quotes:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash split_lock_detect=off"

  4. Save your changes and exit the text editor. If you're using nano, you can do this by pressing Ctrl+O followed by Enter to save, and then Ctrl+X to exit.

  5. After saving the changes to the GRUB configuration, you must update GRUB to apply these changes:

    sudo update-grub

  6. Reboot your system for the changes to take effect.

    sudo reboot

After your system reboots, the new kernel parameter should be in effect. After boot steam and try an online match. Should run at 60FPS now.

brndd commented 1 year ago

Replying to #6817 (comment)

$ sudo sysctl kernel.split_lock_mitigate=0
sysctl: cannot stat /proc/sys/kernel/split_lock_mitigate: No such file or directory

This unfortunately doesn't run on my Ubuntu Machine. The game runs 60FPS perfectly everywhere, except when an online match starts, even the win/lose animation and the intro anitmations are at 60FPS, but as soon as gameplay is starts in an online match, it locks to ~30 FPS.

This sysctl option is added in kernel 6.2, so if you are on an LTS distro you probably don't have it yet.

alosarjos commented 1 year ago

Game is freezing for me when loading new matches (Not always). All I see on the logs:

jul 24 12:54:16 artorias kernel: umip: StreetFighter6.[3140] ip:165d43681 sp:571f7238: SGDT instruction cannot be used by applications.
jul 24 12:54:16 artorias kernel: umip: StreetFighter6.[3140] ip:165d43681 sp:571f7238: For now, expensive software emulation returns the result.
jul 24 12:54:16 artorias kernel: umip: StreetFighter6.[3140] ip:1606fab6c sp:571f7228: SGDT instruction cannot be used by applications.
jul 24 12:54:16 artorias kernel: umip: StreetFighter6.[3140] ip:1606fab6c sp:571f7228: For now, expensive software emulation returns the result.
jul 24 12:54:16 artorias kernel: umip: StreetFighter6.[3140] ip:162c1b4fa sp:571ff718: SGDT instruction cannot be used by applications.
matgd commented 1 year ago

Having the same issues as @alosarjos

6900 XT Output when crashed:

[24413.657790] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process StreetFighter6. pid 1172524 
thread vkd3d_queue pid 1172562)
[24413.657796] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000080009f54c000 from client 0x1b (UTCL2)
[24413.657799] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431
[24413.657800] amdgpu 0000:2f:00.0: amdgpu:      Faulty UTCL2 client ID: SQC (data) (0xa)
[24413.657801] amdgpu 0000:2f:00.0: amdgpu:      MORE_FAULTS: 0x1
[24413.657802] amdgpu 0000:2f:00.0: amdgpu:      WALKER_ERROR: 0x0
[24413.657802] amdgpu 0000:2f:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[24413.657803] amdgpu 0000:2f:00.0: amdgpu:      MAPPING_ERROR: 0x0
[24413.657804] amdgpu 0000:2f:00.0: amdgpu:      RW: 0x0
[24413.657808] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process StreetFighter6. pid 1172524 
thread vkd3d_queue pid 1172562)

I have been logged out and after logging in and trying to launch the game:

[24474.911149] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
kisak-valve commented 1 year ago

Hello @matgd, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

matgd commented 1 year ago

@kisak-valve

Maybe this extra info will help with the issue - I've tried playing with newest Mesa RC drivers to resolve this issue but after having no luck I've restored them to previous version (22.3.5).

dadradish commented 1 year ago

Same match-load issues on Steam Deck. It seems to have coincided with the latest Street Fighter 6 update.

I experience the crash most often when loading into a ranked multiplayer match. The pre-match faces appear, then the screen fades to black, the match background music plays partially and then stalls (the introductory musical phrase loops), and the multiplayer match never loads. I've also experienced the crash in causal matchmaking, and when switching combo trial scenarios.

Thanks for reviewing!

kisak-valve commented 1 year ago

Street Fighter 6 (1364780) Crashes while loading matches

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6970. @malucious81 posted on 2023-07-27T03:49:24:

Compatibility Report

System Information

Symptoms

Street fighter 6 is crashing when entering matches, which for me also ends up crashing my entire system. To describe the crash, the display goes completely black and I can still hear audio from the game. Eventually the audio stops and the system becomes unresponsive, no keyboard or mouse inputs. I end up having to do a manual reset.

Reproduction

Notes

steam-1364780.log

osdamv commented 1 year ago

To everyone having the black screen issue, there is a method to recover control of the system, https://wiki.archlinux.org/title/Keyboard_shortcuts using Alt+SysRq+r I recover my keyboard and i can go to another tty an kill wine streetfighter and gdm

jrosenholtz commented 1 year ago

I am also experiencing this issue where the game crashes when loading to or from matches.

System Information ``` Computer Information: Manufacturer: ASUSTeK COMPUTER INC. Model: PRIME B550-PLUS AC-HES Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 5 5600G with Radeon Graphics CPU Family: 0x19 CPU Model: 0x50 CPU Stepping: 0x0 CPU Type: 0x0 Speed: 4463 MHz 12 logical processors 6 physical processors Hyper-threading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Supported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 6.4.6-arch1-1 X Server Vendor: The X.Org Foundation X Server Release: 12101008 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20230509.49499 Video Card: Driver: AMD AMD Radeon RX 6900 XT (navi21, LLVM 15.0.7, DRM 3.52, 6.4.6-arch1-1) Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.4 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 59 Hz VendorID: 0x1002 DeviceID: 0x73bf Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 2560 x 1440 Desktop Resolution: 5120 x 1440 Primary Display Size: 27.44" x 15.43" (31.46" diag), 69.7cm x 39.2cm (79.9cm diag) Primary VRAM: 16384 MB Sound card: Audio device: ATI R6xx HDMI Memory: RAM: 31889 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 455768 MB Largest Free Hard Disk Block: 32816 MB Storage: Number of SSDs: 3 SSD sizes: 6001G,2000G,500G Number of HDDs: 0 Number of removable drives: 0 ```

steam-1364780.log

kisak-valve commented 1 year ago

Street Fighter 6 black screen, making desktop unusable.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6973. @jcgit1 posted on 2023-07-29T01:23:13:

Compatibility Report

System Information

I confirm:

steam-1364780.log.gz

Symptoms

Game crashes during Story or Training after several minutes. I've tried lowering the resolution, lowering various graphics settings from Highest to High, but it still randomly crashes. This began happening with the update that included the Rashid character.

Reproduction

Enter Story mode, play the game. Seems to crash around 4-9 matches. Note: Brave browser is also open and usually playing a youtube video. This is the only other thing I could think of that could be contributing?

jcgit1 commented 1 year ago

kisak-valve

Unsure if it matters, but when my game crashes to black screen it is in match making or training and happens in the middle of a fight, not loading to or from.

ChristianWSmith commented 1 year ago

@kisak-valve Apologies if I'm supposed to fill out a formal report. I have the same bug described recently: crashing when loading/exiting a match. I was able to reproduce by repeatedly starting a session in training mode. Gist of my Steam system information here. Log file attached. I was tailing the log file while trying to get the bug to happen, and my system froze between lines 23298 and 23307 of the log, somewhere in there. Here's an example of what is being repeated on those lines: 820.741:0140:018c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. Immediately before those lines and also unique in the log: 811.618:0140:01fc:err:sync:RtlpWaitForCriticalSection section 0000020004380888 (null) wait timed out in thread 01fc, blocked by 01f8, retrying (60 sec) steam-1364780.log

P-nguyen commented 1 year ago

@kisak-valve Just an note, seems like this is probably an issue for all steam deck users after the rashid update a few days ago. but for me it seems only battle grounds is crashing with loading screens. World tour is fine and I have not noticed any issues.

safiire commented 1 year ago

Everything seemed fine for me, and after playing a random amount of ranked or casual matches, exiting a match with someone gives me black screen, which subsequently crashes and also completely hoses my x11, and crashes x too.

Easily repro'd just by playing the game online, give it 3-4 matches and it will crash.

Gentoo, with kernel 6.4.7, xorg radeon 6900xt, 7950x, proton 8.0-3

Game was flawless until Rashid update on Monday, I have like 130 hours in so something has changed in this update.

dinotheextinct commented 1 year ago

Can confirm, game worked perfectly fine until Rashid patch and now crashes after a couple of online matches after the character loading screen mostly.

SuperPrower commented 1 year ago

Similar issue. Can consistently replicate by going into Combo Trial and manually switching the trial, crashes every time. steam-1364780.log gist

LorenzoSacchi commented 1 year ago

On steam deck and linux (ubuntu) I get black screen after some gameplay. The number of games may vary: Yesterday I played arcade mode and it crashed:

Looks like it does not happen during the game, but it happens randomly during the loading screens

I did multiple tests with: Tested with proton 7, proton 8, Proton experimental, proton GE Also kernel.split_lock_mitigate=0 does not make any difference

error from my dmesg in ubuntu:

[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[  558.150065] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150071] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150072] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201431
[  558.150073] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: SQC (data) (0xa)
[  558.150074] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x1
[  558.150074] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150075] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[  558.150076] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150076] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150081] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150082] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150083] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150084] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150084] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150085] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150085] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150086] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150086] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150091] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150092] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150093] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150093] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150094] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150094] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150095] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150095] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150095] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150101] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150101] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150102] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150103] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150103] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150103] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150104] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150104] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150105] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150110] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150111] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150112] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150112] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150112] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150113] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150113] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150114] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150114] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150120] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150120] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150121] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150122] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150122] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150122] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150123] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150123] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150124] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150129] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150130] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150131] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150131] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150132] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150132] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150132] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150133] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150133] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  558.150139] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32770, for process StreetFighter6. pid 6539 thread vkd3d_queue pid 6589)
[  558.150140] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000b053e000 from client 0x1b (UTCL2)
[  558.150140] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  558.150141] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[  558.150141] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[  558.150141] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[  558.150142] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[  558.150142] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  558.150143] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[  587.597621] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=107000, emitted seq=107002
[  587.597873] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 2440 thread gnome-shel:cs0 pid 2453
LienNoir commented 1 year ago

Same issue, the game freezes the wholes system, during the loading screen after an online match.

t0rment777 commented 1 year ago

I'm experiencing the same issue with Ryzen 7600x & RX 6800. However, I'd like to add that this black screen/loading crash doesn't only happen when playing online matches. It can happen before a versus screen, after the versus screen, or after finishing a match. Meaning even arcade mode and training mode can crash.

ribbanya commented 1 year ago

Even switching characters in training mode can trigger it, so it is directly tied to loading and not to the versus screen.

LorenzoSacchi commented 1 year ago

It also happened when I was in trial mode and I decided to switch to a different combo from the menu. More specifically: I was using Guile, I was doing Intermediate 7, opened the menu, selected intermediate 5. Black screen. Crash

Every time there is a loading screen (black with Ryu spinning a the bottom right corner) there is a risk of game getting stuck and crashing.

thomasfurland commented 1 year ago

To whom this may concern, maybe @kisak-valve, is this being looked into? Although this crash occurs sporadically it stops me from being able to play ranked mode.

This is due to the fact that SF6 implements a leave mechanic where once you have a history of leaves (regardless of if its a crash) your account becomes quarantined (yellow carded) and you only get matched up with other yellow cards which severely limits how many people you can queue with. I'm at the point where if it crashes even once, the next 20 games i spend in quarantine which amounts to being there all the time.

I believe this is a major compatibility issue which stops me from playing the most important mode of the game and at the very least the steam store needs to reflect this by specifying this game is NOT compatible with the steam deck.

I'm sure this isn't an easy solve and I appreciate any time spent trying to fix this.

Thank you

stevengirving commented 1 year ago

Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 6.4.8-arch1-1 X Server Vendor: The X.Org Foundation X Server Release: 12101008 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20230606.51628 Driver: AMD AMD Radeon RX 7900 XTX (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.8-arch1-1) Driver Version: 4.6 (Compatibility Profile) Mesa 23.3.0-devel (git-746b90839f) OpenGL Version: 4.6 Proton Version: Proton Experimental

dmesg | grep amdgpu

Pastebin

dmesg | grep StreetFighter

[ 5874.587389] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587412] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587429] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587446] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587463] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587479] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587496] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587512] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587528] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)
[ 5874.587544] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784, for process StreetFighter6. pid 9229 thread vkd3d_queue pid 9371)

I am also getting random black screen crashes in online matches, requiring either a PID kill or system restart to fully regain system control. I did not realize I needed to set up the Proton logging in advance, so I do not have that to match this, but could provide it in the future.

HansKristian-Work commented 1 year ago

I'm back from vacation now and actively looking into this.

elijahsgh commented 1 year ago

Chiming in that I also have locks after the Rashid update. Fedora 38 Kernel: 6.4.7-200.fc38.x86_64 Proton version: I've tried GE, Proton Experimental, Proton 8, etc with all the same result

If I play a custom room it seems to happen very rarely. Once every 20 matches or so I have a lock. But in ranked it happens pretty often (probably within 1-3 matches of starting a session) requiring a full reboot. Unlike others I have not been quarantined or yellow carded. For me it seems to happen after the "Quit" prompt and returning to Practice Mode (where I started matchmaking from).

Usually I get a black screen but occasionally I see the little whirlwind kick icon spin for a moment and then freeze.

HansKristian-Work commented 1 year ago

Root caused to a game bug. This PR should fix the hang: https://github.com/HansKristian-Work/vkd3d-proton/pull/1647. Should hit bleeding-edge very soon.