search

ValveSoftware / Proton

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

The Witcher 2 (20920) #2309

Open CuriousTommy opened 5 years ago

CuriousTommy commented 5 years ago

Compatibility Report

System Information

I confirm:

steam-20920.log

Symptoms

Game crashes silently (before showing anything on the screen).

Reproduction

Launch the game

andrewschott commented 2 years ago

I also am running into the issue. Any proton version (6.3-8, 7.0.0RC3-GE, Experimental) does this. Launching via steam will load the launcher, which will turn into the medallion and then after a few seconds disappear and return to the launcher screen.

The taskset trick did nothing. The tip I read somewhere of having to user a launch parameter of using forcing d9vk did nothing.

I did turn on logging and I am not sure what to make of this: ``` 341095.665:012c:0130:warn:seh:OutputDebugStringA "\n" 341095.665:012c:0130:trace:seh:dispatch_exception code=40010006 flags=0 addr=7B012A8F ip=7b012a8f tid=0130 341095.665:012c:0130:trace:seh:dispatch_exception info[0]=00000002 341095.665:012c:0130:trace:seh:dispatch_exception info[1]=02c35f30 341095.665:012c:0130:warn:seh:dispatch_exception "\n" 341095.665:012c:0130:trace:seh:call_vectored_handlers calling handler at 62529DE0 code=40010006 flags=0 341095.665:012c:0130:trace:seh:call_vectored_handlers handler at 62529DE0 returned 0 341095.665:012c:0130:trace:seh:call_vectored_handlers calling handler at 7B00AE30 code=40010006 flags=0 341095.665:012c:0130:trace:seh:call_vectored_handlers handler at 7B00AE30 returned 0 341095.665:012c:0130:trace:seh:call_stack_handlers calling handler at 7B081E40 code=40010006 flags=0 341095.665:012c:0130:trace:seh:__regs_RtlUnwind code=40010006 flags=2 341095.665:012c:0130:trace:seh:__regs_RtlUnwind eax=00000000 ebx=00000000 ecx=40010006 edx=02fbd8a8 esi=02fbd858 edi=02fbd8a8 341095.665:012c:0130:trace:seh:__regs_RtlUnwind ebp=02fbd3a8 esp=02fbd3a0 eip=7b081dd6 cs=0023 ds=002b fs=0063 gs=006b flags=00000206 341095.665:012c:0130:trace:seh:__regs_RtlUnwind calling handler at 7BC585A0 code=40010006 flags=2 341095.665:012c:0130:trace:seh:__regs_RtlUnwind handler at 7BC585A0 returned 1 341095.665:012c:0130:warn:seh:OutputDebugStringA "| MC_RenderObjects | 0 | 0 |" 341095.665:012c:0130:trace:seh:dispatch_exception code=40010006 flags=0 addr=7B012A8F ip=7b012a8f tid=0130 341095.665:012c:0130:trace:seh:dispatch_exception info[0]=0000003c 341095.665:012c:0130:trace:seh:dispatch_exception info[1]=02addf50 341095.665:012c:0130:warn:seh:dispatch_exception "| MC_RenderObjects | 0 | 0 |" 341095.665:012c:0130:trace:seh:call_vectored_handlers calling handler at 62529DE0 code=40010006 flags=0 341095.665:012c:0130:trace:seh:call_vectored_handlers handler at 62529DE0 returned 0 341095.665:012c:0130:trace:seh:call_vectored_handlers calling handler at 7B00AE30 code=40010006 flags=0 341095.665:012c:0130:trace:seh:call_vectored_handlers handler at 7B00AE30 returned 0 341095.665:012c:0130:trace:seh:call_stack_handlers calling handler at 7B081E40 code=40010006 flags=0 341095.665:012c:0130:trace:seh:__regs_RtlUnwind code=40010006 flags=2 341095.665:012c:0130:trace:seh:__regs_RtlUnwind eax=00000000 ebx=00000000 ecx=40010006 edx=02fbd8a8 esi=02fbd858 edi=02fbd8a8 341095.665:012c:0130:trace:seh:__regs_RtlUnwind ebp=02fbd3a8 esp=02fbd3a0 eip=7b081dd6 cs=0023 ds=002b fs=0063 gs=006b flags=00000206 341095.665:012c:0130:trace:seh:__regs_RtlUnwind calling handler at 7BC585A0 code=40010006 flags=2 341095.665:012c:0130:trace:seh:__regs_RtlUnwind handler at 7BC585A0 returned 1 ```
And this: ``` info: Game: witcher2.exe info: DXVK: v1.9.2 info: Built-in extension providers: info: Win32 WSI info: OpenVR info: OpenXR info: Required Vulkan extension VK_KHR_surface not supported 341099.620:012c:0130:trace:seh:raise (22) 341099.620:012c:0130:trace:seh:NtSetInformationThread (0xfffffffe,10,0x2fbf188,4) 341099.620:012c:0130:trace:seh:NtSetInformationThread (0xfffffffe,10,0x2fbf190,4) terminate called after throwing an instance of 'dxvk::DxvkError' ```

