Quick answer: Add the global wind vector to the particle gravity/velocity so rain and snow slant with the wind, and tilt the streak stretch to match the travel direction.

A storm is howling but the rain still drops perfectly vertical, which reads as calm. Precipitation should lean into the wind, with snow drifting more than heavy rain.

How to fix it

1. Combine wind into velocity

Set the particle initial velocity or gravity to downward plus the global horizontal wind vector so drops travel at a slant proportional to wind strength.

2. Align the streaks

For stretched rain billboards, orient the streak along the actual velocity direction (down + wind) so the visual streak matches the path, not just a vertical line.

3. Differentiate snow and rain

Give snow a much lower fall speed and higher wind susceptibility than rain so it drifts and swirls, while heavy rain only leans slightly, selling the same wind at different intensities.

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 Godot 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.