Troubleshooting

Fog does not appear

Run Tools > Kiwi Studios > Fog of War > Install or Repair URP Renderer and confirm that the warning lists the expected Universal Renderer assets before clicking OK. Confirm the camera uses one of those renderers, the world initialized, and either exactly one active world exists or the camera has a configured FogCameraRenderer.

Confirm the source is inside bounds and its Visibility Mask intersects the world Observer Mask. Run ForceRefresh and inspect the combined texture in the diagnostics window.

Fog is visible in Scene view but not Game view

The renderer feature runs per game camera. Confirm the game camera is a URP Base camera and has a FogCameraRenderer binding when more than one world is active. Preview, reflection, and Overlay cameras are intentionally skipped.

The skybox or background turns black

The depth-aware pass preserves the existing camera color wherever the depth texture contains its exact far-clear value, so skyboxes and platform backgrounds remain visible. Rerun Install or Repair URP Renderer after upgrading and confirm there is only one active Kiwi fog renderer feature. A custom renderer feature that clears camera color after the skybox can still replace that background independently of Fog of War.

Fog disappears when the Scene camera moves far away

Current versions compare depth against the platform's exact far-clear value instead of an epsilon, so distant opaque Scene-view geometry remains fogged. If this occurs after upgrading, reimport the package shader and confirm the renderer feature references the included KiwiFogOfWarDepthAware shader.

The fog shader is unsupported

Fog of War 26.8.5 requires URP. Confirm the active render pipeline asset is a Universal Render Pipeline asset and rerun the renderer installer. The installer serializes the included hidden depth-aware shader into the renderer feature so it remains referenced for runtime use.

Transparent content does not match its own height

The depth-aware pass reconstructs positions from the camera depth texture, which normally contains opaque geometry. Transparent pixels are fogged using the opaque surface behind them. Use an opaque depth-writing pass for transparent geometry whose independent world position must drive fog.

A wall does not block LOS

Add FogObstacle, assign the correct FogWorld, and set a supported Collider. Bake static obstacles. For a mesh or unusual footprint, add FogObstacleBoundsOverride or use a conservative collider proxy.

Static Box, Sphere, and Capsule footprints bake correctly even when their hierarchy is inactive. If a bake predates this behavior, rebuild it once so the asset contains the full footprints instead of stale cells.

A door keeps blocking after it opens

Set the obstacle mode to Dynamic. The authoring component detects transform changes and marks the handle dirty. Code-driven custom bounds must call MarkObstacleDirty with the new bounds.

The bake is stale or incompatible

The diagnostics window warns when format, bounds, resolution, checksum, or deterministic scene hash differs. Rebuild from Tools > Kiwi Studios > Fog of War > Bake Active Scene.

Restore fails

Inspect the returned FogRestoreResult. Snapshots are intentionally rejected when observer, bounds, resolution, version, payload length, or checksum differs.

Compute shaders are unavailable

Use Auto to select the Burst CPU fallback. GPU mode logs a warning and falls back when compute support or the compute asset is unavailable.

Console multicast errors

Unity Editor player-connection multicast messages are unrelated to Fog of War unless their stack or context points into this package. Clear the Console and reproduce the fog scenario before filing a package issue.