How to Fix “Invalid AABB” Errors in Unity

“Invalid AABB” floods the console when a renderer's bounding box contains NaN, and culling breaks with it. The error rarely names the object, so isolation is step one. Here is the process.

How to fix it

1. Bisect the scene to find the renderer

Disable half the renderers at a time (or walk renderers logging renderer.bounds and testing for NaN) until the spam stops — particle systems and skinned meshes are the usual suspects.

2. Validate procedural meshes

Before mesh.vertices = verts, assert no vertex is NaN and call mesh.RecalculateBounds() after assignment; a single bad vertex poisons the whole AABB.

3. Check bone scales and animation

A bone animated to scale zero, or a skinned mesh whose root motion divides by zero delta time, produces NaN bounds only during specific animations — match the error timing to the clip.

4. Clamp particle velocities and sizes

Particle systems with velocity inherited from a NaN-poisoned parent or size curves evaluated at NaN time trigger this; sanitize the emitter's transform first.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.