Starwars: Squadrons (1222730)

[Karimicus]

Compatibility Report

• Name of the game with compatibility issues: Starwars: Squadrons
• Steam AppID of the game: 1222730

System Information

• GPU: RTX 2060 + UHD Graphics 630
• Driver/LLVM version: Nvidia 440xx
• Kernel version: 5.8.11-1-MANJARO
• Link to full system information report as Gist:
• Proton version: 5.0.9

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Game fails to load, begins loading up Easy Anti Cheat then crashes out with the following error:
Currently your game purchase cannot be re-validated successfully, please wait 24 hours and try again.

STAR WARS © & TM 2020 Lucasfilm Ltd. All rights reserved. Game code and certain audio and/or visual materials © 2020 Electronic Arts Inc. EA, the EA logo, Motive Studios, and the Motive logo are trademarks of Electronic Arts Inc.

https://support.codefusion.technology/pm_980sgk98hnbp/?e=88500006&l=english

Reproduction

steam-1222730.tar.gz
285ea8b10c430d81beb17f0b73773024-39344ba42c9029ebf512299e9e1f0b201846b79d.zip

[kisak-valve]

Hello @Karimicus, EAC in the game is probably going to be a show stopper here.

Looks like the game also uses Denuvo Anti-Tamper, and adding PROTON_USE_SECCOMP=1 %command% to the game's launch options should help with that.

Separately, this looks like a line of interest from the log: err:steamclient:create_win_interface Don't recognize interface name: SteamUser021

[Karimicus]

Thanks @kisak-valve Just attempted launching with the PROTON_USE_SECCOMP=1 %command% however still no luck in launching.

Still looks to attempt launch EAC then crashes out one EAC has finished loading

[Karimicus]

just looking in the log output theres also the following error seen:
ERROR: ld.so: object '/home/karimicus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

looks to be 10 different variants of it

[Leopard1907]

just looking in the log output theres also the following error seen:
ERROR: ld.so: object '/home/karimicus/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

looks to be 10 different variants of it

That is not related. It is about Steam overlay, totally normal behaviour.

[Karimicus]

Thanks @Leopard1907 Fairly new playing games on Linux, doing some searching and looks like it's trying to pull 32bit drivers from what I have come across for those errors.

[Karimicus]

Interesting there seems to be a stackoverflow near the end of the log before Squadrons stops attempting to load:

35908.287:00cc:00d0:err:seh:setup_exception stack overflow 2800 bytes in thread 00d0 eip 00007fac8b7c2c2b esp 0000000000120b20 stack 0x120000-0x121000-0x220000
35931.818:00b8:00bc:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\api-ms-win-appmodel-runtime-l1-1-1.dll" : builtin
35931.818:00b8:00bc:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\api-ms-win-core-sysinfo-l1-2-1.dll" : builtin
35931.818:00b8:00bc:trace:loaddll:free_modref Unloaded module L"Z:\\home\\karimicus\\Personel\\SteamLibrary\\steamapps\\common\\STAR WARS Squadrons\\EasyAntiCheat\\EasyAntiCheat_x86.dll" : native
35931.818:00b8:00bc:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\CRYPT32.dll" : builtin
35931.819:00b8:00bc:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\bcrypt.dll" : builtin
35931.820:00b8:00bc:fixme:font:RemoveFontMemResourceEx (0x87e2f199) stub
35931.823:00b8:00bc:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-appmodel-runtime-l1-1-1.dll" at 0x6de00000: PE builtin
35931.830:00b8:00bc:fixme:ver:GetCurrentPackageId (0x31fe94 (nil)): stub

[GloriousEggroll]

If the game needs EAC, it's not going to work. There is currently no working version of wine or proton that allows EAC to work. As Leopard mentioned the message you're seeing about 32 bit is because steam overlay tries to load both 64 and 32 bit versions of the overlay and accepts whichever one works. It can be ignored.

[Karimicus]

Thanks @GloriousEggroll, just came across you're proton project some nice patches there.

It's interesting as reviewing the Easy anti cheat forums it lists ubuntu 18.04 as one of the support OS's.
SRC: https://www.easy.ac/en-us/support/miscreated/guides/os/

[Leopard1907]

That is for native games , if they want to use EAC. Not Proton ones which means you would be running Windows version of EAC.

[codeman101]

@kisak-valve is right. I bought this game mistakenly thinking it was a remaster of some old star wars because of the familiar word "squadrons" and therefore wouldn't have EAC or denuvo but it's not that at all. Currently requesting a refund.

[gort818]

Anyone tried this yet to launch without EAC? https://www.pcgamingwiki.com/wiki/Star_Wars:_Squadrons#Disable_Easy_Anti-Cheat

[Ape]

@gort818 I tried that, but it says "Unable to initialize SteamAPI". Perhaps it would work if you also run Steam in Wine.

[ghost]

That website can contain incorrect info. Would take a lot of salt with believing running exe direct would actually disable eac.

As GE stated, running this game is probably dead in the water for Wine/Proton. Personally, I would look at it in years but you never know.

[codeman101]

@GloriousEggroll

I think I read this somewhere but was wondering if you could confirm. Is the reason EAC is hard to support on wine because it's running checks against the windows kernel so in theory wine would have to mimic the windows kernel?

Update:
nevermind found my answer. https://www.gamingonlinux.com/2020/06/an-update-on-easy-anti-cheat-support-for-wine-and-proton

[mimattr]