DXVK should be working, as I use it on a good number of other games that do work just fine. I did verify as I recently updated to F35 via dnf, that amdgpu was still being used. It is. rx590 fwiw.

TIA, Andrew.

kisak-valve commented 2 years ago

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

andrewschott commented 2 years ago

Thanks @kisak-valve!

https://gist.github.com/andrewschott/2c34c69f843ca86e3df93e2eebfc1e5b

kisak-valve commented 2 years ago

@andrewschott, I was looking for the extended diagnostics section of Steam's system information. Unfortunately, you copied it before it finished gathering that information. What I suspect is that you're missing 32 bit Vulkan support for your video card, but wanted to confirm the overall health of your system before suggesting a system package to install. Please give Steam a little more time and update your gist.

andrewschott commented 2 years ago

Sorry about the haste, didn't know it was unfinished. It has been updated.

As for vulkan, thought I was good, but here is my amd,mesa and vulkan packages in case you can quickly spot any mistakes on my end:

#rpm -qa | grep -e vulkan -e mesa -e amd | grep -v devel | sort
amdgpu-pro-opencl-20.45.1188099-1.fc34.x86_64
mesa-demos-8.4.0-12.20210504git0f9e7d9.fc35.x86_64
mesa-dri-drivers-21.3.3-1.fc35.i686
mesa-dri-drivers-21.3.3-1.fc35.x86_64
mesa-filesystem-21.3.3-1.fc35.i686
mesa-filesystem-21.3.3-1.fc35.x86_64
mesa-libEGL-21.3.3-1.fc35.i686
mesa-libEGL-21.3.3-1.fc35.x86_64
mesa-libgbm-21.3.3-1.fc35.i686
mesa-libgbm-21.3.3-1.fc35.x86_64
mesa-libGL-21.3.3-1.fc35.i686
mesa-libGL-21.3.3-1.fc35.x86_64
mesa-libglapi-21.3.3-1.fc35.i686
mesa-libglapi-21.3.3-1.fc35.x86_64
mesa-libGLU-9.0.1-5.fc35.i686
mesa-libGLU-9.0.1-5.fc35.x86_64
mesa-libOpenCL-21.3.3-1.fc35.x86_64
mesa-libOSMesa-21.3.3-1.fc35.i686
mesa-libOSMesa-21.3.3-1.fc35.x86_64
mesa-libxatracker-21.3.3-1.fc35.x86_64
mesa-vdpau-drivers-21.3.3-1.fc35.i686
mesa-vdpau-drivers-21.3.3-1.fc35.x86_64
mesa-vulkan-drivers-21.3.3-1.fc35.i686
mesa-vulkan-drivers-21.3.3-1.fc35.x86_64
vulkan-headers-1.2.189.0-1.fc35.noarch
vulkan-loader-1.2.189.0-1.fc35.i686
vulkan-loader-1.2.189.0-1.fc35.x86_64
vulkan-tools-1.2.189.0-1.fc35.x86_64
xorg-x11-drv-amdgpu-21.0.0-1.fc35.x86_64

:edit: typo. Brain better than fingers.

kisak-valve commented 2 years ago

https://gist.github.com/andrewschott/2c34c69f843ca86e3df93e2eebfc1e5b#file-schotty-steam-sysinfo-L150 and https://gist.github.com/andrewschott/2c34c69f843ca86e3df93e2eebfc1e5b#file-schotty-steam-sysinfo-L167 are the lines you should focus on. You've set the VK_ICD_FILENAMES environment variable somewhere and only told it to look at the 64 bit Vulkan icd instead of both the 32 bit and 64 bit variant, which breaks the 32 bit Vulkan render path.

andrewschott commented 2 years ago

You are correct, sir! I had it in my bashrc. Key word HAD. That fixed things for at least the witcher 2. Likely some other quirkiness too. Thanks!

IBNobody commented 2 years ago

Progress! Decided to play Deus Ex Revision instead (which has no native Linux version), and noticed that it downloaded Steamworks Common Redistributables (which it didn't for Witcher 2). Launched W2 after that, and it automatically installed the prerequisites! Launcher works.

I can confirm that this fixed the issue for me on my Steam Deck where the launcher wouldn't even start. It was so weird. I was able to get far on my own by installing vcredist_x86.exe via protontricks, but couldn't get past the DirectX thing, Not sure how Wine/Proton keep things common between different games like this.

oakad commented 1 year ago

This game has plenty of crashes on all versions of Proton, though Proton 8 is relatively stable (as expressed in crashes per hour terms :-).

However, it also exhibits a peculiar behavior, whereupon the game appears to ignore key presses, to the tune: "press key -> no action -> reload/restart -> key works". I wonder if this arises from the general bugginess of the game or may there be an underlying issue with Proton/Linux input events/whatever else?