-
Notifications
You must be signed in to change notification settings - Fork 998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support getting hit vertex positions. #7141
Closed
Closed
+8,825
−126
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
get up to latest
# Conflicts: # wgpu-core/src/device/resource.rs
# Conflicts: # wgpu-core/src/device/life.rs
# Conflicts: # wgpu-core/src/device/life.rs
# Conflicts: # wgpu-core/src/device/life.rs
# Conflicts: # wgpu-core/src/device/life.rs
# Conflicts: # wgpu-core/src/device/life.rs # wgpu/src/backend/wgpu_core.rs
upgrade ray-tracing branch to main branch
…-tracing-get-vertex # Conflicts: # etc/specs/ray_tracing.md # wgpu-core/src/device/ray_tracing.rs
I seem to have broken something... I'm going to see if I can fix this, otherwise I'll open a new branch with the changes squashed into it. |
Decided that this is unfix-able with my knowledge of git, opened #7183 |
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.
Connections
Fixes #6763
Description
Supports getting the vertices out of the ray query with a new function. In naga's extended WGSL language this requires
acceleration_structure<vertex_return>
, even though other shader languages don't require this, due to validation requirements. If we go the same route as other shader languages, the validation requirements (as far as I can tell) areget*HitVertexPositions
tags ray query object. Thisray_query
then needs to find all uses of itself - iterating through all blocks it's valid in and finding anyrayQueryInitialize
and tagging allacceleration_structure
s. This alternate design could also lead to more user confusion. The implemented design instead disallowsrayQueryInitialize
initializing aray_query<vertex_return>
with a untaged acceleration structure and disallowing callingget*HitVertexPositions
with an untaggedray_query
.Testing
Adds an example which demonstrates the use of the newly added function. Adds two tests for invalid uses of this flag.
Checklist
cargo fmt
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
cargo xtask test
to run tests.CHANGELOG.md
. See simple instructions inside file.