search

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.

Zorrototo commented 2 years ago

Here on Manjaro, Testing branch, with kernel 5.15, default Steam, and Proton 7.0, everything seems to work. Try to reset everything to default, delete the prefix, and try again.

Irets commented 2 years ago

Hi, @daugustin. I can confirm that.

Apex EAC works on my system also, but that is likely because they're using a different implementation of EAC. Apex Legends uses easyanticheat_x64.so, which Insurgency: Sandstorm doesn't. Insurgency: Sandstorm uses the EOS version of EAC, which provides the splash screen among other things.

If you were to launch Apex without EAC, you'd get into the main menu no problem, but the game would create a notification and boot you back out later, while EOS wouldn't let you launch the game at all.

@Zorrototo The only thing that I've not yet "reset", is to launch Steam with --reset. I might try that on my laptop later, as it also has the same issue as my desktop computer and runs the same Linux distribution.

So far we have three reports of Gentoo systems that are unable to launch Insurgency: Sandstorm.

sketch54 commented 2 years ago

I'm on Ubuntu and have just gotten it to work. The only major change I made to make it run was switching to Proton Experimental and it runs well. The only issue I'm getting is only sometimes it will have difficulty starting and getting passed the main loading screen. However I reckon this is due to having FSR enabled, and it doesn't bother me much since this is a rare occurrence and the game typically starts as usual. I'm starting to wonder if this only works on certain distributions. Like I've said before, most users that have gotten it to work on protondb.com are on Arch or Ubuntu-based distros.

privat3dancer commented 2 years ago

@sketch54 Yes, it also takes around 2 - 4 tries to launch fully. It shows a splash screen and then yields zombie processes. Stop from steam and try again repeatedly until it fully launches. I saw the same behavior when we had a brief EAC "alpha" (possibly accidental) last November, so my feeling is that this may not be EAC. I'm attaching a proton log, although I haven't tried to delve into it. It feels a lot like a failure to go fullscreen.

steam-581320_crash.log

abienz commented 2 years ago

I don't have Insurgency: Sandstorm (yet) but I do have Elden Ring, and what you've just mentioned with the game needing a few tries at loading before it works is a very similar problem between the two games.

StuntVist commented 2 years ago

@Irets make that four. Have been unable to launch the game on Gentoo as well, with the same "failed to load anti-cheat module" error. Apex Legends works fine. Can't say anything about other EAC EOS games as Insurgency Sandstorm is the only game with that implementation that I own.

Is there still no solution other than using the flatpak version of steam on Gentoo?

daugustin commented 2 years ago

I tried a lot of things, even stracing it, couldn't find anything why it doesn't launch EAC. If you want to checkout the game, you can launch "Insurgency.exe" instead of "InsurgencyEAC.exe" (e.g. with steamtinkerlaunch). I was hoping this would still launch EAC in the background or something, but this is indeed the "offline" version. You can try the game and play against bots - the game itself works fine.

abienz commented 2 years ago

@daugustin, I just picked this up yesterday and have had a few games with EAC enabled, I did find that using the default Proton compatibility mode didn't launch the game (The EAC popup started and then nothing), but I switched to GE-Proton7-5, which is what I'm also using for Elden Ring and it launches just fine, no other command arguments used.

fayaaz commented 2 years ago

Insurgency was working great for me up until a week or so ago. Not sure what changed but now I just get a black screen after the initial EAC and sandstorm logo here's my logs:

==> .steam/steam/logs/connection_log_7777.txt <==

[2022-04-28 17:31:38] CCMInterface::OnConnectivityTestResult -- Start connecting to Steam

==> .steam/steam/logs/connection_log.txt <==

[2022-04-28 17:31:38] Connectivity test: Starting test, fetching 'http://test.steampowered.com/204'
[2022-04-28 17:31:38] [3,3] StartVoiceRecording() (was recording: 0)
[2022-04-28 17:31:38] [3,3] StopVoiceRecording() (was recording: 1)
[2022-04-28 17:31:38] Connectivity test: OK!
[2022-04-28 17:31:38] Connectivity test: result=Connected, in progress=0

==> .steam/steam/logs/content_log.txt <==
[2022-04-28 17:31:38] Game 581320 no longer tracking PID 137392
[2022-04-28 17:31:38] Game 581320 adding PID 137489 as a tracked process

