RBF Nodes for Blender: Build Complex Rig Controls with Drivers

Brave Rabbit’s RBF Nodes for Blender was featured in a 5 October 2026 article published by 80 Level. The add-on is a node-based solver that connects multiple inputs to multiple outputs. It focuses on defining rig controls using sample poses and creating smooth transitions between them. It requires Blender 4.2 or later.

What problem does RBF Nodes address?

Blender’s drivers work well for direct relationships, such as one simple control managing another property. But when multiple controls need to affect several results at once, setting up and managing those relationships can become difficult. Instead of building these connections one by one using long expressions or helper bones, RBF Nodes handles them through a solver with defined inputs and outputs.

Users specify the inputs they want to control the system and the properties they want to change, then define some poses as samples. The solver calculates the transitions between those samples. The developer emphasizes that the RBF method isn’t necessary for every rig: if existing drivers meet your needs, continuing to use them may be more appropriate.

From character rigs to node parameters

One of the add-on’s key use cases is correcting deformations that can occur during joint movement. Corrective shapes for areas such as the shoulders and hips can be activated based on the positions of multiple controls. In facial rigs, the positions of the controls can also affect different shapes together.

RBF Nodes isn’t limited to character deformation. Transforms or custom values can also be used to control Shader and Geometry Nodes parameters. This allows the same approach to be applied to both rig behavior and node-based content. The source also points to a tutorial showing how to set up these operations, but doesn’t specify any particular tutorial steps or ready-made rig templates.

Sharing and compatibility requirements

Anyone opening a rig created with the add-on also needs RBF Nodes. The free runtime version included with a purchase offers one way to provide this dependency to people who will use the rig. The developer says the runtime can be distributed with rigs, provided to clients, and installed on render farms.

That makes it important to include the RBF Nodes requirement in the sharing process before transferring a file to another artist, client, or rendering infrastructure. The source doesn’t explain the add-on’s price or hardware requirements. It provides a purchase link but no pricing details. The requirement for Blender 4.2 or later should also be taken into account when planning which version to install.

Impact on architecture and archviz workflows

The use cases described for RBF Nodes focus primarily on character rigs and node controls. There’s no claim that it directly speeds up architectural modeling or static visualization. However, archviz teams using animated characters in their scenes could consider this approach for facial or joint deformations. It may also be useful for users who want to drive Geometry Nodes parameters with transforms or custom values.

For studios, the decision depends on whether these kinds of multi-control relationships are actually needed. Standard drivers may be sufficient for simple controls; the RBF approach is worth considering for more complex relationships. Teams sharing rig files should also include any add-on or runtime requirements in their delivery notes, along with the Blender version. Since the source doesn’t provide hardware requirements or license pricing details, these should be checked separately before purchase.