Q100294: Directory location for Nuke Studio and Hiero export presets

Follow

SUMMARY

This article shows where to find your Nuke Studio and Hiero export presets. 

MORE INFORMATION

Your default and custom export presets used in Nuke Studio or Hiero export window, can be located in your .nuke folder. More information on your .nuke folder can be found here: Q100048: Nuke Directory Locations
 
The export presents will be found in the TaskPresets directory which can be accessed under \.nuke\TaskPresets\
 
Unless you've selected the 'Save all Local Presets to disk' option in the export window, the TaskPresets directory would not exist by default. To create it you can either:
  • use the 'Save all Local Presets to disk' option in the export window
  • make changes to a default export preset and save the custom version to disk
  • create a preset from scratch
In the latest Nuke releases you will now see two directories, one for export presets used prior to Nuke 10.5v1 and one directory for presets created after Nuke 10.5v1. They will look as follows:

Directory for export presets prior to Nuke 10.5v1: \.nuke\TaskPresets\Processors\
Directory for export preset post Nuke 10.5v1: \.nuke\TaskPresets\10.5\Processors\

Inside these folders will be 3 more directories, which contain the export presets for the different Process types in Nuke Studio and Hiero. From within these directories you can find the export preset you wish to copy, edit, move etc.
 
 
Upgrading Nuke versions

Upgrading from a release of Nuke Studio/Hiero prior to 10.5 will not carry over your export presets by default. In this instance you will need to copy the presets from the following directory structure:

\.nuke\TaskPresets\Processors\ to \.nuke\TaskPresets\10.5\Processors\ 

to access them in 10.5v1. 

NOTE: Some users have experienced issues with the old export presets copied into the 10.5 version of Nuke Studio and Hiero and if you find this to be the case, then we recommend you delete the preset and recreate it from within Nuke Studio/Hiero 10.5v1.
 
 
Was this article helpful?
0 out of 0 found this helpful

Comments