You're blocking ads, which pay for BlenderNation. Read about other ways to support us.

Shape the Future of Blender Nodes: Enums, Portals and Loops


Blender node godfather Jacques Luckes has just posted not one, not two, but three proposals on devtalk, each pertaining to new areas of development for Geometry Nodes and Blender nodes in general. This post will overview the three topics in question, and I highly recommend you check out the proposals on their respective Dev Talk thread and give any feedback you might have to give these designs the best chance of success. Here are the three proposals in question:


First on the menu, Portals. As described by Jacques, the Portals devtalk thread aims to "determine if and how portals in Blender’s node editor can help to improve the node editing experience".At their core, the concept of portals is to allow the linking of nodes without having a visible noodle, for useability and readibality purposes. Jacques pooled various Right Click Select proposals for portals, and described two potential implementations: Portal links, in which links can be turned into portals themselves, and portal nodes which act as wireless input and output "anchors".

Jacques has already implemented a portal links prototype that is available for download and testing (check out a quick workflow demo in the video above). Join in on the conversation and check out the proposal and community response in detail on the link below:

Enums (dropdowns/options)

Next up are enums, and more specifically the addition of an enum socket Geometry Nodes as a first step and in Blender node editors in general. Enums, commonly known as dropdown menus, are used in many GN nodes, but are not exposed as a socket yet, with all inputs as sockets being one of the purported goals of the system. Jaccques once more built a prototype for his proposed solution to this issue,

Enums exposed as sockets in Jacque's prototype

Jacque's prototype also includes an enum node that handles user-defined enums as seen in the example below:

Join in on the conversation and check out the proposal and community response in detail on the link below:


Last but not least, Loops! Loops are a heavily requested feature for Geometry Nodes, which makes their design all the more important to get right. Jacque's extensive proposal differentiates two potential loop type nodes, a "serial" loop node which is most simply described as a "repeater" loop, and a "parallel" loop which is more akin to a "For each" loop iterating over elements of Geometry. Here is an example of the "parallel" loop in action:

The proposal and discussion aroud it are extensive and too detailed to discuss on this post, so I strongly recommend you check out the dev talk thread for more information and to participate in the conversation:

About Author

Mario Hawat

Mario Hawat is a Lebanese 3D artist, writer, and musician currently based in Paris. He is a generalist with a special focus on environments, procedural and generative artworks. Open to freelance work.


  1. With every iteration, GN gets more and more confused. I kinda get it, one needs low level to build virtually anything using jsut nodes. But non-programmign folks like myself have a hard time getting their head round it. Isn't it a wild goose chase really? One can't create elaborate geometry without having to build a very complex yet hard to read tree with myriads of nodes involved. Of course you can pack some into a node group or even output the result into a modifier with editable parameters but diving deeper into low level makes it one hell of a challenge. Maybe I'm a little too stuck with the traditional modeling approaches and just can't get used to doing it the node way. Whenever I take a glance at that fancy nodevembebr stuff, I get lil dizzy you know.
    Anyways, to each his own.

Leave A Reply

To add a profile picture to your message, register your email address with To protect your email address, create an account on BlenderNation and log in when posting a message.