What Does "Render Root" Do?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Frederik De Ble... on 10 Jul, 2018 08:28 PM
When viewing a subnetwork, you view the output of that subnetwork. By clicking "render root" you don't see the output of the subnetwork, but the output of the root network. This might of course be showing that subnetwork, but it doesn't have to.
We expanded on this concept in NodeBox Live with "pinned functions", which are more logical in my opinion.
Support Staff 2 Posted by john on 11 Jul, 2018 06:30 AM
Frederik,
Ah! That would be a *huge* time-saver for me - if it worked. But unless I am still misunderstanding something, it doesn't work for me.
Yes, clicking render root allows me to see the output of the root network whether or not I am currently rendering the subnetwork of interest. If I uncheck render root while viewing the top level network there is no change. But if I uncheck render root from inside a subnetwork I get nothing. I do not see the correct output of that subnetwork. Usually I see nothing at all. Sometimes I get values in the data view, but they're all zeroes.
If tried this on a bunch of different networks with different subnetworks. I've tried rendering different nodes in the network and subnetwork, selecting different nodes, etc. In every case, if render root is not checked I can't see anything useful from inside a subnetwork.
Can you please verify? Is this a bug which no one has noticed till now because no one ever unchecks render root? If this feature did work it would be great.
Thanks,
John