Compatibility Report

Latest EAC update appears to have broken the game entirely on Proton. Get an EAC violation error upon boot now with every Proton version I've tried.

Thanks to Krang on protondb, the following launch options seem to fix the issue

WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %command%

The launcher starts and starts the game successfully, but then it stays in a black screen forever. It consumes one CPU at 100% for a roughly half a minute and then freezes. I have to close it manually.

I fixed the issue by updating from ubuntu 20.04 to 22.04.

recently stopped working for me even when i tried going back to a proton version i know worked before, adding the WINE_CPU_TOPOLOGY env var fixed it

recently stopped working for me even when i tried going back to a proton version i know worked before, adding the WINE_CPU_TOPOLOGY env var fixed it

@yobson1

Adding
WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %command% doesn't open the game

And by adding
WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 eval $(echo "%command%" | sed 's/Chivalry2Launcher.exe/TBL\/Binaries\/Win64\/Chivalry2-Win64-Shipping.exe/'), the game opens, but with a warning saying to start the game via Chivalry2Launcher.exe, did you experience that? I'm not sure what version of proton worked previously, but trying with some older ones resulted in the same error

do you get the EAC error # 1 or it just doesn't open? my issue was the EAC error, apparently it has a thread limit of 16 and my cpu has 32 so the cpu topology did the trick for me. if your game doesn't open at all it may be a different issue to the one i was having.
when i was troubleshooting i did try that eval sed thing and yes i got a warning to use the launcher and while it did let me initially enter a match it kicked me for not having EAC initialised after about 1 minute.

try make sure the eac runtime is installed with steam://install/1826330

do you get the EAC error # 1 or it just doesn't open?

I see, my game doesn't even open without any parameters, a month ago or so, it would open and play normally, so not sure what changed, nothing is showing up in the logs, so I'm not exactly sure what could be the reason.

when i was troubleshooting i did try that eval sed thing and yes i got a warning to use the launcher and while it did let me initially enter a match it kicked me for not having EAC initialised after about 1 minute.

try make sure the eac runtime is installed with steam://install/1826330

with the eval it does open, but just like you, I get the warning, and then kicked if I try to join a multiplayer game, I did check if I have EAC installed, it looks like it, I'm able to play other EAC Linux supported games too, just chiv2 that is not able to run currently.

I think this is a problem of my own, if I do get through with this, I'll update it here (and in protondb), thanks yobson

--Solution for my problem--
I ran the game with PROTON_LOG=1 and checked the logs, my issue was related to vulkan somehow:

145707.304:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\winevulkan.dll" at 7A1C0000: builtin
info:  Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x7a1d21a0
info:  Extension providers:
info:    Platform WSI
info:    OpenVR
info:    OpenXR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
145707.304:014c:0150:err:vulkan:wine_vkCreateInstance Failed to create instance, res=-9
err:   DxvkInstance::createInstance: Failed to create Vulkan instance
145707.304:014c:0150:trace:seh:raise (22)

I did some research, and installing those sudo pacman -S vulkan-icd-loader lib32-vulkan-icd-loader nvidia-utils lib32-nvidia-utils and removing the old proton config (rm -rf ~/.steam/steam/steamapps/compatdata/1824220/) did the trick, the game at least starts now, not sure how I was able to play any games before, but now it works.

I probably removed something while cleaning up the system a while back.