KhronosGroup / KhronosGroup/glTF
Missing scene support in object model and KHR_node_visibility
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 17h 26m
- Merged PRs (30d)
- 5
Description
Looking over the object model, KHR_interactivity and KHR_node_visibility, it feels like things are underspecified for scenes.
The object model is missing a way to read an asset's default scene or a scene's nodes. Further, there's no way to know which scene is visible, which will ultimately control whether a given node can be visible or not.
It feels like KHR_interactivity needs a notion of the visible scene, which may be the implicit scene defined by all nodes in the asset, and KHR_node_visibility should probably also be applicable to scenes to indicate which scene is visible or not.
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 reading the object model, KHR_interactivity, and KHR_node_visibility material mentioned in the issue. Identify how an asset's default scene, a scene's nodes, and the visible scene are represented today. Done requires an agreed design that addresses scene visibility and its interaction with both extensions.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100