Fix Unity Raytracing Acceleration Structure Missing

When HDRP ray tracing “sometimes works,” the answer is almost always the acceleration structure. The RTAS (ray tracing acceleration structure) is rebuilt every frame from a filtered subset of your scene. The filter runs on layers, flags, and shader support, and each one can silently exclude a mesh. If a particular chair does not cast a ray traced shadow while the one next to it does, work through the filter in order.

Look at the Ray Tracing Settings override

Ray tracing in HDRP is driven by a Volume override named Ray Tracing Settings. Open your scene’s main Volume Profile and add it if it is missing. The Layer Mask field is the first gate. A renderer whose GameObject is on a layer not included here never makes it into the RTAS. Developers often set this to a single layer like Default for performance and then forget that all their imported props are on Environment or Props.

Tighten or loosen the mask depending on your target hardware. Including everything is fine for a small scene; for large worlds you want only layers that contribute visible reflections.

Enable ray tracing on the renderer itself

Every MeshRenderer and SkinnedMeshRenderer has a Ray Tracing block in the Inspector. You need to check the Ray Tracing checkbox and pick a Ray Tracing Mode. Use Static for non-moving meshes so HDRP reuses the bottom-level structure across frames, and Dynamic Geometry for anything that animates, morphs, or is a skinned mesh. Dynamic Transform is the middle ground: the mesh does not deform but the transform changes, so only the TLAS entry is updated.

using UnityEngine.Rendering.HighDefinition;

var renderer = crate.GetComponent<MeshRenderer>();
renderer.rayTracingMode = UnityEngine.Experimental.Rendering.RayTracingMode.Static;
renderer.enabled = true;

If the field is disabled entirely, the mesh is an edge case HDRP cannot handle — typically a procedural mesh created at runtime with no upload path, or a mesh flagged as read-only without CPU access.

Audit the shader

Ray intersection requires a shader variant that HDRP calls for every ray hit. HDRP Lit, Lit Tessellation, Eye, Hair, and Fabric all provide one. Custom shaders written in raw HLSL usually do not, unless they opt in with the Raytracing Shader Pass. Shader Graph materials need their target set to HDRP and the Ray Tracing toggle checked in the graph settings.

Signs your shader is unsupported: the mesh appears in raster but is black or pink in RT reflections, or it simply does not show up at all. Switch temporarily to a plain HDRP Lit material and see if the problem disappears.

Procedural and GPU-generated geometry

Meshes constructed with Graphics.DrawMeshInstancedIndirect, compute-shader output, or VFX Graph do not participate in the RTAS by default. HDRP has a specific entry point — HDRenderPipeline.AddRayTracingInstance — that advanced users can call, but for most projects the fix is to switch to regular MeshRenderers backed by the generated mesh. Expect procedural foliage and particle-driven debris to be missing from reflections unless you handle them explicitly.

Validate with the RenderGraph viewer

Window -> Analysis -> Render Graph Viewer shows the frame’s passes including Build Acceleration Structure. Click it and inspect which renderers were added. If your suspect mesh is not listed, you already know the filter rejected it. Cross-reference with the Frame Debugger to see whether it was the layer mask, the ray tracing flag, or the shader pass.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“An acceleration structure only contains what you told it to. If the mesh looks wrong in the ray traced pass, first ask whether it is in the structure at all.”

Related Issues

For related lighting debugging, see Fix Unity light probe flickering on moving objects. If you are debugging depth-based effects where shader passes matter, Fix Godot shader depth buffer access flipped walks through a similar filtered-pipeline issue in another engine.

Tip: toggle Ray Tracing off and back on in the Volume to force the RTAS to rebuild — sometimes it gets out of sync after a script reload.