Skip to content

Rendernode [Rsn]

by atticus_id·Rendering

Images © atticus_id. Used for product review; image policy.

Why we like it

Rendernode [Rsn] stands out in the superhive library for taking a node-based, Geometry Nodes field style approach to render workflows in Blender, and it ships under the permissive MIT license.

What is Rendernode [Rsn]?

Rendernode [Rsn] is a node-based design and render workflow for Blender, built around a Geometry Nodes field style layout. It lets you assemble render setups from connected nodes, using group nodes to organise the tree and a switch node that works with all socket types through a direct input socket, replacing the older Variants Node.

The node set covers input nodes for object, material, float, vector, integer, boolean and string data, along with utility nodes for math, vector, boolean math and string operations, plus get and set nodes. A render list node and a get render list index node handle render tasks, and a power selector switches the active task within the render list.

The evaluate system is developed on top of rigging_nodes for faster speed, and the UI drops the old outline drawing in favour of showing process time and node names. Dynamic enums and sockets adapt to preferences such as render engine and color management. The project is distributed under the MIT license.

Who is Rendernode [Rsn] best for?

Rendernode [Rsn] is best for blender users who want to build design and render setups through a node-based workflow.

How much does Rendernode [Rsn] cost?

Rendernode [Rsn] is completely free to download and use.

Key features

  • Geometry Nodes field style workflow for building render setups
  • Switch node for all socket types via a direct input socket, replacing the older Variants Node
  • Input nodes for object, material, float, vector, int, bool and string data
  • Utility nodes for math, vector, boolean math and string operations, plus get/set nodes
  • Render list node and get render list index node, with a power selector to switch the active task
  • Evaluate system developed on rigging_nodes for faster speed
  • UI shows process time and node names, and dynamic enums/sockets for preferences like render engine and color management

Tags

#Blender#rendering#node-based workflow#render workflow#geometry nodes#nodes#MIT license

Frequently asked questions

Does Rendernode [Rsn] work with Blender 3.1?

Rendernode [Rsn] lists compatibility with Blender 2.93, 3.0 and 3.1. If you run one of those versions, you should be set to load its node-based design and render workflow. On other Blender releases, behaviour isn't stated here, so it's worth checking the developer's page before installing. The add-on was published over five years ago, so testing on a matching version, or reviewing the documentation linked by the developer, is the safest way to confirm it fits your current setup.

What license does Rendernode [Rsn] use?

Rendernode [Rsn] is distributed under the MIT license, one of the more permissive open-source licenses. That generally allows broad use and modification, though you should read the license text itself for the exact terms rather than relying on a summary. The project is credited to atticus_id, with documentation and develop-branch builds linked from the developer's GitHub and Gitee pages. If you plan to modify or redistribute the code, review those resources and the license file directly to stay within its conditions.

Is Rendernode [Rsn] free to download?

Rendernode [Rsn] is listed as free here. Licensing and any support options can change, so check the developer's page for the current details before you download. The developer offers optional voluntary support tiers on the listing, which are not required to use the add-on. For the latest on availability and how to get the files, including any develop-branch builds, the developer's own page and linked repositories are the place to look first.

Why doesn't the whole tree update when editing inside a render node group in Rendernode [Rsn]?

Rendernode [Rsn] has a documented limitation worth knowing: when you edit inside a render node group, it won't update the whole tree. The developer's guidance is to always set the active task on the base root so the tree evaluates correctly. This ties into the render list node, where a power selector lets you switch the active task. Keeping the active task set at the root is the recommended way to work around the update behaviour when editing grouped nodes.

Similar plugins