You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 11 Next »

    Step by step instructions for submitting Nuke jobs with Qube!

    Step 1 (First Time Only)

    Run WranglerView and go to the Install App UI menu item (File -> Install App UI) as shown.

    Choose "Install Nuke (loadOnce) App UI..." This requires that Python be installed on any Worker that runs a Nuke job. If Python is not installed, please see Installing Python.

    If you can't or don't want to install Python, then choose "Install Nuke (cmdline) App UI..." instead.

    Step 2


    Once installed you should be able to locate the "Qube!" menu in Nuke's "Render" menu.


    Step 3

    With a script loaded in Nuke you can choose to render the entire script, or just the selected write node(s), as either "Render All...(cmdline)" or "Render All...(loadOnce)" depending on your requirements.

    loadOnce vs cmdline


    What's the difference?

    loadOnce will open a copy (instance) of Nuke on the Worker that picks up the job, and that instance will render frames as assigned by the Supervisor. Since the scene file is only being opened one time, this can be faster to generate the full sequence.

    cmdline will use the command line to open a new instance of the Nuke file for each frame that it renders. Although this can be slower for large scenes, it can also be more flexible in large, complex environments.

    This will present a pre filled submission UI. Ensure sections marked in red have the correct details.

    Useful Settings


    While not strictly required, the following settings are useful for getting a better result. You will need to turn on "Expert Mode" (check box at the bottom of the submission UI) in order to get access to them.

    • Optimize the use of cores. Set the "Slots = Threads" checkbox and then set the "Specific Thread Count" to a value like 8 (assuming you have 8 cores). (If you have Designer licenses, only set the thread count. Do not check "Slots = Threads")
    • By default, Qube! will not retry failed frames. So set the "Retry frame/instance" value to 3 or 5, to get 3 or 5 retries before it gives up. Related to that, the default wait between retries is zero seconds, which is typically not useful. Set the "Retry Work Delay" to a value like 5 or 10 to allow machines time to recover from temporary problems such as network errors.
    • Make sure that the Nuke version and the OS are set correctly for the Worker(s) that will execute the job.
    • Because the path to the Nuke executable is part of the submission parameters, it is not possible to mix OSs with Nuke jobs - that is, although you can submit from, say, Windows to OS X, you cannot submit to both Windows and OS X at the same time.



    Step 4

    Click "Submit"

    For further details on the submission UI see below.


    If you find you are getting errors here are some useful links for troubleshooting

    Troubleshooting Flowcharts 


    Job Submission Details


    Not all sections need to be filled in in order to render only the fields marked in red are required


     Primary parameters

    Nuke Version

    Tooltip - Select version numbers and the worker platform to make an educated guess at where the Nuke executable is found on the remote worker.


    Use the spinners to enter the required version of nuke

    Nuke path

    Tooltip - explicit path to Nuke executable


    Browse or enter manually the location of Nuke executable on the workers

    Important : Always double check the location of the workers executable. Be aware that if you are submitting cross platform the path will be different.

    load NukeX

    Tooltip - load NukeX




    Tooltip - nuke script to execute


    Browse or enter manually the location of the nuke file to be rendered. This is a required field for submission

    Important: Best practise is to ensure the nuke file and all of its dependant files such as textures are on network storage accessible by the workers.

     Render Nodes and Script Args

    execute views

    Tooltip - only execute these views (comma-separated list: e.g. 'left,right'


    list comma separated views to render. These are named in your nuke script

    execute nodes

    Tooltip - execute only this node


    Execute on the specified node. These are named in your nuke script

    script args

    Tooltip - All words between the script name and the frame ranges can be used by [argv n] expressions to provide changing arguments to the script. Each must start with a non-digit to avoid confusion with frame ranges.


    Explanation and example needed

     Optional Switches


    Tooltip - formats default to anamorphic


    Tick box to override scene anamorphic settings

    cache size

    Tooltip - limit cache memory usage. Size is in bytes, or append k, M, G or T


    Enter the numeric value to override scene cache size settings


    Tooltip - with -x or -t use interactive, not render, license


    Tick box to override scene interactive settings

    linear transfer

    Tooltip - apply linear transfer to the file read in


    Tick box to override scene linear transfer settings


    Tooltip - set threads to n


    Enter the numeric value to override scene threads settings

    proxy mode

    Tooltip - turn on proxy mode


    Tick box to override scene proxy mode settings


    Tooltip - quiet (do not print stuff)


    Tick box to override scene quiet settings

    stack size

    Tooltip - sets the minimum stack size for each thread in bytes, this defaults to 16777216 (16MB) the smallest allowed value is 1048576 (1MB)


    explanation needed


    Tooltip - verbosity (print more stuff)


    Choose the level of detail you would like the logs to provide

    • No labels