Yakuza 0 runs into a nasty GPU hang on both RADV and RadeonSI which is very tricky to debug.

@doitsujin That's unfortunate that it hasn't yet been fixed although it does work fine for me with RADV + RX 550.

@meaxavier There are reports on this compatibility list that aren't successful, so it might not work consistently across enough systems to be whitelisted yet.

I'm on nvidia and I can't get it to run, it starts running, says failed to initizalize gs settings then just closes

RX480 and Mesa 18.1.7, crashes in fights, otherwise works. Steam info here.

RX560 crashes during the tutorial fight scene when pressing the ( Y ) button. When pressing the button the character changes color and appears to initiate a new special effect which seems to be the cause of the problem.

I'm on nvidia and I can't get it to run, it starts running, says failed to initizalize gs settings then just closes

Same. Though my nvidia-driver isn't the latest version because it doesn't seem to work.

Edit: seems like this error is not specifically for linux and happens on windows as well. And I didn't have this error on the same hardware on Windows 7. I didn't update the driver that much, so I don't think it's related to that either.

Another issue I've found is that sound doesn't work with the emulated arcade games (Space Harrier and Outrun). I tried doing the usual "winetricks xact" workaround but it didn't help in this case.

Also, I can confirm that the GPU hangs still occur with a Vega 56 and RADV. It happens at least 2 more times that I've seen so far in the game.

I have the same issue as above, the games works fine, but if I use the special attack in fights, it just crashes. I tried to use "PROTON_LOG=1 %command%" but for some reason it made my game crash right away on startup...

EDIT: It worked with the logs when I tried again, here is the log:
https://gist.github.com/wolfyos/e26d1536ab83bb65365eaa6ee194ba2c

For the people who are crashing on heavy/special attack like I was, tell steam to install it to a different folder, nowhere specific. I tried this after reading on protondb, and it worked. I have absolutely no clue how this works, it happens to some people on windows as well (not me though). The game runs pretty well for me now though, as baffling as the fix is. Hopefully it works for all of you as well.

confirming installing to a different folder fixes the 'hard punch crash' issue. i've seen some mentions this might be related to path/path length, and that some people have the same issue on windows, but who knows.

note you have to install to the new library; ValveSoftware/steam-for-linux#4851 prevents moving between steam libraries on linux.

