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
Buggy node groups
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
-
Andreas_Resch
- Posts: 319
- Joined: Sat Jul 28, 2018 6:29 am
- Attachments
-
- Octane_Nodegroups_01.mp4
- (4.5 MiB) Downloaded 459 times
Last edited by Andreas_Resch on Sun Mar 03, 2024 2:43 pm, edited 1 time in total.
-
linograndiotoy
- Posts: 1353
- Joined: Thu Feb 01, 2018 7:10 pm
Hey Andreas, please also include the scene, if possible.
-
Andreas_Resch
- Posts: 319
- Joined: Sat Jul 28, 2018 6:29 am
Here's the blend file ...
- Attachments
-
- Octane2023_Scene_Nodegroups_01.zip
- (192.39 KiB) Downloaded 21 times
-
linograndiotoy
- Posts: 1353
- Joined: Thu Feb 01, 2018 7:10 pm
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
- Posts: 319
- Joined: Sat Jul 28, 2018 6:29 am
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.
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
- Posts: 319
- Joined: Sat Jul 28, 2018 6:29 am
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.
- Attachments
-
- Octane_Nodegroups_02.mp4
- (9.03 MiB) Downloaded 353 times