KhronosGroup / KhronosGroup/COLLADA2GLTF
transparency is not clearly exported nor specified
- Dominant language
- C++
- Stars
- 573
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
Replacing https://github.com/KhronosGroup/glTF/issues/105 (see full discussion there)
> We need specify in "About Shaders" section of the spec how transparency is exported.
Especially when using common profile "details".
>
> The converter needs to be fixed to take into account both A_ONE and RGB_ZERO modes. More mode exists with 1.5 but that would be a good start.
>
> At the moment, only A_ONE is assumed.
Not sure if this will be an issue for the glTF 2.0 PBR version.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the full discussion in KhronosGroup/glTF#105 and the converter's transparency handling; no specific files or tests are named. Compare the About Shaders specification text with the common-profile A_ONE and RGB_ZERO modes, including the current assumption that only A_ONE is used. Done means the transparency export behavior is specified and both named modes are accounted for, with the glTF 2.0 impact resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, documentation, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100