Posted on September 30, 2015

The primary goals for this release were performance enhancements and API clean up.  It took a lot longer than I had expected but I’m very happy with the results.  Highlights include improvements in the performance of collision detection and ray casting operations and a much cleaner public API and more thorough javadoc comments.

The API has been changed a good bit and you’ll find some breaking changes.  Most, if not all, should be simple find/replace changes, the behavior should remain the same.  Those of note are:

1. Body.setMass() was deprecated.  Use Body.setMass(MassType) instead.
2. Mass.Type was renamed to MassType.
3. MouseJoint was renamed to PinJoint.

All this got me thinking of the old days of the Turbo button which funny enough did the opposite of what you’d think…

 

Found an issue with this page? suggest edit

« Previous Post

Next Post »

Comments

Your comment will not show up immediately - all comments are moderated before becoming visible.

The value entered into the email/@twitter/github field is only used to pull a gravatar image and will not be stored or visible when the comment is approved. The name and comment will become visible after the comment has been moderated.

Are you sure?

Are you sure you want to add the comment? You can't edit your comment after this point.

NOTE: All comments are moderated before becoming visible.

Comment submitted successfully! Please wait for moderation for it to show.

Failed to submit the toast - see console for more details.

2 responses

---

Olof Andersson

October 26, 2015

Under the section Creating Joints on the Getting Started page
http://www.dyn4j.org/documentation/getting-started/#Creating_Joints
there is a link in "See the Joints page for more details about each Joint."
but the link leads to the outdated wiki page (https://code.google.com/p/dyn4j/wiki/Joints) when it should really lead to the new Joints article (http://www.dyn4j.org/documentation/joints/)

The link to the article about

---

William Bittle

November 02, 2015

@Olof

Thanks for the heads up. Should be fixed now.

William

---