Loic Le Goff

I know that's how it works but in this case, I would have hoped it would use the already promoted, named AND connected ports from the output node to also rename the subnet output because in the end, my nodes are still promoted to an output, it's just the subnet output instead or the main graph output.
That would help a lot with readability but that's the way it is. I've opened a feature request ticket.

Moving on from this, you're suggesting I need to rename the output of my last node being packed before packing? I haven't found a node that allows me to just rename ports though. It's doable manually so I assume there must be a node to do this as well.

Anyone know what node this would be?

Hello,

I've noticed that when I promote ports (inputs and outputs) they appear on the input and output nodes with the correct names fed into the graph::PromotePort nodes.
When I graph::PackSubnet my nodes, the subnet inputs are still named properly but then my subnet outputs don't carry the named ports when the main graph output node does...

I can't find a way to have those named properly.
Any suggestion?

Cheers,

Thx for the update!

I think I get it now, I thought about doing this way but my worry was to have a duplicated setup simply to get static values but it's not actually duplicated since one is in the APEX script so it's not actually creating the final rig nodes, it's just doing a static set of operations during the 'component build'.

Because I currently do it via nodes, I keep on forgetting that it is still nodes scripting and not actually the final graph.