search

ValveSoftware / Proton

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

Squad (393380) #938

Open felschr opened 5 years ago

felschr commented 5 years ago

When downloading the game ¨Squad¨ from Steam it directly finishes and trying to start the game causes en error: ¨An error occurred while updating Squad (missing executable) {some very long path here}/squad_launcher.exe¨

When I use the inspect game folder option I can see that the folder is completely empty.

https://store.steampowered.com/app/393380/Squad/

kisak-valve commented 5 years ago

Looks like this game has an unused linux depot.

solenum commented 5 years ago

There are a few steam games that have non-functional or otherwise useless Linux ports, the ability to install the Windows version of a game that has a native Linux version would be incredibly useful.

nentibusarchitectura commented 5 years ago

@exezin

I agree completely with this.

Battleblock theater's Linux port only works on Ubuntu 14.04.x, however the Linux version works 100% on wine.

Would be great if on the game properties there was a way to override the Linux version and use the windows one.

zaggynl commented 5 years ago

Unofficial workaround here: https://www.reddit.com/r/SteamPlay/comments/9cuigr/downloadrun_windows_versions_using_proton/

Got as far as near native FPS, funky sound on the shooting range. Multiplayer is kaput as AntiCheat appears broken, bug report at wine: https://bugs.winehq.org/show_bug.cgi?id=44235

Agree with exezin: a dropdown box or radio buttons to switch between Windows and Linux build of a game in Steam would be awesome

zaggynl commented 5 years ago

Am happy to report that Squad multiplayer now works out of the box as per Proton 3.16-6 Beta Reddit discussion: https://old.reddit.com/r/joinsquad/comments/ao8dyl/heads_up_squad_now_runs_perfectly_under_linux_via/

