Warhammer: Vermintide 2 (552500)

[h8672]

Compatibility Report

• Name of the game with compatibility issues: Warhammer: Vermintide 2
• Steam AppID of the game: 552500

System Information

• GPU: GTX 1060 6GB
• Driver/LLVM version: Nvidia 396.54
• Kernel version: 4.15.0-34-generic
• Link to full system information: Gist
• Proton version: 3.7-6

I confirm:

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

steam-552500.log

Symptoms

• Normally game doesn't launch after installation.
• Game has a beta, which you can join, to skip the launcher.
• Open library, launch game there for a popup where you can select skip launcher option (doesn't pop up from quick launch).
• Game may crash if you change video settings many times in row.
• If game starts windowed it may start stretched to desktop.
  • Don't move window position before you got to the character selection or it may go to unreachable place.
  • Moving resizes it in Ubuntu 18.04.
  • I used alt + space to move the window and alt stayed down ingame, which caused character walk slowly, and you just have to press alt again to release it.

Reproduction

• Install the game in steam.
• Join temporary_launcher_workaround beta for the game.
  • Verify local files (If you started it before, maybe optional?).
• Launch game through library and select bypass launcher, click play.

[keraldi]

Things to add: System Information Gist

Symptoms

• EAC will not be installed/will not work even if its setup is launched manually in "SteamLibrary/steamapps/common/Warhammer Vermintide 2/installers/EasyAntiCheat/"
• due to bypassing the launcher (and EAC not being usable), progression is not saved on the game servers and trying to retrieve or save information from/to the game servers will give an in-game prompt to quit the game.
• tinted screen after loading in (not affecting the HUD) pitch black (does not resolve itself most of the time, workaround by changing FOV, changing FOV while everything looks as expected in turn turns everything black), green and pink tints or dense "fog" resolve itself after a couple seconds, as do graphical glitches/artifacts/stripes after loading in.

[GloriousEggroll]

just another confirmation here at what @lorce said. game doesnt save progress and you cant join online matches due to easy anti-cheat

[curieos]

Are any of these issues fixable on the Proton side? I found a thread on the fatshark forums that shed some light on the issue with EasyAntiCheat. I'm ok with setting up a VM to run this game, but if it's possible I'd like to stay away from windows.

Also, I was never able to get it to launch properly. I enabled the skip launcher option and it displayed the various splash screens, but when it's supposed to show the menu it crashes. I doesn't really matter if a fix isn't possible, but it was a bit frustrating for me.

[h8672]

There's a thread about it in #1468 and there should be more information about the issue.

Edit: Hmm... maybe I should keep this open as the issue isn't solved... The game doesn't work as intended either...

[romulasry]

"Play Warhammer: Vermintide 2 Play for free! Ends in 2 days"

It is also on sale. https://store.steampowered.com/app/552500/Warhammer_Vermintide_2/?snr=1_4_4__100

I am going to check and see if it works.

[romulasry]

Latest one crashes when selecting (Bypass Launcher --selected under Betas) otherwise it doesn't load. Proton 3.16-7.

[romulasry]

Same on Proton 3.16-8.

[romulasry]

Gist: https://gist.github.com/romulasry/9963e49d07f6c7ec9f6172c7b17bfed5 Log: steam-552500.log Using: Bypass Launcher

[kisak-valve]

Hello @romulasry, your log contains err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased, please run ulimit -Hn and verify it is a high value and not 4096.

[curieos]

Looks like Valve is working to get EasyAntiCheat to work on linux! I'm pretty excited for this, V2 is one of my favorite games.

[Patola]

So, no solution for anticheat yet.

[flindeberg]

An update for the interested: https://www.reddit.com/user/Guy1524/comments/hc3o1y/eac_progress_update/

[flindeberg]

So, no solution for anticheat yet.

No longer true, some crazy frogs did it.

https://drive.google.com/file/d/1KWETkDj89ZCG8p5PHPqLAtgMd4X77gk6/view?usp=sharing

Might take a little while until it comes all the way to Proton though.

[Gibbz]

What is the last file linked?Whats the file provided? Does that allow this game to work multiplay?

[Patola]

@Gibbz After EAC updated, it no longer works.

[flindeberg]

What is the last file linked?Whats the file provided? Does that allow this game to work multiplay?

@Gibbz, as @Patola said, it no longer works since the later EAC-patches.

It was a Wine-tree with EAC specific patches. As such only relevant for those of us with the knowledge and time at hand to compile wine.

Discussion takes place at #easy-anti-lobster-dev in the VKx-discord (https://discord.gg/mjWm8DK should work, it used to be the official invite link AFAIK). But to be honest, the discussion has been quite dead most of the fall and the winter so far.

[Gibbz]

Is it possible to play this via lan multiplay without using EAC in its current state?

[flindeberg]

Is it possible to play this via lan multiplay without using EAC in its current state?

AFAIK you can play on the modded realm. I.e. without progress, but it should be playable.

[NTMan]

The game closes itself a minute after starting. During this time, you can have time to go into the settings and run the benchmark.

Demonstration: https://youtu.be/tN83gdJ35eE

System Information

• GPU: AMD Radeon 6900XT
• Driver/LLVM version: Mesa 21.3-git/12.0.0
• Kernel version: 5.13-rc3
• Link to full system information report as Gist
• Proton version: experimental-6.3-20210604

steam-552500.log

If you hurry up and press "Play", then after the splash with the shark, the message "Backend rejected the challenge response" will be displayed.

steam-552500.log

[flindeberg]

@NTMan The launcher did not work a while back, so they have apparently changed something (or proton / wine includes more dependencies than before). Does modded realm work for you? What is your performance compared to Windows?

[DeathTBO]

@flindeberg I recently delete my Proton prefix, and booted up the game. The launcher worked, but it will crash after ~10 seconds. Just long enough to hit the modded realm check box, and boot up the game.

It performs extremely well. ~80fps on maximum graphics at 1440p. Never goes lower than 65 fps, even when a huge horde is attacking. Highest peaks are 90.

Fedora 34 Kernel 5.13 Ryzen 2700 4ghz oc Radeon 5700xt

Enabling mods can be done by opening the config file located at steamapps/compatdata/552500/pfx/drive_c/users/steamuser/AppData/Roaming/Fatshark/Vermintide 2/user_settings.config and setting each mod to enabled = true

That folder also has a launcher.cfg where you can set SendCrashReports to false and DisableAntiCheat to true.

Technically, you can only progress on the Official Realm, BUT there is a mod known as "Casual Mode". Which allows you to unlock everything straight up, or use a progression system similar to the Official Realm. It uses xp gained from the missions. It's pretty much perfect.

I found some mods were unstable, and crashed the game, so I cut it down to only the Vermintide Mod Framework, Penlight Lua Libraries, and Casual Mode (I assume load order is from top to bottom). I haven't used it very much, but it seems to work pretty well.

[Zorrototo]

Work is being done, we'll see when it will be enabled and working https://steamdb.info/depot/552503/history/?changeid=M:5995370140976663476

[DevanPratt]

Looks like they have been trying to reach out for enabling EAC support: https://steamcommunity.com/app/552500/discussions/0/2960544187643622408/?ctp=26#c3419936604888208895

[Zorrototo]

Seems like people are having some working EAC on the Steam forums https://steamcommunity.com/app/552500/discussions/0/2960544187643622408/?ctp=30#c3457094584911997892 and a dev even replied even if he still didn't confirm they changed something the past days. So far on my end, no luck, can't have anything to work. Will update if I find my issue and a fix.

[GloriousEggroll]

It's working here on Nobara + GE-Proton7-28. Clean install, clean prefix. Multiplayer works.

[DeathTBO]

Proton Experimental allowed me in.

I simply verified the game files -> Made sure Proton Experimental and the Proton EAC Runtime downloaded (I hit the queue download now) -> Bam the game let me in, I collected the daily reward.

[hjri]

i reinstalled proton eac runtime and now instead of "eac not running it says "insufficient resources"

some progress I guess.

[Zorrototo]

Yep that's where I am (see link above, I posted screenshot) since two days, I tried everything possible (I did not do a full reinstall of the 100GB files of the game, I tried at some point to delete everything but the Bundle folder, and verify the files in Steam to re-acquire the missing binaries and other files). I Tested Proton GE, Experimental (and its Bleeding Edge beta), I reset prefix all the time, I also tried to force reinstall EAC in the prefix, tried the various game beta options, tried with or without various launch options in game properties. But it seems my setup is doomed, when some other people can simply make sure to use Proton Experimental and have EAC Runtime installed, and they are all good instantly.

Maybe this is related to network and EAC can not communicate or download something, this is where my thoughts are now that I think I virtually tested everything on the Proton/game side. I might need to fully reinstall the game but to me that makes no sense when the game files verification should have made sure all files were good.

//EDIT: also, it seems it only works when you host the game as the Proton user, if you join other people's game it will kick you out after the usual EAC check.

[r2rX]

I managed to get it running once with Proton GE 7-28 and since testing Proton Experimental, even replicating the method with Proton GE again, I get the State: Untrusted error.

@Zorrototo you might be on to something. I never confirmed this when it was working but at this point in time, if I examine the loader.log file in the prefix' AppData\Roaming\EasyAntiCheat\226 folder, there are attempts to connect to anticheat servers (for wine64) and fails. If I run the URL in a browser, it downloads a file. I'm curious if placing this file in the appropriate folder would get it working again (although I don't know which folder this file is meant to go into or how it's processed).

Edit: Nevermind about the latter...each download is randomized, so it would make sense that each game instance opened up would download a unique file for that specific session.

Edit 2: Seems I was looking at the wrong folder. The correct folder is ~/.cache/com.epicgames.easyanticheat/226/ and the loader.log shows a successful connection to the server.

[Zorrototo]

There might be hope for me, I did not try yet but it smells like a good lead. https://github.com/ValveSoftware/Proton/issues/6051#issuecomment-1207123916

Will report when I can test, I actually deleted the game a few hours ago :1st_place_medal:

//EDIT: doesn't seem to help me.

[r2rX]

Sorry to read that, @Zorrototo . I'm running Fedora 36 KDE and glibc is 2.35. What's strange is that it worked once but not since (and it seems I'm not the only one; comment # 493).

[DeathTBO]

Sorry to read that, @Zorrototo . I'm running Fedora 36 KDE and glibc is 2.35. What's strange is that it worked once but not since (and it seems I'm not the only one; comment # 493).

I'm also running Fedora 36 and KDE. I just played a round perfectly fine. It was a private match, but I got items afterwards and everything.

[cyrv6737]

I was able to play an entire game with glibc-eac and GE-Proton7-28.

What worked:

• Hosting my own match
• Playing with others, other players successfully joining mid-game
• Playing an entire match without getting kicked

What didn't work:

• Joining someone else's game. I could only host my own without getting kicked.
• Experienced a crash on DX12 mode. I only tested this once before going back to DX11. DX12 is desirable for VT2 since it is very CPU heavy.

Other things I noticed:

• DX11 mode requires you to reenable Fullscreen after alt-tab even with "Minimize on Alt-tab" disabled. This behavior was not observed in DX12 mode.
• DX12 (VKD3D) still runs better than DX11 (DXVK) just like on Windows (from what I noticed at Taal's Horn Keep)

System: CPU: 5900x GPU: Radeon RX 6900 XT Mesa: mesa-git (mesa-tkg-git 22.3.0_devel.157575.446d2039cb7-1)

[Green-Sky]

after the proton experimental update yesterday/today the game wont launch for me anymore. both official and modded (-eac-untrusted). BUT changing to proton 7.0-4 (release candidate) works. including hosting games in official realm

system: Ubuntu 20.04.4 lts kernel: 5.15.0-43-generic cpu: AMD Ryzen 9 PRO 3900 gpu: NVIDIA rtx 2070 (mobile?) Driver Version: 470.141.03 (i know its outdated)

[hjri]

i looked into logs of EAC and windows version asks for https://download.eac-cdn.com/api/v1/games/226/client/wow64_win64/download/?uuid={uuid goes here but seems irrelevant} while running on proton it asks for https://download.eac-cdn.com/api/v1/games/226/client/wine64/download/?uuid=...

The first yields a 13.8MiB file that is placed in same directory where loader.log is, named easyanticheat_wow64_x64.eac but wine64 file is a 0 byte file.

[kisak-valve]

Hello @Green-Sky, DXVK and VKD3D-Proton in Proton experimental now requires NVIDIA 510.47 or newer. This minimum driver requirement bump is not a bug.

[Any-Fuel-5635]

Game ran great, updated glibc to 2.36 along with numerous other system updates, game no longer gets beyond the "Preparing to launch Warhammer: Vermintide II..." screen on Steam. Both for steam-native and Steam Flatpak.

[Green-Sky]

Hello @Green-Sky, DXVK and VKD3D-Proton in Proton experimental now requires NVIDIA 510.47 or newer. This minimum driver requirement bump is not a bug.

so i updated to 515, and had to re-restart steam. also switched to proton experimental. now it works again.

[r2rX]

I don't know if this actually helped getting the game working or not but I've repeated this multiple times when the state: untrusted error kicked in and has worked thus far. In the launcher, set it to modded realm and start the game. It gets stuck at the loading screen (after the warning) so I alt+F4, restart the launcher, set it back to the official realm, start the game and it worked. Just F.Y.I, if anyone uses the launcher bypass branch, the desktop shortcut ignores it (so the game needs to be started within the Steam client itself).

The game was hosted on my side, so I can't confirm being kicked when joining a game, and it ran pretty good in DX12. However, I noticed a few glitches which occurs with both DX11 (DXVK) and DX12 (VKD3D-Proton) running on a RX 6800M w/ Mesa 22.3.0-devel drivers.

When adjusting the camera, it can be positioned to expose gaps in the walls/floors (as well as a glitch with a waterfall and geometry of an arrow disappearing when being pulled):

[kisak-valve]

Hello @r2rX, 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.

[r2rX]

Hey @kisak-valve . Here's the Proton Log and system information you requested.

steam-552500.log System Information

Concerning the graphics issue, I could create a ticket on the Mesa git and provide an apitrace, if it will help.

[kisak-valve]

Blind guess that the rendering issue is related to https://gitlab.freedesktop.org/mesa/mesa/-/issues/7018. It might be interesting to test the commit mentioned in that issue report. If not, then a separate issue report on gitlab.freedesktop.org for the mesa/RADV devs to ponder can be useful for them.

[hakzsam]

@r2rX Can you try again after pulling Mesa main again? It might be related to the regression kisak pointed out. Thanks!

[r2rX]

Hi @kisak-valve . Your deduction/intuition was on point so I wanted to let you and @hakzsam know that the dccd6f49 commit in the mesa driver did indeed fix the culling issue! Great job! (The waterfall shader/rendering is still slightly off).

[hjri]

restarted the game and now it works?

although running dx12 version + going to quests tab in okri's book hanged my X11 or something, had to restart sddm.

[hjri]

ok that dx12 hang was one of a kind freak accident, although game didn't want to start at first, complained again about "insufficient resources" even though only 32% of memory (total 32GiB available) was used.

[pprotonrep]

I experience random crashes when running the game (no eror messageis provided, it just closes back to desktop). They may happen within the first five minutes of gameplay or after half an hour - seems random.

Changing graphical settings or dx api (11/12) does not seem to have an effect. Only tried proton stable an experimental and the crashes happen with both.

sysinfo.txt steam-552500.log

[kisak-valve]

Hello @pprotonrep,

These look like some lines of interest from your log:

``` [00000170:] EXCEPTION handling: System.InvalidProgramException: Unrecognizable runtime implemented method 'Microsoft.Web.WebView2.Core.Raw.ICoreWebView2Controller2:_VtblGap1_23 ()' [00000170:] EXCEPTION handling: System.NotImplementedException: Unable to cast to Microsoft.Web.WebView2.Core.Raw.ICoreWebView2Controller2. This may happen if you are using an interface not supported by the version of the WebView2 Runtime you are using. For instance, if you are using an experimental interface from an older SDK that has been modified or removed in a newer runtime. Or, if you are using a public interface from a newer SDK that wasn't implemented in an older runtime. For more information about WebView2 versioning please visit the following: https://docs.microsoft.com/microsoft-edge/webview2/concepts/versioning [...] "" tid=00000170 this=03d50120 , thread handle : 0093a1b0, state : not waiting at Microsoft.Web.WebView2.Core.CoreWebView2Controller.get__nativeICoreWebView2Controller2 () [0x00027] in <24d555f686524c89b51135793780ebc7>:0 at Microsoft.Web.WebView2.Core.CoreWebView2Controller.set_DefaultBackgroundColor (System.Drawing.Color) [0x00000] in <24d555f686524c89b51135793780ebc7>:0 at Microsoft.Web.WebView2.WinForms.WebView2/d__18.MoveNext () [0x001a0] in :0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore/MoveNextRunner.InvokeMoveNext (object) [0x00000] in :0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00071] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00000] in :0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore/MoveNextRunner.Run () [0x00024] in :0 at System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation/<>c.<.cctor>b__7_0 (object) [0x00000] in :0 at System.Windows.Threading.ExceptionWrapper.InternalRealCall (System.Delegate,object,int) [0x000e7] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.ExceptionWrapper.TryCatchWhen (object,System.Delegate,object,int,System.Delegate) [0x00004] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.WrappedInvoke (System.Delegate,object,int,System.Delegate) [0x00001] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.DispatcherOperation.InvokeImpl () [0x00099] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext (object) [0x00008] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00071] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00000] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object) [0x0002b] in :0 at MS.Internal.CulturePreservingExecutionContext.Run (MS.Internal.CulturePreservingExecutionContext,System.Threading.ContextCallback,object) [0x00029] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.DispatcherOperation.Invoke () [0x00016] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.ProcessQueue () [0x00114] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.WndProcHook (intptr,int,intptr,intptr,bool&) [0x00061] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at MS.Win32.HwndWrapper.WndProc (intptr,int,intptr,intptr,bool&) [0x0003a] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at MS.Win32.HwndSubclass.DispatcherCallbackOperation (object) [0x00042] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.ExceptionWrapper.InternalRealCall (System.Delegate,object,int) [0x000c6] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.ExceptionWrapper.TryCatchWhen (object,System.Delegate,object,int,System.Delegate) [0x00004] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.WrappedInvoke (System.Delegate,object,int,System.Delegate) [0x00001] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.LegacyInvokeImpl (System.Windows.Threading.DispatcherPriority,System.TimeSpan,System.Delegate,object,int) [0x000fc] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.Invoke (System.Windows.Threading.DispatcherPriority,System.Delegate,object) [0x00011] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at MS.Win32.HwndSubclass.SubclassWndProc (intptr,int,intptr,intptr) [0x00154] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at (wrapper native-to-managed) MS.Win32.HwndSubclass.SubclassWndProc (intptr,int,intptr,intptr) <0x00067> at <0xffffffff> at (wrapper managed-to-native) MS.Win32.UnsafeNativeMethods.DispatchMessage (System.Windows.Interop.MSG&) <0x00012> at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage (System.Windows.Interop.MSG&) [0x0001a] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.PushFrameImpl (System.Windows.Threading.DispatcherFrame) [0x0004c] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.PushFrame (System.Windows.Threading.DispatcherFrame) [0x00077] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Threading.Dispatcher.Run () [0x00006] in <3fca9819a0fd4fe2950d9c6ef1f9bd63>:0 at System.Windows.Application.RunDispatcher (object) [0x00023] in <3f0ca28258364746b90df0026805ef93>:0 at System.Windows.Application.RunInternal (System.Windows.Window) [0x0010d] in <3f0ca28258364746b90df0026805ef93>:0 at System.Windows.Application.Run (System.Windows.Window) [0x00008] in <3f0ca28258364746b90df0026805ef93>:0 at System.Windows.Application.Run () [0x00009] in <3f0ca28258364746b90df0026805ef93>:0 at Launcher.App.Main () [0x0000b] in :0 at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) [0x00027] in :0 ```

This is followed by and access violation(c0000005).

Later in the log, there's also:

``` ================================================================= Native Crash Reporting ================================================================= Got a UNKNOWN while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Managed Stacktrace: ================================================================= at <0xffffffff> at System.Object:__icall_wrapper_mono_gc_alloc_vector <0x00012> at System.Object:AllocVector <0x0013b> at System.String:SplitKeepEmptyEntries <0x00057> at System.String:SplitInternal <0x002ab> at System.String:Split <0x0009f> at System.IO.Path:CanonicalizePath <0x000b3> at System.IO.Path:InsecureGetFullPath <0x003ef> at System.IO.Path:GetFullPath <0x00023> at System.IO.File:GetLastWriteTime <0x0003f> at System.IO.DefaultWatcher:IterateAndModifyFilesData <0x008cf> at System.IO.DefaultWatcher:DoFiles <0x001cb> at System.IO.DefaultWatcher:UpdateDataAndDispatch <0x0011b> at System.IO.DefaultWatcher:Monitor <0x0023f> at System.Threading.ThreadHelper:ThreadStart_Context <0x00084> at System.Threading.ExecutionContext:RunInternal <0x00197> at System.Threading.ExecutionContext:Run <0x0003b> at System.Threading.ExecutionContext:Run <0x00057> at System.Threading.ThreadHelper:ThreadStart <0x0003f> at System.Object:runtime_invoke_void__this__ <0x0006a> ================================================================= ```

[flindeberg]

@pprotonrep Try skipping the launcher. I.e. use the "Bypass launcher" option when launching the game from steam.

The log-entries mentioned by @kisak-valve concern components only used in the launcher as far as I know.

[pprotonrep]

@flindeberg thanks for the suggestion

I've been switching back and forth between the "bypass launcher" branch and the release branch to see if it made any difference. I get crashes with both, although they may not have the same root cause :shrug:

This is the log from a crash while running the "bypass launcher" branch on dx12 mode. steam-552500.log

I could successfully run through a couple of acts on dx11 mode - but at this point I'm not sure if this was just pure coincidence. I'll do more testing on dx11 mode and report back, in case this helps anyone with similar problems in the future.