Raycaster: Add barycoord to intersection result, make attribution interpolation more convenient. #29340
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.
Related issue: --
Description
Currently raycasting only returns a few pre-interpolated results but not all, which can be useful in cases where other attributes need to be interpolated abitrarily, such as when sampling the recently-added Cesium metadata plugins for 3D Tiles Renderer. This PR outputs the barcoord of the hit point relative to the surface to mesh raycast intersections and adds a
getAttributeInterpolationFromBarycoord
function to Triangle to make interpolating attributes more convenient.Currently this is the code that needs to be run to interpolate a uv3 attribute after raycast:
And this is what it is after:
This contribution is funded by Cesium GIS Ecosystem Grant