@Mkilbride Does this also happen with 1.10.1 or 1.10?
info: Game: bms.exe
info: DXVK: v1.10
info: Built-in extension providers:
info: Win32 WSI
info: OpenVR
info: OpenXR
info: OpenVR: could not open registry key, status 2
warn: OpenVR: VR_InitInternal or VR_ShutdownInternal not found
info: Enabled instance extensions:
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: NVIDIA GeForce RTX 3080 Ti:
info: Driver: 512.59.0
info: Vulkan: 1.3.194
info: Memory Heap[0]:
info: Size: 12108 MiB
info: Flags: 0x1
info: Memory Type[1]: Property Flags = 0x1
info: Memory Type[4]: Property Flags = 0x7
info: Memory Heap[1]:
info: Size: 16344 MiB
info: Flags: 0x0
info: Memory Type[0]: Property Flags = 0x0
info: Memory Type[2]: Property Flags = 0x6
info: Memory Type[3]: Property Flags = 0xe
info: DXGI: NvAPI workaround enabled, reporting AMD GPU
warn: CreateDXGIFactory2: Ignoring flags
info: Game: bms.exe
info: DXVK: v1.10
info: Built-in extension providers:
info: Win32 WSI
info: OpenVR
info: OpenXR
info: OpenVR: could not open registry key, status 2
warn: OpenVR: VR_InitInternal or VR_ShutdownInternal not found
info: Enabled instance extensions:
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: NVIDIA GeForce RTX 3080 Ti:
info: Driver: 512.59.0
info: Vulkan: 1.3.194
info: Memory Heap[0]:
info: Size: 12108 MiB
info: Flags: 0x1
info: Memory Type[1]: Property Flags = 0x1
info: Memory Type[4]: Property Flags = 0x7
info: Memory Heap[1]:
info: Size: 16344 MiB
info: Flags: 0x0
info: Memory Type[0]: Property Flags = 0x0
info: Memory Type[2]: Property Flags = 0x6
info: Memory Type[3]: Property Flags = 0xe
info: DXGI: NvAPI workaround enabled, reporting AMD GPU
warn: DxgiAdapter::QueryInterface: Unknown interface query
warn: 7abb6563-02bc-47c4-8ef9-acc4795edbcf
Yeah it happens on them. Coulda sworn it worked in the past.
Please attach logs as text files or github gists so they don't fill the page.
Does it also happen if you launch the game with -useoldgameui ?
Edit: it might actually be -oldgameui Cant remember.
The game uses both D3D9 and D3D11, from the log it doesn't look like you're using our D3D9 DLL.
That said, it won't work anyway because it requires shared resources for the UI, and the way it does use them is incredibly broken on the game's side.
Huh, I see. Yeah it happens with the oldgamegui.
Weird the PCGamingWiki page states to use DXVK, and a few months ago I was using it, the Xen update happened last year too. Not sure what changed.
As far as i remember it should work with -oldgameui since from what i know that doesn't use shared resources. I think.
But i'll have to check when i get home. Might not have checked on windows.
Yes, then also d3d9.dll suffices.
So I've tried on my windows setup with a R9 380 with both 1.10.2 and 1.10.1.
It works for me if i take the 32bit d3d9.dll and put it into \Black Mesa\bin (which is not next to the exe, tho the conf file needs to be in root next to exe before it gets picked up) and then also run the game with -oldgameui
I haven't tried on the Nvidia setup yet.
The issue I have found with Black Mesa is that -oldgameui has stopped working when added through Steam's Launch Options menu for some reason. If I make my own shortcut to the .exe and apply the launch command there, then it works and I can launch the game with DXVK.
EDIT: This has been addressed by the developers and -oldgameui should work again now.
Closing this because it's mostly likely just caused by the new UI using shared resources, something we cannot support on Windows.
The game works fine on Linux.
d3d9.dllx2 2022-07
Error log
Using the latest, Async or not.