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

    Compare with Current View Page History

    « Previous Version 4 Next »

    Below are instructions on your first steps submitting Nuke jobs with Qube!

    Step 1 (First Time Only)

    The Nuke Jobtype comes with the standard install of Qube! and does not require a specific jobtype to be installed 

    InApp Installation:

    File > Install App UI > Install Nuke (loadOnce) App UI...

    Step 2

    Once installed you should be able to locate the "Qube!" menu in Nuke

    InApp Location:

    File > Render > Qube >

    Step 3

    With a script loaded in Nuke choose "Render All...(cmdline)" or "Render...(loadOnce)" depending on your requirements

    This will present a pre filled submission UI


    Step 4

    Ensure sections marked in red have the correct details

    Click submit

    For further details on the submission UI look in the right panel


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

    Troubleshooting Flowcharts 

    Below Is an expandable view of the "Nuke (loadOnce) Job..." Jobtype Submission UI


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

    Please click on the text below the section of interest


     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 seperated 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)


    explaination needed


    Tooltip - verbosity (print more stuff)


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

    • No labels