nuke6.2v3 ends up complaining for us as Viktor describes: "ERROR: "... on the
first frame on the farm, but you can render it interactively. Interactively,
the script loads with the errors, but they seem to be ignorable. That's why I
was wondering if there's some reload command that will reload a script like you
might reload a python module. I think it's due to the tcl expression we have in
a read's file knob which is inside a gizmo.
nuke6.2v1 doesn't complain (does that mean it worked, or the ERROR just wasn't
displayed?).
Someone posted earlier about using tcl instead of python in expressions. So I
changed the expression I was using in a file knob of a read node from:
read['file'].setValue("[python {nuke.thisParent()['%s'].value()}]" %
parentFileKnob.name())
to:
read['file'].setValue("[value parent.%s]" % parentFileKnob.name())
That's when everything started to blow up. I discovered after changing it, that
while it technically worked, the rest of the node didn't (first and last frames
were ignored, left and right eye error when there shouldn't be and other
issues). Changing the expression back to python took care of the wacky errors.
The python expression seems to work in both 6.2v1 and 6.2v3. Is python doing
some sort of active evals while tcl is 'lazier'? Seems really weird (like a lot
of things...).
Viktor, while our situations are different, the disease seems to be the same.
Have you tried using a python style expression for what you are doing?
cheers
JRAB
On May 18, 2011, at 11:45 PM, John RA Benson wrote:
> hey there -
> this makes me wonder - is there a way to force reloading the script?
>
> I've seen this with some of our gizmos that are built at launch, where the
> nodes that depend on them error because (i'm guessing) the gizmo is still
> building itself after the node that depends on it is created. Once the script
> is fully built, everything is ok. There might still be errors in the gui, but
> viewing the bottom of the tree makes them un-errored because the script
> evaluates and all nodes end up in a stable state.
>
> I think it might be handy to be able to pull all the errors out with a reload
> sort of function (for non gui or rendering situations) so frame 1 wouldn't be
> the guinea pig? is that possible? I've been seeing it with 6.2v3, which fixed
> the problem in interactive From 6.2v1, but it still shows up in rendering.
>
> thanks
> jrab
>
>
>
>
> On May 18, 2011, at 17:13, Deke Kincaid <[email protected]> wrote:
>
>> There have been 4 bug updates to the 6.1 train. You should try
>> updating to 6.1v5 and see if that fixes it.
>>
>> -deke
>>
>> On Wed, May 18, 2011 at 04:35, Viktor Daniels <[email protected]>
>> wrote:
>>> Hello everyone, I'm experience problem with Expression node, on script
>>> loading Nuke shows error "ERROR: mychanname.temp_expr0: Nothing is
>>> named 'Mask1.red'" and then the scripts works fine. I can live with
>>> that when working on my workststion, but when i trying to render
>>> scripts with expression on my server it renders with skipping
>>> expression node in first frame, any other frames except first one
>>> rendered with no error. Any suggestions how to fix it? Nuke 6.1v1
>>>
>>> Sent from my iPhone
>>> _______________________________________________
>>> 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
