jMonkeyEngine / jMonkeyEngine/jmonkeyengine
KinematicRagdollControl assumes mesh coordinates = model coordinates
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
I tried applying a KinematicRagdollControl to Jaime.j3o, and the collision objects came out backward (rotated 180 degrees around the model's Y axis).
This occurs because KRC translates between mesh coordinates and world coordinates using the controlled spatial (typically the model's root node) instead of using an animated geometry. Jaime's animated geometry is rotated relative to its model root. See also PR #637.
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 with KinematicRagdollControl and reproduce the issue using Jaime.j3o; compare the mesh, model-root, and animated-geometry coordinate assumptions described here. Review PR #637 for related context. Done means the collision objects are no longer rotated 180 degrees when applied to Jaime.j3o.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100