search

ValveSoftware / Proton

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

Dying Light 2 (534380) #5542

Open Meulengracht opened 2 years ago

Meulengracht commented 2 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Experiencing game hang and eventually crash consistently while playing Dying Light 2 in co-op mode after 5-10 minutes. We just played singleplayer for around 2 hours without experiencing any kind of issues.

Reproduction

Start Dying Light 2, enter game, invite a friend and starting playing normally. Crash will occur after a some minutes gameplay. We experience it after max of 10 minutes play.

hockdudu commented 2 years ago

I played the game a few hours with my friend, and for some reason his game crashed often while mine worked without any problems. We compared our settings, and the only difference was that he was using Proton Experimental and I was using Proton 6.3-8.

When he switched to Proton 6.3-8, his game didn't crash anymore and we were able to play together for hours without any crash.

StripedMonkey commented 2 years ago

I cannot get the game to run at all using my 2060m and the Nvidia 510 drivers. Tried Proton 7.1 GE and Proton 6.3 and Experimental. All result in a black bar for a splash screen, the game comes up in windowed mode (completely black) then it crashes. According to the logs it's a PageFault but the reason why is lost on me.

Using the intel igpu in this laptop will get me past the intro cutscene however.

Arch Linux Kernel 5.16.5

valters-tomsons commented 2 years ago

The game runs just fine except it's not possible to play Co-op together with a Windows player. Other player is usually kicked within 10 minutes. Tested with Proton 6.3-8. (might've been my problem)

System info - https://gist.github.com/valters-tomsons/1bf0c73442d59c3465383fb8827ecad0

l0wl3vel commented 2 years ago

Works well with Proton-7.1-GE-2, was able to play Co-Op with two friend for three hours without any problems yesterday.

Meulengracht commented 2 years ago

Works well with Proton-7.1-GE-2, was able to play Co-Op with two friend for three hours without any problems yesterday.

Yes, I want to confirm this. Switching to 7.1-GE-2 fixed Co-Op. We played for hours afterwards without any issues.

valters-tomsons commented 2 years ago

@Meulengracht @l0wl3vel Just wondering, were your co-op partners running on Windows?

Meulengracht commented 2 years ago

@Meulengracht @l0wl3vel Just wondering, were you co-op partners running on Windows?

Nope, we were both running experimental, and both switched to GE

l0wl3vel commented 2 years ago

@Meulengracht @l0wl3vel Just wondering, were you co-op partners running on Windows?

My co-op partners were both running Windows 10. I was hosting the session.

puerto-rico commented 2 years ago

i experience that same issues with the game crashing almost every 15-30 min, No other proton games does that. i I have tried both Steam Beta, Proton Experimental and the stable version with no luck. both on dx11 and dx12

I have read on forums and on proton DB to find similar users with similar problems and it looks like something that happens more often for Ryzen users not distro specific. Not sure if it is a fact but i looks like it from the amount of comments.

i will be happy to provide any details, it is on Ubuntu 20.04 with nvidia 510 drivers. bios on the motherboard have been updated to the newest and have tried many of the proposed steam launch options with no luck

LiamDawe commented 2 years ago

Seems Proton 7 is much worse. After 20 minutes it gave stuttering to a crawl, then a hard lock up. Proton experimental is still fine.

alasky17 commented 2 years ago

Seems Proton 7 is much worse. After 20 minutes it gave stuttering to a crawl, then a hard lock up. Proton experimental is still fine.

@LiamDawe Does the game work with 6.3-8 or does it work well only with experimental-6.3?

aeikum commented 2 years ago

It'd be helpful if you could gather a Proton log showing the issue. It's working well on my AMD desktop machine so far.

digitalcircuit commented 2 years ago

I've run into this issue on my Intel Xeon desktop with an AMD Radeon RX 5600 XT, on Kubuntu 20.04 with Hardware Enablement Stack active.

