KhronosGroup / KhronosGroup/COLLADA2GLTF
2.0 models should not have BINORMAL
Open
bug
- Dominant language
- C++
- Stars
- 573
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
Currently we write out BINORMAL from COLLADA if it is present, but it is no longer a valid semantic in glTF 2.0 since it can be computed from TANGENT and NORMAL.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests. Start by locating the COLLADA BINORMAL handling and the glTF 2.0 model-writing path, then trace where the semantic is emitted. Done means BINORMAL is no longer written for glTF 2.0 models when it is present in the COLLADA input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100