Java Collision Detection and Physics Engine

This release of dyn4j is a maintenance release to fix a bug in the Vector2.distance(double,double) method.  It also had a few methods added to the Body class to get BodyFixture(s) at a given world space point.  See the change detail in the release notes.

A new release of the Sandbox was published for this release due to changes in WebStart security and an API change by JOGL.

This release of dyn4j is a maintenance release to fix bugs in the Ellipse.contains, Ellipse.getHalfHeight and HalfEllipse.contains methods.  This release also had a bug fix in the Graphics2DRenderer class.  See the change detail in the release notes.

This release has one breaking change: the Ellipse.getPointClosestToPoint method has been removed.  This method was based on an incorrect assumption and was removed for the time being.

No new release of the Sandbox was published for this release.

This release of dyn4j is a maintenance release to fix a bug in the Segment.getSegmentIntersection method.  A new method, setSlackEnabled, was also added to the PulleyJoint class to support a rope like constraint.  See the changes in the release notes.

This release should not contain any breaking changes.

No new release of the Sandbox was published for this release.

This release of dyn4j includes a number of new features including 4 new primitive shapes and convex casting.  In addition, a number of new helper methods have been added to the Geometry class.  See all the changes in the release notes.

This release should not contain any breaking changes unless you were using anything in the org.dyn4j.collision.continuous package directly.

The output of the convex casting features may be tweaked in future releases.

No new release of the Sandbox was published for this release.

This release of dyn4j is a small maintenance release to fix a bug introduced in 3.1.3. With this some flip methods have been added to the Geometry class to allow flipping of polygons about arbitrary axes and points.

This release should not contain any breaking changes unless you were using or storing shape, fixture, body, joint, etc. ids. These ids were of type String, but have been changed to UUID for performance (they were actually UUID.toString() anyway). You can still get the old String value by getId().toString().

No new release of the Sandbox was published for this release.

This release fixes a bug in the Polygon inertia and center of mass calculations. This bug would also throw off multi-fixture body’s inertia. This bug would manifest if a polygon was created away from the origin. This version has no API changes.

No new release of the Sandbox was published for this release.

This release of dyn4j is a small maintenance release to add unique contact ids to the engine. This allows you identify a contact throughout the ContactListener events (begin, persist, end, etc). You can test if a contact is the same as another by using the ContactId.equals method.

This release should not contain any breaking changes unless you were manually creating ContactPoints or subclasses thereof. See the Release Notes for more details.

No new release of the Sandbox was published for this release.

This release of dyn4j was focused on performance and the API. Many API changes, both breaking and non-breaking, have been made. See the Release Notes for more details. Many new small features have been made as well. You can see them on the Features page or in the Release Notes.

The Sandbox app. reflects the changes above. The biggest change is the addition of the Help Contents. This will provide those unfamiliar with dyn4j with help on how to use the application.

Launch the Sandbox (Sandbox-v1.0.4/dyn4j-v3.1.1)

When running the Sandbox application you may be asked to accept a certificate from me (I just self signed the JARs). The certificates will expire six months from today.

The Sandbox has no dependencies and requires Java 1.6 or higher.

The latest release of dyn4j adds a number of new features. See the features page for more details or the release notes. It also contains a number of important bug fixes. On the other hand, the API has been changed slightly and may break code written against older versions.

The Sandbox app has also seen some changes. Many bug fixes along with the features in dyn4j have been added. In addition, the threading issue on some platforms has been resolved by using the Newt-AWT bridge offered by JOGL. This makes the app far more efficient at handling input. The Sandbox includes precompiled tests along with the declarative (xml) tests. This allows the deprecation of the TestBed application. The Sandbox will take its place as the sole testing application.

Launch the Sandbox

When running the Sandbox application you may be asked to accept a certificate from me (I just self signed the JARs). The certificates will expire six months from today.

Both applications require Java 1.6+.

Version 3.0.3 is a maintenance release with very few changes. The primary change was the move of the Settings class from being a singleton to being a member of the World class. This allows each instance of the World class to have different settings. The changes may break compatibility with previous versions, although they should be minimal.