![]() Prepare OFX Cache Before Rendering: If enabled, Deadline will try to create the temporary ofxplugincache folder before rendering, which helps ensure that comps that use OFX plugins render properly.Įnable Path Mapping: If enabled, a temporary Nuke file will be created locally on the Worker for rendering because Deadline does the path mapping directly in the Nuke file. Use a, to separate multiple Worker names, for example: worker001,worker002,worker003 Workers To Use Interactive License: A list of Workers that should use an interactive Nuke license instead of a render license. Multiple exe paths can still be declared and the first one that is found on a Worker will be used from the exe list. We don’t directly support ’s of Nuke, but rather just the first two levels MAJOR.MINOR and leave the specific REVISION to a studio to control. If you wish to run a particular REVISION of Nuke then you will need to change the actual exe path under 9.0v1 to actually point at say, the 9.0v8 version. Note that the versions supported are the MAJOR.MINOR (9.0 or 9.1) versions of Nuke. Different executable paths can be configured for each version installed on your render nodes. Enter alternative paths on separate lines. Nuke Executable: The path to the Nuke executable file used for rendering. While in super user mode, select Tools -> Configure Plugins and select the Nuke plug-in from the list on the left. You can configure the Nuke plug-in settings from the Monitor. Since Quicktime generation only uses a single thread, you can get much better throughput with this option on multi-core machines. You can enable this option, and bump up the Concurrent Tasks value toĪllow machines to process multiple write nodes concurrently. The Submit Each Write Node As A Separate Task option can be useful if you have a bunch of write nodes in a Nuke script to output different Quicktime movies. Only Simulate Eddy Nodes: If enabled, only the Eddy Nodes will be simulated. Only Render Precomp Nodes: If enabled, only the Write nodes that are in precomp nodes will be rendered. ![]() ![]() Render Precomp Nodes First: If enabled, all write nodes in precomp nodes will be rendered before the main job. Nodes With ‘Read File’ Enabled Only: If enabled, only the Write nodes that have the ‘Read File’ option enabled will be rendered. Selected Nodes Only: If enabled, only the selected Write nodes will be rendered. Submit Write Nodes As Separate Tasks For The Same Job: Enable to submit a job where each task for the job represents a different write node, and all frames for that write node are rendered by its corresponding task. Set Dependencies Based on Write Node Render Order: When submitting write nodes as separate jobs, this option will make the separate jobs dependent on each other based on write node render order. Use Node’s Frame List: If submitting each write node as a separate job or task, enable this to pull the frame range from the write node, instead of using the global frame range. Submit Write Nodes As Separate Jobs: Each write node is submitted as a separate job. Render Mode: Use scene settings, the proxy file paths, or force Nuke to use full resolution when rendering.Ĭhoose Views To Render: Enable this option to choose which view(s) to render. XML Directory: If Use Performance Profiler is enabled, this is the directory on the network where the performance profile xml files will be saved. Use Performance Profiler: If enabled, Nuke will profile the performance of the Nuke script while rendering and create a xml file per task for later analysis (Nuke 9 and later only). This can add overhead, but ensures that Nuke’s memory is flushed between tasks. Reload Plugin Between Tasks: If enabled, Nuke will be restarted between tasks. Set to 0 to not enforce a minimum stack size.Ĭontinue On Error: If enabled, Nuke will attempt to keep rendering if an error occurs. Minimum Stack Size: The minimum stack size (in MB) to be used for rendering. Maximum RAM Usage: The maximum RAM usage (in MB) to be used for rendering.Įnforce Write Node Render Order: Forces Nuke to obey the render order of Write nodes. Use Specific GPU Override: If Nuke should use the specified GPU, otherwise the Workers GPU Affinity will be used ( Nuke 8 and later only ). Use The GPU For Rendering: If Nuke should also use the GPU for rendering (Nuke 7 and later only). Render Threads: The number of threads to use for rendering. Use Batch Mode: If enabled, Deadline will keep the Nuke file loaded in memory between tasks. Render With NukeX: Enable this option if you want to render with NukeX instead of Nuke. The general Deadline options are explained in the Job Submission documentation, and the Draft/Integration options are explained in the Draft and Integration documentation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |