Sequential node groups for Materials doesn't work

Forums: Sequential node groups for Materials doesn't work
Sub forum for bug reports
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)

Sequential node groups for Materials doesn't work

Postby ChrisH » Sun Mar 17, 2019 6:51 pm

ChrisH Sun Mar 17, 2019 6:51 pm
Hi!

I came across a problem where I can't pipe the material output from one node group into another node group (for mixing etc), it just appears as the default white material (see picture).
It works fine if I just connect a material node to the second node group.

Here's the setup:
A node group with a material setup.
Another node group with another material setup + a mix material (and texture to control it, just a checker texture in the test) to combine the material with an incoming material.
OctaneBlender_NodeGroups.png

(The third Suzanne should be gold + red)

(I've also had problems with a node group, with a material setup, inside another node group [same result: it gets ignored], but that I couldn't replicate in my test file, but can't get to work in my real project. ETA: The problem appeared in my test file as well: If I [in a node group] connect the output [OutMat] of the group, instead of just a material node, it tries to refresh the viewport, but just stays at "Waiting for image", if I reload the viewport the material appears white)

Using the 17.5 TEST / 2018.1 RC 6 version.

(I've tried with Nodegraph optimization ON and OFF, with the same result)
Attachments
OctaneTest2.blend
(810.35 KiB) Downloaded 9 times
Windows 10 Pro - AMD Ryzen 7 2100X 8 core 3.70GHz - 32GB RAM - GeForce GTX 1080 8GB
Stand Alone + Blender Plugin user
User avatar
ChrisH
Licensed Customer
Licensed Customer
 
Posts: 53
Joined: Sun Mar 06, 2011 12:13 am
Location: Lidköping, Sweden

Re: Sequential node groups for Materials doesn't work

Postby linograndiotoy » Wed Mar 27, 2019 5:14 pm

linograndiotoy Wed Mar 27, 2019 5:14 pm
Thanks for you report Chris!
linograndiotoy
OctaneRender Team
OctaneRender Team
 
Posts: 131
Joined: Thu Feb 01, 2018 7:10 pm

Re: Sequential node groups for Materials doesn't work

Postby DrawFun » Sat Apr 13, 2019 4:16 am

DrawFun Sat Apr 13, 2019 4:16 am
Hello Chris,

Thanks for your report and sample scene.

This is addressed in OctaneBlender with blender 2.8, which is currently in development. So is the meaningless naming issue.
These issues are tough to fix in the current shader node graph system so we rewrite a new one in blender 2.8 to get them sorted. Now we still need some more tests to make sure the new system is stable enough. After that, it will be merged into blender 2.79 builds.

Cheers,
DrawFun
DrawFun
OctaneRender Team
OctaneRender Team
 
Posts: 249
Joined: Fri Aug 25, 2017 5:02 am

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 1 guest

Thu Jun 20, 2019 3:58 pm [ UTC ]
cron