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.
model.humanoid.setPose(model.humanoid.restPose) Bug?
See original GitHub issueI don’t know if is this a bug or I misused this function, when I call model.humanoid.setPose(model.humanoid.restPose) to reset the VRM model’s pose, the model is getting weird.
After I dig in the code, I think the reason causing this bug is in here, which the original bone position is added to the pose data passed by the argument, then the position of all bones are doubled: https://github.com/pixiv/three-vrm/blob/1b4aa0a72b7153a6fba5bc575932f7a8dcb807b8/src/vrm/humanoid/VRMHumanoid.ts#L86-L93
If this is not a bug, is there any proper way to reset the model to its initial state?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 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
I have roughly looked for usage of
getPoseon GitHub and I could find a sample, it manually removes positions though 😩 I guess I can safely change the behavior. Let me do this. Thanks a lot for the issue, @JLChnToZ ! Let me notify once it gets updated.whoa, I didn’t expected
getPosereturns positions and rotations of each bone without taking a diff from its rest pose. It’s not working as intended. I want to fix this. Let me check whether we have a lot of user of the function or not.