Unity’s Graph Toolkit (Experimental), AVAILABLE TODAY in Unity 6.2!

After experiencing the powerful and user-friendly node system in Houdini, I would like to offer a few suggestions for the GTK node graph:

a. Use color to represent commonly used port types.
b. Omit port names and instead display port information (such as the name) on hover.
c. Remove input controls directly on the ports; instead, input values through the node inspector. If a port’s value is important enough to be visible in the graph, use a dedicated constant node as the input.

Why:
The node graph should convey only the most essential information: what each node does, and how nodes are connected. In contrast, the ports of a node tend to be relatively stable — after using them a few times, users usually remember their functions even without visible UI. When in doubt, hovering the mouse over a port can provide the necessary details. Displaying all port information directly on the graph wastes both the user’s cognitive bandwidth and valuable canvas space.

Here is a screenshot of a node graph in Houdini — it uses icons, shapes, colors, and label text to help users quickly identify nodes and key information.

4 Likes