[0041] TriangleObjectPositions proposal #632
Merged
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
damyanp
requested changes
Sep 11, 2025
tex3d
approved these changes
Sep 11, 2025
Co-authored-by: Damyan Pepper <[email protected]>
jenatali
force-pushed
the
triangle-hit-pos
branch
from
2c702e6 to
6a64bb3
Compare
jenatali
changed the title
damyanp
approved these changes
Sep 11, 2025
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.
Replaces #571 and #572.
I've also fleshed out the doc slightly, to codify that this is targeting shader model 6.10, and now that shader model 6.9 is available, to unresolve the DXIL opcode discussion about return type to mention that
float3andvector<float, 9>are available as options. I added a SPIR-V section and references to DXIL SER as well.