LOL Thanks Marty but the versioning is really not the issue here! :) Even if I save hundreds of different versions the problem is still there. Just by copying the roto node I'm getting the keyframes problem I've described earlier. A workaround that seems to be working so far would be to convert the bsplines into bezier curves.
On 2013-02-06, at 2:09 PM, Marty Blumen wrote: > the classic work around is always version up when saving. Use _v001 in your > file name, that uses the in-built versioning system; It's in the file menu as > 'save a new version' > > Sent from iEarth > > > On 7/02/2013, at 3:08, Philippe Roberge <[email protected]> wrote: > >> I spent a whole day rotoscoping a running wolf and I encountered several >> bugs with the "Roto" node… >> >> - Sometimes, after your roto is all done, some points decide to go to the >> 0,0 position >> - When you do a "ctrl-z", the "undo" is applied BUT random keyframes are >> adde throughout the shot. >> - NOW THE MOST FRUSTRATING… I was all done, everything was working, I >> saved, sent it to render farm and left. When I came back this morning and >> loaded the same script, several shapes were out of place and/or had >> different keyframes!!! Now, I have to completely redo these shapes! >> >> Anybody got these *&#?$ bugs and/or have a workaround?! >> >> -- >> Philippe Roberge >> >> Senior Compositor >> Mokko Studio >> >> _______________________________________________ >> 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
