Implement support for depth bounds testing.#189
Merged
Conversation
crud89
added
Vulkan 🌋
Owner
Author
|
Run: checks |
Owner
Author
|
Run: tests |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Describe the pull request
This PR implements support for depth bounds testing. It requires the new
GraphicsDeviceFeature::DepthBoundsTestto be enabled. If supported, a render or mesh shading pipeline can be created with the depth bounds test enabled. This is done by setting theDepthStencilState::DepthState::DepthBoundsTestEnablesetting in the rasterizer state. If a currently bound pipeline has been initialized this way, it is possible to set the minimum and maximum depth bounds on a command buffer by callingICommandBuffer::setDepthBounds.Related issues
Resolves #35.