Closed stephengold closed 3 years ago
I think this is caused by an invalid mesh somewhere in the scene.
I never figured out a way to reproduce this issue every time, however it happened frequently as of e6ac179 (22 November) and I'm fairly sure it hasn't been seen since a55ea38 (also 22 November).
Until I see it again, I'll assume a55ea38 solved this issue.
JME could be more cautious when it comes to picking custom meshes. If the custom mesh doesn't invoke updateCounts()
then its vertex count is -1
, a value which the BIHTree
constructor accepts uncritically and passes to the VirtualIndexBuffer
constructor, which also does no range checking.
I'm not saying that's the root cause of this issue in all cases, but it seems a plausible scenario.
Perhaps this is related to issue #1, since it happens about the same time as adding a vehicle to the scene. However, the stack trace is quite different: