Nuke - Proxy() mode check in submission code

Deadline
1

Hi,
If you leave the global proxy mode switched ON (Ctrl+p in Nuke) and submit to Deadline and your render nodes have a custom path location for their “global temp caching” then Deadline-Nuke jobs fail!
Please could we add a submission check to halt submission within Nuke/Monitor if this situation occurs?
Thanks,
Mike

2

That’s a +1 from me too. It’s probably the most annoying (but small) thing about Deadline and Nuke at the moment.

3

Hey guys,

Are you just looking for a warning when submitting when Proxy Mode is enabled, or is it more in depth than that? I’m not sure where this “global temp caching” path is set for the nodes, so if this is a property we need to check as well, can you provide more information on where this property is set?

Thanks!

  • Ryan
4

Hi Ryan,
I’ve done some research and we just need to make sure it is turned off during submission either from within the Nuke submission script interface or the deadline monitor submission interface. I also checked to see if leaving ROI (Region of Interest) enabled caused problems as well, but it works fine :slight_smile:

Proxy mode specified by a knob on the root node. You can access it like this in Python:

rootNode = nuke.root()
isProxy = rootNode[‘proxy’].value()
rootNode[‘proxy’].setValue(False)

or via TCL:

[python {some python code}]
so, for example,
set x [python {nuke.root()[‘proxy’].value() }]
python {nuke.root()[‘proxy’].setValue(False) }

or natively in TCL:

to get:
value root.proxy
to set:
knob root.proxy 1

Thanks,
Mike

5

Thanks for the info Mike!