Quick answer: Enable cloud shadows on the directional light (or project a scrolling cloud-coverage mask as a light function) so moving cloud shadows sweep across the ground.

Big volumetric clouds roll by but the landscape below never darkens under them. Cloud shadows are an opt-in feature; without them, the ground ignores the clouds entirely.

How to fix it

1. Enable cloud shadows

On the Directional Light enable Cloud Shadows (and set Cloud Shadows on the Volumetric Cloud component) so the cloud density attenuates sunlight reaching the ground.

2. Or project a coverage mask

If volumetric cloud shadows are too costly, drive a light function or a scrolling shadow texture from the same cloud coverage and wind so soft shadow patches sweep across terrain cheaply.

3. Match wind and density

Move the cloud shadows with the same wind vector and tie their darkness to cloud coverage so the shadows on the ground line up with the clouds the player sees overhead.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.