search

ValveSoftware / Proton

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

Sniper Elite 4 (312660) #2003

Open GhChancellor opened 5 years ago

GhChancellor commented 5 years ago

Compatibility Report

System Information

I confirm:

Symptoms

i would like play to Sniper Elite 4, with Steam play proton 3.16-4 it doesn't work. With Steam windows + wine 3.20 staging it's work well but there are not audio.

Someone can help me?

Reproduction

kisak-valve commented 5 years ago

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

GhChancellor commented 5 years ago

Hi @kisak-valve

steam-312660.log

GhChancellor commented 5 years ago

@kisak-valve

On winestaging 3.20 this work

`winetricks xact

wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v xaudio2_7 /t reg_sz /d native,builtin /f` Forum WineHq

But on Steam play it doesn't work...... Lele

GhChancellor commented 5 years ago

Update: with Lutrix ( dxvk enable ) + steam windows + dll xaudio2_7 native,builtin It looks perfect.

But on Proton still does not work

GhChancellor commented 5 years ago

At the moment is there a solution to play on Proton?

Guy1524 commented 5 years ago

@GhChancellor You can try to compile proton with the staging patches and use protontricks to for installing native xact. If this application is 64-bit you may have to revert a winetricks patch though.

GhChancellor commented 5 years ago

Ok thank you, i will try.

GhChancellor commented 5 years ago

@Guy1524 You can try to compile proton with the staging patches and use protontricks to for installing native xact. If this application is 64-bit you may have to revert a winetricks patch though.

Question, what is it for compile Proton if the game does not run? I can run it ONLY with Lutrix ( dxvk enable ) + winestaging 3.2x + steam windows + dll xaudio2_7 native,builtin

GhChancellor commented 5 years ago

No news? Nobody can help me?

GhChancellor commented 5 years ago

with 3.16-5 beta it still does not work

GhChancellor commented 5 years ago

with 3.16-6 beta it still does not work

Jacalz commented 5 years ago

Hopefully Proton developers update Wine to version 4.0 when it is released in week or two. There have been a lot of development between 3.16 and 4.0 so hopefully it can solve som issues along the way, especially since you got it working with wine staging 3.20.

EDIT: Wine 4.0 is now released so it would be wonderful if we could see an updated version of Proton :+1:

NTMan commented 5 years ago

EDIT: Wine 4.0 is now released so it would be wonderful if we could see an updated version of Proton

Unfortunately the game still crashes even with Proton 4.2-4 steam-312660.log

$ inxi -bM
System:    Host: localhost.localdomain Kernel: 5.2.0-0.rc0.git6.1.fc31.x86_64 x86_64 bits: 64 Desktop: Gnome 3.33.1 
           Distro: Fedora release 31 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 2202 date: 04/11/2019 
CPU:       8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 4160 MHz min/max: 2200/3700 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.4 driver: amdgpu resolution: 3840x2160~60Hz 
           OpenGL: renderer: AMD Radeon VII (VEGA20 DRM 3.32.0 5.2.0-0.rc0.git6.1.fc31.x86_64 LLVM 8.0.0) 
           v: 4.5 Mesa 19.1.0-rc2 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: rtw_pci 
Drives:    Local Storage: total: 11.57 TiB used: 7.98 TiB (69.0%) 
Info:      Processes: 450 Uptime: 43m Memory: 31.33 GiB used: 14.35 GiB (45.8%) Shell: bash inxi: 3.0.34
opal1974 commented 4 years ago

Using the following commands:

PROTON_NO_ESYNC=1 WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=90 %command%

..allows Sniper Elite 4 to work for me now. I have gone through about 1/2 the game. Occasionally, there are performance issues with lag but I havent seen any other problems.

mloveley commented 3 years ago

