ValveSoftware / Proton

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

Insurgency: Sandstorm (581320) #1651

Open ricardoalcantara opened 6 years ago

ricardoalcantara commented 6 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Insurgency: Sandstorm local game works with a minor framedrop, but runs smooth even on Very High, but does't work for online game because Easy Anti-Cheat will kick you.

Reproduction

Just try online game.

Swivelgames commented 1 year ago

Continue to get kicked when trying to join online due to EAC NullClient error. According to protondb, the game seems to work for some but not others...

privat3dancer commented 1 year ago

@Swivelgames I don't know why this happens, but when it does, I can still fix it by forcing a reinstall of EAC from the setup script. See my comment above: https://github.com/ValveSoftware/Proton/issues/1651#issuecomment-1224906309

Zorrototo commented 1 year ago

Are you sing latest Proton 8 version? Do you have the EAC Runtime installed in Steam? Did you try to remove the prefix to generate a clean one from Proton 8?

jkcdarunday commented 9 months ago

If it helps anyone, I've had EAC Unexpected Error #1 in ArchLinux recently that prevents the game from running when using Steam Native and Steam Runtime.

After looking around for a bit, it turns out that this is because EAC needs a certain patch for glibc in order for it to work (that ArchLinux probably removed recently).

The workaround for me is to use the Steam version from Flatpak that includes its own compatible glibc which is kinda nice as it also gives some degree of isolation/sandboxing.

kisak-valve commented 9 months ago

Insurgency Sandstorm (581320)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7517. @Tune45 posted on 2024-02-23T07:09:11:

Compatibility Report

System Information

I confirm:

Symptoms

issue with alphabet keyboard controls .etc when i would to move fordword i need to press W.but in game these key are unreponsive .and i must press Alt+ W to move forword .maybe Locale or keyboard layout conflict relate idk. My locale is Thai and i have EN-US for default layout and TH,RU and DE(german) on KDE settings (screenshot attached)

i tried to disable all layout and switched to EN_US .issue still persist steam-581320.tar.gz Screenshot_20240222_190048

Tune45 commented 9 months ago

Thanks @kisak-valve i'm new for github and my limited english skill

Tune45 commented 9 months ago

If it helps anyone, I've had EAC Unexpected Error #1 in ArchLinux recently that prevents the game from running when using Steam Native and Steam Runtime.

After looking around for a bit, it turns out that this is because EAC needs a certain patch for glibc in order for it to work (that ArchLinux probably removed recently).

The workaround for me is to use the Steam version from Flatpak that includes its own compatible glibc which is kinda nice as it also gives some degree of isolation/sandboxing.

@jkcdarunday if you on Arch base distro just install glic-eac in AUR .No config needing

Tune45 commented 7 months ago

easy fix without techticual knowlage by switch both locale gui game menu with US insteadd of TH

Swivelgames commented 5 months ago

@Tune45 glibc-eac is upstreamed to Arch's main glibc, so installing glibc-eac usually isn't necessary. However, even after installing glibc-eac (and lib32-glibc-eac), I'm still not able to get it to work.

I've tried:

With and without glibc-eac.

I'm using zen kernel.

Thank you @privat3dancer for your regedit trick; it definitely saved me a lot of time going through all the different Proton versions I tried, before and after installing glibc-eac.

BRS5672023 commented 5 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/1651#issuecomment-2139023742

I don't build glibc-eac myself but I found the package glibc-eac from Chaotic AUR just won't work for me, while the package from Andontie AUR does work...

Revival8697 commented 5 months ago

glibc-eac is upstreamed to Arch's main glibc

It is not.

The patch was removed and haven't been added back since.

However, even after installing glibc-eac, I'm still not able to get it to work.

You also need lib32-glibc-eac btw.

Swivelgames commented 5 months ago

@Revival8697 Yeah, I realized it had been rolled back after the fact, but forgot to update my comment. ๐Ÿ˜…

And, indeed, I also installed lib32-glibc-eac.

