-
Notifications
You must be signed in to change notification settings - Fork 18
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
Refactor raytrace node configurations and introduce non-hit distance handling #257
Conversation
9bbfcc4
to
67e5d88
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job 👍
The proposed changes make NON_HIT_VALUE
to be inconsistent in some scenarios. It needs to be corrected (I have left a suggestion for it).
The rest of the comments are more about cosmetic changes.
+ Please rebase PR onto the latest |
Co-authored-by: Mateusz Szczygielski <[email protected]>
4960c4b
to
aa22f09
Compare
aa22f09
to
cf763c2
Compare
cf0e14a
to
ae8df93
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 could be merged if CI passes 🤖
…handling (#257) * Add prototype of rgl_node_raytrace_configure_velocity * Add prototype of tape_node_raytrace_configure_velocity * Add invalid_node_object test * Add prototype of rgl_node_raytrace_configure_distortion * Add documentation * Refactor usage of raytrace in motion & with distortion * Changes in the api documentation * Add prototype of raytrace_configure_non_hit_distance_values * Add prototype of raytrace_configure_non_hit_distance_values * Finish implementation and tests * Apply suggestions from code review Co-authored-by: Mateusz Szczygielski <[email protected]> * Review fixes * Re-review fixes --------- Co-authored-by: Mateusz Szczygielski <[email protected]>
No description provided.