The game has started crashing in 6.3-6 or newer (I don't even see the launcher now), on earlier 6.3-x versions the launcher was rendering correctly. I can get it running using 5.13-6 but the launcher has no images, and just a few hyperlinks.

$ inxi -bM
System:    Host: ASUS-TUF-Gaming-A15-FA506IV Kernel: 5.11.0-27-generic x86_64 bits: 64 Desktop: Gnome 3.36.9 
           Distro: Ubuntu 20.04.3 LTS (Focal Fossa) 
Machine:   Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A15 FA506IV_FA506IV v: 1.0 serial: <superuser/root required> 
           Mobo: ASUSTeK model: FA506IV v: 1.0 serial: <superuser/root required> UEFI: American Megatrends v: FA506IV.316 
           date: 03/12/2021 
Battery:   ID-1: BAT1 charge: 42.8 Wh condition: 43.2/48.1 Wh (90%) 
CPU:       8-Core: AMD Ryzen 7 4800H with Radeon Graphics type: MT MCP speed: 1584 MHz min/max: 1400/2900 MHz 
Graphics:  Device-1: NVIDIA TU106 [GeForce RTX 2060] driver: nvidia v: 470.57.02 
           Device-2: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu resolution: 1920x1080~144Hz 
           OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 470.57.02 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8822ce 
Drives:    Local Storage: total: 238.47 GiB used: 794.87 GiB (333.3%) 
Info:      Processes: 412 Uptime: 23h 35m Memory: 15.12 GiB used: 4.43 GiB (29.3%) Shell: bash inxi: 3.0.38

steam-312660.log

https://gist.github.com/mloveley/94e2915e13e93543d92380f171f9b7b7

kisak-valve commented 3 years ago

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

mloveley commented 3 years ago

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

updated above. Let me know if you need anything else.

alasky17 commented 3 years ago

@mloveley I uploaded a copy of Proton 6.3-5 here with the unlock code "regression": https://www.codeweavers.com/xfer/alasky/proton-6.3-6/

Could you try this build to see if the Sniper Elite 4 crash is caused by a change in 6.3-6 or a change in your system? You can drop this build into the ~/.steam/steam/steamapps/common/Proton 6.3 folder to replace the current build, and then use "Verify the integrity of tool files" on the Proton 6.3 tool in the Steam client to trigger 6.3-6 to redownload after you are done testing 6.3-5.

mloveley commented 3 years ago

Could you try this build to see if the Sniper Elite 4 crash is caused by a change in 6.3-6 or a change in your system? You can drop this build into the ~/.steam/steam/steamapps/common/Proton 6.3 folder to replace the current build, and then use "Verify the integrity of tool files" on the Proton 6.3 tool in the Steam client to trigger 6.3-6 to redownload after you are done testing 6.3-5.

I can confirm that it works with the files from 6.3-5. I switched the Proton version back to 6.3-6 from 5.13 and tried to launch, as before it crashed before the launcher appeared.

Extracted the Files from the download and copied them into the proton directory overwriting what is there currently.

~/.steam/steam/steamapps/common/Proton 6.3$ ls -la proton_dist.tar
-rwxrwxr-x  1 mloveley mloveley 1100451840 Aug 23 21:53 proton_dist.tar
~/.steam/steam/steamapps/common/Proton 6.3$ mv ~/Downloads/proton_6.3-5/* .
~/.steam/steam/steamapps/common/Proton 6.3$ ls -la proton_dist.tar
-rwxr-xr-x 1 mloveley mloveley 1047756800 Aug 30 15:05 proton_dist.tar
~/.steam/steam/steamapps/common/Proton 6.3$

Then after clicking play the laucher appeared images, buttons, adverts and all. I could get into the game without issues at this point.

I then validated the Tool Proton-6.3, after the updates were downloaded I ran the game again and it crashed before the launcher started.

Looks like a regression to me. I can upload working a broken logs from PROTON_LOG=1 output if it helps. Let me know if you need anything else.

alasky17 commented 3 years ago

@mloveley Thank you for testing that :) I'm a bit stumped because I can't reproduce the failure here on AMD or NVIDIA.

Both DXVK and VKD3D-proton were updated between 6.3-5 and 6.3-6 - It looks like there is a way to switch between dx11 and dx12 in Sniper Elite 4 via the launcher. Could you try switching from whichever dx mode you are currently using to the other one and see if you still get the crash?

mloveley commented 3 years ago

It seems to make no difference if DX11 or DX12 is selected in the launcher. I was using DX11 previously. Trying DX12 I see similar behavior.

I selected DX12 while starting the game with 5.13. then when launching on 6.3-6 It crashed. Applying the 6.3-5 files I could see in the launcher that DX12 was still selected.

Comparing working and broken session Logs I see the following difference.

The working one has "Fossilize INFO: Overriding serialization path:" whereas the broken has a EXCEPTION_ACCESS_VIOLATION mesage steam-312660.log.dx12.broken.6.3.6.log steam-312660.log.dx12.working.6.3-5.log

Working:-

grep -A20 "DXGI: NvAPI workaround enabled, reporting AMD GPU" steam-312660.log.dx12.working.6.3-5
info:  DXGI: NvAPI workaround enabled, reporting AMD GPU
info:  Adapter LUID 0: 0:3f5
304:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.3.1.
304:info:vkd3d_instance_init: vkd3d-proton - build: 72d9b322b89c325.
skipping config: /home/mloveley/.config/MangoHud/wine-SniperElite4.conf [ not found ]
skipping config: /home/mloveley/.local/share/Steam/steamapps/common/Proton 6.3/dist/bin/MangoHud.conf [ not found ]
skipping config: /home/mloveley/.config/MangoHud/wine-preloader.conf [ not found ]
skipping config: /home/mloveley/.config/MangoHud/MangoHud.conf [ not found ]
304:fixme:d3d12_find_physical_device: Could not find Vulkan physical device for DXGI adapter.
304:warn:d3d12_find_physical_device: Using first available physical device...
Fossilize INFO: Overriding serialization path: "/home/mloveley/.local/share/Steam/steamapps/shadercache/312660/fozpipelinesv5/steamapprun_pipeline_cache".
304:warn:vkd3d_memory_info_find_global_mask: Blocking memory type 10 for use (PCI-pinned memory).
304:info:vkd3d_bindless_state_get_bindless_flags: Device does not support VK_VALVE_mutable_descriptor_type.
304:fixme:d3d12_device_caps_init_feature_options1: TotalLaneCount = 1920, may be inaccurate.
17490.787:012c:0130:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\d3d11.dll" at 6A540000: native
17490.788:012c:0130:trace:seh:NtQueryInformationThread (0xd8,0,0x6df154,1c,(nil))
17490.788:012c:0130:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\d3d11.dll" : native
17490.789:012c:0130:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\d3d11.dll" at 6A540000: native
17490.790:012c:0130:trace:seh:NtQueryInformationThread (0xe8,0,0x6df0a4,1c,(nil))
info:  Game: SniperElite4.exe
info:  DXVK: v1.9

Broken

grep -A20 "DXGI: NvAPI workaround enabled, reporting AMD GPU" steam-312660.log.dx12.broken.6.3.6
info:  DXGI: NvAPI workaround enabled, reporting AMD GPU
info:  Adapter LUID 0: 0:3f5
304:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.4.0.
304:info:vkd3d_instance_init: vkd3d-proton - build: cafe99e223296e2.
skipping config: /home/mloveley/.config/MangoHud/wine-SniperElite4.conf [ not found ]
skipping config: /home/mloveley/.local/share/Steam/steamapps/common/Proton 6.3/dist/bin/MangoHud.conf [ not found ]
skipping config: /home/mloveley/.config/MangoHud/wine-preloader.conf [ not found ]
skipping config: /home/mloveley/.config/MangoHud/MangoHud.conf [ not found ]
304:fixme:d3d12_find_physical_device: Could not find Vulkan physical device for DXGI adapter.
304:warn:d3d12_find_physical_device: Using first available physical device...
17286.678:012c:0130:trace:seh:dispatch_exception code=c0000005 flags=0 addr=F16E5792 ip=f16e5792 tid=0130
17286.678:012c:0130:trace:seh:dispatch_exception  info[0]=00000000
17286.678:012c:0130:trace:seh:dispatch_exception  info[1]=bdb8a218
17286.678:012c:0130:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
17286.678:012c:0130:trace:seh:dispatch_exception  eax=f2c7e250 ebx=7e5c6f10 ecx=00000000 edx=f6ea5b58 esi=f7588860 edi=00000000
17286.678:012c:0130:trace:seh:dispatch_exception  ebp=f2c7e250 esp=006dcb2c cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010286
17286.678:012c:0130:trace:seh:call_vectored_handlers calling handler at 6FAD1550 code=c0000005 flags=0
17286.678:012c:0130:trace:seh:call_vectored_handlers handler at 6FAD1550 returned 0
17286.678:012c:0130:trace:seh:call_vectored_handlers calling handler at 6F488E50 code=c0000005 flags=0
17286.678:012c:0130:trace:seh:call_vectored_handlers handler at 6F488E50 returned 0
17286.678:012c:0130:trace:seh:call_vectored_handlers calling handler at 7B00AE10 code=c0000005 flags=0
alasky17 commented 3 years ago

@mloveley Unfortunately there isn't anything super useful in the logs :/ It turns out that the test I had you do with dx11 vs dx12 wasn't very conclusive. I think that the simplest way to rule out a dxvk/dxgi regression is for you to drop in older dxvk into Proton 6.3-6.

To do this, you can just untar the dxvk release that was included in 6.3-5 (https://github.com/doitsujin/dxvk/releases/tag/v1.9) and drop the x64 files into Proton 6.3/dist/lib64/wine/dxvk/. and the x32 files into Proton 6.3/dist/lib/wine/dxvk/. Please make sure that you have the real 6.3-6 in Proton 6.3-6 first :)

After this test, you can just delete the whole dist folder, and it will recreate itself with the official 6.3-6 files the next time you launch a game with Proton :+1:

mloveley commented 3 years ago

Gotta love a weird issue. I first validated Proton-6.3, launching Sniper elite failed as normal

Before:-

~/.steam/steam/steamapps/common/Proton 6.3/dist$ md5sum lib*/wine/dxvk/*
60a1ba705ffc5e9678654cb075d2b705  lib64/wine/dxvk/d3d10_1.dll
7ac995ffed3f51a654988274d8e58b21  lib64/wine/dxvk/d3d10core.dll
b9c8d259a1f24ac0cd4c94e31b0c1889  lib64/wine/dxvk/d3d10.dll
4346bd690e777fdb12090c1cf3c5cd77  lib64/wine/dxvk/d3d11.dll
b0ec01e7af13734a5a1dfb25bb00dca3  lib64/wine/dxvk/d3d9.dll
082477a7fe64c9cf1bfd946a0b6db0be  lib64/wine/dxvk/dxgi.dll
3ae15b731390d8c881c026aec951426d  lib64/wine/dxvk/dxvk_config.dll
ebf9f56361474be9221fb983805f1b48  lib64/wine/dxvk/openvr_api_dxvk.dll
46b0402464f4eb8dc2660f17f3883ddf  lib64/wine/dxvk/version
0a0dfda779854d1f62e8da43d6be3e6f  lib/wine/dxvk/d3d10_1.dll
0087cf35c4e766368fb3b61a2b22332f  lib/wine/dxvk/d3d10core.dll
c9a15f91ebe061f6d080fb13e0e442b5  lib/wine/dxvk/d3d10.dll
b18b8c263e003706868cd1459b7b4300  lib/wine/dxvk/d3d11.dll
7dfd1ff56c5f149136f8010bec3e039f  lib/wine/dxvk/d3d9.dll
94019b00cb7ad96566c00a31d591770a  lib/wine/dxvk/dxgi.dll
5c6c51477deffab2e19691dde594fbb3  lib/wine/dxvk/dxvk_config.dll
296e1b6ac5f0287f9cd1590b76662d15  lib/wine/dxvk/openvr_api_dxvk.dll
46b0402464f4eb8dc2660f17f3883ddf  lib/wine/dxvk/version
~/.steam/steam/steamapps/common/Proton 6.3/dist$

After replacing the DXVK with the 1.9 version

~/.steam/steam/steamapps/common/Proton 6.3/dist$ md5sum lib*/wine/dxvk/*
bd3abb16f4ed16dfbfc37ced2716a2b8  lib64/wine/dxvk/d3d10_1.dll
f7020f79f38e24d7ed862c759c5ec5e0  lib64/wine/dxvk/d3d10core.dll
6c3b9659350dfda45f6d4f108fbe363d  lib64/wine/dxvk/d3d10.dll
a2c2fa6e1e2fbb2f1545af52c8f110a3  lib64/wine/dxvk/d3d11.dll
1a93272ed35cc6276934cf9c5a28ec36  lib64/wine/dxvk/d3d9.dll
65068f691225fa31858e46ba55cc5a2e  lib64/wine/dxvk/dxgi.dll
3ae15b731390d8c881c026aec951426d  lib64/wine/dxvk/dxvk_config.dll
ebf9f56361474be9221fb983805f1b48  lib64/wine/dxvk/openvr_api_dxvk.dll
46b0402464f4eb8dc2660f17f3883ddf  lib64/wine/dxvk/version
12eec2830ec45a17df84b3a181e6050e  lib/wine/dxvk/d3d10_1.dll
511cc556068519714e61ec304d38aab9  lib/wine/dxvk/d3d10core.dll
7d425739a77ec644d94bab32805da69f  lib/wine/dxvk/d3d10.dll
f7682d8da9655003b88b8347eceb6a2b  lib/wine/dxvk/d3d11.dll
12c2be145ab7f3072a873f9ddad4a74e  lib/wine/dxvk/d3d9.dll
3177f3ba6f7b8fb194942d6c3e0da241  lib/wine/dxvk/dxgi.dll
5c6c51477deffab2e19691dde594fbb3  lib/wine/dxvk/dxvk_config.dll
296e1b6ac5f0287f9cd1590b76662d15  lib/wine/dxvk/openvr_api_dxvk.dll
46b0402464f4eb8dc2660f17f3883ddf  lib/wine/dxvk/version
~/.steam/steam/steamapps/common/Proton 6.3/dist$

No change in the game behavior. The launcher again failed to start. steam-312660.log.6.3-6.dxvk.1.9.log

alasky17 commented 3 years ago

@mloveley well dang ... I guess it's lucky that I already had a backup next thing for you to test to try to narrow this down haha. Part of the issue here is that there were a ton of commits between 6.3-5 and 6.3-6, so I'm attempting to narrow down the regression as much as possible. I uploaded another build to the same folder as the 6.3-5 build for you to try - this one is an old experimental build. Lock code is still regression. https://www.codeweavers.com/xfer/alasky/proton-6.3-6/ Edit: you can drop this one in the same way as the 6.3-5 build :)

mloveley commented 3 years ago

Ok I tried this version. it looks like it has the same behavior.

steam-312660.log.experimental-6.3-20210730.log

kisak-valve commented 3 years ago

Maybe try temporarily disabling MangoHUD with something like sudo mv /usr/share/vulkan/implicit_layer.d/MangoHud.json /usr/share/vulkan/implicit_layer.d/MangoHud.json.disabled and see if that has an effect?

mloveley commented 3 years ago

Moved the MangoHud Json file,

$ ls -la /usr/share/vulkan/implicit_layer.d/MangoHud.json*
-rw-r--r-- 1 root root 595 Jul 31 22:30 /usr/share/vulkan/implicit_layer.d/MangoHud.json.disabled
$

and theres no change in behaviour.

steam-312660.log.experimental-6.3-20210730.no-mangohud.log

I removed everything in ~/.local/share/Steam/steamapps/common/Proton 6.3 and redownloaded Proton 6.3. Same behavior in Sniper elite with Mango Hud Disabled.

steam-312660.log.6.3-6.no-mangohud.log

kisak-valve commented 3 years ago

Thanks for checking at least. It should be fairly obvious how to revert that change.

mloveley commented 3 years ago

I'm good with how to revert that ;)

As for your trouble replicating this. My laptop has a Hybrid Rysen7 (integrated AMD) with a Nvidia RTX. At the start of this I had the nvidia in performance mode (ie X was running by default on it). I tried switching to on demand and added some extra env variables to pick the NV card. However sniper elite with 6.3-6 seems to be affected in either mode, with or without the env variables. In all cases reverting back to 6.3-5 works for me (the launcher and therefore the game start). I haven't noticed anything else being borked on Proton 6.3-6.

amdgpu drivers are pretty stock for whatever ubuntu 20.04 installs, I didn't mess with them. Ubuntu was a minimal install which has gradually grown over time as I play and get other stuff working.

Heres a updated steam system information in case it helps. steam-sys-info.txt

I'm happy to try other proton versions to narrow this down. if you want to make a few available I'll give each a go in turn.

alasky17 commented 3 years ago

@mloveley Thank you for being so willing to spend time testing :) I agree its likely something specific to your laptop setup, which sadly doesn't narrow it down quite as much as I'd like.

On a positive note, I was actually hoping that the experimental build would have the failure :D I just uploaded a build to the same place called "sniper-elite-regression-deploy" -- if that one does not crash, then I can create a lineup of builds for you to try tomorrow. Fingers crossed :)

mloveley commented 3 years ago

Progress - That one worked as you expected.

steam-312660.log.sniper-elite-regression-deploy.log

alasky17 commented 3 years ago

@mloveley Woohoo!! That narrows it down to 6 commits if I remember correctly from yesterday. It will probably take me until sometime tomorrow to get the first batch of test builds prepared. Thank you again!! :grinning:

alasky17 commented 3 years ago

@mloveley The first round of test builds is uploaded to that same folder :) In order to minimize the amount of testing, you should test in this order, stopping if you get a failure: cdb1448e1, 9db90e3a3, 2b2e44835 :+1:

mloveley commented 3 years ago

All 3 are working for me. cdb1448e1 : working 9db90e3a3 : working 2b2e44835 : working

I have logs if you would like them. Between each test I reset the Proton version to stock by removing the previous files and validating 'Proton 6.3'.

alasky17 commented 3 years ago

@mloveley Sweet! I'll get round 2 building :)

No need for logs yet. A log could be useful once we find the problematic patch and can add more useful logging, but even then I'm not sure.

alasky17 commented 3 years ago

@mloveley 2 final builds to try in this order: bd2e216f5, c70932f ... Hopefully one of these fails :)

mloveley commented 3 years ago

bd2e216f5 - failed to start c70932f - failed to start So both failed. hopefully that points you in the right direction.

As before both were tested from what I belive was a clean and freshly validated Proton 6.3 base.

alasky17 commented 3 years ago

@mloveley I have one final build with just the suspected commit reverted to confirm that I did all of this right. sniper-elite-regression-deploy-revert-1cc210d in the folder. Then we'll have to figure out what to actually do about this next week.

Thank you again for all of this testing!!!

mloveley commented 3 years ago

Actually this version seems to still be broken for me. 1cc210d - failed to start

I guess it was the other commit. steam-312660.log.1cc210d.log

alasky17 commented 3 years ago

@mloveley Whoops, I think that was my fault for misinterpreting the results - I uploaded what is hopefully one final build to test : sniper-elite-regression-deploy-revert-71849a9f.tar.xz

mloveley commented 3 years ago

Success! Sniper elite launches for me with that version of proton. Need anything else from me?

alasky17 commented 3 years ago

@mloveley Not that I know of right now. Looking into next steps now that we have the commit narrowed down. Thank you!

alasky17 commented 2 years ago

@liam-middlebrook It looks like the recent VK spec version bump is causing a launch failure with Sniper Elite 4. Unfortunately it appears to be a somewhat specific problem as I was unable to reproduce locally. The regression test blamed: commit 71849a9f5b0f04c7987d2d7707298ea6834d3d8f Author: Liam Middlebrook lmiddlebrook@nvidia.com winevulkan: Update to VK spec version 1.2.178.

Interestingly, the build that works for @mloveley includes winevulkan: Update to VK spec version 1.2.176 so it is something specifically about the bump from 1.2.176 to 1.2.178 that is causing Sniper Elite 4 to crash. (The final test working build is 6.3-6 with only 71849a9f reverted).

opal1974 commented 2 years ago

With the current proton experimental, the game now seems perfect. I no longer need to use the 6.0 release to get it to launch. The launcher, for the first time for me, now appears as it should.

gregor3000 commented 2 years ago

experimental no longer works. worked out of the box before. played the whole July, got all master skins, but after latest update it would no longer start. 7.0.3 does not start it at all. experimental worked well before but no longer works and instead gives an error.

steam-312660.log

https://gist.github.com/gregor3000/972de41982e9cd8aa95c1fbc7bec01aa#file-se4sysinfo-txt

System: Host: stari Kernel: 5.4.0-122-generic x86_64 bits: 64 Desktop: KDE Plasma 5.18.8 Distro: Ubuntu 20.04.4 LTS (Focal Fossa) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser/root required> Mobo: ASUSTeK model: PRIME B450M-A II v: Rev X.0x serial: <superuser/root required> UEFI [Legacy]: American Megatrends v: 0310 date: 09/01/2020 CPU: 6-Core: AMD Ryzen 5 3600 type: MT MCP speed: 2196 MHz min/max: 2200/3600 MHz Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nvidia v: 470.141.03 Display: x11 server: X.Org 1.20.13 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa tty: N/A OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 470.141.03 Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Drives: Local Storage: total: 5.46 TiB used: 1.22 TiB (22.3%) Info: Processes: 327 Uptime: 6h 19m Memory: 31.34 GiB used: 3.45 GiB (11.0%) Shell: bash inxi: 3.0.38 `

Error that is thrown out says: " DirectX failed to initialise. This game requires at least a DirectX11-level graphics card, and a version of Windows which supports DirectX11 (windowsXP is not supported). Error Code: -2005270526 "

kisak-valve commented 2 years ago

Hello @gregor3000, the build of DXVK which is part of Proton Experimental was updated and now requires NVIDIA 510.47 or newer.

opal1974 commented 2 years ago

Still works for me on latest experimental. I don't use Nvidia but rather AMD so it seems like its related to that for the other user.

lucifertdark commented 2 years ago

@gregor3000 your drivers are out of date, I'm using the same graphics card as you & the game runs perfectly with the 515.65.01 drivers.

gregor3000 commented 2 years ago

but then why it doesn't work on 7.0.3? i read that some games do not run if you upgrade to 5.10+ and this is not the only game i play. so makes me a bit worried to just upgrade to 5.10 + which is the next recommended version in additional drivers. currently other games work well. just Sniper Elite with this new issue.

sak96 commented 1 year ago

i am having issue when using audio with Bluetooth headphone no audio is generated. but if i connect it via wired mode it works once i set headphone as default profile