I continued my Dying Light 2 world, had a friend join, and after roughly 15 minutes, the game hung - sounds played, but the video output froze, and I had to forcibly terminate it to exit.

Click/tap to show Steam System Information: ``` Computer Information: Manufacturer: Gigabyte Technology Co., Ltd. Model: Z97X-SLI-CF Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3900 Mhz 8 logical processors 4 physical processors HyperThreading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Supported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.4 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.13.0-30-generic X Server Vendor: The X.Org Foundation X Server Release: 12013000 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20211207.0 Video Card: Driver: AMD AMD Radeon RX 5600 XT (NAVI10, DRM 3.41.0, 5.13.0-30-generic, LLVM 12.0.0) Driver Version: 4.6 (Compatibility Profile) Mesa 21.2.6 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x1002 DeviceID: 0x731f Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 1920 x 1080 Primary Display Size: 20.04" x 11.26" (22.95" diag) 50.9cm x 28.6cm (58.3cm diag) Primary VRAM: 6144 MB Sound card: Audio device: Realtek ALC1150 Memory: RAM: 15881 MB VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 1804284 MB Largest Free Hard Disk Block: 1271475 MB Storage: Number of SSDs: 0 Number of HDDs: 0 ```

And here's my full Proton log with PROTON_LOG=1 %command% as launch options - 7.6 MiB.

Let me know if there's any other information I can provide or things to test!

Also, GloriousEggroll's 7.2-GE-3-test-2 has been working without crashing for an entire hour! Co-op multiplayer disconnects after about half an hour, but the game itself doesn't crash and I can quit to menu, then continue to reconnect multiplayer. (My internet itself seemed stable, Mumble voice chat remained connected, but I'm not 100% certain of that.)

NTMan commented 2 years ago

The game randomly hangs with latest Proton Experimental. steam-534380.log steam-534380.log steam-534380.log

With Proton GE 7.2 the game randomly crashed. steam-534380-GE-crash.log

Hardware: CPU: AMD Ryzen 3950X GPU: AMD Radeon 6900XT Mesa: Builded from git commit 53ca85a

tizzir commented 2 years ago

As of update 1.3.0 that was released today, the game now crashes for me before displaying anything other than a black window. I've attached the output of PROTON_LOG=1. steam-534380.log

amajauskas commented 2 years ago

Same issue as tizzir. Also attached log steam-534380.log .

iknowican commented 2 years ago

Same as above. Have never seen DL2 working via proton (6, 7, exp). Usually i get a black screen and a crash. I checked d3d11 log inside app folder and saw an attempt to use CPU integrated graphics (that brought to an error). Hope this will help somehow.

steam-534380.log DyingLightGame_x64_rwdi_d3d11.log DyingLightGame_x64_rwdi_dxgi.log

digitalcircuit commented 2 years ago

I still get crashes with the current Proton version, but after my earlier comment, even with the 1.3.0 update, GloriousEggroll's 7.3-GE-1 somehow continues to work - not the newer versions of GE, etc. 1.3.0 appeared to fix the disconnect issue and I've played as host with a Windows user joining for a few hours.

I don't advise settling for this as Proton itself should be fixed, but if you're looking to just play the game after submitting your logs here, this might work for you. Speaking of, if there's any testing I could do to help diagnose this, let me know!

tizzir commented 2 years ago

Rather embarrassingly, I have discovered that the 1.3.0 update was not to blame for the game not starting for me. At least, not in its entirety. It turns out that I had some mods installed that had not been updated, which caused the game to crash on startup. After removing the mod files, the game starts just fine with the latest proton experimental (and likely other proton variants as well.)

DMGPage commented 2 years ago

For some reasons I can't play it. Even in menu my FPS is around 2. Tried different proton versions, but nothing helps.

Relwi commented 2 years ago

For some reasons I can't play it. Even in menu my FPS is around 2. Tried different proton versions, but nothing helps.

Same here, I tried Proton Experimental and Proton 6.3-8 but the performance is very poor. And I can't even try the Proton 7.0-3, it gives me the 'compatibility tool configuration failed'.

DMGPage commented 2 years ago

It might be not for everyone, but I fixed my issues with launch option: DXVK_FILTER_DEVICE_NAME="GeForce RTX 2070" PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr %command% -nologos Now everything works just fine. "DXVK_FILTER_DEVICE_NAME" is most important, because I tried without and it wasn't working. And yes "GeForce RTX 2070" is my video card, so for everyone it will be different name.

SergeiGuriev commented 1 year ago

It might be not for everyone, but I fixed my issues with launch option: DXVK_FILTER_DEVICE_NAME="GeForce RTX 2070" PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr %command% -nologos Now everything works just fine. "DXVK_FILTER_DEVICE_NAME" is most important, because I tried without and it wasn't working. And yes "GeForce RTX 2070" is my video card, so for everyone it will be different name.

Mr. @DMGPage advice helped me, but if this does not help you, then you can also go along the path: ~/.steam/steam/steamapps/compatdata/534380/pfx/drive_c/users/steamuser/Documents/dying light 2/out/settings .

534380 - game App ID. In your case, everything will look about the same.

There is a file: video.scr. And it needs to be: RendererMode("d3d11") AsyncCompute(0) Not d3d12, despite the fact that during the game you can change everything as you wish (this does not negate the fact that everything can break again after graphics changes). In addition, most likely you will also need to lower the graphics using this file by changing other settings.

I also set compatibility with Proton 7.0-4.

Blub commented 1 year ago

When using the Intel Arc A770, it only runs with the d3d11 renderer, but produces hangups and some transparency issues (a lot of black squares around things that should be transparent). With d3d12 on the A770 I get the following on stderr:

wine: Unhandled exception 0xc0000417 in thread 12c at address 000000007B01253E (thread 012c), starting debugger...
Unhandled exception: 0xc0000417 in 64-bit code (0x000000007b01253e).
Register dump:
 rip:000000007b01253e rsp:000000000011b120 rbp:0000000000000000 eflags:00000202 (   - --  I   - - - )
 rax:000000007b0124f0 rbx:00000003af6fa146 rcx:000000000011b140 rdx:0000000000000001
 rsi:00000003af6fa146 rdi:0000000004d2d570  r8:0000000000000000  r9:0000000000000000 r10:0000000067fe3284
 r11:000000000000f010 r12:0000000000000000 r13:0000000000000000 r14:00000000241d0150 r15:000000000011b400
Stack dump:
0x000000000011b120:  000000000011b140 0000000000000000
0x000000000011b130:  0000000000000001 00000003af6daec9
0x000000000011b140:  00000001c0000417 0000000000000000
0x000000000011b150:  000000007b01253e ffffffff00000000
0x000000000011b160:  0000000000000000 00000003af6e44c2
0x000000000011b170:  45363344347b224c 353233452d383639
0x000000000011b180:  46422d454331312d 32303038302d3143
0x000000000011b190:  7d38313330314542 0000000000000022
0x000000000011b1a0:  0000000000000027 000000000011b340
0x000000000011b1b0:  0000000000000026 00000003af6eade8
0x000000000011b1c0:  0000000000000000 0000000000000000
0x000000000011b1d0:  0000000000000000 0000000000000000
Backtrace:
=>0 0x000000007b01253e AccessCheckByTypeAndAuditAlarmW+0x1153e() in kernelbase (0x0000000000000000)
  1 0x00000003af690b8f _Cmulcc+0x1fb8f() in ucrtbase (0x0000000000000000)
  2 0x00000003af69154e _Cmulcc+0x2054e() in ucrtbase (0x0000000000000000)
  3 0x00000003af6f1113 _Cbuild+0x363a3() in ucrtbase (0x0000000000000000)
  4 0x0000000037c424cc in xefx_loader (+0x24cc) (0x0000000000000000)
  5 0x0000000037c41e56 in xefx_loader (+0x1e56) (0x000000000011b4d0)
  6 0x0000000037c43846 in xefx_loader (+0x3846) (0x000000000011de80)
  7 0x0000000037c438f4 xefxLoadLibrary+0x54() in xefx_loader (0x000000000011de80)
  8 0x00000000379740fc xessD3D12BuildPipelines+0x2bafc() in libxess (0x000000000011de80)
  9 0x000000003794888c xessD3D12BuildPipelines+0x28c() in libxess (0x000000000011de80)
  10 0x0000000036fcb498 ffxGetCommandListDX12+0xbac8() in rd3d12_x64_rwdi (0x000000000011de80)
  11 0x0000000036fc232a ffxGetCommandListDX12+0x295a() in rd3d12_x64_rwdi (0x000000000011df09)
  12 0x00000000017f27ad ??0?$CAbstractSystem@VCoAudioPropagation@@@cbs@@QEAA@XZ+0xc621dd() in engine_x64_rwdi (0x000000000011dfe0)
  13 0x0000000000f282c0 ??0?$CAbstractSystem@VCoAudioPropagation@@@cbs@@QEAA@XZ+0x397cf0() in engine_x64_rwdi (0x000000000011e110)
  14 0x0000000000f1830a ??0?$CAbstractSystem@VCoAudioPropagation@@@cbs@@QEAA@XZ+0x387d3a() in engine_x64_rwdi (0x000000000011ee70)
  15 0x000000014000738b in dyinglightgame_x64_rwdi (+0x738b) (0x000000000011ee70)
  16 0x0000000140001df3 in dyinglightgame_x64_rwdi (+0x1df3) (0x0000000000000000)
  17 0x000000014007ec2a in dyinglightgame_x64_rwdi (+0x7ec2a) (0x0000000000000000)
  18 0x000000007b62c9e9 ActivateActCtx+0x20da5() in kernel32 (0x0000000000000000)
  19 0x000000017005f627 A_SHAFinal+0x3caa7() in ntdll (0x0000000000000000)

With an nvidia 1060 it runs fine either way. So I guess the blackness-instead-of-transparency part is on the intel mesa side? Not sure. But would definitely be nicer to run in d3d12 mode, the trace there is weird though.

UPDATE: Tested mesa-git and the black squares seem to be gonethere (previously was on 22.2.3-1 on Arch) Still some pretty hard short stalls but no complete hangup yet. (Another update: another git update a day later and the glitches are back and worse lol)

mixolydianmel commented 1 year ago

I seem to be having a somewhat similar issue, at least judging by the appearance of that ??0?$CAbstractSystem@VCoAudioPropagation key in my logs. The symptom for me however is the game completely crashing after clearing the "Press any key to continue" splash just after launch. Pretty sure this has something to do with audio, as I'm not getting any on the splash screen or after I press the key to continue. I use pulseaudio and alsa if that helps.

CLI Args: PROTON_LOG=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 %command% -nologos

Proton Log

Hope this issue is solved soon! I'm happy to provide more information, but I'm at a dead end here.

rcbevans commented 1 year ago

Just tried running this and the game fails to launch with both Proton 8, and Proton Experimental due to an Access Violation in dsound.dll (logs attached).

Forcing compatibility to Proton 7.0-6 and the game launches correctly.

Not sure how Proton works when it comes to system dll versioning, but since Proton 7 works and Proton 8+ doesn't, I assume this is a regression in Proton? Not sure if it should be flagged up somewhere else, since this game hasn't had any activity in a few months and is an older title.

steam-534380.log

rcbevans commented 1 year ago

As a secondary issue, the game fails to launch into the game from the menu if any DXR graphics options are enabled using Proton 7.0-6. After selecting continue or play campaign, the screen goes back and freezes with the music still playing. After 30s or so the force quit system message is shown. Non-RT launches into the game just fine.

rcbevans commented 1 year ago

Manually copying dsound.dll from steamapps/common/Proton 7.0/dist/lib64/wine/x86_64-windows/ to steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-windows allows the game to launch when running under Proton Experimental, fixes DLSS not being available, and fixes the game hanging when trying to load from the menu when RT is enabled as is the case running under Proton 7.0-6.

gardotd426 commented 1 year ago

I'm having the same issue with DLSS not being available as @rcbevans. RTX 3090, 530.43.01 drivers. DLSS works fine in Lutris, but it's not available in the Dead Space Remake or Dying Light 2 no matter what I do. The fix rbcevans suggested doesn't work.

gardotd426 commented 1 year ago

Just to add to that, it's NOT a VKD3D or Proton issue, as Deathloop allows DLSS (and RayTracing) with no issues.

gardotd426 commented 1 year ago

So @kisak-valve is right, it is in fact a regression in Proton and it affects all games that use VKD3D (at least).

Deathloop running using GE-Proton7-53 works perfectly. Moving it to Proton Experimental or anything from the past few weeks (including GE-Proton7-55) kills DLSS capability. Seems like Dead Space and Dying Light 2 have the same issue. I'm going to test out DL2 with GE-Proton7-53 and see if DLSS comes back, that would at least narrow the breaking change to at least the last month or so, hopefully.

alasky17 commented 1 year ago

@rcbevans The dsound issue you were running into on 8.0 is quite odd from looking at the log. In order to try to figure out what is going on, could you: 1) Switch to the Steam Beta client 2) Run "Verify the integrity of files" on Proton Experimental to get the original dsound.dll back 3) Assuming you are still hitting the problem, try deleting the prefix just in case. 4) Assuming that didn't fix things, get a log of the crash with PROTON_LOG=+dsound,+sync,+mmdevapi,+pulse %command% 5) Get the output of pactl info, pactl list sources and pactl list-source-outputs and upload in addition to the log.