==> .steam/steam/logs/stats_log.txt <==
[2022-04-28 17:31:38] [AppID 581320] CAPIJobRequestUserStats - no stats data in server response, we must be up to date

==> .steam/steam/logs/systemmanager.txt <==

[2022-04-28 17:31:38] Initializing System Manager
[2022-04-28 17:31:38] Node mode active on resume 0
[2022-04-28 17:31:38] wifi power management: 1
[2022-04-28 17:31:38] Error: BYieldingRunJob: failed to query system battery state

==> .steam/steam/logs/connection_log_7777.txt <==
[2022-04-28 17:31:40] IPv6 HTTP connectivity test (ipv6check-http.steamcontent.com / [2a01:bc80:8:103::9b85:fc12]:80 ([2a01:bc80:8:103::9b85:fc12]:80)) - TIMEOUT
[2022-04-28 17:31:40] IPv6 UDP connectivity test (ipv6check-udp.steamcontent.com / [2a01:bc80:c:103::9b85:e232]:27019) - SUCCESS

==> .steam/steam/logs/systemmanager.txt <==
[2022-04-28 17:31:40] Error: BYieldingRunJob: failed to query system battery state

==> .steam/steam/logs/configstore_log.txt <==
[2022-04-28 17:31:40] Flushed store 'install' to '/home/fayaaz/.local/share/Steam/config/config.vdf'

==> .steam/steam/logs/systemmanager.txt <==
[2022-04-28 17:31:42] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:44] Error: BYieldingRunJob: failed to query system battery state

==> .steam/steam/logs/custom_log.txt <==
[2022-04-28 17:31:44] IssueClientServiceCall: 25128992 ac9916fb 4 3

==> .steam/steam/logs/systemmanager.txt <==
[2022-04-28 17:31:46] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:48] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:50] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:52] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:54] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:56] Error: BYieldingRunJob: failed to query system battery state

Not sure if these are important:

Error: BYieldingRunJob: failed to query system battery state
IssueClientServiceCall: 25128992 ac9916fb 4 3
Zorrototo commented 2 years ago

Did you try to delete the prefix folder, and use the normal Proton7 or Proton Experimental? It is working properly on my side I just checked.

fayaaz commented 2 years ago

Did you try to delete the prefix folder, and use the normal Proton7 or Proton Experimental? It is working properly on my side I just checked.

Thanks that solved it! Using Proton Experimental and launch options:

mangohud %command%  -nominidumps -dx12

Edit: I had to use GE-Proton-7-15 to get the first time DirectX install to work properly.

xDShot commented 2 years ago

Getting black screen as well. Clearing compatdata didn't help, commandline options above didn't help either.

panzerlop commented 2 years ago

tried the launch options suggested above, tried disabling shader pre-caching, tried proton-GE and Proton Experimental, stuck on the launch banner, the EAC logo shows but moves very slowly in the bottom left of the banner, game doesn't launch, right side of banner stuck on "initialising", no .so easy anticheat file that I can see in the steamapps folder but there is a windows exe, just to note: Apex legends runs perfectly for me and I'm using Nvidia 515.48.07 driver

Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-41-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

abienz commented 2 years ago

Yes no longer working for me either, I have been playing regularly until August, and after recent updates I get an error on the Splash Screen as EAC is initialising.

Launch Error Failed to load the anit-cheat module.

I have tried the suggestions above with file validation and prefixes, and I have tried GE Proton 7.5, GE Proton 7.29 and Proton Experimental

puresick commented 2 years ago

It stopped working for me with the lateste Proton experimental update. Now the game crashes before joining a server.

journalctl -p 3 -b outputs this for me: image

[🡕] Process 5289 (InsurgencyClien) of user 1000 dumped core.

Stack trace of thread 5290:
#0  0x0000000000000000 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

I am on Arch with Linux 5.19.3-arch1-1 and amdgpu driver. My launch options are DXVK_ASYNC=1 mangohud %command% -nominidumps

It works with Proton 7.0-4, but there are quiet some lags which I assume are due to texture and shader loading which were not that bad in Proton experimental.

privat3dancer commented 2 years ago

@abienz

