-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VKD3D-Proton Support Request #324
Comments
nice review! |
opened issue (#341) asking specifically for taskShader for enable mesh shaders under VKD3D now that games like Alan Wake 2 can make use of it.. (for better perf?) |
I see that the 2024.Q1.2 driver now has |
@bluestang2006 VK_EXT_graphics_pipeline_library is disabled for dxvk now because of a corruption with VK_EXT_graphics_pipeline_library enabled. This will be fixed in next release. |
I'm using a much more recent version of VKCTS, off the main branch. I'll wait for the next release when it's enabled for DXVK. Any updates on the Feature Level (FL) and Shader Model (SM) requests for VKD3D? |
We reproduced failures in dEQP-VK.pipeline.fast_linked_library.bind_buffers_2.* with new version CTS. It's pre-existing and has to do with robustness 2 not GPL fast link. We are working on it. Regarding the Feature Level (FL) and Shader Model (SM) support for VKD3D: |
Adding workarounds for broken apps that are already in the wild is fine, but when AMDVLK just selectively chooses not to fully support all apps except for some specific ones, that only makes me as an app developer selectively not want to support AMDVLK at all — or support it by faking VkApplicationInfo and possibly detouring other detection mechanisms, which, I think, might actually be a good technical measure to counter this practice. Especially if this filtering is done to show strong sides of the hardware/driver in a few curated examples while sweeping the subpar aspects under the rug, then I don't think it would be respectful to use apps relying on certain features as word-of-mouth marketing demos when in reality you're actively setting up roadblocks for developers who want to use that functionality. This is not the responsibility of a driver, especially in Vulkan which is explicitly designed in a way that lets drivers and apps communicate as much information about each other as possible. on a semi-unrelated note, I'm planning to expose 1000+ descriptor sets and around 64 KB of push constants (minus things like the workaround for missing cubemap array size queries in the hardware) in my Vulkan driver for ancient AMD GPUs (that exists because I started working on Mesa due to that fragment shader interlock drama)… but they have a completely different binding model of course 🙃 |
Task shader support is open-source. It's part of VK_EXT_mesh_shader, but it's conditional on kernel and firmware support. I've added more info in #341. |
@Triang3l Thanks for your feedback! For VK_EXT_fragment_shader_interlock, we will consider the decision to expose it by default once we have an implementation. |
@jinjianrong really, many thanks for sharing your plan/roadmap on AMDVLK VKD3D support!! "finally" expectations are clear! |
@jinjianrong @Triang3l a suggestion regarding VK_NV_compute_shader_derivatives and VK_EXT_fragment_shader_interlock exposure.. even if you have concerns enabling unconditionally, excepting selected/curated apps, you have already a mechanism in place via AMDVLK_ENABLE_DEVELOPING_EXT env variable to expose such extensions maybe.. |
adding latest results of running latest AMDVLK around various VKD3D profiles: basically primary problems the same but adding new:
Testing profile VP_D3D12_maximum_radv adds:
and older ones like:
|
This issue is to request required features and extensions that should improve AMDVLK on VKD3D-Proton. Just recently, VKD3D added VK Profiles for D3D feature and shader model level support.
AFAICT, AMDVLK can support baseline D3D Feature Level (FL) 12.0 and up to Shader Model (SM) 6.6 but doesn't support FL 12.2 and SM 6.6 because of a few missing features/extensions. While some D3D12 games are playable on AMDVLK w/ current drivers (v2023.Q2.2), others are not due to missing features/extensions.
Lastly, there are a few other features that are needed for optimal performance.
For FL 12.1, AMDVLK will need:
For FL 12.2, AMDVLK will need:
For SM 6.6, AMDVLK will need:
For overall optimal performance, AMDVLK will need:
Updated June 26, 2024
The text was updated successfully, but these errors were encountered: