Hi,
I am testing the Deadline after refactor together with Nuke.
Previous versions didn’t delete the work area rendered files after publish. This allowed artists to have easy access to the latest render; very convenient. I am trying to setup Ayon to not cleanup the files.
The collect_rendered_files in ayon-core flags files for cleanup if there is no persistent staging dir.
I set the nuke
ayon+settings://core/tools/publish/custom_staging_dir_profiles
and made a template in anatomy
This seems do do the trick, but is the best practice?
Thank you
That was a very long time ago though, right? Or was that, for Nuke, only after recent updates?
I believe using Custom Staging Dir is currently the only way to force disable the deletion. Nonetheless, I still feel we should have the ability to disable the deletion of rendered outputs without requiring to use custom staging dirs.
@antirotor thoughts?
My bundle from November didn’t require persistent staging. That is ancient by Ayon standards, but not that far production wise…
Thank you for confirming
Any chance you can provide me the different versions you were using in that bundle at the time, in particular core, deadline and nuke?
Sure, here it is: core 1.0.11, deadline 0.3.2, nuke 0.2.6
Thank you @BigRoy, looks gr8, will try!
1 Like
