Releases

Known Issues

A bug in Blender 3.6 causes custom nodes not to appear in the Search menu, so they can only be added from the Add menu. This has been fixed in Blender 4.0.
A bug in Blender 3.5 causes files with custom nodes to crash in some situations. This has been fixed in Blender 3.5.1, so it is critical to update, in order to avoid crashes when using UDON.

Blender 4.0 brings a new and extremely useful subpanel feature, which allows you to organise your node group input/output sockets into collapsible sections (this does not seem to be documented yet, but you can find an explanation here and here). These subpanels work with UDON out of the box, so any panels you add to your node group will automatically be carried over with their sockets to your custom nodes! Though it should be noted that adding UDON custom properties to the subpanels is not currently possible, and at the moment they all appear above the subpanels.
Since Blender 4.0, all custom nodes (including library nodes) appear in the node search again.
Some node property names have been changed in Blender 4.2, to fix name collisions. This only affects the Geometry Color node, Shader AOV Output node, and the Compositor Box/Ellipse Mask nodes. If you have used any of these nodes inside your custom nodes and exposed their properties, they were likely working unpredictably in the first place due to the name collision, but they will now require you to manually fix the property links and recook the nodes.

Due to changes in Blender's menu system, custom nodes are no longer inserted in alphabetical order, instead being added to the end of the menu.

UDON v0.3.0 will require Blender 3.6 LTS or later, dropping support for Blender 3.3 LTS (as well as 3.4 and 3.5), since it has reached EOL. As per the compatibility policy, this means that unless another v0.2.x patch release becomes necessary, this is the last UDON version to support Blender 3.3 LTS, Blender 3.4, and Blender 3.5.

Implemented support for exposing Image properties:
- Expose Image properties by clicking anywhere on the property UI widget (including the Open and New operators);
- Custom Image properties are displayed with an ID selector including Open and New operators (matching native Image properties);
- A full image UI, matching Blender's native UI, is (optionally) generated under custom Image properties, to control image parameters (color space, frame ranges, layer selection, etc.);
- When loading image sequences with the Open operator, the frame range is automatically detected (matching the bahaviour of native Image properties);
- Links to the main socket ("Image" or "Combined") of comp Image nodes are automatically managed, so they are preserved if the socket changes name when loading different images;
- Many, MANY tiny details to ensure custom Image properties behave as close as possible to native Image properties across the board.
The default width of custom nodes (used for new instances of the node) can now be customised, and defaults to the width of the group instance being cooked;
Full support for Blender 3.6.

Fixed cooking being slightly slower when using nested custom nodes;
Fixed a rounding error that caused float properties to sometimes have a step of 0, which made it impossible to manipulate them with the mouse;
Fixed node links inside custom nodes disappearing in some cases.

For clarity, the name of the property being exposed is now shown on the "Expose to Custom Node" operator in the context menu;
If no properties have been exposed, the Properties box in the Node Kitchen shows a hint explaining how to expose properties;
A new option was added (disabled by default), to hide the Node Pantry while the editor is inside a node group, to reduce clutter,

Optimised performance when changing property values on custom node instances (significantly reduces latency with complex node setups, especially when using many nested custom nodes);
Store an "udon_type" property on custom nodes (in preparation for stand-alone export capability);
Various code quality and architectural improvements with no user-facing changes.

Fixed mistake in version comparison code (used for checking compatibility of UDON nodes);
Fixed error when cooking a node with a property called "type".

Initial release.