Java Collision Detection and Physics Engine

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.

3.0.2 introduces significant changes in the Sandbox application along with some minor bug fixes to dyn4j and some new features. Specifically, small CCD improvements, a new fixture filter TypeFilter, and tangent speed settings on contacts. Bug fixes include: a fix to the Body.setMass(Mass.Type) method, auto-sleeping bug, and a rotation disc computation bug. In addition, both dyn4j and Sandbox have been internationalized (any volunteers for translating?).

The Sandbox includes many new features and fixes. First, is the ability to add Rays to test raycasting. Next, all output angles are in Degrees (GUI, xml, and java files). Finally there is a new Export feature to export a simulation to a Java class file. This allows you to create a simulation inside the Sandbox application and export it for use in your application.

Soon I plan to post some videos on how to get started and some of the useful features contained in the Sandbox application.

Launch the TestBed		Launch the Sandbox

When running either test 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+.

3.0.1 incorporates many small changes. JUnit test, the TestBed and a new testing/demo application, Sandbox, have been moved around to better structure the project. Many major and minor bug fixes have been made. The most visible change is the normalization of the Joint class methods. In addition, the WeldJoint class now supports a soft joint setting.

Launch the TestBed		Launch the Sandbox

When running either test 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+.

In the TestBed application, be sure to type the “c” key to get the TestBed Control Panel so you can play with the simulator. Use the Controls tab to view all the key board and mouse options. Use the Tests tab to run a test of your choosing. Use the Draw Options tab to set what is drawn to the screen. And finally, use the Simulation Settings tab to play with all the different settings allowed by the engine.

In the Sandbox application, use the menus, toolbar and the tree (right click for context menus) to run tests, save them, add bodies/joints, etc.

3.0.0 incorporates big changes to the library. The base package has been changed, the broadphase collision detection code has been updated adding 3 new implementations, many bug fixes and performance enhancements, a new joint, better documentation, many more JUnit tests, new example applications, and more.

Show Me The TestBed!

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

All the releases require Java 1.6+. Be sure to type the “c” key to get the TestBed Control Panel so you can play with the simulator.

Use the Controls tab to view all the key board and mouse options. Use the Tests tab to run a test of your choosing. Use the Draw Options tab to set what is drawn to the screen. And finally, use the Simulation Settings tab to play with all the different settings allowed by the engine.

The new version, 2.2.3, features updated Javadocs, 3 different CCD modes, and a new JOGL based TestBed.

Show Me The TestBed!

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

All the releases require Java 1.6+. Be sure to type the “c” key to get the TestBed Control Panel so you can play with the simulator.

Use the Controls tab to view all the key board and mouse options. Use the Tests tab to run a test of your choosing. Use the Draw Options tab to set what is drawn to the screen. And finally, use the Simulation Settings tab to play with all the different settings allowed by the engine.