When I tried it didn't recognize my steam controller at all. Only keyboard input.
Steam Controller is known to not work with proton atm.
Steam controller works for me on Street Fighter and Nier. :shrug:
That sucks. At least I can say that my ds4 controller works.
Also Valve will probably fix it soon since a few other people have had a similar issues.
I cannot confirm that it works with a ds4.
Manjaro has a package called steam-devices which contains some fixes i guess? for controllers. Don't know if this exists for other distros as well. Probably is the reason why it works for me
Hmm. Cannot find the package to look into it. @Yuri-Makina Could you link it somewhere?
I searched here
https://repology.org/metapackages/?inrepo=manjaro_stable
Here. https://github.com/manjaro/packages-community/tree/master/steam-devices
I think this should be it.

Got this on first start. Keyboard input is not working...
Proton 3.7-3
I tested the game and it works with several arcade sticks. Xbox 360 compatible and sticks for ps3/ps4.
It worked flawlessly. I think this can be approved. Unfortunately it didn't worked with with a dualshock 4 for me.
Performance is kinda average. Most of the time I get 60 fps.
Hardware and OS
So the game works perfect with 3.7.8 however once you upgrade to 3.16 the ground textures disappear tested on several stages.
Hardware and OS
arch linux
Intel i5 7500 @ 3.8 ghz
Nvidia GTX 970
32gb ram
Hello @douggle, if possible, please retest with nvidia's vulkan dev branch (currently 396.54.09).
Have you guys played online?
I tried with 396.54.09, and can confirm the floor texture is missing with Proton 3.16-4 beta, if I switch back to Proton 3.7.8 it works as expected
Played a bit yesterday, and have run into a crash I can reproduce at will.
Proton 3.7-8 Beta
If I start an M.O.M. game and play as Chipp vs Leo it crashes every time during the transition between player select and starting the fight.
How might I pull logs? I know I've done this once before for another game.
EDIT: Never mind, I found the logging parameter
PROTON_LOG=1 %command%
Proton 3.7-8 Beta
System: https://gist.github.com/nightsky30/1e52d47066cdaa584e64cb38b0ae0888
Here's the crash log:
steam-520440.log
Hello @nightsky30, please retest with nvidia 396.54 or newer.
@kisak-valve Sorry after posting the steam log I've played against another character in M.O.M. mode, and then played against Leo again. I have not been able to recreate the crash after selecting a different challenging fighter. Leo had 2 stars at the time indicating it was a special match, and the challenges are randomly generated as you progress. Perhaps the circumstances of the match affected the game in a way that caused issues with Proton compatibility. Maybe a special/alternate intro or something.
I'll retest if I encounter Leo again with 2 stars in M.O.M. mode and the crash returns.
Guilty Gear Xrd -Revelator- is also affected by the lack of .wmv support. #1464 Some movies unlocked in the game's gallery cannot be played in game. The game skips the movie, and the gallery simply reloads.
The .wmv files are located in:
/home/.../.steam/steam/steamapps/common/GUILTY GEAR Xrd -REVELATOR-/REDGame/Movies/
Note: Some of the cutscene movies play because they are presumably a different movie file type, but the movies that correspond with the files in that directory do not.
@kisak-valve I've encountered the same reproducible crash while starting a match versus Leo and playing as both Chipp and Sin in episode mode. I also upgraded my drivers to nvidia 410.73 and collected new crash logs.
Proton 3.7-8 Beta
https://gist.github.com/nightsky30/6c90d51ce00af8d58b95a6bb740408f3
Here's the new crash log:
steam-520440.log
latest nvidia driver breaks this altogether GTX 970 driver 415.18 i5 7500 MSI B250 PROVD 32GB DDR 4 Corsair Vengance LPX Arch Linux 4.19.2 game doesn't launch under either version of proton 3.7.8 and 3.16-4
Hello @douggle, if possible, please test the same nvidia driver version with a 4.18 kernel.
unfortunately with arch 4.19 kernel is a requirement for the 415.xx driver
Tested this for a bit and haven't found any crashes (haven't tested the match against leo though).
Performance is perfect. I get a solid 60fps, except in loading screens when it dips to ~40. I also haven't seen any glitches in the stages. Audio is ok too.
I have a Genius Blaze 3 (a generic dual-shock-like) and the game didn't pick it up, neither the steam controller. I remember this was a problem in Windows too, so I'll try with xbox360ce soon.
The only problem is online. I can connect to lobbies, walk around and all but there is no one anywhere. Looking for a ranked match bails out immediately telling me no player was found. Has anyone had any luck playing online?
Specs:
Fedora 29 / Kernel 4.19.2-300 / AMDGPU (Vega RX 54) / Mesa 18.2.4
Tested this for a bit and haven't found any crashes (haven't tested the match against leo though).
I'd be very interested if someone else could reproduce the crash when facing Leo. A few times I've played him without a crash, but the majority of the times it has induced said crash.
The only problem is online. I can connect to lobbies, walk around and all but there is no one anywhere. Looking for a ranked match bails out immediately telling me no player was found. Has anyone had any luck playing online?
I too have not found anyone online. I wasn't sure if that was an underlying network glitch or if it is simply nobody playing online matches.
I was able to get the game running again with Proton 3-16.4 on nvidia 415.22 however, the black textures on the floor remain if I switch back to 3-7.8 it works as intended
I got the gampads working, here's an update:
Gamepads: I got my generic USB gamepad and the Steam controller working with Kozec's Dumbinput. This is the same as in Windows, so no issues with gamepads.
Online: I did some digging and it looks like the community doesn't really like lobbies and ranked. Most people only play player matches. Also everyone is on Rev 2, and I have the basic Revelator so that's probably why I couldn't find a soul to fight. If guys on Rev2 can find matches then online must be working fine.
The Leo Crash: I fought a 2-star Leo on M.O.M. once and didn't get any crash (playing as Sol). I also fought Leo several times (normal and 1-star) and never got a crash. I tried finding him with chipp/sin in episode mode but never got a match with him. All in all, no crashes so far.
Story mode: There is one problem that I've noticed with the audio in story mode. The ambient sounds are super loud, overpowering the voices and everything else. Changing the settings didn't fix it.
Online works fine for me, I have rev 2, as far as gamepads both my ds4 and my mayflash arcade fightstick f300 work fine out of box too just have the black floor textures on 3-16.4
REV 2 DLC also crashes in the same manner.
An update on this: it only works with proton 3.7-8. Later versions have black textures or don't even run at all.
I am on Arch with kernel 5.2.14 and mesa 19.2 (with the ACO compiler patch set but this shouldn't matter for my input issues here) on a Radeon RX 480 8GB.
With Proton 4.2-9 the black texture glitch is still there but everything else is working for me.
Switching to Proton 4.11-3 fixes the black texture glitch (yay!) but makes my "Madcatz TE2 Fightstick" (for Xbox One) stop working. I tried to get some debugging output by setting the PROTON_LOG=1 environment variable but the log doesn't contain any errors about input (or I have missed them).
Please let me know if there is anything I can do to help you debug this. I also own a PS3/4 compatible fight stick as well as a Xbox-One-to-PS4-adapter but PS4 sticks have stopped working with the game even before for me. If I can figure out a way to debug input in Proton, it would be interesting to see what's going on there as well.
It is hanging on the startup videos now with Proton 5.13-1. Logs:
steam-520440.tar.gz
Screenshot:

@ranplayer I believe that this regression is fixed in the latest Proton Experimental build, and the game now proceeds correctly after the test pattern to the main menu :)
Been trying out the new rollback netcode beta in Proton, Xrd seems to exhibit the same frametime problems as Tekken 7:
https://github.com/ValveSoftware/Proton/issues/5992
Edit:
@AED-001's fix for Tekken 7 works well here, but I think setting bSmoothFrameRate=FALSE in GUILTY GEAR Xrd -REVELATOR-/REDGame/Config/REDEngine.ini and changing your steam launch options to DXVK_FRAME_RATE=60 %command% might work even better.
This also fixes an issue I was having when returning to the game after alt-tabbing, the framerate would drop to ~20 and slowly rise back up to 60 over the next 10-20 seconds.
GUILTY GEAR Xrd REV 2 (520440)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8074.
@robotman40 posted on 2024-09-06T00:42:50:
NOTE: I am filing this report on behalf of someone who is struggling to run this game on their PC
The game will open a window with a black screen then close after a few seconds.
steam-520440.log
Just launch the game
Replying to https://github.com/ValveSoftware/Proton/issues/174#issuecomment-2332992538
Just an update, but the issue was easy to solve since he just had to press the game icon in the taskbar to run the game successfully afterwards. Subsequent launches show the black window, but then open another window that shows the game itself.
I seem to have found a convergence of a lot of issues when trying to play this game.
LD_PRELOAD="", but that stops my controller from working-steamos3, but that causes issues with changing my speakersI am running NixOS on a Framework 16 Laptop, AMD 7700S, Mesa version 25.0.1, Kernel 6.13.7
proton 9.0-4x1 2025-03proton experimentalx1 2021-01proton 5.13-1x1 2020-10proton 4.11-3x1 2019-09proton 4.2-9x1 2019-09proton 3.7-8x4 2019-06proton 3.7x3 2018-11proton 3.16-4x1 2018-11proton 3.7-3x1 2018-08DXVK_FRAME_RATE=60x1 2022-10PROTON_LOG=1x2 2019-09DXVK_FRAME_RATE=60 %command%x1 2022-10
Worked flawlessly during a short test.
Steam log