Hasta La Motion!

Is there any reason why using a PreComp node within a gizmo might lead to undesired results? We have been trialing the use of the PreComp node to reference scripts that contain nodes that require occasional updates.

When the node tree is used in a group it works correctly, but when used as a gizmo the PreComp node forces parts of the node tree to be disconnected and re-wired on save & reopen. If I remove the PreComp node from the gizmo it’s all ok.

Drew

Are there any nodes or combination of nodes from which I could derive this or is this something that I would have to do with NDK?

I’m using a TCl-Expression (in the file-parameter) to build dynamic folder-names in write-nodes.
for example:

/sh020/versions/v[string trimleft [lindex [split [string trim [file tail [value root.name]] .nk] _] 1] v]/[string trim [file tail [value root.name]] .nk].%04d.jpg

I’d now like to parse this expression and have it return the proper string. I tried nuke.tcl(). It does parse the expression correctly, but somehow assumes, i wanna run the result as a command and returns this error:

RuntimeError: sh020_v00_sys.nk: Unknown command

sh020_v00_sys.nk is the resulting string but i can’t explain the runtimeerror.

If someone has an idea, i’d greatly appreciate it 🙂

cheers,
sean

I’m trying to work with some 3D imported geometry in NUKE and my viewer keeps cutting the geometry out..

now I remember that in older versions of NUKE there was a 3D tab in Project Settings were you would adjust the NEAR and FAR planes.. but its not there any more in NUKE 6.2 and I can’t find it anywhere else.. maybe somebody can give me a hint..?