I just created a folder, simply named ".Yakuza0", in my home folder. After purchasing the game again and installing it to that folder the game STILL crashes during heavy attacks :( I'll try installing to a different partition and see if that makes a difference; I've got no secondary drives to install to.

Edit: Okay, so I moved the game files from that folder to a new folder, "Yakuza0" also in the home folder, and then added the library to steam and installed it there. Now I can actually get past the tutorial without crashing! :D I don't know if the difference was moving the game files before adding the library, or even the folder name change, either way something worked!

Following the tip from @hadbabits I tested installing Yakuza 0 to the following steam libraries:

• ~/SteamLibrary — the "hard punch crash" does not happen;
• ~/.SteamLibrary — the "hard punch crash" happens;
• ~/Steam.Library — the "hard punch crash" happens.

Given the fact that by default Steam for Linux is installed under ~/.local/share, it is evident that the crash occurs whenever there is a dot (.) character in the path to the game directory.

Would be glad if someone with a Windows machine could test whether the game crashes on Windows when it is installed under a path containing a dot. The same crash is a problem for some Windows users, so if it is the case for Windows, this is an issue that needs to be reported to Sega.

I booted to windows 7 on my nvme and moved yakuza0 onto my C: drive in a new library called "y.akuza". Sure enough the heavy attack crashed, but when i renamed the new library to just "yakuza" the heavy attack worked. It makes me wonder if other characters in the path cause an issue.

EDIT: I couldn't find a support area on SEGA's site for Yakuza 0 on PC, so I made a steam discussion, maybe they will see it there.https://steamcommunity.com/app/638970/discussions/0/1741103267301795215/

So it is a game issue. Thank you for confirming that!

I'm sure if we get this to Sega they can fix it, as they have fixed a few issues that were present on release. After that the game should be good for whitelisting.

I doubt other characters in the path can cause this behaviour. Usage of "." in file or directory names on Windows is discouraged, but not forbidden. It's probably an issue with path resolution (for example everything after a dot is assumed to be a file extension, or something like that).

The game is still missing audio completely in the SEGA splash screen (not a big deal) and the arcade machines (a showstopper bug, IMO). ProtonDB has a few reports mentioning this and I've noticed it myself. FAudio doesn't seem to have helped with this in any way.

According to PC Gaming Wiki, these scenes also cause the game to hijack the operating system's global volume setting. It could be related to the issue, I guess?

Doesnt work at all for me - On every Proton version, it crashes on the initial load screen after a few seconds. Heres the log: https://bin.disroot.org/?543b1d6ae37effdd#GtpliXWKfFj/BMVc4x5BSrSQWcWAWozq7dFit4UlE7M=

Arch, kernel 4.20, latest Mesa from git.

In case anyone missed it, the latest beta has a fix for the "." in the path bug. https://steamcommunity.com/app/638970/discussions/0/1776010325134009474/

3.16-7 fixes the loading screen crash for me on Arch.

With Proton 4.2 and the game's "community_test_branch" I have now almost finished the game completely on proton. (on final chapter) The game rarely crashes now on this version. (can play for several hours before any crash)
The test branch patch v4 has now been pushed out also to the main branch. So it should be plug and play at least with x360 controller on an AMD system.

Does not work with latest proton version, Arch kernel 5.1-2. Attached is the output of Steam when running the game
output.txt

I'm having the same issue, it wont work anymore

Game still works for me, but controller support is broken when the Steam client beta is used (along with Yakuza Kiwami, Hitman 2, and a few others).

I actually just finished this game on proton 4.2-4 on my arch AMD machine.
I am using the Steam beta client and latest MESA and AMD gpu that comes on arch right now. (nothing special or custom built)
Also I was going to say I was using a custom TKG kernel but arch was sneaky and booted "5.1.2-arch1-1-ARCH" last time I booted.

Anyway comparing this proton to the old one or custom builds like TGK 4.7 this one appears to be the most stable. I found out that the game's ending sequence is VERY LONG. With the other proton versions it would crash at some point before the final boss. With this version I played through many hours of the end game and post game parts.
I had no issues with my x360 wireless controller on this game with the current proton. Will test the other 2 yakuza games on it soon.

Edit: I finally played far enough into the business aspect of the game to find a sound bug. When you play the rideout arcade game in the SEGA arcade there is no sound.

Yakuza0-outrunAudiosteam-638970.log
It looks like I maybe got something useful with just the basic log. I can run again with more log options if needed.

So in this game once you get past a certain point there are actually 2 of these arcade games with broken audio. In this log I loaded the game save, ran down to the SEGA, played each of the 2 games 2 times (
only for about 10 seconds each), then ran to the nearest save point, saved, and hit ALT+4.

I've encountered a bug in the game.

The emulated minigames (eg Space Harrier) don't work (when you try to play Space Harrier, after the animation plays, there's a black screen, and the game doesn't proceed further) If Yakuza 0 is not installed in the main /home/user/.local/share/Steam location, but on another partition eg on /mnt/partitionx/SteamLibrary.

Most of my library is outside of my main root / home partition, so I thought the emulated mini-games not working was a Solus bug.

It's only now that I installed the game on my main partition, that Space Harrier started working.

Here's the PROTON_LOG up to the moment the black screen happens when I try to play Space Harrier, and I close the game by doing ALT-F4 [with the game installed on a non-local partition such as /mnt/something/SteamLibrary]
steam-638970.log

Edited with updated system/driver info. No change to the game itself.

Everybody is writing how Yakuza is working perfectly so I bought it, and can't even run the thing. Well... I can run it, Steam says I'm playing it, but nothing's happening.
What I tried, and the specs:

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Laptop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz
    CPU Family:  0x6
    CPU Model:  0x5e
    CPU Stepping:  0x3
    CPU Type:  0x0
    Speed:  3200 Mhz
    4 logical processors
    4 physical processors
    HyperThreading:  Unsupported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Ubuntu 19.04 (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.0.0-23-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12004000
    X Window Manager:  Xfwm4
    Steam Runtime Version:  steam-runtime_0.20190711.3

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 950M/PCIe/SSE2
    Driver Version:  4.6.0 NVIDIA 418.56
    OpenGL Version: 4.6
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x10de
    DeviceID:  0x139a
    Revision Not Detected
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 13.54" x 7.60" (15.51" diag)
                                            34.4cm x 19.3cm (39.4cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 2048 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: Realtek ALC898

Memory:
    RAM:  7857 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  937367 Mb
    Largest Free Hard Disk Block:  111018 Mb
    VR Headset: None detected

Recent Failure Reports:

I tried noesync - no change, wined3d - game crashes in less than a second. Tried running with all versions of proton, tried disabling Steam Overlay.

I'm attaching the log. Would appreciate if somebody could point me in the direction of some solution.
steam-638970.log

Edited with updated system/driver info. No change to the game itself.

Everybody is writing how Yakuza is working perfectly so I bought it, and can't even run the thing. Well... I can run it, Steam says I'm playing it, but nothing's happening.

Unfortunatley, I did exactly the same and must confirm. Immediate crash, with different options and or Proton versions...

Edit later the same day: I downgraded from Ubuntu 19.10 to 18.04 (because of some other reasons) and it works now. No parameters needed... It seems like vulkan is broken on 19.10.

Edit 2 weeks later again: It works with 19.10 with a small workaround. Jusst call sudo vulkaninfo and it should work.

So I found something very strange with both yakuza 0 and kiwami. When installed onto a second drive, they crash instantly, all other proton games work, even run a few lutris installed games from there and they work with no problem, the drives are formatted properly and everything, no mans sky works, fallout 4 works, shenmue 1 and 2 works, even warframe works. Yet something about the yakuza games make them the only ones to crash when not installed in the default steam library. I have reinstalled, moved and moved files back and they simply will not work using a second drive. Have tried this with 3 different operating systems and 2 different computers. On linux the game just will not run when on a second drive.

Okay so scratch that, right after I posted that comment I had an idea, I mounted my external drive in my home folder and it just worked. I think the issue may lie somewhere in that my original mount point was in /run/media/user/ which may be the case for other users running something similar. I edited my fstab to auto mount the drive into /home/user/drive and now everything works flawlessly

New bug in yakuza 0 that seems to show up in installations that use a nettle version newer than 3.4.1. Three instances of the bug occuring in different hardware (all running calculate linux). Had a working yakuza 0 on each Calculate install with nettle 3.4.1, and the upgrade to 3.5.1 made it crash predictably. Tested 5.0-7 and 4.11 (deleting the compatdata folder each time, and had identical crashes from each.

output of steam -vvv output during Proton 5.0-7 crash:
https://hastebin.com/kevoramira.sql
output of steam -vvv output during Proton 4.11 crash:
https://hastebin.com/jatatarafu.sql

Aforementioned issue was solved today by calculate linux downgrading the nettle version back to 3.4.1, and masking 3.5.1 until issues such as this are resolved.

New bug in yakuza 0 that seems to show up in installations that use a nettle version newer than 3.4.1. Three instances of the bug occuring in different hardware (all running calculate linux). Had a working yakuza 0 on each Calculate install with nettle 3.4.1, and the upgrade to 3.5.1 made it crash predictably. Tested 5.0-7 and 4.11 (deleting the compatdata folder each time, and had identical crashes from each.

output of steam -vvv output during Proton 5.0-7 crash:
https://hastebin.com/kevoramira.sql
output of steam -vvv output during Proton 4.11 crash:
https://hastebin.com/jatatarafu.sql

Just a heads up for fellow Yakuza 0 players ; saving game doesn't work when Fsync is on ( obviously you need to be on a kernel with Fsync patches ) and game hangs when quitting from app. Both of those issues doesn't exist with esync.

Issue noted here:

https://github.com/ValveSoftware/Proton/issues/2922#issuecomment-664968925

So people with Fsync patched kernels should run game like this:

PROTON_NO_ESYNC=0 PROTON_NO_FSYNC=1 %command%

Esync var is probably not needed but i use it like that anyways , in case of Fsync variable also might affect it.

I've been testing this game extensively this week on Proton 5.0-9. So far due to my findings , game is not actually playable unless you are a man that is determined to finish the game at one sitting. Because game has issues on Proton that affects saving mechanism of game and also affects stability.

1-) Game doesn't save when Fsync is in use and hangs when quitting from the game , no hangs when playing the game ( my previous message also mentions that )

2-) Game does save when Esync is on and also can properly quit but game hangs after approx. one hour of gameplay (which is very bad because some missions are very long and game doesn't have autosave feature). I'm able to repro this all the time , just leaving the game running is sufficent to repro hang. I got log from it.

steam-638970-one-hour-hang.log

3-) When you run the game without esync and fsync , symptoms are the same as running it with Fsync. Saving game feature doesn't work, game hangs when quitting from the game, no hangs observed at one hour and longer gameplay session ( since game doesn't save in this condition , we can call this basically unplayable )

Also so far i noticed Sega logo at the beginning of intro cinematic sequence is inaudible.

For repro purposes: Game doesn't have any autosave mechanism , you can try to save game progress from the phone booths in the game , which are marked as S on the minimap of the game. At the beginning of the game , there is one of them which should be very helpful for at least looking into save game feature issue in a quick fashion.

I've also tested the game with Proton 4.11-13 now. With this Proton version , saving game works and game doesn't hang when closing the app. So looks like there is a regression. @kisak-valve

steam-638970-fsync-can-save-4.11-13.log

Can you please take a log with +esync,+fsync,+sync,+server,+timestamp,+seh,+pid, at least of the fsync crash?

A hang after 1 hour would be difficult if not impossible to debug, but because of the symptoms I'm more than a little inclined to blame exhaustion of some resource, probably virtual memory or number of open files. The log doesn't really mention either, but I'm not sure that rules it out. (esync will always warn if we run out of VA or hit ENFILE, but esync isn't the only thing that might hit that condition). In that case there's not much I think we can do.

(esync will allocate 8 bytes of shm + 16 bytes of local (cache) memory for each object, and as we've seen objects can number near the millions. It can also run out of cache space, since there's a fixed amount, but it should complain in terminal if that was the case.)

@zfigura With logging these debug channels , it is kinda impossible to get fsync crash. Just doesn't happen with +esync,+fsync,+sync,+server,+timestamp,+seh,+pid in a short time amount that i won't waste so much time on it and log will be in sane amount of levels in size.

Here is the log from no-sync version though, same hang that normally occurs on fsync after a time also. So maybe QA should look at it if they can.

steam-638970-triggered-nosync.log.tar.gz

I've found an easy way to reproduce the hang with either fsync or wineserver sync without needing to play through the first section of the game to be able to save. Just go into the game's graphics settings, change the resolution and accept. Doing this, the game will hang with fsync and wineserver sync, but not with esync. Here is a log with server side sync and +sync,+server,+timestamp,+seh,+pid:

steam-638970.zip

@Leopard1907 the game makes a very creative use of semaphores to wake up worker threads. The worker threads are prone to deadlock depending on the order of them waking up and how the threads are scheduled in and out of execution afterwards.

This causes both the saves to be broken and the hang on exit.

Those deadlocks happen even on Windows, but are a bit more rare.

esync seems to have the closes behavior to Windows wrt semaphores, and it improves the chances of the game working, but in my testing we are still far from matching Windows' (un)reliability due to differences in operating system's scheduling.

I am afraid that Yakuza 0 will remain somewhat broken until either the developer or the community will patch the game itself.

Replying to https://github.com/ValveSoftware/Proton/issues/492#issuecomment-664970908

When I disable FSYNC, I still have the no save problem, the only way I have to solve this is to reboot and boot into the normal kernel without the fsync patch.

I'm not able to launch the game via remote play / in home streaming.

I have two via LAN connected linux PCs: one for couch gaming and my beefy PC upstairs.
When I try launching the game via remote play / streaming, the game apparently tries to start but crashes.
However when I start the game manually on my beefy PC and THEN connect via streaming, everything works perfectly fine.

When launching other games (Proton or native) launching via remote works perfectly fine. Just the Yakuza series (I also tried Kiwami) seem to cause issues.

I tested using:

• Proton Experimental
• Proton 6.3-6
• Proton 6.16-GE-1

I also tried reinstalling the game to no avail. The issue is still the same.
However, I remember this was working on my old PC just fine.

Here's the log when starting steam via terminal: https://pastebin.com/W99Z3cKP

Is there anything obvious I'm missing or is there some kind of incompatibility with my setup?

Not sure if this is the right place but I don't know where else to ask - feel free to point me in the right direction.

Hello, the game is still not working on my platform. It crashes just after launch.

Here are the logs:
steam-638970.log

Strangely, the command launched by Steam does not correspond to the installation path I chosen in Steam. However, there are indeed files at .local/share.

I can't get the game past the initial loading screen.

Can manage to get it to open but it crashes immediately.
This works with Proton 6.3.8 (community build via flatpak) and Proton experimental and GE 7.x (community build via flatpak)

@kisak-valve here's the gist you asked for https://gist.github.com/ChildishhAlbino/a8b87fa10fb175f8f2eab4561d92e7bc :D

Just wanted to gauge if any progress has been made on this issue or if there's a workaround I can try?

Well, is there a solution for my issue?

Well, is there a solution for my issue?

What Distro? How did you start Steam? I had once an issue that Proton games would only start if i start steam from a console. Native games would simply run. You could try that

Well, is there a solution for my issue?

What Distro? How did you start Steam? I had once an issue that Proton games would only start if i start steam from a console. Native games would simply run. You could try that

The distro in question and more info was posted above, but for simplicity sake: EndeavourOS up-to-date.
I started Steam via a shortcut I made and put onto my KDE Plasma task manager.
The issue only exists on Yakuza 0, and there seems to be no difference with starting Steam via terminal.

EDIT: Nope, nothing changed when trying to run it via terminal. RotMG Exalt, for instance, runs flawlessly.

Well, is there a solution for my issue?

What Distro? How did you start Steam? I had once an issue that Proton games would only start if i start steam from a console. Native games would simply run. You could try that

The distro in question and more info was posted above, but for simplicity sake: EndeavourOS up-to-date. I started Steam via a shortcut I made and put onto my KDE Plasma task manager. The issue only exists on Yakuza 0, and there seems to be no difference with starting Steam via terminal.

EDIT: Nope, nothing changed when trying to run it via terminal. RotMG Exalt, for instance, runs flawlessly.

I missed the part about your system, my bad. In the past I had to do a little workaround for some titles but especially Yakuza 0: https://github.com/ValveSoftware/Proton/issues/492#issuecomment-605429005

The issue hasn't been fixed, even after attempting to downgrade my Vulkan packages.

@MephresGH

I'm just shooting in the dark here - but according to your logs, you're running the game on an external medium/mount (/run/media/...).
Is this by any chance an NTFS partition of eg. a dual-boot system? I know I had a lot of trouble with some other games not working well with non-native filesystems. Have you tried reinstalling Yakuza 0 to the default volume used for steam (~/.local/share/Steam)?

@TheTee82

No, all my drives are ext4, while my Linux drive is btrfs.
There is a bit more information that I forgot to mention, though:
My game crashes all the time when the SEGA intro should play.
This might be helpful

I wanted to chime in here to say that I am no longer able to install this game in Linux. The same goes for Teenage Mutant Ninja Turtles: Out of the Shadows for some reason

Game runs perfectly out of the box after installing via Steam, no tweaking or special steps required.
Beat the game and all substories (approx 200 hours played).

CPU: AMD Ryzen 7 3800X
GPU: AMD Radeon RX 6700 XT
Distro: Fedora 36
Proton version: Proton Experimental (set via Steam settings for all games in library)
Steam System Info: https://gist.github.com/CorruptComputer/f164c2d48606808dbfbc07ee8810efd5

@faedy2 Make sure you have the setting in Steam -> Settings -> Steam Play -> enable Steam Play for all other titles checked?

@faedy2 Make sure you have the setting in Steam -> Settings -> Steam Play -> enable Steam Play for all other titles checked?

Yep

Bought the game today as it looked like it worked on ProtonDB, but doesn't even start.

Crash Log: https://gist.github.com/hausofwong/1dd54faa7b30db4768f13de67a17d5e2
Steam System Info: https://gist.github.com/hausofwong/66bd3ae098c6606ce945fb54e8038227

The logs are from Experimental, but I've tried various iterations of Proton from 5 to the latest and still the same.

@faedy2 Make sure you have the setting in Steam -> Settings -> Steam Play -> enable Steam Play for all other titles checked?

Yep

So... Apparently Steam has a bug where the "Play" button will be grayed out unless you manually choose a Proton version. I chose my installed Glorious Eggroll version, and the game loaded.

After some more digging it looks like it's due to my Optimus laptop.

The solution I found was this: https://github.com/ValveSoftware/steam-runtime/issues/312#issuecomment-739441559

Running on the latest Proton (7.0-4) and disabling the Intel Vulkan driver, as per the solution above, worked for me.

However, just removing the vulkan-intel driver worked for me as I never use it anyway.

Hi All,

I'd like to join in the work and testing. For our use, having everything in
a docker is best.
Would someone be open to a few short emails on a sidebar to help me get up
to speed ?

Many thanks!

On Fri, Oct 7, 2022 at 2:10 AM Luke Wong @.***> wrote:

Bought the game today as it looked like it worked on ProtonDB, but doesn't
even start.

Crash Log:
https://gist.github.com/hausofwong/1dd54faa7b30db4768f13de67a17d5e2
Steam System Info:
https://gist.github.com/hausofwong/66bd3ae098c6606ce945fb54e8038227

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/492#issuecomment-1271329697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWOIRPUBYZ37U2RCUYBAREDWB7SJ5ANCNFSM4FRREQPQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I'm suffering crash to desktop after first loading screen instead of first FMV sequence. Can't play.

Game window appears, loading screen works. FMV sequence does not and causes the CTD.

I seem to be missing the necessary support to display the video sequence, or reason is completely different?

Maybe issue is in the media foundation DLLs?(?)

Running under Proton Experimental but happening under any version, Manjaro on Linux 5.15.91-1. NVIDIA proprietary driver 525.85.05 with GTX 1060 6gb.

Tested also the prior on Kubuntu 22.04 with same result. Stumped.

In particular, system specs are:

AMD Ryzen 5 3600
16gb of DDR4,3000
NVIDIA GTX 1060 6gb

Game installed on LUKS encrypted ext4 partition with huge file path, using same on Kubuntu also.

Which logs are necessary? Is this one?
steam-638970.log

I have run into an issue with Y0 where the emulated arcade games don't run on linux. When you sit down to play them, the screen fades to black and stays that way until you Alt-F4 out of the game. I'm still fairly new to Linux so I'm also new to Proton but I have downgraded to several earlier versions of Proton to no avail.

CPU: AMD Ryzen 7 3700X
GPU: Nvidia GeForce 1060 6GB
Distro: Fedora Kinoite 39
Proton version: Proton Experimental, Hotfix, 8, 7, 6

Yakuza 0 is currently broken with Proton 11, it doesn't get past the loading at the very start.

@kisak-valve I won't be able to give precise and detailed info right now due to being on the road.

This is the useful info I can give right now:

Device: Steam Deck OLED
OS: SteamOS 3.8.5

Which Proton fails: Latest 11.0 Beta (should be Beta 5)
Which Proton works: Latest 10.0 (likely 10.0-4) and latest Proton-GE (likely 10-34)

It will take a bit until I am able to get the Proton log and attach here.

Steam Runtime Diagnostics

@kisak-valve Here you go:

https://gist.github.com/MateusRodCosta/0210cd6ea25c9bf4b8ee0de2e58d4262

And the attached log:

steam-638970.log

Seems everything is fine with Proton 10, whether Valve's or GE's.