ode4j icon indicating copy to clipboard operation
ode4j copied to clipboard

Java 3D Physics Engine & Library

Results 28 ode4j issues
Sort by recently updated
recently updated
newest added

More out of curiosity than anything else, has anyone compared ode4j to jBullet? There is PAL (http://www.adrianboeing.com/pal/index.html) which has some comparisons of C/C++ engines. However, I've seen a number of...

question

MTJ/MTJ-n: https://github.com/fommil/matrix-toolkits-java EJML: http://code.google.com/p/efficient-java-matrix-library/ Comparison: https://code.google.com/p/java-matrix-benchmark/wiki/RuntimeCorei7v2600_2013_10 Also, any inclusion of such libraries should consider that ODE partly takes special precautions to improve mathematical instability.

enhancement

ODE uses by default the OPCODE trimesh collider. ode4j has currently only the GIMPACT collider which is a secondary option in ODE. For more compatibility and to add flexibility, it...

enhancement

There are two issues, both point to a (two?) problems in the collider: - Letting DemoCrash sit still for a few second will occasionally show the box stack becoming "active",...

bug

Boxes sometimes fall very slow or not at all: - DemoTrimesh: If the fourth dropped body is a Box, it will land on an edge and then fall **very slowly**...

Cylinder trimesh collision may fail with: ``` java.lang.RuntimeException at org.ode4j.ode.internal.Common.dIASSERT(Common.java:131) at org.ode4j.ode.internal.CollideCylinderTrimesh$sCylinderTrimeshColliderData.TestOneTriangleVsCylinder(CollideCylinderTrimesh.java:1002) at org.ode4j.ode.internal.CollideCylinderTrimesh$sCylinderTrimeshColliderData.TestCollisionForSingleTriangle(CollideCylinderTrimesh.java:1080) at org.ode4j.ode.internal.CollideCylinderTrimesh.dCollideCylinderTrimesh(CollideCylinderTrimesh.java:1301) at org.ode4j.ode.internal.CollideCylinderTrimesh.dColliderFn(CollideCylinderTrimesh.java:68) at org.ode4j.ode.internal.DxGeom.dCollide(DxGeom.java:1698) at org.ode4j.ode.OdeHelper.collide(OdeHelper.java:850) ``` This is currently not reproducible with tests.

It seems the module name for the core is just `core` instead of `org.ode` (as specified in the core module file). It should be `org.ode` or `org.ode.core`. Is this related...