ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context Three.js InstancedMesh uses a single boundingSphere computed from the base geometry at construction time. This sphere drives frustum culling for the entire batch, but it is not automatically updated when instance matrices change via setMatrixAt or direct instanceMatrix manipulation. Goal Achieve correct frustum culling for a large dataset (10,000+ in
Goal: render several thousand copies of one geometry within a draw-call budget while only a subset of instances changes transform each frame. InstancedMesh uses one draw call and stores per-instance matrices, but the batch is frustum-culled as one volume and changed matrices require marking the attribute for upload. Merging compatible BufferGeometries also u
When managing thousands of identical objects in a Three.js scene, the primary goal is to minimize draw calls and garbage collection overhead without sacrificing runtime performance. InstancedMesh provides a significant reduction in CPU-to-GPU communication by utilizing a single draw call for all instances. However, its frustum culling mechanism operates on t
threejs