Engine & runtime
Bounding volumes & culling
Why your model disappears at the edge of the screen.
What this is
Sphere, AABB and OBB bounds tested against a live frustum, with the culled fraction and the wasted draws counted every frame.
Renderers cull against a bounding volume, never against geometry — testing a million triangles against six planes would cost more than drawing them. So the volume you pick is your culling accuracy. The demo also reproduces the most common WebGL bug there is: animate vertices without recomputing the bounding sphere and objects vanish while still clearly on screen.
Things worth trying
- Orbit outside the yellow frustum and watch the cull happen from the outside
- Switch sphere → AABB → OBB and watch the wasted-draw percentage fall
- Turn on 'simulate stale bounds' and watch objects pop out of existence
- Note that culling never reduces draw calls — only instancing does
Bring us the product you were told could not be configured.
Tell us the option count, the CAD you already have and the frame budget you need to hit. An engineer reads it and replies with a straight answer — including when the answer is that good photography would serve you better.
We reply to every enquiry within one business day, in your timezone — with a frame budget, not a brochure.