TriMesh TriMesh collisions Array Index Out of Bounds

Game Mechanics
#1

I tried to run the TriMeshTriMeshCollisionTest and got

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
	at java.util.ArrayList.RangeCheck(Unknown Source)
	at java.util.ArrayList.get(Unknown Source)
	at org.xith3d.utility.geometry.nvtristrip.Stripifier.findAllStrips(Stripifier.java:964)
	at org.xith3d.utility.geometry.nvtristrip.Stripifier.stripify(Stripifier.java:1333)
	at org.xith3d.utility.geometry.nvtristrip.TriStrip.generateStrips(TriStrip.java:148)
	at org.xith3d.utility.geometry.GeometryInfo.optimizeTrianglesForCache(GeometryInfo.java:224)
	at net.java.dev.joode.test.xith.XithConverter.convert(XithConverter.java:147)
	at net.java.dev.joode.test.xith.XithBindingManager.addBinding(XithBindingManager.java:33)
	at net.java.dev.joode.test.collision.TriMeshTriMeshCollisionTest.<init>(TriMeshTriMeshCollisionTest.java:39)
	at net.java.dev.joode.test.collision.TriMeshTriMeshCollisionTest.runTest(TriMeshTriMeshCollisionTest.java:319)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at net.java.dev.joode.test.JOODETestLauncher.runTest(JOODETestLauncher.java:631)
	at net.java.dev.joode.test.JOODETestLauncher.onStartButtonClicked(JOODETestLauncher.java:174)
	at org.xith3d.utility.launching.DisplayOptions.waitForStart(DisplayOptions.java:1029)
	at org.xith3d.utility.launching.DisplayOptions.<init>(DisplayOptions.java:1059)
	at org.xith3d.utility.launching.DisplayOptions.<init>(DisplayOptions.java:1064)
	at net.java.dev.joode.test.JOODETestLauncher.<init>(JOODETestLauncher.java:602)
	at net.java.dev.joode.test.JOODETestLauncher.main(JOODETestLauncher.java:687)
#2

I think this is an error that has crept in after upgrading our Xith version. Anyway I removed the line:

//xgi.optimizeTrianglesForCache();

and it worked (note to Xith and JOODE people, can we fix this please? ).
Please note that the trimesh test cases are pretty complicated trimesh objects (Disicosidodecahedrons). I found that although the test ran, the physics engine took most of the CPU time so sometimes when I ran the test, I didn’t visually see the results (because rendering was deprioritized). However, I have added some degub output so you can see the collisions being caught. Also our trimesh expert is currently optimizing so it all should run faster soon.

Tom

#3

Fixed.

Marvin