my whole setup is a bit heavy to copy but the principle is simple :
in my gizmo, some attributes are looking for infos in the metadata,
exemple focal length.
as it is to apply corrections to a shoot, the value may change each frame.
but all of that wouldn't make a difference if it was keyframs anyway
then i have in my gizmo a file with a path full of variables calling
those attributes
ex: mypath/[value parent.focal].jpg
this work in the gui but the render is using only the latest path loaded
when the render was kicked, so if the focal change on a frame it does't
care and still use the wrong file.
I have been told that it is not possible for nuke to refresh that in its
renders (I hope it is wrong), and I would have to iterate all the frame
and create some temp file like 1 nuke script per frame with the good
values baked in...
but I am not sure how to do it and I keep thinking if it can bake those
file it should be able to render those expressions...
I don't know the forceValidate it didn't seems to work but I may have
try it wrong.
thx
Olivier
Nathan Rusch wrote:
The first thing that comes to mind is forceValidate, but I may be
misunderstanding your issue. Can you send an example of the setup you're using?
Nathan
On May 8, 2012, at 3:45 AM, olivier...@moving-picture.com wrote:
anybody know how to force nuke to re evaluate all the expressions in the script
?
I can maybe use that in the render option if nobody has an other idea.
cheers
Olivier
olivier...@moving-picture.com wrote:
Hiya,
I have a couple of expressions :
in a few knobs some expressions looking at the metadata to get some values,
then in a read node an expression in the path to feed those values as the name
of the path.
everything is fine in nuke (even if the refresh is not refreshing the new file
until i look something else and get back to it... ideas welcome)
but when I render the file is the last path loaded, it doesn't refresh it at
all.
Is there anything I can do to force nuke to re evaluate the expressions and
refresh the file for each frame during the render ?
maybe something to add in the tab Python 'before each frame' ??
cheers
Olivier
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