However, I posted in #7721 that I found (with the help of someone in the GZW Discord) an old workaround that Star Citizen lug-helper left over in my /etc/hosts. Commenting out or removing this line out in my /etc/hosts fixed the NullClient issue:

127.0.0.1   modules-cdn.eac-prod.on.epicgames.com #Star Citizen EAC workaround

Now EAC can communicate with the EAC servers again, instead of been looped back.

However, I'm now getting the error #1 when the initial EAC prompt pops up. I'll poke more at it tomorrow ๐Ÿ‘

Swivelgames commented 5 months ago

@BRS5672023 Arch's AUR has [lib32-]glibc-eac-bin as well if you don't want to build it ๐Ÿ™Œ

Zorrototo commented 5 months ago

Clean Proton 9 prefix, EAC popup downloads the EAC update, then EAC error appears on screen. Here are the EAC logs: anticheatlauncher.log loader.log Copie d'รฉcran_20240603_141706

Swivelgames commented 5 months ago

Solved. Back to playing again! by reinstalling lib32-glibc-eac + glibc-eac after removing the following from my /etc/hosts from an old workaround that was added for Star Citizen by lug-helper:

127.0.0.1   modules-cdn.eac-prod.on.epicgames.com #Star Citizen EAC workaround

I'll post an update to my ProtonDB entry :+1:

cncz42 commented 2 months ago

still broken, not great considering how behind glibc-eac is by now. Is there a way to use some runtime sanboxing shenanigans to get glibc-eac running only for this game? I'd prefer not to run a seperate steam flatpak instance for this one game

Revival8697 commented 2 months ago

how behind glibc-eac is by now

Like 10 days? You could just modify the PKGBUILD to match the repo one.

cncz42 commented 2 months ago

how behind glibc-eac is by now

Like 10 days? You could just modify the PKGBUILD to match the repo one.

Last update was in july as far as I can tell, either way my main concern is it messes up debug symbols for programming so a system install ain't great since I'd have to containerize everything while debugging.

Revival8697 commented 2 months ago

Last update was in july as far as I can tell

I meant the last update only include 10 days worth of commits.

Anyway, if you want keep it up-to-date, just modify the PKGBUILD to the equivalent commit and checksum.

solenum commented 2 months ago

There's a lot of mixed comments here. I can't get past the launcher just like @Zorrototo, is there any workaround or is the game borked? I see people recommending a variety of libs to install but no clear answer to which specific ones.

Zorrototo commented 2 months ago

Yes I just deleted the old prefix, verified the game files, and started the game, it is exactly the same as last time I checked on Proton 9, and did the same again with Proton Experimental bleeding edge. It is broken.

solenum commented 1 month ago

There's at least a few reports on protondb from the last few weeks of it apparently working with GE/experimental. I've had no such luck no matter what I try, just fails on the launcher as usual. Anyone else made progress?

Revival8697 commented 1 month ago

There's at least a few reports on protondb from the last few weeks of it apparently working with GE/experimental. I've had no such luck no matter what I try, just fails on the launcher as usual. Anyone else made progress?

You need glibc-eac and lib32-glibc-eac on Arch distros.

UsernamesAreNotMyThing commented 3 weeks ago

I'm seeing quite a few reports that this game has apparently stopped working on Steam Deck after the 3.6.19 update (same error code), and I suspect it's related to the above issues with glibc on Arch Linux.

kisak-valve commented 3 weeks ago

Insurgency Sandstorm EasyAntiCheat give Unknon Error #1 after updating to SteamOS 3.6.19 Stable

Issue transferred from https://github.com/ValveSoftware/SteamOS/issues/1697. @positiveoctopus posted on 2024-10-31T00:13:13:

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen.

Games with EasyAntiCheat give Unknown Error #1 when booting up, making them unplayable after the update, works fine if i revert to SteamOS 3.5

Steps for reproducing this issue:

  1. Open a game with EasyAntiCheat, in my case the game is Insurgency Sandstorm which is listed playable on SteamOS
  2. Wait for the EasyAntiCheat Client to load to 100%
  3. It gives an error and you can only exit the game