Pavlov wrote:MIXER NODE:
Now we have separate multiply, mix, add (etcetc) nodes, with no masking and no percent amount. This is a big limit i meet several times per day.
It's needed to have a single, fully featured mixer node with multiple inputs (multiple maps plugged) and for each one we need a menu with blending modes. I know there is something coming in OSL, but this node is a fundamental part of any nodeflow and i really would not rely on OSL, which also means reloading OSL code each time we need it - unless you manage to embed it in Octane nodes so we can just add it like any other node.
More details about masking, percent and multiple inputs:
- Masking - an input where i can plug a greyscale map to decide where mixing happens.
Now, if i need to multiply two maps with masking, ive to create a huge nodeflow to mask maps before they get mixed, and this is very time consuming.
- Percent - same as above - most of the times i do NOT want to mix map 1 and map 2 by 100%, but in a variable amount. Once we have Masking, we can plug a float value there and this would solve, but again it's a matter of workflow optimization. The less nodes we need to get a result, the better. So please, put also a % parameter in new mixer node.
- Multiple inputs - please do not allow just map 1 and map 2 - make a node which can get as many inputs as we need, and allow stacking in photoshop -style so we can set mask, percent, blending mode for each layer.
yoscoob wrote:Let's face it, Octane crashes sometimes - like any program. It's generally really really stable these days, but if Octane crashes in C4D the dreaded 'Render Failure' written in red in the Live Viewer is a pain! Is there a way we could restart Octane from within C4D rather than having to save everything and quit out of C4D to restart Octane?
Keep up the amazing work!
frankmci wrote:Pavlov wrote:I agree with a lot of what you have said, but just FYI, there is already a pretty good OSL mixer node that includes support for a separate alpha. I do wish Octane nodes had multiple output pins for all sorts of basic info, especially RGBA for image nodes, but that seems to contradict their "One and Only One Pin" philosophy, no matter how basic and useful more might be.
Pavlov wrote:i knew some OSL thing was in the work (i think i've mentioned it) but for me, using mixer 100 times per day, OSL is a no-way since every time i've to load code in the node.
There are already several slow-down factors in Octane workflow and i would not add new ones This is something at the root of any Nodal toolset and i really think it must be native.
Anyway, while we wait for Otoy taking care of nodes, it can be surely useful - can you please point me at a link so i grab it ?
color comp(color a, color b, float m, int t)
else if(t==1) c=a*(mix(1,b,m));
else if(t==2) c=a+(mix(0,b,m));
else if(t==3) c=a-(mix(0,b,m));
color tex1 = 0,
int filter2=0 [[string widget = "mapper", string options = "mix:0|multiply:1|add:2|sub:3"]],
float mix2 = 0.5[[float min=0, float max=1]],
color tex2 = 0,
color alpha2 = 1,
int filter3=0 [[string widget = "mapper", string options = "mix:0|multiply:1|add:2|sub:3"]],
float mix3 = 0.0[[float min=0, float max=1]],
color tex3 = 0,
color alpha3 = 1,
int filter4=0 [[string widget = "mapper", string options = "mix:0|multiply:1|add:2|sub:3"]],
float mix4 = 0.0[[float min=0, float max=1]],
color tex4 = 0,
output color out = 0)
out = comp(tex1,tex2,mix2*alpha2,filter2);
if(mix3>0) out = comp(out,tex3,mix3*alpha3,filter3);
if(mix4>0) out = comp(out,tex4,mix4,filter4);