Witcher 2 doesn't start

Question

Witcher 2 doesn't start

Closed this issue 5 years ago · 18 comments

Just tested latest d9vk master with The Witcher 2 in Wine, and strangely it fails to start with such errors:

info:  Required Vulkan extension VK_KHR_get_physical_device_properties2 not supported
info:  Required Vulkan extension VK_KHR_surface not supported
info:  Required Vulkan extension VK_KHR_win32_surface not supported
terminate called after throwing an instance of 'dxvk::DxvkError'

That's with Mesa 19.2.0 rc3, so I think those extensions should be supported. I have these installed: libvulkan1:i386, mesa-vulkan-drivers:i386.

Answer 1 · 2019-09-24T03:05:50.000Z

I have it installed as I said: libvulkan1:i386. Something else is off.

Answer 2 · 2019-09-24T03:06:30.000Z

Yeah I deleted that comment already 🐸

This isn't a D9VK bug, but rather a setup issue.

I'm not too familiar with using Vulkan on Debian/Ubuntu so I'm not sure. Definately not on my end though.

Answer 3 · 2019-09-24T03:08:36.000Z

Can you install vulkanutils:i386 and see if 32-bit vkcube or vulkaninfo work?

Answer 4 · 2019-09-24T03:12:38.000Z

I just tested running TW1 with d9vk which is also 32-bit. It started fine, so 32-bit Vulkan in general is OK. Both are symlinking to the same .so files for d9vk. So something got messed up with TW2 somehow.

vkcube from vulkan-tools:i386 also works fine.

Answer 5 · 2019-09-24T03:19:03.000Z

Are you doing this in the same prefix?

Answer 6 · 2019-09-24T03:19:13.000Z

No, separate prefixes. Both created as win32 ones.

Answer 7 · 2019-09-24T03:20:21.000Z

For a test, I can try copying one to another, and see what's going to happen

UPDATE: Hm, TW1 doesn't start at all in TW2 prefix, but probably due to other reasons.

Answer 8 · 2019-09-24T03:29:46.000Z

This is already interesting. I made a copy of TW1 prefix for a test, and also copied TW2 game directory in it. From that prefix, TW1 starts OK with d9vk. TW2 fails like before with same errors.
May be TW2 is some weird mix of 32/64 bit?

Answer 9 · 2019-09-24T03:30:33.000Z

It's not x64 is it? 🐸

Answer 10 · 2019-09-24T03:30:43.000Z

Nope, it shouldn't be. But let me try in 64-bit prefix just to be sure.

Answer 11 · 2019-09-24T03:37:57.000Z

Are you using winelib builds btw?

Answer 12 · 2019-09-24T03:38:27.000Z

Yep, I'm using winelib.

Answer 13 · 2019-09-24T03:40:41.000Z

Right, can you try using a normal mingw build?

https://git.froggi.es/joshua/d9vk/-/jobs

Just to rule that out.

Answer 14 · 2019-09-24T03:42:10.000Z

Let me try with 64-bit one, and then I'll try mingw build.

Answer 15 · 2019-09-24T03:58:57.000Z

With 64-bit prefix + winelib build, same errors as before. Trying now 64-bit prefix + mingw build.

Answer 16 · 2019-09-24T04:02:44.000Z

Same error with 64-bit + mingw build. Game is quite unlikely 64-bit though. I'm going to try now 32-bit + mingw.

Answer 17 · 2019-09-24T04:04:25.000Z

Oh, I think I know what's going on. Let me check something.

Answer 18 · 2019-09-24T04:33:39.000Z

Yep, that was my misconfig. In the startup script it tried to use non existing Mesa. I managed to start it now, though it hangs on the loading screen (not the whole computer, just the game gets stuck). But that would be a separate bug if anything. Closing.