Oh! Have I been so long in NS land that I’ve forgotten hav the regular Nuke is working. =/
So you’re saying that in a vanilla Nuke with scripts created from scratch, the write node does NOT version up when you save a new version of the .nk…? Merry Christmas Howard! =)) -- Henrik Cednert cto | td | compositor Filmlance International www.filmlance.se > On 23 dec 2016, at 09:43, Howard Jones <[email protected]> wrote: > > Are we talking nukeStudio here? As I haver seen (or would want) that > behaviour in Nuke > > God Jul och Gott Nytt År > > Howard > >> On 23 Dec 2016, at 8:20 am, Henrik Cednert <[email protected]> wrote: >> >> Fancy seeing you here! But… Va mena'ru nuuuu? =) >> >> Not sure what knob and tab you’re referring too here. To clarify, it breaks >> even for simple two node scripts I create from scratch in Nuke. >> >> Add a checkerboard. >> Connect a write, set to /tmp/poop_v001.%06d.dpx >> Save script as SuperPoop_v001.nk >> Version up comp from file menu, script versions up but not the write. >> >> Cheers and meeeeeerry christmas! Don’t forget that ‘dammsugare' is also a >> valid christmas tree decoration! >> >> -- >> Henrik Cednert >> cto | td | compositor >> >> Filmlance International >> www.filmlance.se >> >>> On 23 dec 2016, at 09:14, Simon Björk <[email protected]> wrote: >>> >>> Does the WriteDpx knob in the root settings (Studio tab) use the correct >>> name? >>> >>> Skickat från min iPhone >>> >>>> 23 dec. 2016 kl. 08:54 skrev Henrik Cednert <[email protected]>: >>>> >>>> Hello >>>> >>>> Seeing something so odd here that I have to ask you guys if you’ve seen >>>> the same. I’m on OS X 10.10 up to 10.12. >>>> >>>> On all the systems where I have installed 10.5v1 it looks like the auto >>>> version up of write nodes breaks. I’m talking about when you save a new >>>> comp version from the file manu and how it previously have versioned up >>>> the version number in your write nodes. >>>> >>>> Here it seems like as soon as 10.5 is installed this functionality breaks >>>> for: >>>> * new scripts created in 10.5v1 >>>> * new scripts created in 10.0v4 >>>> >>>> it does however work in OLD scripts created before 10.5 was installed. >>>> >>>> yeah i know, sounds impossible and extremely odd. But it’s the only >>>> conclusion i’ve been able to come to after investigating it. >>>> >>>> have anyone else seen this behavior? >>>> >>>> Cheers and thanks >>>> >>>> -- >>>> Henrik Cednert >>>> cto | td | compositor >>>> >>>> Filmlance International >>>> www.filmlance.se >>>> >>>> _______________________________________________ >>>> Nuke-users mailing list >>>> [email protected], http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> _______________________________________________ >>> Nuke-users mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > -- > > > > *A X I S V F X* > > The Bottle Yard Studios > > Whitchurch Lane > > Bristol BS14 0BH > > > > axis-vfx.com > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
