Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestHoveringTank exposes a jme3-bullet performance issue #1037

stephengold opened this issue Mar 9, 2019 · 1 comment


Copy link

commented Mar 9, 2019

The TestHoveringTank example is more playable with jme3-jbullet than with jme3-bullet. With jme3-bullet on my desktop, flipping the tank onto its back causes the frame rate to drop from about 100 to about 5. I think this is because the tank's collision shape (a compound of a hull with 6464 vertices) comes into contact with the terrain. The Bullet Manual recommends that hull shapes be limited to not more than 100 vertices.

Most of those 6464 vertices are duplicates or lie inside the convex hull. In this case, the set of vertices can be optimized down to 522 using Bullet's btConvexHullShape::optimizeConvexHull() method. Doing so greatly improves the performance of TestHoveringTank and should also benefit many other apps that uses HullCollisionShape.

stephengold added a commit that referenced this issue Apr 13, 2019


This comment has been minimized.

Copy link
Contributor Author

commented Apr 13, 2019

Fixed in master branch at 35b9d9d

riccardobl added a commit to riccardobl/jmonkeyengine that referenced this issue Apr 15, 2019

@stephengold stephengold added this to the v3.2.4 milestone Jun 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.