Even though I’m not getting a console log verifying it, I believe it has to do with how I’m creating LiDAR terrain with MeshBuilder, as when I exclude the LiDAR tiles I don’t get the error. MeshBuilder worked with version 4.2.2 but doesn’t seem compatible with 5.1.
I think I’m on to something, and now that I’ve narrowed it down I’ll try reconstructing it in the playground. Here’s my train of thought:
It’s hard to diagnose the problem because the Web App worked with previous versions of BabylonJS, and now all of a sudden crashes within seconds of loading with the Uncaught TypeError: subMesh.getBoundingInfo() is undefined message and doesn’t highlight a particular line of my code (even in WebPack developer mode).
However, I did disable a “clean cache” feature in my LiDAR class that calls scene.clearCachedVertexData(); & scene.cleanCachedTextureBuffer(); when tiles are being disposed – and that seemed to fix it!
I’m going to investigate further, as like I said before it worked not that long ago and kept the JS Heap Size wayyy down as LiDAR tiles where built and disposed dynamically.
I’m still not exactly sure how scene.clearCachedVertexData(); & scene.cleanCachedTextureBuffer(); inside my LiDAR class was breaking the render engine, but removing them and placing them in a higher level in the code seemed to fix it.
Unfortunately, it didn’t work. Here was my implementation based on your suggestion:
// intermittently clean cache (this was taken from inside the LiDAR class *broke app for some reason*)
setInterval(() => {
scene.meshes.forEach((mesh, index) => {
// eslint-disable-next-line no-underscore-dangle
mesh._updateBoundingInfo();
if (index === scene.meshes.length - 1) {
scene.cleanCachedTextureBuffer();
scene.clearCachedVertexData();
}
});
}, 1500);
I can’t seem to reproduce the error inside of the playground, hence why I haven’t sent an example. Not clearing vertex and texture caches fixes the error but bloats the heap after a little while, so I’m in a bit of a pickle…
setInterval will do it several time and _updateBoundingInfo will need the data cleared on the first tick I believe, this should happen only once per mesh when the datas are present.
The reason I was using a setInterval in the code above was because the LiDAR class is basically a quadtree that subdivides a LiDAR tile as you zoom in, dynamically creating all this new geometry which gets stored in the heap – so when I removed that class method that triggered the cleanup automatically, I just called scene.cleanCachedVertexData every 1500 milliseconds in a much higher level part of the program for the time being.
Your most recent playground example worked, so I put it back in the LiDAR class and cleaned vertex data on newly created geometry, but unfortunately it pales in comparison to the old method (which still works with Babylon.js v5.0.0-alpha.63)
I ll check if you could somehow lock the bounding box to prevent the crash despite not having any cpu data but without a fully specialized case for it.
Sounds good. All meshes have the pickable feature disabled; Im not doing any physics calculations, just seeing what the distance is between the camera and mesh, which tells the program whether to subdivided or hide meshes. Cleaning the cache only gets turned off if I have to do that kind of stuff in controlled areas (which worked in 4.2)
Not really as we should always have one. The main issue is when we delete it we lose some of the global availablity of the bounding info, that we should retain. I am trying to see how we can improve this without a manual workaround.
