Hi! This is what you're looking for. Look at the tabs on the write node and invoke this pre-render (you can populate it by default facility wide in your menu.py).
http://www.nukepedia.com/python/render/checkoutputpath On Thu, Nov 27, 2014 at 9:36 AM, Elias Ericsson Rydberg < elias.ericsson.rydb...@gmail.com> wrote: > I haven't tried studio, but could you not write a a preRenderScript? Check > if the path exists, otherwise create it. > Den 27 nov 2014 17:21 skrev "Mads Lund" <madshl...@gmail.com>: > >> Hey guys. >> >> Nuke write nodes does not create folders by default. While its nice that >> in Nuke 9 it will bump the path folders to the same as the script version, >> it still doesn't create those folders, forcing the artists to create them >> by hand. (introducing human errors and what not) >> >> Back when we were doing our pipeline tools our selves directly inside >> Nuke, we would just make a custom write node that dealt with that. However >> Nuke Studio does not have a option to modify the write node. And there >> doesn't seem to be any build-in python calls to modify existing nuke >> scripts. >> >> So i am wondering how you guys are making sure that Nuke will create the >> folders needed every time your artists bump up the version number. And make >> sure that Nuke Studio don't get stuck because a render folder does not >> exist. >> >> >> >> _______________________________________________ >> Nuke-users mailing list >> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