So, I've never had EAC load reliably, but I'll give you two hacky workarounds that generally have worked (and continue to work, since nobody seems to be patching this).

Trick 1: Use the script linked here: https://github.com/ValveSoftware/Proton/issues/1328#issuecomment-511651465

Which I run as follows to load regedit: ./protoncfg.sh 7.0 581320 regedit

Yes, I'm using Proton 7.0 as well. In regedit, delete the following keys:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Valve\Steam\Apps\sandstorm_EOS_anticheat
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Valve\Steam\Apps\581320
HKEY_LOCAL_MACHINE\Software\Wow6432Node\EasyAntiCheat_EOS

Close regedit. Then retry launching from Steam. Steam will reinstall EAC in the winedir. I have to do this more often following patches, although that might be psychosomatic. (I should probably be crediting someone somewhere on the internet for this trick, but I can't recall who or where it was.)

Trick 2: ...And this is going to sound a little bit ridiculous, but here goes. The vast majority of attempts to launch the game show only the first splash screen but not the second, and the game is stuck in some state that doesn't generate error messages but also does not kill itself or load any further. You have to kill the processes manually or from steam. However, if I load a youtube video or do something else that adds a little bit of graphics lag as it attempts to load past the first splash screen, the game loads the second splash much more reliably and continues to launch normally. Last time I tried to spend a few minutes on it, it seemed like there might be a race condition in finding the game window...

Good luck all.

EDIT: I realized that the version of the bash script I'm using seems to be available only off site, so I'm going to paste it into a gist here. Credits to the link above: https://gist.github.com/privat3dancer/965f976ca7990e2a04e1856a22073fe2

Zorrototo commented 2 years ago

LOL that's the script I made from pieces and bits from the internet :D here is the source http://gromano.fr/bludit/using-winecfg-or-regedit-on-a-proton-game-prefix

:+1: Funny to find people using the stuff I post on my "hidden"/personal blog :P (I write it in english so people can actually find something useful for them one day, and it is not really hidden since I posted a link to it once or twice on Github).

For the EAC issue on my side (I got to retest) I never had issue with this game (but I have with Vermintide 2 for example).

//EDIT: yeah, I started the game, I was still on Proton Experimental, it updated the prefix I guess as it took 5 seconds to launch, but I'm playing COOP on official matchmaking rght now for 10 minutes so EAC works here.

//EDIT2: do you have the Proton EasyAntiCheat Runtime installed? Not sure if required but I have it.

alasky17 commented 2 years ago

It stopped working for me with the lateste Proton experimental update. Now the game crashes before joining a server.

@puresick If this is still happening to you, could you provide more details (which type of server, random auto-match, etc)? I was unable to reproduce the issue on my AMD Arch machine.

abienz commented 2 years ago

I just today (26th Aug) updated my Arch system to the latest packages, and ran Insurgency Sandstorm with Proton Experimental, and I successfully got past the Splash panel, loaded up the game and completed a full round of Firefight, all seems to be working for me now.

I noticed there was also a hotfix for the game too, but the changelog didn't mention anything with Linux.

Zorrototo commented 2 years ago

They didn't even announce the "Linux support" as far as I know so you'll never see changelog or changes related to Linux in my opinion.

puresick commented 2 years ago

@alasky17 Sure!

I tried joining an official PVP Push server with my region settings only having Europe selected. I have no mods installed.

My system specs are:

I just tried joining a server today after a new Proton Experimental updates has been installed via Steam, but that did not improve anything visibly.

puresick commented 2 years ago

I did some testing changing some of the "variables":

EDIT:

Adding -dx12 as a launch option seems to work. I can successfully joing an official Versus Push server/match. The problem I am having with that launch option i.e. forcing DX12 usage is having bad micro-stuttering if I turn texture pool streaming on, which I have to because disabling it with -dx12 results in me having no proper textures ingame at all or only really low-res textures at best.

alasky17 commented 2 years ago

@puresick Since adding -dx12 seemed to fix the problem, I'm wondering if it is a dxvk regression. Unfortunately, I was able to get into the community server in the screenshot just fine on experimental :/ Could you try dropping the dxvk files from experimental into Proton 7.0 to see if that breaks dx11 mode? By default this would mean: cp -rf ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/dxvk/ ~/.steam/steam/steamapps/common/Proton 7.0/dist/lib64/wine/dxvk/. and the same for the 32-bit files: cp -rf ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/dxvk/ ~/.steam/steam/steamapps/common/Proton 7.0/dist/lib/wine/dxvk/.

After you are done with the test, you can just delete the Proton 7.0/dist folder and it will recreate itself. This is why you should pop the files from experimental into 7.0 rather than the reverse :)

