For those who don’t know the tool: Hurricane is a Blender add-on for artists building FX shots directly inside the DCC. It sits beside B3FX Studios tools such as RBDLab, VDBLab and FluidLab, targeting simulation-heavy VFX work rather than layout, modelling or rendering alone.
A broader Blender solver
Hurricane is a physics simulation engine and particle solver for Blender. It creates fluids, fabrics, soft bodies, sand, grain particles, and dynamic interactions within a single add-on workflow. The current release is Hurricane Beta 0.9.0 by BeFX Studio, compatible with Blender 5.1 to 5.2.
The product is sold through Superhive, formerly Blender Market. Pricing is $98 for an individual licence, $392 for an indie licence covering up to five seats, and $784 for a studio licence covering up to ten seats.
What it is meant to simulate
The add-on is a high-performance physics simulation engine and particle solver for fluids, fabrics, soft bodies, sand and grain particles. The interesting part is the interaction claim. Hurricane is a tool for building different physical materials and particle types in a shared simulation environment, rather than handling each effect as a sealed-off system. For Blender users who have bounced between native particles, cloth, soft bodies, rigid bodies and fluid tools, that is easy to understand. Whether a shot stays stable at production scale is the part artists will want to test, because physics has a sense of humour and usually terrible timing.
Cloth setup
For cloth-style setups, Hurricane starts from the familiar Blender problem: a deforming mesh needs enough resolution to fold cleanly, collision geometry needs sane thickness, and the material response needs tuning before the shot becomes useful. The controls to watch are the usual suspects: stiffness for stretch and bend resistance, damping for killing jitter, mass or density for weight, friction for contact behaviour, collision distance for surface separation, and solver iterations for stability. Low stiffness gives saggy fabric.
High stiffness helps panels hold shape, but can expose collision noise if the mesh or timestep is not up to it. Pinning or constraint weights are the practical route for flags, hanging cloth and character-attached pieces. Start with a simple collision scene, cache early, then add folds and secondary motion. Cloth solvers are honest in the most annoying way: bad scale, thin collision objects and heroic frame ranges tend to fail before they become art.
Soft body setup
Soft body work is about volume, deformation and recovery. The setup usually begins with a closed or well-behaved mesh, clean normals, sensible object scale and collision objects that do not already intersect the simulated surface. The useful parameters are stiffness, damping, pressure or volume preservation where available, mass, friction, collision margin and solver iterations.
Stiffness controls how strongly the object resists deformation. Damping controls how quickly wobble dies out. Volume preservation keeps a body from collapsing into an expensive puddle, which is funny once and rarely billable. Collision margin needs enough room to prevent interpenetration, but too much offset makes contact look floaty. For production, soft bodies should be tested with the actual camera distance and animation timing, because a setup that looks plausible in a viewport turntable can still look like rubberised soup in a cut.
Sand and grain setup
Sand and grain simulations depend less on beautiful hero meshes and more on particle count, contact behaviour and scale. A basic setup needs an emitter or initial particle volume, collision surfaces, gravity, material-style controls and enough solver quality to keep the grains from tunnelling or clumping in strange ways.
The parameters to check are particle size, density, friction, cohesion or stickiness where available, damping, collision distance, substeps, solver iterations and cache settings. Smaller grains can look better, but they raise the particle count fast, so preview sims should stay deliberately ugly until the behaviour works. Dry sand needs friction and separation. Wet sand or snow-like material needs more cohesion. For shot work, the cache path, playback speed and reproducibility matter as much as the first nice spill, because grains have a gift for becoming a million tiny reasons to miss a deadline.
Beta status and compatibility
The tool currently carries the Beta 0.9.0 label. That matters for pipeline deployment because beta software should never be treated like a locked production dependency, even when the demos look lovely and the deadline is already glaring at you from across the room.
GPU acceleration is roadmap, not current fact
A GPU-accelerated version is planned for a future release, with the stated goal of faster simulation performance. That does not make the current release a GPU simulation engine for production decision-making.
The listing includes “GPU accelerated fluid solver” as marketplace metadata, while the FAQ frames GPU acceleration as future work. That mismatch needs clarification before anyone builds a schedule around GPU speed.
Where it fits for artists
Hurricane is aimed at artists who want more simulation work inside Blender rather than round-tripping to a dedicated FX package. That makes it relevant for motion design, small VFX teams, freelance shot work, previs-style physical effects and Blender-centric pipelines that need cloth, particulate and fluid-like behaviour in one scene context.
It is not presented as a replacement for full procedural FX environments such as Houdini. For now, the safer reading is simple: Hurricane tries to give Blender users a broader local simulation tool without leaving Blender.
Hurricane is one of the more ambitious Blender add-on pitches in the simulation space: fluids, fabric, soft bodies, grains and dynamic interaction under one product name. The verified facts support real interest, especially for Blender-first artists who want more FX work inside the DCC. The beta label, the roadmap GPU language and the limited public technical documentation also make the responsible advice obvious: test it on duplicate project files, cache-heavy scenes and ugly collision cases before putting it anywhere near final delivery.
https://superhivemarket.com/products/hurricane
https://b3fxstudios.com/documentation/hurricane/#/en/introduccion/introduccion
https://b3fxstudios.com/
https://b3fxstudios.com/support/
Suggested tags:
