Version 3.3.0

This release was focused on Java 9, OSGi, and Maven but also includes some behavior changes and performance improvements.

For those just using the library, the behavior changes to be aware of are:

  • The GJK algorithm has changed slighty.  It now exits after N number of iterations.  This has been changed to ensure that the algorithm doesn’t run forever in some rare instances.  If you need to go back to the original behavior you can set the maximum number of iterations to Integer.MAX_VALUE, but it’s not recommended.
  • The ContactListener.sensed method is deprecated now and is no longer being called.  Instead, you will get notifications of sensed contacts through the other methods (begin, persist, etc.). This was done so that sensed contacts have the same lifecycle as normal contacts.  There’s a flag on the Contact argument that flags the contact as a sensor contact.
  • Some of the ContactListener methods should return true or false, indicating whether the contact should be solved or not.  The behavior here has changed a bit.  Before 3.3.0 the processing of that contact would halt whenever false was returned and drop the contact.  The new behavior is that the contact proceeds as normal through the pipeline, but is just disabled from contact resolution.  The effect is the same, apart from the fact that all caching information and the contact’s state is retained.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.