Edit: EAC broke the next day :( http://i.imgur.com/3NnZwYF.png Edit2: Appears to be working again as per: https://old.reddit.com/r/joinsquad/comments/ao8dyl/heads_up_squad_now_runs_perfectly_under_linux_via/egd5805/

Bumbadawg commented 4 years ago

It's free weekend but launching it with 4.2-9 fails with the fact it cannot find /squad_launcher.exe error since it didn't download it. Checking files won't help.

It fails using Native2Proton (also it still runs on 3.16 beta instead of 4.2-9)


[1] Use winetricks on prefix
[2] Install Non-Steam App [Experimental]
[3] Recreate config
[4] Quit
What would you like to do? 0
Please enter the Steam app ID: 393380
Got: Squad
Please enter your Steam username: xxx
Redirecting stderr to '/home/xxx/.steam/steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.
"@sSteamCmdForcePlatformType" = "windows"
Logging in user 'xxx' to Steam Public ...
Logged in OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Error! App '393380' state is 0x212 after update job.
Please select the game executable by number:```
kisak-valve commented 4 years ago

Squad (sudden fps drops)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3071. @aly199 posted on 2019-09-19T23:29:24:

Latest Proton (4.11-5) has Squad dropping fps, from 60-90fps, down to 15fps. It happens sort of every 20-30s, drops for about 5-10s, then gets back to normal, cycling like this through the entire game. Reverting back to Proton 4.2-9, the issue disappears.

Proton 4.11-5 Linux Mint 19.1 (Tessa) NVIDIA Driver 430.4 Kernel 4.15.0-55-generic

kisak-valve commented 4 years ago

Hello @aly199, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

solenum commented 4 years ago

Counter point to the above, I put in a few hours in the game today on the latest Proton (4.11-5) and it runs flawlessly, multiplayer works perfectly as well and I had no issues with the anticheat (this used to play up with Proton)

I do use these launch commands, not sure if they'll make a difference for @aly199

__GL_THREADED_OPTIMIZATIONS=1 PROTON_NO_ESYNC=1 gamemoderun %command%
aly199 commented 4 years ago

@kisak-valve, I've played for some 5 minutes or so, and the generated log file is 1.8GB in size! I mean, I'm willing to upload it through whatever means, but github accepts 10MB maximum.

kisak-valve commented 4 years ago

Ouch, Proton logs compress well, but even in an archive there's a good chance it'll be larger than github is happy with.

aly199 commented 4 years ago

Yep. 113MB was the best gzip could do. I've uploaded the compressed file to pcloud. Here's the link.

kisak-valve commented 4 years ago

Not that it helps with diagnosing the perf issue, but debugstr is very active with lines like 4460.245:0033:0034:warn:debugstr:OutputDebugStringA "[2019.09.20-22.02.28:146][ 0]LogPackageLocalizationCache: Warning: Skipping the cache update for the package asset groups due to a cache request from a non-game thread. Some localized packages may be missed for this query.\r\n" 4460.246:0033:0034:warn:debugstr:OutputDebugStringA "[2019.09.20-22.02.28:147][ 0]LogPackageLocalizationCache: Warning: Skipping the cache update for 3 pending package path(s) due to a cache request from a non-game thread. Some localized packages may be missed for this query.\r\n" 

grep "Warning: Skipping the cache update" steam-393380.log | wc -l
90520

This along with the seh lines that fire off with it makes up the majority of the log.

aly199 commented 4 years ago

Oh, I had to do some other stuff here, and forgot to mention: I'm running Steam on a firejail, with an overlay-fs. Don't know if it has something to do with anything, but thought I should mention it. It probably doesn't matter, since the game ran on Proton 4.2-9 without any hiccups, under the same circunstances.

HarleyLorenzo commented 4 years ago

I'm unable to run Squad suddenly due to EAC. No one else is having this issue that I can see. Running on the latest Proton 4.11-7 on Ubuntu 19.10. When I launch the game, it tells me that EAC could not initialize a game client and subsequently, I could not join any online servers.

zaggynl commented 4 years ago

I'm unable to run Squad suddenly due to EAC. No one else is having this issue that I can see. Running on the latest Proton 4.11-7 on Ubuntu 19.10. When I launch the game, it tells me that EAC could not initialize a game client and subsequently, I could not join any online servers.

Working for me on 1570630972 proton-4.11-7, using Ubuntu 18.04. There was a Steam outage yesterday, maybe it was related? https://twitter.com/SteamStatus/status/1188893289409400832

HarleyLorenzo commented 4 years ago

I'm unable to run Squad suddenly due to EAC. No one else is having this issue that I can see. Running on the latest Proton 4.11-7 on Ubuntu 19.10. When I launch the game, it tells me that EAC could not initialize a game client and subsequently, I could not join any online servers.

Working for me on 1570630972 proton-4.11-7, using Ubuntu 18.04. There was a Steam outage yesterday, maybe it was related? https://twitter.com/SteamStatus/status/1188893289409400832

Still not working. It worked before I reinstalled Ubuntu on this new disk (but with no other hardware changes) and I know others still have it working. I'm tempted to spin up the debugging and see what's wrong.

Byter09 commented 4 years ago

Wanted to play again since the last time two weeks ago. Same problem. Game runs fine but shows a little popup with: EasyAntiCheat Error: Failed to create IGameClient instance!

The game has not updated in these two weeks and as far as I can see only proton updated in that time (I saw it shortly in my download list downloading 4.11 (or an update for it?)). Anyway, its practically borked now, cause without EAC you can not play on any of the public servers.

Update: I nearly forgot to mention, that I ran WINEPREFIX=~/SteamLibrary/steamapps/compatdata/393380/pfx/ ./EasyAntiCheat_Setup.exe which surprisingly worked and I could select "repair". Though sadly without any success.

BRMateus2 commented 4 years ago

Fresh install by Steam (without Proton) still with the empty repo.

With Proton 4.11-9 it works perfectly fine after deleting the Movies folder (Proton does not have the needed codec), except for the Easy Anti Cheat/EAC which intermitently stopped working since Alpha 16 was launched.

EasyAntiCheat Error: Failed to create IGameClient instance!

Current version is 17.

antimech commented 4 years ago

Hello guys. I'm playing >20 hours online with zero configuration. I'm kinda lucky.

Current version: Beta v18.0.5 Proton: 4.11-11 Distro: Linux Mint 19.2 Tina Kernel: 5.3.0-24-generic RAM: 16 GB GPU Driver: NVIDIA 440.44 GPU: NVIDIA GeForce GTX 1070 CPU: Intel Core i7-6700K @ 4.00GHz

This game is still laggy however.

BRMateus2 commented 4 years ago

Beta v18.0.5 has EAC working back, finally. But you have to run it multiple times until it does not show the EAC error.

Byter09 commented 4 years ago

I can sadly not confirm @BRMateus2's results. I verified my game data, deleted the prefix to have a fresh start and I still get the EAC GameClient error even after starting it 10 times in a row. I'm open to suggestions for what else I could try...

Current version: Beta v18.0.5 Proton: 4.11-11 Distro: Manjaro Linux x86_64 Kernel: 5.4.6-2-MANJARO RAM: 16 GB GPU Driver: X.Org Radeon RX Vega (VEGA10, DRM 3.35.0, 5.4.6-2-MANJARO, LLVM 9.0.0) Driver Version: 4.5 (Compatibility Profile) Mesa 19.3.1 GPU: AMD ATI Radeon RX Vega 64 CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

greymood09 commented 4 years ago

@Byter09 What DE are you using? lxde on arch gave me a startup error but switching to lightdm got rid of the startup error.

Byter09 commented 4 years ago

@greymood09 I'm using KDE. Does something like this really have that much impact? Wow.

Stumpftopf commented 4 years ago

Since I use Mesa 19.3 I have randome crashes.

My System:

System: Host: stumpftopf-pc Kernel: 4.19.92-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.14.1 Distro: Manjaro Linux CPU: 8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 1884 MHz min/max: 2200/3700 MHz Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.6 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 590 Series (POLARIS10 DRM 3.27.0 4.19.92-1-MANJARO LLVM 9.0.0) v: 4.5 Mesa 19.3.1 Drives: Local Storage: total: 1.59 TiB used: 822.63 GiB (50.5%) Info: Processes: 317 Uptime: 29m Memory: 15.66 GiB used: 2.76 GiB (17.6%) Shell: zsh inxi: 3.0.37

Proton-Log:

Unhandled exception: page fault on write access to 0x7f7d303f0000 in 64-bit code (0x00007f7d08ec06bd).
00cd:fixme:dbghelp:elf_search_auxv can't find symbol in module
Register dump:
 rip:00007f7d08ec06bd rsp:000000001463f890 rbp:00000000fffffffc eflags:00010283 (  R- --  I S - - -C)
 rax:00007f7d303cd000 rbx:0000000000000009 rcx:00007f7cf011047c rdx:0000000000023000
 rsi:00000003fffffff0 rdi:00007f7d303cd001  r8:00007f7cf001dfb0  r9:0000000000000001 r10:0000000000000009
 r11:0000000000000000 r12:00007f7cf01121c0 r13:00007f7cf0110458 r14:00007f7cf0110458 r15:0000000000000001
Stack dump:
0x000000001463f890:  0000000000000001 000000001463f950
0x000000001463f8a0:  0000000000000000 00007f7d00000000
0x000000001463f8b0:  00000002001d6000 0000000000014000
0x000000001463f8c0:  00007f7cf001dfb0 93c825bd001f3b00
0x000000001463f8d0:  0000000000000000 000000006a59e380
0x000000001463f8e0:  000000006a59f4f0 00007f7cf010eea8
0x000000001463f8f0:  00007f7c8c2030a8 00007f7b76d4b3d8
0x000000001463f900:  00007f7cf01116a8 00007f7d08e39d5a
0x000000001463f910:  0000000000000000 00007f7cf010eea8
0x000000001463f920:  00007f7cf010eea8 000000001463fa30
0x000000001463f930:  00007f7cf01116a8 00007f7c8c2030a8
0x000000001463f940:  00007f7c94243198 00007f7d08cd3041
Backtrace:
=>0 0x00007f7d08ec06bd vkCreateInstance+0xffffffffffffffff() in amdvlk64.so (0x00000000fffffffc)
0x00007f7d08ec06bd vkCreateInstance+0xffffffffffffffff in amdvlk64.so: movups   %xmm0,(%rax,%rdx,1)

steam-393380.log.zip

kisak-valve commented 4 years ago

Hello @Stumpftopf, a crash in amdvlk64.so sounds like a video driver issue in AMDVLK instead of mesa.

Stumpftopf commented 4 years ago

@kisak-valve Yes you are right. It was AMDVLK. Seams to be fixed after i installed some extra Packages: sudo pacman -S vulkan-icd-loader lib32-vulkan-icd-loader sudo pacman -S vulkan-radeon lib32-vulkan-radeon I am not sure now if i realy used amdvlk before and not the amdgpu vulkan implementation.

imaami commented 4 years ago

Getting the IGameClient error from EAC. Nothing seems to help.

imaami commented 4 years ago

I found a janky fix to the EAC IGameClient instantiation error:

  1. Delete the Squad wineprefix;
  2. switch Squad to use Proton 4.11;
  3. start Squad to recreate the wineprefix (this also installs EAC);
  4. exit Squad;
  5. switch Squad back to using Proton 5.0;
  6. start Squad again to upgrade the wineprefix to 5.0 - EAC should now work normally.

@Byter09 can you try this?

Heads up, Valve, there might be a regression in 5.0.

Byter09 commented 4 years ago

@imaami Followed your instructions:

So... no idea what I'm doing wrong :(

Also another quick note: I have reinstalled my setup since then and yeah the error is still there. Just thought this could help reduce the search area for the bug.

imaami commented 4 years ago

@Byter09 You need to first delete the wineprefix dir. Depending on where you've installed Squad it could be $HOME/.steam/steam/steamapps/compatdata/393380. In my case it's /opt/steam/steamapps/compatdata/393380, but you get the idea. Delete the dir called 393380, that's the wineprefix.

After you've done that switch to the older version. Start and exit Squad. Switch to the new Proton version, start again.

Deleting the wineprefix is a key part of this because otherwise EAC won't be reinstalled. You need to start from scratch when you do the first run with 4.11-13.

kinetic5 commented 4 years ago

@imaami Tried your instructions exactly also, no luck.

Operating System: Manjaro Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.5.11-1-MANJARO

Byter09 commented 4 years ago

@imaami Sorry I forgot to mention it. I of course did that. I updated the original comment to reflect that.

imaami commented 4 years ago

@imaami Sorry I forgot to mention it. I of course did that. I updated the original comment to reflect that.

Could you try with these additions/changes:

The above should pretty much 100% replicate my first successful trick yesterday.

@ryangodfrey Could you try those as well?

PS: I've heard back from one person on Reddit who was able to fix his EAC with my instructions yesterday, so I don't know how arbitrary it might be to be lucky. I'm sure this thing will get solved eventually, now we at least have some clue for where to hunt for the bug.

Byter09 commented 4 years ago

Alright. I'm writing this comment as I go to not forget anything and give you as much information as I can on this.

I was really hoping this would work. :sob:

ipimpat commented 4 years ago

Game starts on first attempt, but with EAC error, but works after switching Steam Play compatibility tool version to previous version and back to newest as suggested here.

Game runs at about 80-90 FPS, but drops after a few minutes to about 5-30 FPS and stays there, but with the PROTON_NO_ESYNC=1 this was only periodic (tested in one match)

Game is not playable !

Proton: 5.0-6 OS: Linux Mint 19.3 Tricia KERNEL: 5.6.7-050607-generic CPU: Intel Core i7-7700K @ 4.20GHz GPU: AMD NAVI10 GPU DRIVER: 4.6 Mesa 20.0.5 - kisak-mesa PPA RAM: 32 GB

steam-393380.log.gz

BRMateus2 commented 4 years ago

I actually found the culprit - EAC is actively trying to detect Wine and there is a possibility the Squad devs are building against Wine, as there are some past builds that worked without any single problem versus the Windows counterpart, it might be an "tick Wine detection or not".

I have another game that runs with EAC that works flawless, its EAC dlls don't have any Wine function using the strings command, but Squad has the well known (#1, #2) little problem.

LogEasyAntiCheatServer: Warning: Failed to locate EasyAntiCheat server library eac_server64.dll LogEasyAntiCheatClient: Error: Failed to create IGameClient instance!

strings EasyAntiCheat_x64.dll | grep wine wine32 wine64 wine_get_version wine_x86 wine_x64

It might not be a regression in Proton as older Protons don't even run the game anymore. I tried the steps below and strangely there are some (interface? hardware?) combinations that seems to work (do they break the EAC check?), but I could not get Squad to run with EAC at all with my Fedora 31 KDE, DXVK and Mesa.

Delete Squad (393380) Wine Prefix: rm -r "$HOME/.steam/steam/steamapps/compatdata/393380" Switch Proton to use Proton-i-4.13-3. Move the Movies folder so it does not crash the game (by not having codecs): mv "$HOME/.local/share/Steam/steamapps/common/Squad/SquadGame/Content/Movies" "$HOME/.local/share/Steam/steamapps/common/Squad/SquadGame/Content/Movies.backup" Run the game until menu, then exit and kill all Squad instances (killall --signal SIGHUP "squad_launcher.exe" "SquadGame.exe"). Switch Proton to use Proton-5.4-GE-3 and run the game until menu.

ipimpat commented 4 years ago

Good news - things for me have changed from not playable to playable with issues.

I have actually being playing Squad for a couple of hours now, two days in a row - still no EAC issues what so ever, and that's very positive - thanks to the people who made that possible !

I think I have gotten the general stuttering under control by installing the XanMod Linux kernel which includes the fsync patch - getting around 80-95 FPS.

But sometimes the FPS still drops to 5-10 and stays there only to return to normal a little later.

I noticed while that is going on, my video cards VRAM is nearly maxed out and and I verified that the Full Texture Loading option was not actually turned on.

Here is a screenshot of "radeontop" while Squad is running and the frame dropping issue is going on:

amdgpu The video card model is a GIGABYTE Radeon RX 5700 XT GAMING OC 8GB

I have also had weird AMDGPU graphics driver crashes - I have experienced everything from complete system lock ups, to screens turning off or and then turning on, but only displaying green, and one time Squad crashed and my screens turned off and on again, and when the desktop environment restarted/recovered from that event, there were strange artifacts/colored pixels all over the screens.

Here is a log of one of those events (when that event occured I was running 5.6.7 Ubuntu mainline Linux kernel)

amdgpu_crash_10-04-2020_1447.log

NGGJamie commented 4 years ago

Used @imaami's instructions and had the game working yesterday without issues, not even lag. However, today I began to experience intermittent crashing(via freeze), and tried to work the issue out. This ended in seemingly having EAC re-install itself via steam and breaking the anti-cheat.

Replicating the steps I did the first time, attempting to install EAC in 4.11.13 has had no luck in getting the anti-cheat to run, though the crashing seems to be gone in training. I've also attempted using a newer version of GE's proton instead of the GE 5.6 I was using previously to no avail, as well as imaami's build of proton 4 posted above. I have not, as of yet, successfully gotten the anti-cheat to run again. Notably, between each failed attempt, I have deleted the compatdata directory for Squad, prefix included.

OS: Arch Linux x86_64 Kernel: 5.6.13-arch1-1 CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1080 Memory: 4112MiB / 32057MiB

aCeTotal commented 4 years ago

I have tried everything to make this work. I hope someone will find a fix for this soon! <3 It is probably the latest Squad Patch.

Avionyx commented 4 years ago

I've been trying for several days to get this working, following all the steps detailed here and no luck, same popup every time. It's a shame as Squad was running flawlessly until about 8 days ago.

aCeTotal commented 4 years ago

New patch out today. Something about EAC Index. Crossing my fingers.

BRMateus2 commented 4 years ago

New patch out today. Something about EAC Index. Crossing my fingers.

Please report back because I even uninstalled.

Byter09 commented 4 years ago

I removed the prefix and tested again with B19.4.2. Same error message.

:disappointed:

Avionyx commented 4 years ago

Have just tried again, after a 55MB update and still the same EAC error, unable to play online.

aCeTotal commented 4 years ago

Please add a report at https://www.protondb.com/app/393380

sticsk commented 4 years ago

Yeah I did, I said about the IGameClient error, Jensen's works (which is Local I presume) but any EAC protected Servers tell me that I need to activate the Anti-Cheat

simonvanderveldt commented 4 years ago

@imaami Is the game/your workaround still working for you?

imaami commented 4 years ago

@imaami Is the game/your workaround still working for you?

Yes, the game is still working. I haven't had to wipe the prefix or game files in a while because I haven't had problems. I don't know what would happen if I wiped them and reinstalled, and I'm not going to risk it if I don't absolutely have to. :)

I did get the error message once when I launched Squad, but I closed & restarted the game and it worked again. The only difference at that time was that I accidentally switched to another workspace soon after pressing "Start" in Steam. I wonder if the launcher gets confused in some situations where the game client and the EAC launcher window are not on the same workspace (virtual desktop).

My current graphics fullscreen setting is borderless fullscreen window, btw, not the "real" fullscreen mode. Maybe that can have some effect.

My window manager is i3, and I have the Steam client bound to workspace 3. Whenever I launch Squad I make sure I don't switch between workspaces until the game is fully loaded. I don't know if this is just a ritual based on coincidental experiences, but I've gotten the impression that things get weird if Squad or EAC (or Proton) aren't focused 100 % during launch. Could it maybe be related to the alt-tabbing bug where mouse events aren't captured after returning focus to the game window?

Just thinking out loud here. I suggest sacrificing a chicken just in case, we all know that the EAC gods who live in volcanoes are fickle and demanding.

NGGJamie commented 4 years ago

I'd caught a reddit thread a few weeks ago that claimed uninstalling EAC through wine uninstaller and reinstalling it had a chance to make it work. I didn't bother to mention it here because the claim was never really substantiated. It may truly just be a matter of playing the odds and hoping you get a lucky draw.