Compatibility Report

UPD.
The good news: The game now start and it possible end the tutorial.
The bad news: Any match ended after one minute. I suppose it related to anticheat issue.

steam-872200.zip

Good news, they migrated to EOS eac and enable linux module. The only downside is steam overlay doesn't work with version of eac.

Edit: If eac failed to load anti cheat module, try to use steam flatpak

Good news, they migrated to EOS eac and enable linux module. The only downside is steam overlay doesn't work with version of eac.

Edit: If eac failed to load anti cheat module, try to use steam flatpak

I need to use steam flatpak to play, but when I play I have audio issues. There is an audio buzz and most sounds don't play. I occasionally hear sound, including footsteps, but the key word is occasionally. Most of the time, I hear nothing, which makes the game somewhat unplayable given that gameplay is heavily dependent on hearing the footsteps of other players.

I also have stutter every time I kill an opponent. :/

https://github.com/doitsujin/dxvk/issues/2643

I just filed an issue with DXVK regarding the stutter problem. It is highly reproducible inside the shooting gallery.

Any idea why it only works with the flatpak ?

Any idea why it only works with the flatpak ?

Would like to solve this too, I've seen a report on SteamDB of a user who seemingly launched the game on Linux Mint without flatpak.

But I can't get the game to launch without flatpak either (I'm on Arch)

Any idea why it only works with the flatpak ?

Would like to solve this too, I've seen a report on SteamDB of a user who seemingly launched the game on Linux Mint without flatpak.

But I can't get the game to launch without flatpak either (I'm on Arch)

To add up to this:

I've searched around a bit and it may be glibc causing the issues.
I run Arch and have glibc version 2.35 installed, the flatpak uses 2.33.

Just a wild guess tho because some gentoo users reported an issue regarding EOS and glibc as seen here: https://forums.gentoo.org/viewtopic-p-8693987.html?sid=50844f96bd5faab2547370ca53b7d652

The same fix is probably required for the Arch packages?

Edit: Okay after checking the fix-commit mentioned in the gentoo thread I'm not sure if this is a glibc issue anymore since the fix for it was committed a month before the latest glibc version on arch was released, so it seems like it should already be included in the latest arch package if I'm not mistaken

I did more research. It turns out that the game works in a Ubuntu 20.04 chroot, but not in a Ubuntu 22.04 chroot. My audio issues turned out to be related to noise torch, and disabling it fixed them. The stutter on an opponent's death is almost non-existant with a Ubuntu 20.04 chroot. I documented the specifics of how I setup the chroot here:

https://github.com/anyc/steam-overlay/issues/313

I am not sure if the issue is the glibc version, but it would be fairly trivial to upgrade glibc inside the ubuntu chroot to see if that breaks the game. However, before doing that, I would prefer to test ubuntu 21.04 and 21.10 to see if it works on either of them. Call it the equivalent of git bisect on the distribution level. ;)

Also, these findings would strongly suggest that the EOS EAC used by this game is broken on the steam deck, so when we find out how it is broken, Valve should be able to raise an issue with Epic to get this fixed.

For those interested there's some discussion going on about the flatpak thing over here:
https://github.com/anyc/steam-overlay/issues/313

Replying to https://github.com/ValveSoftware/Proton/issues/5214#issuecomment-1132281764

That glibc issue was Gentoo specific and the fix was already present on my system when Rogue Company's proton support was turned on by the developer.

For those interested there's some discussion going on about the flatpak thing over here: anyc/steam-overlay#313

Those would be my latest findings on this. I posted an abridged version two comments above yours. ;)

I hope to do some more with this in the evening EST today.

Replying to https://github.com/ValveSoftware/Proton/issues/5214#issuecomment-1132281764

That glibc issue was Gentoo specific and the fix was already present on my system when Rogue Company's proton support was turned on by the developer.

Maybe there's a regression in the glibc package, but I'm certain it's some dependency like glibc or maybe something like zlib, that had issues with CRC too a while back

Replying to https://github.com/ValveSoftware/Proton/issues/5214#issuecomment-1133148151

It is a regression in glibc. I was able to install glibc versions from newer versions of ubuntu in my 20.04 chroot. 2.33 from 21.04 worked fine, but 2.34 from 21.10 broke Rogue Company. My guess is that some change made between 2.33 and 2.34 broke it.

Also, this would suggest that it works as long as glibc is version 2.33 or older. Now to figure out how to git bitsect glibc in the least painful way possible. :/

@GloriousEggroll volunteered to do the bisect and found that these patches need to be reverted in glibc 2.34 and later to make Rogue Company's EAC happy:

• 8208be389bce84be0e1c35a3daa0c3467418f921
• 6bf789d69e6be48419094ca98f064e00297a27d5
• b89d5de2508215ef3131db7bed76ac50b3f4c205
• 86f0179bc003ffc34ffaa8d528a7a90153ac06c6
• 7a5db2e82fbb6c3a6e3fdae02b7166c5d0e8c7a8

I have my own revert against glibc 2.35 here:

http://dpaste.com/FC5GVYB2K

I have tested this on Gentoo and it appears to let Rogue Company work. Note that needs to be rebased before it will work against glibc 2.34.

The last I heard, GloriousEggroll planned to do more testing. I also need to do more testing. However, this discovery should be enough for Valve to raise an issue with Epic asking them to fix the issue affecting the EAC version used by Rogue Company.

Any further updates on this issue?

The game crashes after playing a sponsored video and keeps kicking me out of the match, even with glibc-eac installed.

one issue : trying to apply the patches on Ubuntu causes a broken glibc and an unbootable system, tried removing other patches, applying the patch then making a diff, pulling the patch from tkg, nobara, all lead to the same result, heck one time i even rewrote the entire debian build process for it to more closely resemble tkg glibc and other distro, and without the patch it freaking worked perfectly, apply the patch and you can't boot!