Ali Şahan Yalçın
DocsTroubleshooting

Reference

Troubleshooting

When nothing shows up, or it looks wrong.

I see no difference

  • Check Allow Static Lighting first. It is on in new projects and turns the plugin off.
  • The viewport's Ambient Occlusion view mode shows the engine's own AO, not MultiAO's. Use Buffer Visualization > Material Ambient Occlusion instead, or r.MultiAO.Debug 2 in Lit.
  • Check the log for a Block message for your method.
  • With Screen Space GI, material AO barely shows. Try Diffuse Strength.
  • r.MultiAO.Debug 2 shows without and with side by side.
  • Substrate, static lighting and r.GBufferDiffuseSampleOcclusion all turn the plugin off, because material AO does not exist there.
  • With MeshBlend, the Material AO buffer shows MeshBlend's IDs instead, and its shader patch hides material AO from lighting. See MeshBlend.

It is noisy

  • Raise Quality.
  • Turn on Temporal if you use TSR.

Dark halos around thin objects

Every screen space method guesses what is behind a surface. Try SSILVB with a lower SSILVB Thickness, or lower Radius.

ASSAO or CACAO bleeds across edges at half resolution

Use quality Medium or higher. Their Low quality has no edge detection, by design.

A faint wave along long contact lines with ASSAO or CACAO

That is how both originals behave at low internal resolution. Use full resolution.

The ray traced switches do nothing

RTAO and the path tracer need hardware ray tracing turned on in the project and a GPU that supports it. Lumen AO needs Lumen GI. The log says which rule blocked them.

INFO: These switches are not verified yet. They only change engine settings, so if one misbehaves, set the engine options by hand and pick a plugin method instead.