puresick commented 2 years ago

@alasky17 Seems like you are on a good path here: After copying the described files over from Proton Experimental to Proton 7.0 the game crashes exactly like with regular Proton Experimental.

alasky17 commented 2 years ago

@puresick Since I can't repro, it would be difficult for me to file a dxvk bug :sweat_smile: If you are able to file a dxvk bug here, that would be awesome :) https://github.com/doitsujin/dxvk/issues

Right now, experimental is on a different dxvk branch from stable Proton - if you mention the specific Proton versions where it fails and worked, the dxvk devs should hopefully be able to work out where the regression is happening.

doitsujin commented 2 years ago

As mentioned in the DXVK report, I don't know how to reproduce this. If anybody has got more info on this and can give me step-by-step instruction on how to actually make the game crash, as well as tell me which Vulkan driver is being used, please post there.

puresick commented 2 years ago

Just a heads up: It seems to be an AMDVLK issue. I was using AMDVLK but did not know that it was unsupported by DXVK. Using RADV solved the crashes.

I will open an issue on the AMDVLK repository soon.

Zorrototo commented 2 years ago

Do you ALT-TAB and open the Steam overlay regularly?

Zorrototo commented 2 years ago

I meant before it happens.

I had once a real FPS drop like going to 75 FPS to 20 then 10 then less.. it wouldn't go up, anytime, so I had to restart the game then it worked well.

Maybe there are settings that create bugs, I don't know. Try to change some settings and see if the issue is reproducible. Also maybe try to see if you can reproduce the issue solo, offline, with the minimum action going on (if possible, solo on a map offline).

kisak-valve commented 1 year ago

Steam overlay not working and other graphical glitches after "Insurgency: Sandstorm" update

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6450. @mlandalv posted on 2023-01-12T18:39:46:

Compatibility Report

System Information

I confirm:

steam-581320.log.zip

