Preventing higher level LOP nodes from cooking

   1984   3   0
User Avatar
Member
209 posts
Joined: 11月 2013
オフライン
I've noticed that when inside a Subnet or otl in LOPs, the topmost visualized node (ie: /stage node displaying the visualize flag) will still be evaluated in the Scene Graph Tree and cook, despite the fact that I am one level lower.

Example:
I'm in a subnet that lives at /stage/mysubnet. I start doing work in this subnet (in this case manipulating assets or adding lights etc). Now let's say that at the /stage level there is a node connected to the output of mysubnet, and this node is visualized at the /stage level. Whilst I'm working inside /stage/mysubnet the visualized node one level above will continue to cook.

Is there a way to only evaluate up to and including the node that I am inside? This is largely confusing for artists as they get a lot of unwanted re-cooks for potentially heavy stuff that is downstream of where they are working.
User Avatar
スタッフ
4559 posts
Joined: 7月 2005
オフライン
Have you got a display flag set inside the subnet? If not, then the viewport will show the LOP node in the parent network with its display flag set. Which is very much by design, so you can work inside a subnet without losing track of the effect on the overall scene. But if you set one fo the nodes inside the subnet with a display flag, the viewport should track that node inside the subnet and things outside should not be cooked.
User Avatar
Member
209 posts
Joined: 11月 2013
オフライン
Yes, display flag is set inside.
User Avatar
スタッフ
4559 posts
Joined: 7月 2005
オフライン
As has often been the case for me these days, I cannot reproduce this issue. If you have a reasonably simple hip file that demonstrates the issue, please pass it along (submit a bug if you don't want to post the hip file publicly). And you might also want to check if this only happens with certain dekstop configurations. If so, please pass along the offending desktops as well. Thanks!
  • Quick Links