Hi ! I've tested lot of stuff yesterday to find a solution, because in our studio we are using a lot of FBX file loaded in Axis node, and the same popup message don't allow me to script automation for changing FBX file from shot to another easily.
I came with a little hacky solution, tested only with Axis node loaded with FBX file, so I hope this will also work for you guys with Camera node ;) https://gist.github.com/maty974/c076ff829063f70db3d9 On Wed, Jun 10, 2015 at 11:32 PM, Aurélyen Daudet <[email protected]> wrote: > Hi, > > I've searched, but had no luck, to use nuke.tcl('tcl code') and try to > execute the reload button using TCL code, > instead of Python code. I was hoping that the prompt would not pop, as the > TCL is more low level than Python for Nuke. > As the 'reload' button is a TCL script button, I hoped it would work. But > it seems that it's not possible to run a script button with TCL. > D'oooh... (Seems odd enough to make me think I missed something...) > The trick using version knob that seems to work with the file knob of Read > does not seem to work for camera and FBX. > (Did not try with abc files though) > > I'll be glad to hear a solution to the prompt issue. > (And if there is any, a solution to use tcl to run Script Button) > > Cheers. > > > > > > > -- > Aurélyen DAUDET - Enseignant Nuke et Compositing > [email protected] - www.artfx.fr - blog.artfx.fr > > > > On 10 June 2015 at 15:13, Jake Richards <[email protected]> wrote: > >> I guess my issue is a little different than the original issue. For what >> I'm attempting to do is look at all the camera's in the nuke script and see >> if the file they are reading is out dated. So, if my camera is reading >> data from alembic1.abc but I need to update it to alembic2.abc, I get the >> popup message. So, it's not really an issue of changing mount points, I >> want to update the camera in place with a script without having human >> interaction. Sorry if I wasn't clear! My hope is that there would be some >> way to update the read from file without the prompt, something like: >> >> camera2['file'].setValue("alembic2.abc") >> camera2['reload'].execute(dontPromptMe=True) >> >> >> ------------------------------ >> >> *From: *"Erwan Leroy" <[email protected]> >> *To: *"Nuke Python discussion" <[email protected]> >> *Sent: *Tuesday, June 9, 2015 8:54:43 PM >> *Subject: *Re: [Nuke-python] Updating file paths for cameras/axis >> >> >> If it's solely to migrate the script to a different system, I would >> probably try to handle that with a filenamefilter if a simple setValue >> doesn't do the trick. >> Also if you're loading in the same camera, it shouldn't change anything >> if you do destroy the animation, as it will reload the same. Unless you >> modified it, in which case you probably want to turn read from file off. >> On 10 Jun 2015 02:19, "Jake Richards" <[email protected]> wrote: >> >>> I'd be interested to know this as well. The closest I can get is to >>> hide the properties panel and then update the knobs, but the camera doesn't >>> re-read the new file. I've tried executing the reload button and also >>> deleting any animation on the other knobs first but can't get it to update >>> without the prompt. >>> >>> Jake >>> >>> >>> ------------------------------ >>> >>> *From: *"Simon Björk" <[email protected]> >>> *To: *"Nuke Python discussion" <[email protected]> >>> *Sent: *Tuesday, June 9, 2015 9:13:59 AM >>> *Subject: *[Nuke-python] Updating file paths for cameras/axis >>> >>> Is there a way to update the file path of a camera without getting the >>> "Destroy animation" dialog? >>> >>> I know I can create a new camera with nuke.createNode('Camera', 'file >>> {%s}'% path), but I only need to update the file path (moving to a >>> different system). I guess I could create a new node and reconnect/copy >>> knob values but it seems there should be a better way. >>> >>> >>> ------------------------------- >>> Simon Björk >>> Compositor/TD >>> >>> +46 (0)70-2859503 >>> www.bjorkvisuals.com >>> >>> _______________________________________________ >>> Nuke-python mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >>> >>> >>> _______________________________________________ >>> Nuke-python mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >>> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > -- Matthieu Cadet Compositor Artist & TD, nWave Digital [email protected]
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
