public static void main(String[] args) {
        test = new TestGimpactShape();
        test.setSettings(new AppSettings(true));
        test.settings.setVSync(true);
        if (SKIP_SETTINGS) {
            test.settings.setWidth(1920);
            test.settings.setHeight(1150);
            test.showSettings = !SKIP_SETTINGS;
        }
        test.start();
    }
This test demonstrates various GImpactCollisionShapes colliding against two identical curved surfaces. The
left surface is a MeshCollisionShape, right surface is another GImpactCollisionShape. An ideal result is
for all objects to land and change to a blue colored mesh indicating they are inactive. Falling through the
floor, or never going inactive (bouncing forever) are failure conditions.
<p>
Observations as of June 2019 (JME v3.3.0-alpha2):
<ol>
<li>
With default starting parameters, Native Bullet should pass the test parameters above. JBullet fails due to
the rocket/MeshCollisionShape never going inactive.
</li>
<li>
Native Bullet behaves better than JBullet. JBullet sometimes allows objects to "gain too much energy" after
a collision, such as the rocket or teapot. Native also does this, to a lesser degree. This generally
appears to happen at larger object scales.
</li>
<li>
JBullet allows some objects to get "stuck" inside the floor, which usually results in a fall-through
eventually, generally a larger scales for this test.
</li>
<li>
Some shapes such as PQTorus and signpost never go inactive at larger scales for both Native and JBullet (test
at 1.5 and 1.9 scale)
</li>
</ol>

@author lou
jme3-examples/src/main/java/jme3test/bullet/shape/TestGimpactShape.java