And a few more context questions -- 1) On 7.0, did you do anything wrt voice chat in the game / playing online? 2) Where exactly is the game crashing? Before a window shows up?

I know you have a working game now, so I get if you don't want to go through this hassle. This is really a mystery right now. I believe that if the game is still broken after "verify integrity of files" you could just copy the 7.0 dsound.dll again and fix things while we see if anything can be gleaned from the results of these tests :)

alasky17 commented 1 year ago

@Corbent Thank you so much!! I am hoping there will be some clue in there :) I also don't think I have any system info from anyone who has run into this bug yet. Could you 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. If you're using the Steam client beta, then please also include the output from Steam Runtime Diagnostics.

LiamDawe commented 1 year ago

Swapped from NVIDIA to AMD 6800xt and now Dying Light 2 won't launch.

Log file: steam-534380.log

kisak-valve commented 1 year ago

Hello @LiamDawe, looking at your Proton log, it hints more towards an audio-related issue with an access violation (c0000005) in DSOUND.dll instead of direct result of a video card vendor swap.

LiamDawe commented 1 year ago

Okay firstly here's a log with "PROTON_LOG=+dsound,+sync,+mmdevapi,+pulse %command%" using Proton Experimental:

steam-534380.tar.gz

Some other logs that @alasky17 asked for above:

liam@liam-kub:~$ pactl info Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 466 Tile Size: 65472 User Name: liam Host Name: liam-kub Server Name: PulseAudio (on PipeWire 0.3.65) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_0b_00.4.analog-stereo Default Source: alsa_input.usb-046d_HD_Pro_Webcam_C920_B33EF4BF-02.analog-stereo Cookie: ea1f:ad4f

pactl list sources: https://gist.github.com/LiamDawe/6c0d9c63b1f3e4bfd9039ff4a6cbed1b

And also:

liam@liam-kub:~$ pactl list-source-outputs No valid command specified.

I don't even seem to have dsound.dll in Proton 7, I tried verifying files and completely uninstalled and reinstalled Proton 7 and still don't have it. Weird?

Edit: okay removing Proton 7 folder entirely, re-installing and then running a game unpacked it properly. Weird how verifying didn't pick up the missing file though. Anyway, did the copying from 7 to Experimental and yup it now launches. So a regression from 7 to Experimental? Log file of it now working:

steam-534380.log

rcbevans commented 1 year ago

Coming back to add that I am seeing (what appears to be) the same DSOUND.dll crash in Remnant: From the Ashes

rcbevans commented 1 year ago

@alasky17 Beta Steam client log with PROTON_LOG=+dsound,+sync,+mmdevapi,+pulse

