Troubleshooting

intermediate troubleshooting

This page covers the most common issues encountered with Volumetric Fog & Mist 2 for the Built-in Render Pipeline and how to resolve them.

Symptom	The VolumetricFog component is added to the camera but no fog appears in Play mode.
Cause	Incorrect setup, zero density, or the component is on the wrong camera.
Solution	Confirm the VolumetricFog script is attached to the active Main Camera. Check that Density is greater than 0. Verify the camera is using the Built-in Render Pipeline (not URP or HDRP). Try assigning one of the included presets from `VolumetricFog/Resources/Profiles`.

Symptom	Fog renders but appears completely dark or nearly invisible.
Cause	No light source assigned or ambient light is too low.
Solution	Assign a Directional Light to the Sun property. Increase the Light Intensity parameter. Check that the Fog Color Mode matches your lighting setup (try "Natural" or "Single Light"). Increase Ambient Light intensity in Window > Rendering > Lighting.

Symptom	Visible concentric rings or color banding in the fog, especially on the sky.
Cause	Insufficient color precision or ray-march sampling.
Solution	Enable HDR on the camera. Enable Dithering and Jittering in Optimization & Quality settings. Increase the dithering intensity for low-density fog. Enable Blue Noise in Shader Options.

Symptom	Significant FPS drop after enabling Volumetric Fog.
Cause	Too many expensive features enabled, or excessive render distance/quality.
Solution	Reduce Max Distance and Stepping. Increase Downsampling to x2 or x4. Disable unused features: Light Scattering, Point Lights, Fog of War, Compute Depth. See the Performance Tips page for a complete optimization guide.

Symptom	Particles or transparent objects are clipped, invisible, or show strange colors when fog is active.
Cause	Render order conflict between fog and transparent objects.
Solution	Try one of these approaches (they are mutually exclusive): Render Before Transparency — fastest option. Transparent objects draw on top of fog. Compute Depth with "Tree Billboards And Transparent Objects" scope — treats transparent objects as cutout. Adjust Cut Off value for best result. Transparency Mode: Blend — blends transparent objects with fog. Adjust Blend Power for the desired look.

Symptom	Fog works in the Editor but fails or looks wrong in builds.
Cause	Shader variant stripping removes required keyword combinations.
Solution	Disable Strict Shader Variant Matching in Player Settings > Configuration. Use Shader Options in the Inspector to remove unused keywords before building. Check Edit > Project Settings > Graphics > Shader Stripping and reduce stripping level.

Symptom	Walking through a Fog Volume does not change fog settings.
Cause	Missing colliders or incorrect target assignment.
Solution	Ensure the Fog Volume game object has a Collider component with Is Trigger enabled. Ensure the camera (or assigned Target Collider) has a Collider and Rigidbody (or CharacterController). Verify the Target Fog property points to the correct VolumetricFog instance. Enable Debug Mode on the FogVolume component to check enter/exit events in the Console.

Symptom	Fog renders incorrectly in VR (offset, duplicated, or missing in one eye).
Cause	Single-Pass Stereo setting mismatch.
Solution	Verify that the VR mode shown in the VolumetricFog Inspector matches your Player Settings stereo rendering mode. If XR is not needed, disable it by commenting `#define ENABLE_XR` in `VolumetricFog.cs`.

If your issue is not listed here, check the FAQ or contact support at contact@kronnect.com with your Unity version and a description of the problem.

Was this page helpful? |