Buggy node groups Tweet

[Andreas_Resch]

Node groups are really buggy right now. Aside from the lacking compatibility between the Cycles inputs and the Octane nodes, there are also issues when using Octane inputs only. As you can see in the attached video, the inputs aren't transported to the nodes correctly. You can also see that when you manipulate the values outside the group, strange flickering happens with the material rendering.

I think that's something that should looked into rather soon. Node groups are a huge part in Blender and everybody uses them regularly.

Octane 28.9 CB, Windows 10, RTX 3060

[linograndiotoy]

Hey Andreas, please also include the scene, if possible.

[Andreas_Resch]

Here's the blend file ...

[linograndiotoy]

To make it work, you'll need to rename at leats one of the inputs, since they can't have the same name when used with Octane.

[Andreas_Resch]

Thanks for clearing that up. But that's still a bug then. Your addon probably refers to the output sockets by name but should do so by ID. Should be a quick fix.

Nonetheless - I've had several others issues with node groups as well. It would be great if the whole node group infrastructure could be made watertight. As I said - Blender users need them all the time.

[Andreas_Resch]

Here's another example of how the node groups wont update. The color field goes into a Float3ToColor node inside the group and then into a Composite Texture Layer. So please check that those socket changes cause a refresh.