We don't enable the feature unless the driver exposes it. The GetPhysicalDeviceFeatures2 returned value is passed directly to vkCreateDevice() here, so I'm unsure how this is possible.
Uh... that's awkward.
Could this be something related to having multiple GPU on my system?
I have an AMD RX6800, an Intel A380 and ADLP (integrated)
Is this reproducible in the test suite?
Is this reproducible in the test suite?
What test would that be in?
I guess any :)
No, test suite appears to work fine.
I wanted to print out the device features using export VKD3D_DEBUG=trace but apparently that's not working in steam proton experimental
Test suite reports values correctly :
6b65:trace:vkd3d_trace_physical_device_features: VkPhysicalDeviceMeshShaderFeaturesEXT:
6b65:trace:vkd3d_trace_physical_device_features: meshShader: 0x1
6b65:trace:vkd3d_trace_physical_device_features: taskShader: 0x1
6b65:trace:vkd3d_trace_physical_device_features: multiviewMeshShader: 0
6b65:trace:vkd3d_trace_physical_device_features: primitiveFragmentShadingRateMeshShader: 0x1
It's possible there's some confusion with DXGI here and device selection. Does isolating the ICD with VK_ICD_FILENAMES fix it? I've never run into this before fwiw.
For Steam, trace debug is disabled, so you'd want to build yourself with debugoptimized.
It's possible there's some confusion with DXGI here and device selection. Does isolating the ICD with VK_ICD_FILENAMES fix it? I've never run into this before fwiw.
Yeah, I'm running exclusively with VK_ICD_FILENAMES set.
Will build my own version and test.
Okay apologies... The Mesa overlay layer is screwing with the features.
Since I wrote it I guess I get to fix it.
We're running into this error :
Seems like vkd3d-proton is trying to enable this feature we haven't fully worked out yet.
You probably want to check for that before trying to enable it?
Not reporting the extension makes it work for us.