OTOY Forums

Please, this is a desperate request,
we really need to be able to set up user default values for Kernel nodes, and other nodes too.
Is there a way to do this?

Kind regards
Filipe

Why not use local DB to keep nodes with default values ?

Many times we toggle from Pathtracing to direct lighting so we can have a faster feedback, when we turn back to pathtracing all our values are gone...
I know we could use nodes and switch between 2 different kernel node in the nodegraph, but we have enough nodes already.

It would be cool to have a switch-statement case on nodes... if anybody is into programming they will know what I mean.

So it would be nice to put for example 4 kernal nodes in a group, give them each a kernal output. But when the group is placed in your hierarchy, it would show only 1 output. The group would have a case-setting, set to either 1, 2, 3 or 4. Then it picks the output of the corresponding index.

Get it? This would be very useful.

I've used a switch Lua script node myself for cameras and it works (could be adapted for any value). Let me see if we can validate it for 3.06 and post the .orbx node.

That would be sweet! I could really use that

manalokos wrote:Many times we toggle from Pathtracing to direct lighting so we can have a faster feedback, when we turn back to pathtracing all our values are gone...
I know we could use nodes and switch between 2 different kernel node in the nodegraph, but we have enough nodes already.

I do this a lot too. My solution is to group both of my kernels into a node and just change which one is plugged into the output. Keeps it clean and allows you to have the same kernel plugged into multiple render targets.

Not perfect but what we really need is to be able to have the connection lines invisible so we can have this kernel node off to the side not messing up everything else.

It would be simple if octane kernel node would be only one, with different modes, this way the data would be stored even if you changed from direct lighting to pathtracing.

manalokos wrote:It would be simple if octane kernel node would be only one, with different modes, this way the data would be stored even if you changed from direct lighting to pathtracing.

I'm no Octane dev but I do work with their XML node format to integrate my own software and this would cause a lot of problems... most likely not going to happen. And in fact I think this shouldn't be in, nodes should only store what it is using. With the switch-statement case the entire problem is solved.