This is a workaround:

KIE() {
for (( ; ; ))
do
  killall iscriptevaluator.exe
done
}

and then Ctrl+C.

I can't reproduce this anymore, it was a two-times issue.

By the way, this issue reappears with this exact game after every proton update!

I have strange issue with this game. I always have micro stutters when I move the mouse, even in the main menu, not only in game.

No mouse movement:

With mouse movement:

Edit: this issue only appears with composition disabled in KWin.

I'll tack on that the game is not launching for, potentially due to compatibility issues with the eye tracking middleware. Unfortunately, there is little documentation about WINE compatibility with EyeX and disabling the DLL via overrides prevents the game from starting.

• Proton: 5.9 GE ST
• Hardware: Radeon VII, 2990WX (though I had never managed to get DL working in proton with my 4790k either)
• Kernel: 5.7.0-1-amd64 (debian)

wine: Unhandled page fault on write access to 0000003800000002 at address 0000000001583A4F (thread 00f4), starting debugger...
Unhandled exception: page fault on write access to 0x3800000002 in 64-bit code (0x0000000001583a4f).
Register dump:
 rip:0000000001583a4f rsp:000000000021ba10 rbp:000000000021bae9 eflags:00010212 (  R- --  I   -A- - )
 rax:0000000000000020 rbx:0000000000000008 rcx:0000000000000001 rdx:0000000000000002
 rsi:0000000000000010 rdi:000000001021cb60  r8:0000003800000002  r9:0000000000000000 r10:0000000010236200
 r11:0000000010236200 r12:0000000000000000 r13:0000000000000002 r14:00000000102386f0 r15:0000000000000001
Stack dump:
0x000000000021ba10:  0000000010236a40 0000000000000010
0x000000000021ba20:  000000000000000f 0000000010237f80
0x000000000021ba30:  0000000001583504 0000000000000330
0x000000000021ba40:  ffffffff0000000f 0000000000000020
0x000000000021ba50:  0000000000000027 0000004000000000
0x000000000021ba60:  0000000000000001 00000000102386f0
0x000000000021ba70:  0000000000000002 00000000102382f0
0x000000000021ba80:  0000000010236200 0000000000000001
0x000000000021ba90:  0000000000000040 0000000010236200
0x000000000021baa0:  0000000000000000 0000000000000000
0x000000000021bab0:  0000000000000000 fffffffffffffffe
0x000000000021bac0:  0000000000000000 0000000001636e68
Backtrace:
=>0 0x0000000001583a4f EntryPoint+0xffffffffffffffff() in msvcr110 (0x000000000021bae9)
  1 0x0000000001583eab EntryPoint+0xffffffffffffffff() in msvcr110 (0x000000000021de40)
  2 0x000000000157239e EntryPoint+0xffffffffffffffff() in msvcr110 (0x000000000021de40)
  3 0x000000000157af9e EntryPoint+0xffffffffffffffff() in msvcr110 (0x000000000021de40)
  4 0x00000000014f97b9 EntryPoint+0xffffffffffffffff() in msvcp110 (0x000000000021de40)
  5 0x000000000110f624 EntryPoint+0xffffffffffffffff() in tobii.eyex.client (0x000000000021de40)
  6 0x000000000110efe8 EntryPoint+0xffffffffffffffff() in tobii.eyex.client (0x000000000021de40)
  7 0x0000000001174bd4 EntryPoint+0x4732b() in tobii.eyex.client (0x000000000021de40)
  8 0x00000000015d6280 EntryPoint+0x42f13() in msvcr110 (0x000000000021bf10)
  9 0x00000000015cddb9 EntryPoint+0x3aa4c() in msvcr110 (0x000000000021bf10)
0x0000000001583a4f EntryPoint+0xffffffffffffffff in msvcr110: orl       %edx,(%r8,%r9,4)

I might have a similar issue to RomanHargrave, despite his issue being over a year old. Our proton logs look very similar.
I created a post about this on the r/linux_gaming reddit, but was told there that here might also be good.

For me, using proton experimental (and every other version of proton that I have tried), the game launches and becomes fullscreen, but never renders anything and hangs for about 10 seconds, then crashes.

Here is the steam-239140.log: https://pastebin.com/qSRJrh4G
Here is the Dying Light crash log: https://pastebin.com/T0i1UX3y
Here is a video of me demoing the issue with a new proton prefix: https://youtu.be/zZ3rdmAeWpk
Here is the link to my original reddit help post on r/linux_gaming: https://www.reddit.com/r/linux_gaming/comments/rcemut/dying_light_via_proton_crashes_on_startup/
Here is my system information from inxi -Fz: https://pastebin.com/BMYDcuPE

@kisak-valve that was my first suggestion to Sfven, but they said it had no effect.

This is the only thing I see before the page fault:

1616.214:0108:010c:warn:seh:virtual_unwind exception data not found in L"DyingLightGame.exe"

Actually correction, I did say to use taskset -c 0-8, @Sfven you might want to try taskset -c 0-15, and make sure it's before the %command%

@gardotd426 @kisak-valve Fixed! Adding taskset -c 0-3 to the launch options fixed the issue!

Other interesting info: This actually isn't the first time I have had to use taskset -c 0-3. The Forest also has issues without it (unlike DL, TF launches, but only has like 3 fps, whereas I get a solid 60 on max graphics with the taskset stuff). Furthermore, for whatever reason, anything higher than cores 0-3 causes DL to not work (i.e. taskset -c 0-15 did not fix the issue, only 0-3 did).

Correction: taskset -c 0-7 also works, and is the highest amount of cores I can use before the game crashes. Any cores within 0 and 7 work because of how the numa nodes are divided on my threadripper (I found this out using lstopo (part of the hwloc package)). Using cores 8+ in conjunction with cores >8 causes the crash.

Seems like my crash is similar but rooted in a different problem.

Dying Light hangs when trying to upscale a lower resolution to native in fullscreen mode. It runs fine if it's started in Borderless/Windowed.
I know this works otherwise, because I've played this game on the same machine, only on a 1080p monitor instead of the 4K display I'm using now, merely four/five-ish months ago.
Unfortunately, unlike some games, KDE's forced window scaling doesn't work (it's just a tiny window in the corner of a fullscreen black frame).