steam-534380.log

pactl-info.txt pactl-list-sources.txt pactl-source-outputs.txt

rcbevans commented 1 year ago

It's something to do with my connected SteelSeries Arctis Pro Wireless headset.

If I disconnect the headset GameDAC, the game launches fine.

Here's updated pactl logs without the SteelSeries connected.

pactl-info.txt pactl-list-sources.txt pactl-source-outputs.txt

rcbevans commented 1 year ago

It appears the issue is having two active audio input devices, as reported https://github.com/ValveSoftware/Proton/issues/6964.

Using pavucontrol to disable the additional multiple inputs (leaving only the one I want with an active configuration) the game launches.

kisak-valve commented 8 months ago

Game crashes while trying to load main menu.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7367. @something12356 posted on 2023-12-22T16:07:32:

Compatibility Report

System Information

I confirm:

steam-534380.log Crash log created by the game.

Symptoms

After launching the game and getting to the screen where it says "press any button to continue", and then pressing a button, the game crashes. I can't even reach the main menu.

Reproduction

Install Dying Light 2, click play, the game crashes. I'm on Arch Linux and running the version of steam I got through pacman.

something12356 commented 7 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/5542#issuecomment-1867872319

I've now also tried changing the renderer between dx11 and dx12 in the settings file, changing between Windowed and Fullscreen, and a few other proton versions. So far hasn't fixed it.

something12356 commented 7 months ago

@Corbent Thanks for the response. I just tried again and the game still crashes before getting to the main menu. Recently wine has started saying mono is not installed when I launch steam, even though I have the most up to date version, so maybe it's due to that? But I don't have an issues with other games.

simifor commented 7 months ago

@something12356 I can launch the game just fine with a RX 6600 and the same mesa drivers, tested proton 8 stable and proton experimental. From your message it sounds like you're using the windows version of steam, any reason why?

something12356 commented 7 months ago

@simifor I'm just using the version of steam in the Arch repo, it's not the Windows version. Here's the output from pacman -Qs steam:

local/python-steamgriddb 1.0.5-2
    Python API wrapper for SteamGridDB.com
local/samrewritten-git r258.39d524a-1
    A Steam Achievement Manager For Linux.
local/steam 1.0.0.78-2
    Valve's digital software delivery system
simifor commented 7 months ago

@simifor I'm just using the version of steam in the Arch repo, it's not the Windows version. Well, you said the following: " Recently wine has started saying mono is not installed when I launch steam" which doesn't make sense unless you're launching the windows version of steam, though I had missed your logs ina previous message.

Anyway, your crash log from the game says that your data is corrupted. Have you tried to verify the gae files to see if they haev an effect?

something12356 commented 7 months ago

I have, nothing is caught. I've also re-installed the game and that hasn't fixed anything.

simifor commented 7 months ago

@something12356 I'm comparing against my crash log, and I see that data4 and data7 aren't loaded in my case, do you have DLC installed?

something12356 commented 7 months ago

No, I don't own any DLC for the game. I could try deleting data4 and data7 and seeing if that works. I'll get back to you after I've tried that.

something12356 commented 7 months ago

@simifor That fixed it, thank you! I'm not sure why those files were there but deleting them makes the game work.