jMonkeyEngine / jMonkeyEngine/jmonkeyengine
SkeletonDebugger assumes all bones extend in the local +Y direction
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
When bone lengths are provided to SkeletonDebugger, it draws them extending in the local +Y direction, which is fine for models like Oto which don't violate that assumption. However, for models like Elephant and Ninja, which have bones extending in directions other than +Y, SkeletonDebugger with bone lengths renders bizarre and confusing results. To render bones properly for all models, SkeletonDebugger would need bone directions as well as lengths. In other words: vectors.
I discovered this issue in JME 3.1-stable.
Contributor 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.
Research direction
Start by locating SkeletonDebugger and the code that renders bones from their lengths. Compare the behavior with the Elephant and Ninja models shown in the issue, and verify that bone directions as well as lengths are used so those skeletons render correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100