Quoting: ArehandoroWhy is dxvk reporting I have 396.24-0?

Because your -20 is the package revision, not the driver version. There is no such thing as 396.24.20 anyway.

Quoting: ShmerlI have no idea why it logs the same thing several times,

DXVK logs that stuff when the game creates a new IDXGIFactory. Now for some reason, game developers seem to think that creating one instance and one device isn't enough and do it over and over again.

Quoting: ShmerlHow did you manage to work around the lack of stream output like features

I didn't, that's kind of the point. And that's also why it might still take several months for this to go live, but it should happen eventually.

Quoting: YoRHa-2B

Quoting: ShmerlHow did you manage to work around the lack of stream output like features

I didn't, that's kind of the point. And that's also why it might still take several months for this to go live, but it should happen eventually.

Interesting, so it would render what's possible, omitting those minor details like decals and the like that are strictly what's used in stream output? I.e. when Khronos and drivers will come around implementing such feature in Vulkan you would be able to make it look even better?

Quoting: YoRHa-2BDXVK logs that stuff when the game creates a new IDXGIFactory. Now for some reason, game developers seem to think that creating one instance and one device isn't enough and do it over and over again.

I see.

Quoting: YoRHa-2B

Quoting: ArehandoroWhy is dxvk reporting I have 396.24-0?

Because your -20 is the package revision, not the driver version. There is no such thing as 396.24.20 anyway.

Gotcha, thanks. Do I only have to wait till a newer version of the drivers is released? I thought in dxvk 0.63 that requirement was going to be relaxed.

Quoting: Shmerl

Quoting: YoRHa-2B

Quoting: ShmerlHow did you manage to work around the lack of stream output like features

I didn't, that's kind of the point. And that's also why it might still take several months for this to go live, but it should happen eventually.

Interesting, so it would render what's possible, omitting those minor details like decals and the like that are strictly what's used in stream output? I.e. when Khronos and drivers will come around implementing such feature in Vulkan you would be able to make it look even better?

I read that in a completely different way.
No point for further speculating though in my view, sometimes the gears just turn slowly.

I installed 396.45 and now I get the following output:

000f:err:service:process_send_command receiving command result timed out
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 1053
002f:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
002f:err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 4.5.
info:  Game: witcher3.exe
info:  DXVK: v0.63-8-g0aa7ab8
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
002f:err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
002f:err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3
err:   DxvkInstance::createInstance: Failed to create Vulkan instance
0015:err:service:process_send_command receiving command result timed out
002a:err:plugplay:handle_bus_relations Failed to load driver L"WineHID"
002a:err:plugplay:try_add_device Building report descriptor failed, removing device
002f:fixme:msvcrt:__clean_type_info_names_internal (0x2421878) stub
002f:fixme:msvcrt:__clean_type_info_names_internal (0x2335768) stub

There is also a prompt that reads: "GPU does not meet minimal requirements. Support for Directx is required." but the GTX 970 has it, so not sure how to tackle that one.

Quoting: Arehandoro

Quoting: YoRHa-2B

Quoting: ArehandoroWhy is dxvk reporting I have 396.24-0?

Because your -20 is the package revision, not the driver version. There is no such thing as 396.24.20 anyway.

Gotcha, thanks. Do I only have to wait till a newer version of the drivers is released? I thought in dxvk 0.63 that requirement was going to be relaxed.

What requirement?

You don't have to use beta drivers anymore for DXVK 0.63 , you can use 396.45

Quoting: Leopard

Quoting: Arehandoro

Quoting: YoRHa-2B

Quoting: ArehandoroWhy is dxvk reporting I have 396.24-0?

Because your -20 is the package revision, not the driver version. There is no such thing as 396.24.20 anyway.

Gotcha, thanks. Do I only have to wait till a newer version of the drivers is released? I thought in dxvk 0.63 that requirement was going to be relaxed.

What requirement?

You don't have to use beta drivers anymore for DXVK 0.63 , you can use 396.45

The requirement to have 396.45 for "VK_EXT_vertex_attribute_divisor" though apparently that's only when building from master. Not sure if the version in AUR includes that. I have managed to get a different log, and the window prompt doesn't happen anymore, but still fails to launch:

000f:err:service:process_send_command receiving command result timed out
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 1053
info:  Game: witcher3.exe
info:  DXVK: v0.63
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  GeForce GTX 970:
info:    Driver: 396.45.0
info:    Vulkan: 1.1.70
info:    Memory Heap[0]: 
info:      Size: 4096 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 11960 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[9]: Property Flags = 0x6
info:      Memory Type[10]: Property Flags = 0xe
info:  D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
warn:  Vulkan extension VK_EXT_vertex_attribute_divisor not supported
info:  Enabled device extensions:
info:    VK_EXT_shader_viewport_index_layer
info:    VK_KHR_dedicated_allocation
info:    VK_KHR_descriptor_update_template
info:    VK_KHR_get_memory_requirements2
info:    VK_KHR_image_format_list
info:    VK_KHR_maintenance1
info:    VK_KHR_maintenance2
info:    VK_KHR_sampler_mirror_clamp_to_edge
info:    VK_KHR_shader_draw_parameters
info:    VK_KHR_swapchain
0036:fixme:ver:GetCurrentPackageId (0x19fcfdc0 (nil)): stub
002e:fixme:msvcrt:__clean_type_info_names_internal (0x2421878) stub
002e:fixme:msvcrt:__clean_type_info_names_internal (0x2335768) stub

The VK_EXT_vertex_attribute_divisor requirement was removed in 0.63 (although of course DXVK will still print a warning if it isn't available). Not sure what your issue is, but this is not it.

FWIW, Witcher 3 should run out of the box with a fresh wine prefix that just has 64-bit DXVK set up. Maybe try that.

It’s actually a new prefix/installation I did recently because the old one wouldn’t work either.

Fun fact, if I launch the game from the gui it works. But fails to launch from the terminal.

Quoting: ArehandoroBut fails to launch from the terminal.

You likely are launching it incorrectly. When you run the binary with Wine, you have to be in the directory where the binary is located.