You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The
TestHoveringTank
example is more playable withjme3-jbullet
than withjme3-bullet
. Withjme3-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 ofTestHoveringTank
and should also benefit many other apps that usesHullCollisionShape
.The text was updated successfully, but these errors were encountered: