[Vulkan] Fix handling of render target depth #820
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Think I'll have to extend the API a bit, also for Metal. But please create a GitHub issue about it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This restores the functionality of using render targets with depth buffers in Vulkan.
Using multiple render targets is still broken, because the shared render pass is set to only 1 color attachment (and only
VK_FORMAT_B8G8R8A8_UNORMformat) .https://github.com/Kode/Kinc/blob/main/Backends/Graphics5/Vulkan/Sources/kinc/backend/graphics5/vulkan.h#L54
Should more render pass combinations be created in advance or on demand?