Unity Adaptive Probe Volumes Pink Probes in Player Build but Fine in Editor - Fix

Problem: Adaptive Probe Volumes (APV) light your scenes correctly in the Editor Play Mode view, but the standalone, Deck, or WebGL player shows pink/magenta or black probe shading—often on streamed sub-scenes or moving characters.

Who is affected now: Teams adopting Unity 6 default APV workflows in 2026 while CI still screenshots Editor only. APV streaming, baking set inclusion, and shader stripping bugs surface in players, not in the Scene view you tuned yesterday.

Fastest safe fix: Rebake the full lighting scenario with all shipped scenes included → verify APV streaming offsets on volume profiles → warm probe sampling shader variants in the player build → confirm probe buffer binding in Frame Debugger on a Development player.

Direct answer

Pink/black probes in players while Editor looks fine usually means the built player is not loading the same probe data the Editor used—missing baked cells, wrong streaming index offsets, excluded additive scenes, or stripped shaders that sample APV. Rebake + inclusion + stripping fixes beat tweaking exposure in post.

Why this issue spikes in 2026

Unity 6 templates enable APV by default for URP/HDRP lanes.
Multi-scene streaming and Addressables loads probe cells the Editor never baked together.
URP 17 stripping can remove probe sampling variants from custom lit shaders.
Deck Verified autumn 2026 retests probe-heavy stylized titles on Vulkan players.

Pair with URP 17 stylized lit pink on Deck when materials are pink (shader variants), not probe cells. Pair with Shader Graph pink in player for Shader Graph lit paths.

Symptoms and search phrases

Probes pink/magenta or flat black in player only.
Editor Play Mode and Windows dev build OK; Linux Deck or WebGL bad.
Wrong lighting after LoadSceneAsync / additive UI scenes.
Adaptive Probe Volumes warning in Player.log about missing data or index.
Frame Debugger: probe buffer invalid or default black.

Root causes (check in order)

Lighting scenario missing additive/streamed scenes in bake set.
APV streaming offsets not baked or profile mismatch per platform tier.
Probe volume bounds do not cover streamed content spawn points.
Shader stripping removed APV / _APV sampling variants.
Quality tier in player uses different URP asset than Editor active tier.
Graphics API path (Vulkan/WebGL) exposes different tier limits—not APV data itself.

Fastest safe fix path

Step 1 — Freeze lighting scenario and included scenes

Window → Rendering → Lighting (or Lighting Settings asset).
Create/update Lighting Settings assigned to all shipped scenes.
Under Adaptive Probe Volumes, ensure baking set lists every scene in your build order (boot, hubs, streamed levels).
Generate Lighting — full rebake (not “Bake Probes” on one scene in isolation).

Success check: probe count in Lighting window matches expected world bounds; no yellow “scene not in set” icons.

Step 2 — APV streaming offsets and volume profiles

Select Probe Volume components in each scene.
Confirm mode matches shipped design (single brick vs streaming).
For streaming: bake with same cell size you ship; document streaming index in a apv_streaming_manifest.json if your pipeline uses custom loaders.
After additive loads, call ProbeReferenceVolume.Refresh() (or equivalent API for your Unity minor) if your loader moves volumes.

Rule: if characters spawn outside baked bounds, probes read as black—expand volume or add local volume per arena.

Step 3 — Shader stripping and Always Included Shaders

On the URP Asset used by the player quality tier:

Temporarily disable aggressive shader stripping; rebuild player.
If probes fix → allowlist variants that sample APV on your custom lit shaders.
Add lit shader / Shader Graph generated shader to Always Included Shaders if needed.

Cross-check URP 17 Deck stylized pink help when entire materials are error-pink, not probe-tinted.

Step 4 — Editor vs player quality tier parity

Edit → Project Settings → Quality — note tier for Standalone / WebGL / Server (if any).
Match Render Pipeline Asset to the tier you used when baking.
Rebuild Development player with Script Debugging off but Development Build on for Frame Debugger.

Step 5 — Frame Debugger verification (player)

Launch Development build.
Attach Frame Debugger to player process.
Inspect a failing draw call — confirm probe buffer / APV resource bound (not default).
Capture one screenshot per platform (Windows, Deck, WebGL) for cert packet.

Verification checklist

[ ] All shipped scenes in APV baking set; rebake completed after last scene add
[ ] Probe volumes cover spawn + streamed arena bounds
[ ] Player quality tier URP asset matches bake tier
[ ] No APV-related shader strip warnings in build log
[ ] Frame Debugger shows valid probe binding in player
[ ] Additive scene load test: lighting stable after async load

Alternative fixes

Branch	When	Action
Pink entire material	Error shader pink	Shader Graph SVC help
Deck-only + stylized lit	URP 17 keywords	URP 17 Deck stylized help
Wrong GPU API	Log shows unexpected device	Deck OLED Vulkan launch help
WebGL memory	OOM after load	Unity WebGL WASM memory help

Prevention

Player-only lighting CI: one screenshot diff per platform after additive scene load.
Block merges that add scenes without updating APV baking set in PR template.
Pin Lighting Settings asset path in release-evidence/README.md.
Store rebake timestamp beside build ID—partners ask “which bake is in this depot?”

FAQ

Is pink always missing shaders?
Often yes for magenta error color; black probes usually mean missing or unbound APV data.

Do I need lightmaps if I use APV?
Many Unity 6 URP setups use APV for dynamic objects and lightmaps for static—follow your template; do not delete lightmaps without retesting.

Does rebaking fix streaming offsets?
Yes—offsets are baked data. Changing cell size without rebake breaks streaming indices.

WebGL and APV?
Supported with tighter memory budgets—verify probe count and brick size; watch WebGL player separately.