RainFlow requires Blender 5.2 or newer. It supports Windows, macOS, and Linux wherever that Blender version is supported.

Download the complete RainFlow ZIP from your Superhive order. In Blender, go to Edit > Preferences > Get Extensions, open the menu, choose Install from Disk, and select the ZIP without extracting it. Enable RainFlow Surface Raindrops, then open the RainFlow tab in the 3D View sidebar.

RainFlow creates a separate controller and does not apply the simulation to the original collision mesh. Selected emitter hierarchy roots are temporarily parented to the controller so they follow rigid motion, while their initial world transforms are preserved. Removing the setup keeps user-supplied emitters and removes only RainFlow-managed copies and generated objects.

Yes, for rigid motion. A setup follows its sole simulation mesh or the nearest parent shared by all simulation meshes, making the target stationary from the simulation's local point of view. Independently rooted meshes cannot share one safe transform and leave the controller in world space with a warning. Rapid deformation and independently moving components can stretch or detach existing trails.

Yes. Put one or more emitter surfaces in a collection and select it as the Rain Spawner Collection. Its top-level object hierarchies will follow the RainFlow controller without jumping when the parent is assigned. If left blank, RainFlow creates a fitted wireframe emitter hidden from renders.

Yes. Each setup has an independent controller and node-tree graph. If another setup would share an emitter collection already used by a different controller, RainFlow creates a setup-owned emitter copy so both simulations can move independently.

No. RainFlow generates the physical droplet and trail geometry. Wet-surface darkening, reflective wet shaders, puddles, and material blending must be created separately for the scene.

No. It is an efficient artistic surface-rain system rather than a Navier–Stokes fluid solver. It does not perform physically accurate liquid merging or full surface-tension simulation.

Use a simplified outer collision shell, keep Iterations at the default of 1 while working, reduce dynamic or static density, shorten trail lifetime, and lower mesh detail. RainFlow is primarily CPU-bound, and performance also depends on simulation age, viewport mode, cache state, scene complexity, and hardware.

RainFlow works best with a clean outer simulation shell. Internal components, very thin surfaces, sharp edges, deep concavity, and extreme topology can produce unintended projections. A cleaner collision mesh and a higher iteration count can improve reliability.

Baking is recommended for final rendering and render-farm use when appropriate. Include the bake data when transferring the project and use the same compatible Blender version used to prepare the shot. Always test a short render range first, especially when using motion blur.

The public GitHub repository contains only the GPL-licensed Python integration source. It intentionally excludes the commercial Geometry Nodes asset, example scene, documentation, and complete installer. Customers should install the ZIP supplied through their Superhive order.

Use the Superhive product inbox, email [email protected], or message @MrBullCrap on Discord. Include your order number, Blender version, operating system, reproduction steps, screenshots, and a minimal .blend file when possible. Response time is normally within seven calendar days, subject to any faster support requirement shown on the Superhive product page.

RainFlow has a 30-day limited refund policy for qualifying product defects, material misrepresentation, duplicate purchases, and qualifying accidental purchases that have not been downloaded. Contact support through the Superhive purchase conversation first so troubleshooting can be attempted. Superhive's marketplace policy and applicable consumer law take precedence.