Key takeaways
- Solid props: use a single conservative axis-aligned or oriented box for crates, barrels, and boulders; it is fast to evaluate and predictable for player sliding.
- Enterable buildings: split walls, door frames, and interior furniture into local boxes so passages stay walkable (Mossgate Passage uses 28 local boxes around its 3.3 m arch).
- Walkable terrain: sample a shared heightfield grid (49 × 49 heights / 4,608 ground triangles in SceneCrate’s terrain demos) kept identical across Standard and Lightweight tiers.
- Reject silent hull bugs: single convex hulls fill rings, hollow containers, and doorways; automated single-collider pipelines must refuse concave or non-manifold inputs.
1. Use conservative boxes for solid static props
For an opaque, closed, solid prop such as a supply crate, oak barrel, or moss stone, a single bounding box gives cheap, deterministic collision without per-triangle raycast spikes. On rounded objects like our Oak Barrel, a box slightly overestimates diagonal corners, so walk a 1.7 m reference capsule next to it to confirm corridor clearance.
A single convex hull hugs angled silhouettes tighter than a box, but mathematically seals every concave opening. Rings, hollow tubs, archways, and thin zero-volume sheets turn into solid invisible blocks under a convex hull. SceneCrate’s automatic prop pipeline rejects open, non-manifold, sheet, and concave shapes upfront rather than marking a blocked opening as a valid delivery.
2. Keep building doorways and arches open with local boxes
Wrapping an enterable building in one outer bounding box seals every doorway. On Mossgate Passage, a single box around the twin towers would block its entire 3.3 m central road. Instead, our building scene decomposes collision into 28 local boxes (13 bands around each octagonal tower base plus 2 gate uprights), leaving the ground passage open while keeping diagonal corner overestimation within 0.126 m.
Test building collision with your actual player radius and height, not a zero-width camera ray. Across SceneCrate’s building demos, automated checks test a 1.7 m figure (0.22 m radius) along 270 route rays and 1,275 sampled points across both Standard and Lightweight tiers to verify unobstructed doorway clearance and solid walls.
3. Share an identical heightfield across terrain LOD tiers
Walkable outdoor ground works best as a bounded heightfield that interpolates surface elevation across explicit grid triangles, paired with max-slope and boundary rules (for example, keeping players off steep canyon walls or painted coastal water). Never substitute a prop box for terrain.
Crucially, never decimate the walkable ground independently between quality tiers. All three SceneCrate terrain demos share the exact same 49 × 49 heightfield (2,401 elevation samples, 4,608 ground triangles) in both Standard and Lightweight; triangle savings come strictly from simplifying decorative pines, rocks, and shrubs (for example, Highland Trail drops from 8,940 to 7,002 triangles) so character footing never drifts.
4. Verify transforms and engine boundaries in-scene
Inspect rendered meshes and collision wireframes together in metres, testing approaches from outside walls, angled doorway grazing, interior furniture, and terrain borders across every LOD tier.
Remember that glTF 2.0 stores visual scene graphs by default. Importing standard.glb into Three.js, Rapier, Cannon-es, Unity, or Godot does not automatically wire up scene.json boxes or heightfield slope limits; translate those collision definitions into your target physics engine and re-test player movement.
- Spawn the player capsule outside all collision volumes with base at ground height.
- Apply one shared world transform to both the visual GLB and its collider data.
- Test full capsule width and height through doorways and against solid walls.
- Keep ground heightfields identical across Standard and Lightweight quality tiers.
Frequently asked questions
Why does a convex hull collider block doorways and hollow objects?
By definition, a single convex hull stretches like shrink-wrap across outer vertices, bridging over every dent, doorway, arch, or interior cavity. Enterable structures need compound local boxes or convex decomposition.
Why avoid raw triangle-mesh (trimesh) colliders on high-poly web assets?
Testing a moving capsule against tens of thousands of arbitrary visual triangles every frame is expensive in JavaScript/Wasm physics engines and prone to snagging on thin decorative bevels or internal faces.
Should Standard and Lightweight terrain models use separate heightfields?
No. If low-end devices walk on a simplified ground mesh with shifted heights, players and placed props will float, clip underground, or get blocked on paths that work on high-end devices.
Does SceneCrate generate multi-box colliders for custom uploaded buildings?
No. Custom building and terrain orders are not offered; the paid automated service only accepts closed, convex, opaque static props that fit a single conservative collider.