@Karimicus @gort818 @Ape The application appears to launch as expected with Proton Experimental though multiplayer modes will not function due to EAC (anti-cheat software)

A message dialog regarding an "UNKNOWN" AMD driver version is displayed during launch but selecting OK will continue as expected:

System Information

• GPU: RTX 2060
• Driver/LLVM version: NVIDIA 455.45.01
• Kernel version: 5.4.0-58-generic
• Link to full system information report as Gist
• Proton version: Proton Experimental
• SteamVR version: 1.15.16

[Fyro-Ing]

is it ok for VR ?

I play with 5.21-GE, but VR doesn't launch

[mimattr]

is it ok for VR ?

@Fyro-Ing With the exception of multiplayer VR appears to work as expected using Proton Experimental (tested with Valve Index on Ubuntu 20.04 LTS)

[Fyro-Ing]

I didn't know "Proton Experimental"

Great, thx !

[zefrof]

Tried launching (vr and flat) this today with no luck. Steam says the game is running, but nothing shows up. Eventually Steam no longer says it's running. I don't even get the EAC splash or driver warning. It worked on Proton 15.3-4, but 15.3-5 and Experimental aren't working. I'm on PopOs 20.04. Open to suggestions.

[kisak-valve]

Hello @zefrof, 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 put it in a gist, then include a link to the gist in this issue report.

[zefrof]

@kisak-valve for whatever reason the game launched fine with PROTON_LOG=1 %command% and Proton 5.13-5. Worked after I removed the launch option too. I'm guessing a system update fixed something. I've attached the requested files just in case.

steam-1222730.log

System Info

[volkertb]

Will the inclusion of Syscall User Dispatch support in the soon-to-be-released Linux 5.11 kernel be of any help in getting multiplayer to work in this game?

See https://www.phoronix.com/scan.php?page=news_item&px=Syscall-User-Dispatch-Queued

[jp7677]

The single player mode of this game works perfectly in desktop and VR mode on Proton 5.13. With Proton 6.3 it does no longer picks up the VR mode. When starting in VR on Proton 6.3, the Desktop version is started (which works nicely, albeit of course single player only).
Are there any specific useful logs, since this is VR related only, which I could provide?

Work-around for now is to enforce Proton 5.13.

[kisak-valve]

Hello @jp7677, I take it you intended to write Proton 6.3-2? Please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, 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 put it in a gist, then include a link to the gist in this issue report.

[jp7677]

Hi @kisak-valve, yeah, sorry for the typo, fixed. Will do, give me a bit of time to provide the Proton log file. Let me also know if there is an additional interesting wine channel for the VR things, then I can include that one.

[jp7677]

Here are the logs, for both Proton 5.13 and 6.3:
steam-1222730-5.13.zip
steam-1222730-6.3.zip
Let me know if I can assist any further.

I can see the following line in the 5.13, but not in the 6.3 logs:

info:  OpenVR: Compositor interface found

[jp7677]

I can confirm that the VR issue is indeed fixed with Proton 6.3-4 RC as stated here #4821
Thanks a lot!

[tomaszg7]

I'm trying to run the game but it won't start. After initial splash and a message about "UNKNOWN" graphic card, it silently crashes. I tried several Proton versions (including 6.3-5, 5.13-6 and Experimental, as well as GE version 6.12-1) and only result was that I was apparently banned by EA servers for 24h and the game wouldn't even try to start (something about unable to confirm legality of my copy).

There is also the following in my dmesg:

[45349.148702] umip: starwarssquadro[12901] ip:14da13c40 sp:22fba0: SGDT instruction cannot be used by applications.
[45349.148707] umip: starwarssquadro[12901] ip:14da13c40 sp:22fba0: For now, expensive software emulation returns the result.

It is probably related to #2927 but adding clearcpuid=514 didn't change the game behaviour, only made the message disappear. I'm on kernel 5.12.9 in any case, so it shouldn't be an issue.

Proton log
System info

[Fl0ux]

Sometimes, in VR, the game becomes very laggy with something like 64ms frame time. I have to restart the game, so it becomes normal again. I have a similar issue with Arizona Sunshine.

[kisak-valve]

STAR WARS Squadrons won't launch on linux

Issue transferred from #6074.
@drivera73 posted on 2022-08-07T18:58:27:

Compatibility Report

• Name of the game with compatibility issues: STAR WARS Squadrons
• Steam AppID of the game: 1222730

System Information

• GPU: GTX 3090
• Driver/LLVM version: nVidia 515.65.01-0ubuntu0.22.04.1 , Mesa 22.0.5-0ubuntu0.1
• Kernel version: 5.15.0-43-generic
• Link to full system information report as Gist
• Proton version: 7.0-3

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

The log can be found here

Symptoms

EAC window opens, progress bar goes all the way, game exits without errors.

Reproduction

1. Launch the game
2. Watch EAC show up, and go all the way to completion
3. Game stops without error message, no game window is ever shown

Looking at the ProtonDB page for the game it appears that many people are having solid success running it. It also appears to run on the Deck without issue, which suggests it could be something in my installation. I'm well aware this may not be a Proton issue inasmuch as game compatibility, but the lack of a clearer error indication to dig for a solution to the issue could be a Proton issue (I don't know if/how this could be resolved, though).

At any rate, I'm hoping someone with a keener eye than mine can spot what the issue might be.

I've also tried with the two prior Proton versions (6.3-8, 5.13-6) as well as the Experimental one. I have so far abstained from ProtonGE b/c reasons :)

Cheers!