Be able to choose to work in subnet or not.

[fantome]

Hi,

It would be great to be able to have the choice to use or not the subnetwork inside the octane material builder.
In previous octane version we could create node directly at the root of the shop.
Now we are force to use a subtnework to build our shader.

I find overkill to have to dive each time in a subnetwork when my shader is just a simple glossy.
in fact i have to do the following :

- create subnet
- dive in subnet
- create glossy
- plug the glossy output to the subnet output
- leave the subnet
- plug the subnet output in the shop output
=> 6 steps

it would be cool to be able to
- create glossy
- plug it to the shop output
=> 2 steps

I find that the behavior in octane standalone is great. You have the choice to build directly your nodes and if you want to you can pack them in a subnet.

To be able to do so i have to create my node in the subtnet and CTRL+X / CTRL+V them each time.

Cheers
E

[juanjgon]

Sorry, I'm not sure to understand your workflow using subnets. In Houdini 16.x you can use the Octane material nodes directly as materials for the objects (while working inside the new /mat networks), or you can add the materials inside a material builder, liking it directly to the material output. Why are you using subnetworks?

Thanks,
-Juanjo

[fantome]

Thanks for your very fast answer Juanjo !

Well it's because i am a total has been and was still using the old Shop context to work with octane.
As LiveDB still import shaders in Shop i have the wrong feeling that it was still the default context for octane.
But indeed i have just double check , in the new mat context things work perfectly -> subnetwork if you need but not an obligation !

So now can we consider shop kinda legacy with octane like for mantra ?
In that case that would be great to also have the ability to import liveDB in Mat context, and create the render target node in Mat context
in order to get one consistant context to store octane nodes.

Thanks again for your help !
Cheers
E

[fantome]

As a side note i am not able to see octane shader located in a Mat context to assign them at obj level.
It does work in shop context.

when i do the assignation of the path manually it does work, so it's more a UI problem i guess.

[juanjgon]

You need to enable the material flag in the node (the top-right brown flag)

Thanks,
-Juanjo

[fantome]

Great Juanjo ! It works

thanks for your great support.

[fantome]

As a side note that would be great to have the octane default render target also available in the Mat context.
In octane options panel that would be great to be able to choose the context where we want to import livedb mat.
In order to unify all in one context.

cheers
E

[juanjgon]

Yes, true, at some point all the plugin features should have a version for the new /mat networks because if fact the SHOP based workflow is deprecated in Houdini 16.x and it could be even removed by SideFX in the future.

Thanks,
-Juanjo

[blobbybarack]

Well it's because i am a total has been and was still using the old Shop context to work with octane.

I know how you feel.

[fantome]

Hi Juanjo !

Do you have any ETA for the creation of the Octane Render Targets in Mat context instead of Shop context ?
That would also be nice to adapt the Octane light to use the Mat context also in order to unify the workflow.

Cheers
E