Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Animations do not export well if the mesh and armature have different origins
See original GitHub issueA Blender project where I imported an OBJ+MTL file, rigged the model, and animated it, fails to texture when loaded in three.js. Additionally the animation has vertex errors when played. When exported using the Khronos exporter, the model textures, and the animation has no noticeable errors.
The raw blender project is located here https://github.com/sctincman/gameoff2017/blob/master/src/blender/fox.blend, the original OBJ mesh used was taken from here, and imported into blender.
A modified three.js example is attached (exported model expected at “models/gltf/fox/” relative to html file.
Additionally, the GLTF export appears to have extra nodes. There are 3 copies of the Fox node “Fox, Fox.001, Fox.002”, and the top-level scene contains an extra “Root” scene node below it.
+ Scene
|-- + Scene_Root
| -- Fox
| -- Camera
| -- Sun
Kupoman exported
Khronos exported
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@tkazik The errors were unrelated to this bug, but they should be fixed now.
@tkazik Thanks for testing it. I’ll take a look at it.