Hmm just sent through the gizmo, i don't actually know if attachments are llowed on this mailing list..? or dumb question?

-------- Original Message --------
Subject:        Re: [Nuke-users] Gizmo Crashes on loadup
Date:   Fri, 07 Mar 2014 11:22:49 +0000
From:   Neil Rögnvaldr Scholes <[email protected]>
Reply-To:       Nuke user discussion <[email protected]>
Organisation:   Ultraviolet
To:     Nuke user discussion <[email protected]>



Hi yes it does funnily enough ...:)

Ive also attached the gizmo for any thoughts...
It is using another 3D Equalizer Lens Distortion plugin (.so) created by Science D Visions, so ive attached this as well so it will hopefully work on your station.

So, on a few nodes im referencing an input camera using the 'topnode' expression:
*
**[topnode parent.input1].vaperture*

An others to this effect.

I wondered if this referencing to inputs might be the problem, so i also used this expression on the disable parameters:

*[exists parent.input1]==0?1:0*

So basically to make sure the culprit nodes are disabled until the input is hooked up to a camera.

Well it had no effect. So perhaps it is because it has another plugin wrapped up inside...? I'm pretty sure your allowed to do this with gizmos...

By the way the 3DEqualizer plug-in needs no licensing ( i don't think) obviously i have 3D Equalizer installed.

Anyway - any thoughts would be most appreciated.

Many Thanks


N



Neil Rögnvaldr Scholes

www.neilscholes.com

On 07/03/14 06:50, Srinivasan C.C wrote:

Did your gizmo having any expression are py scripts inside referring to any particular inputs?

On 07-Mar-2014 1:24 am, "Neil Rögnvaldr Scholes" <[email protected] <mailto:[email protected]>> wrote:

    Â Hi

    I'm building a gizmo that crashes Nuke when i load it, and i
    cannot work out why....:(

    If i have the viewer connected to something, say a read node or a
    dot or anything, then select the read node and apply the gizmo -
    i'm fine all loads fine.

    BUT if I load the gizmo without anything selected, (and the viewer
    connected) or in other words just bring it into the node graph
    unconnected to anything - then BOOM - Nuke crashes.

    I think its related to not having the viewer connected......

    Can anyone suggest any cause here? Any thoughts most appreciated.

    Thanks

    N

-- Neil Rögnvaldr Scholes

    www.neilscholes.com <http://www.neilscholes.com>

    _______________________________________________
    Nuke-users mailing list
    [email protected]
    <mailto:[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

Reply via email to