Add isoline domain tessellation test#1285
Open
EmilioLaiso wants to merge 1 commit into
Open
Conversation
Tessellate one isoline into four segments and capture each generated vertex's along-line coordinate (SV_DomainLocation.x) from the domain shader into a UAV; the five evenly spaced values prove the isoline domain ran and subdivided the line as expected.
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
2 participants
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.
Adds a graphics test covering the isoline tessellation domain — tessellate one isoline into four segments and capture each generated vertex's along-line coordinate (
SV_DomainLocation.x) from the domain shader into a UAV.The five evenly spaced values
[0, 0.25, 0.5, 0.75, 1]prove the isoline domain ran and subdivided the line as expected.The two isoline
SV_TessFactorslots are ordered as so:Edges[0]= number of lines,Edges[1]= segments per lineon real D3D12 hardware and on Vulkan, which agree.
WARP orders them the opposite way (a bug?), so it tessellates this patch into four single-segment lines and produces
[0, 0, 0, 0, 1]instead.