armature.saveBindPose() corrupts model
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start with SeparateJointModelTransform.java at the referenced inverseModelBindMatrix line and review the saveBindPose() path described in the issue. Reproduce repeated saveBindPose() calls and trace whether the inverseModelBindMatrix is modified; done means repeated calls no longer corrupt or distort the model's bind pose.
Written by the indexing model from the issue text.
Description
As reported here: https://hub.jmonkeyengine.org/t/issue-calling-armature-savebindpose/48046
Essentially, calling saveBindPose() many times will eventually corrupt/distort the model's bind pose.
My best guess so far is that the inverseModelBindMatrix value in this class at this line ends up corrupted from repeatedly being modified one way or another: SeparateJointModelTransform.java#L33
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jMonkeyEngine/jmonkeyengine
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jMonkeyEngine/jmonkeyengine#2928 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jMonkeyEngine/jmonkeyengine#2919 · 1 comment ·
Maintainers usually reply within 1 day
-
defect
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jMonkeyEngine/jmonkeyengine#2717 ·
Maintainers usually reply within 1 day
-
Documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
jMonkeyEngine/jmonkeyengine#2931 · 1 comment ·
Maintainers usually reply within 1 day
-
Documentation
Difficulty 3/5 1-2 days Newbie friendliness 57/100
jMonkeyEngine/jmonkeyengine#2930 · 3 comments ·
Maintainers usually reply within 1 day
All issues in jMonkeyEngine/jmonkeyengine
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liquid-java/liquidjava#321 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenConext/OpenConext-access#1015 ·
Maintainers usually reply within 1 day
-
68000: FDBcc branch target is 2 bytes too low (uses inst_start+2 instead of the displacement word)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NationalSecurityAgency/ghidra#9702 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/rocketmq-dashboard#5358 ·
Maintainers usually reply within 3 days