jMonkeyEngine / jMonkeyEngine/jmonkeyengine
HingeJoint.enableMotor() not working
Open
Nobody has claimed this yet.
Needs investigation
Physics
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
TestAttachGhostObject and TestPhysicsHingeJoint both use the enableMotor() method to drive the motion of a HingeJoint. Even with the maxMotorImpulse cranked up to 1e10, invoking enableMotor() appears to have no effect in these simulations. I tested both JBullet and NativeBullet.
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 running TestAttachGhostObject and TestPhysicsHingeJoint, then inspect their uses of HingeJoint.enableMotor() and compare behavior in JBullet and NativeBullet. Reproduce the report with maxMotorImpulse set to 1e10; the issue is done when enableMotor() visibly drives the hinge in both simulations.
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
- Needs clarification
- Newbie friendliness
- 25/100