Metaverse Renderer: LOD & Frustum Culling

World Density

Node count 1200

Level of Detail

High → Low switch distance 18

Low → Impostor / cull distance 42

Live Renderer Stats

FPS

Triangles drawn

Rendered nodes

Culled nodes

Tier split (high / low / impostor)

0 / 0 / 0

High detail (320 tri) — inside near ring Low detail (20 tri) — mid ring Impostor (4 tri) — far ring Beyond render distance — culled

How it works

A metaverse-scale scene cannot draw every object at full detail every frame — a persistent world has orders of magnitude more geometry than any GPU can rasterise at 60 FPS. Two classic techniques make it tractable, and this simulation runs both for real on every one of the 1200 world nodes, every frame:

View-frustum culling:
  visible(obj) = frustum.intersects(boundingSphere(obj))
  (6 clip planes derived from projection × view matrix)

Level of detail (distance-based):
  d = |camera.position − obj.position|
  tier(d) = HIGH        if d < d_near
          = LOW          if d_near ≤ d < d_far
          = IMPOSTOR     if d_far ≤ d < d_max
          = CULLED       if d ≥ d_max

Node count — how many objects populate the world grid; more nodes means more candidates for the culling test each frame.
Switch distances — the two radii that define the LOD rings around the camera; drag them to see geometry pop between the 320-, 20- and 4-triangle meshes live.
LOD toggle — forces every visible node to full detail, so you can compare "Triangles drawn" with and without distance-based simplification.
Frustum cull toggle — disables the visibility test, so every node behind and beside the camera is drawn too (watch "Rendered nodes" jump).
Auto-fly camera — flies a fixed path over the world so the culled/visible split changes continuously, the way it would as an avatar moves through a real metaverse instance.

Real engines (Unreal Nanite, Unity LODGroup, Three.js LOD, most WebGL metaverse clients) combine exactly these two techniques, usually adding octree/BVH spatial partitioning so the culling test itself doesn't have to touch every object either — here it deliberately does, so the cost is visible in the stats panel.

camera height: —

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.

Metaverse Renderer: Level of Detail & Frustum Culling