Add metadata flags to noa's generated terrain/object meshes, in case

client needs to find/distinguish them
fenomas · May 19, 2023 · e6c305e · e6c305e
1 parent 2bd7693
commit e6c305e
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 2 deletions.
diff --git a/src/lib/objectMesher.js b/src/lib/objectMesher.js
@@ -56,9 +56,11 @@ export function ObjectMesher(noa) {
             }
         }
         this.allBaseMeshes.push(mesh)
+        if (!mesh.metadata) mesh.metadata = {}
+        mesh.metadata[objectMeshFlag] = true
         return managers[id] = new InstanceManager(noa, mesh)
     }
-
+    var objectMeshFlag = 'noa_object_base_mesh'
 
 
 

diff --git a/src/lib/terrainMesher.js b/src/lib/terrainMesher.js
@@ -95,8 +95,11 @@ export function TerrainMesher(noa) {
             mesh.freezeNormals()
             mesh.freezeWorldMatrix()
             chunk._terrainMeshes.push(mesh)
+            if (!mesh.metadata) mesh.metadata = {}
+            mesh.metadata[terrainMeshFlag] = true
         })
     }
+    var terrainMeshFlag = 'noa_chunk_terrain_mesh'
 
 }
 
@@ -705,7 +708,7 @@ function MeshBuilder(noa, terrainMatManager) {
                 mesh.setVerticesData('texAtlasIndices', atlasIndexes, false, 1)
             }
 
-            // disable some babylon bounding internals
+            // disable some unnecessary bounding checks
             mesh.isPickable = false
             mesh.doNotSyncBoundingInfo = true
             mesh._refreshBoundingInfo = () => mesh