NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
TilesRenderer: Raycasting / visibility checking will fail if geometry is modified outside the tile bounding box
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
This can happen with the tile flattening plugin or other custom geometry modification or animation. Related to #1321.
One option is to update the tile bounds as the geometry is modified. Or to fix raycasting the ability to disable to tree-traversal optimization could be brought back at the cost of performance. In most use cases, though, I suspect including a "raycast geometry" for the flattening shape could be good enough.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing TilesRenderer's raycasting and visibility-checking path, then compare the behavior described here with related issue #1321. Reproduce the case where tile geometry is modified outside its bounding box, including the tile flattening plugin scenario; done means modified geometry is correctly considered during raycasting and visibility checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100