Standard Surface Child Nodes Naming

[rubberchicken]

Adding this material brings in nine child nodes, all called "Octane RGB Colour" and offset from their vertical location in the material node. Can these be named to match the inputs? It would be much easier to see what is going on.

[face_off]

Adding this material brings in nine child nodes, all called "Octane RGB Colour" and offset from their vertical location in the material node. Can these be named to match the inputs? It would be much easier to see what is going on.

Agreed. However this comes back to the question of "how should the plugin name the schematic nodes?". They can either be:

- Named by Octane Node Type (the current system), or
- Named by the parent pin the node is plugged into

I don't think it can be a mix, it needs to be one or the other. I would have thought that knowing the node type would be more important than the pin it's connected to, but I may be wrong. You can also script the renaming of the schematic nodes. Happy to change to option 2 if this is how everyone thinks the plugin should work.

Paul

[Vaughan]

Could it be a Preference that the user could choose?

[face_off]

Could it be a Preference that the user could choose?

I had a deeper dive into this FR. I think the concept of naming the node after the pin that it is plugged into doesn't work as a node can be plugged into multiple pins, all with different pin names.

Thanks

Paul

[rubberchicken]

Thanks for looking into it Paul. I need to start making some node modules setup the way I prefer, that might help. I rename nodes a lot, especially if keying so they can make sense in a pass group.