FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

WIP: Parse glTF extensions by keveleigh · Pull Request #1231 · StereoKit/StereoKit · GitHub

WIP: Parse glTF extensions - #1231

Draft
keveleigh wants to merge 4 commits into
StereoKit:developfrom
keveleigh:gltf-extensions
Draft

keveleigh wants to merge 4 commits into
StereoKit:developfrom
keveleigh:gltf-extensions

Conversation

Copy link
Copy Markdown

This test implements the KHR_node_visibility extension and sets the visibility of each node.

Open questions/tasks:

  1. Should extension data be saved in each node's info dictionary? Since the extensions list is a dictionary of dictionaries, we may need to squash the two keys to fit into info (something like { "KHR_node_visibility: visibility": "true" })
  2. I'm sure there's a better way to iterate through a dictionary_t than what I'm doing here 😅

Important

KHR_node_visibility is not yet a merged and ratified glTF extension. See KhronosGroup/glTF#2410 for more info

Signed-off-by: Kurtis <keveleig@qti.qualcomm.com>
Signed-off-by: Kurtis <keveleig@qti.qualcomm.com>
Signed-off-by: Kurtis <keveleig@qti.qualcomm.com>
Signed-off-by: Kurtis <keveleig@qti.qualcomm.com>

This branch has not been deployed

No deployments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant


Back | FazBrowse Home | New Git URL