Dynamic Weather System - Unreal 5 - Tech Art

Overview of weather system

Rain Niagara System

Rain Niagara System

Properties that control the system

Properties that control the system

Blueprint Breakdown _01

Blueprint Breakdown _01

Blueprint Breakdown _02

Blueprint Breakdown _02

Blueprint Breakdown _03

Blueprint Breakdown _03

Dynamic Weather System - Unreal 5 - Tech Art

One slider👏 Everything responds👏
I spent the last few weeks building a dynamic weather system in Unreal Engine 5.8. A single Storminess value from 0 to 1 drives the rain, surface wetness, puddles, wind, cloud coverage, fog and lighting. No presets, no cutting between states.
✒️The structure is simple. A Material Parameter Collection acts as the bus. A Blueprint controller reads seven float curves, one per system, and writes the results into that collection. Materials read from it. Niagara gets its values through user parameters.
✒️The curves are the interesting part. They are what give the transition its shape. Clouds roll in first, then the wind picks up, then the rain starts, and the puddles only form once the ground has been wet for a while. Without them everything moves at once and it looks like a slider, not weather.
✒️The wetness is a reusable material function, so every master material in the scene gets the same darkening, roughness and specular response, with a per instance porosity value. Sand soaks fast. Painted metal barely changes.
💡Three things I learned:
1. Overcast is flat, not dim. My first storm pass turned the sun down and tinted it blue, and it read as dusk. Real overcast is still bright, it just has no direction. I had to raise the sky light as the storm came in, not lower it, before the scene looked like weather instead of nightfall.
2. GPU particle events do not support boolean payloads. My rain was a GPU sim and the splashes needed collision events, and the shader simply would not compile. Moving the emitter to CPU fixed it in two minutes, at the cost of particle count. Worth knowing before you build everything on the fast path.
3. Most of my bugs were silent. Adding a scalar to a Material Parameter Collection quietly drops existing bindings in your materials. Set Niagara Variable takes an unvalidated string, so a typo just does nothing. A Blueprint node disconnected from the exec chain looks completely normal. None of these throw an error. You only find them by checking the thing you were sure was fine.

The cost surprised me too. Nearly all of the extra expense at full storm sits on the game thread. The GPU barely reacts to the volumetric clouds, the fog and the wetness function combined. Environment is from Fab Store, Dekogon's Powell Docks. The systems are mine.