Symptoms

  1. Graphical artifacts if not using native resolution (I'm using 1920x1200 on my 3840x1600 monitor) As soon as I take a screenshot or start screen recording the artifacts go away, hence the mobile photo. The issue starts being visible on picture 4 although not easy to spot on the picture due to so much dark. Easy to spot IRL due to some flicker. 1 2 3 4 5 6

  2. It is not possible to open the steam overlay Not working regardless of resolution.

  3. Steam FPS counter (top left) isn't working Not working regardless of resolution.

Reproduction

Happens 100 % of the time since the 2023-01-10 update of the game.

Other notes

The graphical glitches disappear if i take a screenshot with grim or if I record with wf-recorder. After that the window also gets stretched (same thing happens when switching workspace and back).

When exiting the game this is printed:

src/steamexe/main.cpp (254) : Assertion Failed: reaping pid: 7557 -- gameoverlayui

src/steamexe/main.cpp (254) : Assertion Failed: reaping pid: 7557 -- gameoverlayui

src/steamexe/main.cpp (254) : Assertion Failed: reaping pid: 7596 -- gameoverlayui

src/steamexe/main.cpp (254) : Assertion Failed: reaping pid: 7596 -- gameoverlayui

src/steamexe/main.cpp (254) : Assertion Failed: reaping pid: 7627 -- gameoverlayui

src/steamexe/main.cpp (254) : Assertion Failed: reaping pid: 7627 -- gameoverlayui

Also tried with GE-Proton7-43 but it's even worse. So many graphical artifacts it's not possible to see anything.

solenum commented 1 year ago

Myself and a bunch of other users are suddenly being kicked from every server we join with "Kicked from server: Anti-Cheat: Client integrity violation". Game was working fine Friday night, there where no updates and then this suddenly started happening Saturday night.

I've tried reinstalling, clearing the prefix, a few different proton versions (experimental, hotfix, normal versions, GE ones including 43 which was the one the game was working with Friday night). Tried different launch arguments including with and without -dx12, no luck.

I did update my Nvidia drivers (RTX 3070) sometime Saturday, I can't recall if it was before or after I first tested sandstorm, haven't had a chance to roll back and see if that's causing any issues but I am getting a lot of crashing in a lot of games with the latest Nvidia drivers.

Thread with other reports, for some the game still works, for others it doesn't: https://old.reddit.com/r/linux_gaming/comments/10ihf1x/eac_doesnt_work_with_insurgency_sandstorm/

Edit; I'm starting to see a few threads on this on steam discussions as well, may not be a Linux/Proton related issue, could just be EAC playing up.

JellyWX commented 1 year ago

I haven't had that specific issue, but have been having a tonne of issues getting the game to even open for the past couple of days. Constantly getting stuck on the splash (the one that opens after the EAC splash)

More details:

solenum commented 1 year ago

I haven't had that specific issue, but have been having a tonne of issues getting the game to even open for the past couple of days. Constantly getting stuck on the splash (the one that opens after the EAC splash)

Do you have a VR headset? I've had the same issue, rename the OpenXR folder in steamapps/common/sandstorm/Engine/Binaries/ThirdParty/ to "_OpenXR" (or something else). That resolved it for me. This appears to happen to Windows users as well.

mlandalv commented 1 year ago

I haven't had that specific issue, but have been having a tonne of issues getting the game to even open for the past couple of days. Constantly getting stuck on the splash (the one that opens after the EAC splash)

Do you have a VR headset? I've had the same issue, rename the OpenXR folder in steamapps/common/sandstorm/Engine/Binaries/ThirdParty/ to "_OpenXR" (or something else). That resolved it for me. This appears to happen to Windows users as well.

I have the same problem as @JellyWX. I don't hade a VR but will try your fix later anyway.

I've played quite a bit the last few weeks but haven't had a single EAC error. I did delete the steamapps/compatdata/581320 folder when trying to fix the steam overlay issue though. I'm using Proton 7.0-5. Not using any launch options.

mitchpk commented 1 year ago

Is anybody else getting this horrible stuttering both in the main menu and in match? I've tried clearing shader cache, compatdata, and reinstalling the game. The stuttering sometimes subsides but starts up again within a minute or so, and it does not go away like shader compilation does.

image

solenum commented 1 year ago

Is anybody else getting this horrible stuttering both in the main menu and in match? I've tried clearing shader cache, compatdata, and reinstalling the game. The stuttering sometimes subsides but starts up again within a minute or so, and it does not go away like shader compilation does.

Are you launching with the -dx12 flag? If so, per a previous comment here having the texture pool streaming option on in-game could cause stuttering when running with -dx12.

Personally, when the game was actually working for me, I wasn't using the -dx12 flag and the game was running very well for me at max settings on my RTX 3070 & 5900x.

mitchpk commented 1 year ago

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

No, unfortunately I'm not running dx12. There is no difference in the amount of stuttering when using max and lowest settings. I'm using a RX 6700 XT & 13600k

JellyWX commented 1 year ago

Verifying game files on every reboot allows me to launch. This forces the EOS installer to re-run is my guess as to why this resolves it for me.

...seems resolved now, I guess either by the Steam client update or by the various patches to the client runtime and Proton bleeding edge that just shipped.

Spoke too soon. Stopped working again now.

solenum commented 1 year ago

This has suddenly started working again for me, I've not changed anything or done anything.

mitchpk commented 1 year ago

Did some more testing, the stuck on loading screen issue appears to happen randomly and you can get to the main menu by relaunching the game at most a few times. Now to the stuttering, weirdly this only happens when the game is connected to the New World Interactive servers. If the game is launched in offline mode there is no stuttering, but of course you can't play anything other than bot matches.

AIC1Drew commented 1 year ago

Looks like I'm not the only one having EAC issues since v1.13 or the subsequent hotfix. However, my issue is a little different, I have no issues launching/playing sandstorm using the EAC exe launcher. I don't receive any sort of EAC invalidation error or have issues getting kicked, BUT I do have issues with trying to exit the game, the process doesn't seem to terminate properly and Steam will still show the game running. When bringing up task manager, there is no insurgency sandstorm process to terminate, instead I noticed one of my logical cores maxed out at 100% usage. The process maxing this usage is "system", so I can't terminate it. The only way I can fully terminate the process is by restarting the whole PC. As a test, I launched the game using the non-EAC exe located in the same parent folder (insurgency.exe) and had no issues exiting the game. SO, this leads me to believe there is some on-going bug between EAC and the game.

If anyone would like a workaround just to be able to play the game and omit EAC-associated issues until things are patched, I am running 2 community servers without EAC (one modded, one vanilla). You just need to first launch the game with the non-EAC exe (typically located at \SteamLibrary\steamapps\common\sandstorm). Then in community servers, make sure modded is checked on the left and checkpoint is selected from the mode dropdown. Then search "Nancy's Insiders" and you should see the 2 servers.

kisak-valve commented 1 year ago

Hello @AIC1Drew, just in case it wasn't clear, you've come across the issue tracker for Proton.

Proton is a compatibility layer for running Windows games on Linux. Your issue with a runaway task called "system" isn't particularly relevant here since there isn't a direct equivalent on Linux.

mlandalv commented 1 year ago

Update. I have now also started to get EAC errors. Not often but sometimes. Usually only a restart of the game is required to fix it.

The game still doesn't launch sometimes. Renaming OpenXR didn't fix it.

JellyWX commented 1 year ago

It seems I spoke too soon before. Can't get the game to get past the splash again: verifying files, restarting, using different Protons, etc. makes next to no difference. I got it to open once using Proton GE 7-48, but even then couldn't get into any matches due to EAC integrity.

privat3dancer commented 1 year ago

Has anyone successfully found a workaround for the steam overlay?

These are the only log entries I have when grepping for overlay:

3590458.849:016c:0170:trace:loaddll:build_module Loaded L"C:\\Program Files (x86)\\Steam\\gameoverlayrenderer64.dll" at 0000000012680000: native 3590468.147:016c:0170:warn:seh:OutputDebugStringA "[2023.04.02-06.52.46:826][ 0]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n" 3590468.147:016c:0170:warn:seh:dispatch_exception "[2023.04.02-06.52.46:826][ 0]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n" 3590493.272:016c:0170:warn:seh:OutputDebugStringA "[2023.04.02-06.53.11:956][872]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n" 3590493.272:016c:0170:warn:seh:dispatch_exception "[2023.04.02-06.53.11:956][872]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n"

Zorrototo commented 1 year ago

Nothing to do as far as I know. The overlay opens in the initial EAC popup, not in the game, so you have no overlay. Maybe if you find a way not having the EAC popup on game launch it could fix the issue.

kisak-valve commented 1 year ago

Hello @privat3dancer, looks like #5794 is relevant to this game.

privat3dancer commented 1 year ago

The overlay opens in the initial EAC popup, not in the game, so you have no overlay.

This is correct. I managed to lag the splash screen long enough to trigger the overlay key combo, which works fine while the splash is up. So the splash window opens and closes, and the overlay process appears exit with that window. The game window itself doesn't get the overlay. After the game fully launches, I can see a process called gameoverlayui trying to load repeatedly and exit.

[gameoverlayui] <defunct>
[gameoverlayui] <defunct>
[gameoverlayui] <defunct>
 /home/xxxx/.local/share/Steam/ubuntu12_32/gameoverlayui -pid xxxx -steampid xxxx -manuallyclearframes 0 -gameid 58132

But I'm a little confused why the log claims it loads gameoverlayrenderer64.dll, i.e. as a dll. Is the working overlay supposed to be a wine process or native process? If native, why is it trying to load the 32-bit version? And how safe is it to try to breakpoint these processes with this EAC crap running?

kisak-valve commented 1 year ago

Insurgency: Sandstorm crashes on proton experimental

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6805. @HASKADOG posted on 2023-05-27T16:18:53:

Compatibility Report

System Information

I confirm:

Symptoms

When I run the game, it crashes with the crash report window that is impossible to see

Reproduction

Run the game with proton experimental

steam-581320.log

kisak-valve commented 1 year ago

Hello @HASKADOG, DXVK and VKD3D-Proton in Proton 8.0 and newer requires a video driver that provides Vulkan 1.3. The NVIDIA 470 series video driver provides Vulkan 1.2. Please update your video driver and retest.