CesiumGS / CesiumGS/cesium

Consider adding a `tileset.debugShowModelBoundingVolume` flag

Open
#10,213 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

category - 3d tiles category - model/gltf
Dominant language
JavaScript
Stars
15.8k
Forks
3.9k
Avg merge
4d 6h
Merged PRs (30d)
34

Description

Right now, both Model/ModelExperimental and Cesium3DTileset have a debugShowBoundingVolume flag, but they do two different things:

  • tileset.debugShowBoundingVolume shows the tile bounding volumes.
  • model.debugShowBoundingVolume shows the bounding volumes for each primitive.

Sometimes when debugging tilesets, the primitive bounding volumes would be helpful.

For ModelExperimental, this would be easy, just need to set model.debugShowBoundingVolume = tileset.debugShowModelBoundingVolume in ModelExperimental3DTileContent when constructing a model. I'm not sure about the other older Xxx3DTileContent classes such as Vector3DTileContent off the top of my head.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading ModelExperimental3DTileContent and the existing debugShowBoundingVolume handling in ModelExperimental and Cesium3DTileset. Trace how the older Xxx3DTileContent classes construct models, including Vector3DTileContent. Done means the new tileset flag consistently exposes primitive bounding volumes wherever the relevant content supports it.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.