search

ValveSoftware / Proton

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

Dying Light (239140) #2569

Open ghost opened 5 years ago

ghost commented 5 years ago

This is a regression in 4.2.3 because it worked in 3.16.x. I'm on ubuntu 18.04.

ghost commented 5 years ago

This is a workaround:

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

and then Ctrl+C.

kisak-valve commented 5 years ago

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

ghost commented 5 years ago

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

ghost commented 5 years ago

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

magist3r commented 5 years ago

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: no mouse movement With mouse movement: with mouse movement

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

kisak-valve commented 4 years ago

Dying Light Won't Launch because global_opengl.mp is missing.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3563. @gardotd426 posted on 2020-02-23T08:26:06:

Compatibility Report

Dying Light (239140)

System Information

I confirm:

steam-239140.log

When trying to launch the game through Proton, there's just a black screen with a popup error window saying: "Materials database was not correctly initialized. Please make sure that global_*. mp files are present in Assets_XXX (platform specific) folder or in build Data folder." Upon clicking "OK" the game exits. After searching for the issue, it seems there's supposed to be a global_opengl.mp file or something like that in the Data folder for the game. There's not. Everything I've searched for online show people with this issue fixing it by renaming the incorrectly named data folder to Data, but mine is already Data, and those people also DID have the missing file already. I've spoke with one other person who similarly can't get the game to work in Proton and doesn't have that file.

I know there's a native version, it runs like trash and most people can't even hardly get it to run.

For some reason, this game has a platinum db rating (for the Windows version) but it won't launch at all and it apparently didn't install all the necessary files. Yes, I've already tried verifying the game files in Steam.

Reproduction

Install Dying Light Check "Force the use of a specific Steam Play compatibility tool" and select a proton version Wait for any necessary updates Launch the game

RomanHargrave commented 4 years ago

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.

Backtrace, if anyone's interested -

``` 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) ```

pcfirebeats commented 3 years ago

Compatibility Report

Name of the game with compatibility issues: Black Mesa
Steam AppID of the game: 362890

System Information

GPU: AMD Rrx 470

Driver/LLVM version: Mesa 21.2.0

Kernel version: 5.11.0-25-generic

Link to full system information report as Gist: https://gist.github.com/pcfirebeats/8da25f34cc45d8ac0d954111ea68a899

Proton version: Experimental

I confirm:

That I haven't found an existing compatibility report for this game. That I have checked whether there are updates for my system available.

Symptoms Default: When I use a Nintendo Switch Pro Controller the game crashes before it reaches the start menu. With an Xbox 360 controller the right joystick acts as if it is drifting (but it is ok on other games).

If I disable the steam input on the game properties: The Nintendo Switch Pro Controller does not work, but it appears several notifications that the controller is detected. The Xbox 360 controller works normally

Reproduction

Open the game.

Sfven commented 2 years ago

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 commented 2 years ago

Hello @Sfven, your log looks similar to https://github.com/ValveSoftware/Proton/issues/1479#issuecomment-738981368. You might get lucky setting the game's launch options to something like taskset -c 0-15 %command%.

gardotd426 commented 2 years ago

@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"
gardotd426 commented 2 years ago

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%

Sfven commented 2 years ago

@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).

Sfven commented 2 years ago

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.

SeongGino commented 2 years ago

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).

kisak-valve commented 2 years ago

Dualsense not working with Dying Light 1

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6121. @marcellmittnacht posted on 2022-08-27T07:09:44:

Compatibility Report

System Information

I confirm:

Symptoms:

When I start Dying light from steam, the Dualsense controller buttons simple not working, pressing them result nothing. The touchpad works however. Tried all 3 mode without success (Disabled, Default, Enabled steam input). Tried Dying light 2 with the same 3 mode, works perfectly. (With disabled with Playstation button icons, with default the button icons are the Xbox icons.)

Reproduction

  1. Plug Dualsense through USB cable.
  2. Start Dying light through proton.
  3. Press the buttons to skip the intro(nothing happens)
  4. Press the touchpad to skip the intro(The intro being skipped)