KhronosGroup / KhronosGroup/glTF

KHR_draco_mesh_compression: Clarify accessor details and indices resolving.

Open
#1,306 4 comments 0 reactions 0 assignees View on GitHub
mesh compression needs discussion needs pull request
Dominant language
HTML
Stars
7.8k
Forks
1.2k
Avg merge
17h 26m
Merged PRs (30d)
5

Description

Please clarify, which values the accessor should have:

count: Is this the value for resolved or unresolved values? From my understanding it should be the resolved value.

componentType: If the uncompressed data is decoded, the result has the given component type and no conversion is needed? I assume no conversion is needed.

type: If the uncompressed data is decoded, the number of elements are "correct" and no conversion is needed? Like above, I assume no conversion is needed.

Finally, it should be explained, how indices have to be resolved.

Contributor guide

Open the contributing guide

Research direction

Review the KHR_draco_mesh_compression specification and its accessor and index-resolution guidance. Clarify whether count, componentType, and type describe resolved data, and document how indices are resolved; the issue is complete when these cases are explicit.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.