Why does my Unity skinned mesh disappear when I look at the head?

SkinnedMeshRenderer caches local bounds at import based on the bind pose. If animation moves bones outside that box (a long-reach attack, jump animation), the renderer thinks the mesh is offscreen and culls it. Enable Update When Offscreen or expand Local Bounds manually.

What does Update When Offscreen do?

It recalculates the renderer's bounds every frame from the current bone positions. More expensive but always accurate. Use it for hero characters or any mesh whose silhouette changes dramatically with animation. Skip it for crowds where the cost adds up.

How do I expand Local Bounds without enabling Update When Offscreen?

On the SkinnedMeshRenderer, manually edit Local Bounds Center and Extents in the inspector to encompass the largest pose your animations produce. This is cheaper than recalculating each frame but requires you to know the worst-case extents in advance.

Fix: Unity SkinnedMeshRenderer Bounds Wrong After Animation

Quick answer: SkinnedMeshRenderer uses bind-pose bounds for culling. Animations that extend the silhouette beyond bind pose can fall outside the cached bounds. Enable Update When Offscreen for hero characters, or expand Local Bounds manually to cover worst-case poses.

Here is how to fix Unity skinned characters that pop out of view when the camera focuses on a body part. The mesh disappears just as the player swings a sword overhead, then reappears when the animation ends. The cause is a static bounding box that was computed from the bind pose — animations stretching beyond that box trigger frustum culling early.

The Symptom

A character animates correctly when the entire body is in view. Camera moves close, framing only the head or weapon, and the character vanishes from the frame. Pulling the camera back makes them reappear. Static meshes nearby render fine.

What Causes This

Bind-pose bounds. SkinnedMeshRenderer caches bounds from the bind pose at import. Animations stretching outside (raised arms, leaping, large attack animations) put parts of the mesh outside the cached box, causing the entire renderer to be culled when its center is offscreen.

Update When Offscreen disabled. The default is off because every-frame bounds recomputation costs CPU.

Bone influences outside bind extents. Bones that move significantly (cloth, hair, weapon attachments) can also push the actual silhouette beyond the cached bounds.

Wrong root scale. A scale baked into the root bone can make the bone-space bounds smaller than the world-space silhouette.

The Fix

Step 1: Enable Update When Offscreen for hero characters. On the SkinnedMeshRenderer, check Update When Offscreen. Bounds recalc every frame from current bone positions. The mesh stays visible when any part of it is in frustum.

Step 2: Expand Local Bounds manually for crowd characters.

using UnityEngine;

[RequireComponent(typeof(SkinnedMeshRenderer))]
public class ExpandSkinnedBounds : MonoBehaviour
{
    [SerializeField] private Vector3 extents = new Vector3(2, 3, 2);

    void Awake()
    {
        var r = GetComponent<SkinnedMeshRenderer>();
        r.localBounds = new Bounds(Vector3.zero, extents * 2f);
    }
}

Set extents large enough to cover the largest pose. A bigger box culls slightly less aggressively but avoids per-frame recompute.

Step 3: Compute worst-case bounds at edit time. Write an editor script that scrubs through every animation clip and unions the resulting renderer.bounds. Bake the result into the SkinnedMeshRenderer’s Local Bounds:

#if UNITY_EDITOR
[UnityEditor.MenuItem("Tools/Compute Skinned Bounds")]
static void Compute()
{
    var smr = Selection.activeGameObject.GetComponent<SkinnedMeshRenderer>();
    var animator = smr.GetComponentInParent<Animator>();
    var bounds = new Bounds(smr.transform.localPosition, Vector3.zero);

    foreach (AnimationClip clip in animator.runtimeAnimatorController.animationClips)
    {
        for (float t = 0; t <= clip.length; t += 0.1f)
        {
            clip.SampleAnimation(animator.gameObject, t);
            bounds.Encapsulate(smr.localBounds);
        }
    }
    smr.localBounds = bounds;
}
#endif

Step 4: For attached weapons, parent to the mesh. A weapon as a separate Renderer is culled independently. If you want it visible whenever the character is, place it under the same SkinnedMeshRenderer’s GameObject or wide-set bounds on its own renderer.

Step 5: Avoid root scale baking. If your character’s import has scale 100 baked into root, bone-space bounds are tiny relative to world-space. Reset root bone scale to (1,1,1) and re-author the rig if needed.

Cost Tradeoffs

Update When Offscreen costs roughly 0.05–0.2ms per character per frame depending on bone count. For 50 visible characters, this is meaningful. Use it for protagonists; bake bounds for crowds.

Understanding the issue

Render pipelines have ordering: which pass runs when, what state is bound, which targets are written. Bugs at this layer are often invisible in code review and only manifest at runtime.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Skinned bounds are static unless you tell them otherwise. Animations beyond bind pose require Update When Offscreen or larger Local Bounds.”

Related Issues

For animation playback issues, see Animation Not Playing. For LOD issues, see LOD Group Not Switching.

Update When Offscreen for heroes. Bake bounds for crowds. The character stops vanishing.