Support for Morphed `Texcoord_n` and `Color_n` Attributes
See original GitHub issueLooks like the glTF spec added the optional Texcoord_n, and Color_n morph targets. Should this be supported in IMorphTargetBuilder
and IMeshDecoder
?
Client implementations SHOULD support at least three attributes — POSITION, NORMAL, and TANGENT — for morphing. Client implementations MAY optionally support morphed TEXCOORD_n and/or COLOR_n attributes. https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#morph-targets
I have a file format I’m converting to that supports Texcoord_0 and Color_0 morphing, however it’s not an often used feature.
Issue Analytics
- State:
- Created 2 years ago
- Comments:22 (22 by maintainers)
Top Results From Across the Web
Support Import/Export of Morphed Texcoord_n and ...
Support for importing and exporting animated morph targets for Texcoord_n and Color_n. Client implementations SHOULD support at least three ...
Read more >Texture based morph targets with meshopt compressed ...
Hello, I'm converting morph targets to a texture to overcome webgl limit (4 active ... I see only blinking patches and stripes of...
Read more >Feature Matrix
Support for complex assets consisting of a high number of morph targets/joints/weights including texcoord and color morph target attributes. Inspecting.
Read more >moglmorpher
indices into the vertices, texcoords, colors and normals vectors ... Note: The current implementation doesn't support morphing of vertex
Read more >Changing the color of the individual vertices in vertex shader
I tried changing the value of the color variable in the external shader file based on a uniform variable but that doesn't help...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yes, it’s a useful feature, and I’m surprised it was not part of the spec since the very beginning.
Although I don’t think I’ll be able to work on it for the next release, I’ll add it to the roadmap, though.
@ptasev I couldn’t replicate that scenario, could you write a test case for it?
I thick after the morph targets and a few other issues are resolved, I’ll publish new nugets