Edit context options not updating evaluated fields?

   803   5   0
User Avatar
Member
16 posts
Joined: Feb. 2016
Offline
We use context options to manage render versions, output paths etc. We can access these options through expressions such as `@task`, `@render_version`, but the edit context options node doesn't seem to update any of the evaluated expressions in the nodes, only variables in the stage (i.e. render products). Is there any way to fix this or a workaround?

Thanks
User Avatar
Staff
4525 posts
Joined: July 2005
Offline
If a context option is defined at the global level (Edit->Context Options dialog), then parm dialogs will _always_ show the value of an expression evaluated with that global value. Edit Context Options nodes only modify the context option value for the duration of one cook request. If the context option is not defined at the global level, then nodes will recook, and the parm dialog should evaluate expressions using the value for the context option that was last used to cook the node (this is how you can inspect a LOP node inside a For Each loop without it recooking or complaining about an unknown context option value). You can also see these "last cooked context option values" as text badges in the network editor, which can be very handy.
User Avatar
Member
16 posts
Joined: Feb. 2016
Offline
Thanks! How are context options not defined at a global level? I've been having trouble finding this information.
User Avatar
Staff
4525 posts
Joined: July 2005
Offline
Elliot Stronge
How are context options not defined at a global level?

I'm not sure how to answer this questions... If you don't explicitly define them at the global level (Edit->Context Options dialog), then they are not defined at the global level, and so may only exist in parts of your LOP Network.
User Avatar
Member
16 posts
Joined: Feb. 2016
Offline
Sorry I should elaborate, I can't figure out how to define them in a LOP network. Edit Context Options doesn't create them, the only way I can create context options is through the Context Options Editor. The documentation is frustratingly sparse on this.
User Avatar
Staff
4525 posts
Joined: July 2005
Offline
The Edit Context Options LOP does create context options, but only in the "context" of cooking that LOP node (and the inputs to that LOP node). So you can only read context options created by an edit context options LOP on expressions on LOP nodes connected (directly or indirectly) to the input of the Edit Context Options LOP. Can you attach a hip file that shows the problem you're seeing with Edit Context Option LOP not working as you expect?
  • Quick Links