Skip to content
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

Problems with Vulkan/DXGI interop on AMD GPU #24

Open
SaltyBet opened this issue Sep 28, 2024 · 4 comments
Open

Problems with Vulkan/DXGI interop on AMD GPU #24

SaltyBet opened this issue Sep 28, 2024 · 4 comments

Comments

@SaltyBet
Copy link

Thread for context:

Developer comments on that thread:

In the Vulkan case, what's happening is SK is changing the D3D12 SwapChain format, and through a mechanism I don't know, they're copying the Vulkan image over to the D3D12 SwapChain without accounting for format mismatch.
It's difficult for me to develop a fix for this problem without getting my hands on an AMD GPU. I expect if they were doing the copy D3D12-side, SK would already be able to detect the format mismatch and correct it.
So it's either Vulkan-side or some proprietary thing in their driver that is exempt from validating image format I'm leaning heavily toward it's something in the driver I probably can't see. If it were being done D3D12-side and not accounted for, the format mismatch would be caught by the driver and the game would instantly crash.

This seems to work fine on NVIDIA.

@owenzhangzhengzhong
Copy link
Collaborator

Hi @SaltyBet,

From reading that thread it seems to be an issue in the vulkan application layer validating image format when translated from D3D12 SwapChain. Can you provide your system specs and a minimally compilable code source that reproduces this issue?

Thanks,
Owen

@SaltyBet
Copy link
Author

SaltyBet commented Oct 1, 2024

Specs:

  • AMD Radeon RX 6800 XT
    • 24.10.37.04-240823a-407010C-AMD-Software-Adrenalin-Edition
  • AMD Ryzen 9 5900X 12-Core Processor
  • Windows 10 Professional (64 bit) 22H2

Latest source (from the dev's repo):

@owenzhangzhengzhong
Copy link
Collaborator

Hi @SaltyBet,

Are you able to provide full runtime of the issue? That's the source for the SK dll that does the injection from application to driver. Which could be the source of the issue, meaning it's not driver related, rather an application issue requiring a SK developer to dig into further. It doesn't seem like there's evidence that it's a driver issue currently.

Thanks,
Owen

@SaltyBet
Copy link
Author

SaltyBet commented Oct 5, 2024

Hi, @owenzhangzhengzhong.

Will forward your comment to the developer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants