Vulkan : Create a custom pipeline for viewports #7398
Closed
Conversation
This file contains hidden or 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
ocornut
added a commit
that referenced
this pull request
Apr 30, 2024
ocornut
pushed a commit
that referenced
this pull request
Apr 30, 2024
|
Now merged #6325 |
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.
As described in #6325, sometimes we may need a new pipeline for secondary viewports,.
Without this, vulkan validation layer will throw errors and a user may not know what to do.
This is the same patch, but updated to the latest upstream commit and to hopefully gain more attention. I have personally encountered this issue and requesting maintainers to push this upstream.