Projector 0.0.1 Error While Generating Dome "nothing Is Named Parent.use_input", Alternative Techniques Generating A Base For A Mattepainting?

[doublecee]

Hey everybody,

couldn't think about a better nick ... sorry for that.

At the moment I'm trying to use Frank Rueters Projector 0.0.1 (http://www.fxshare.com/nuke/downloads/gizmos/3d/4128.html) in Nuke 4.7v5 to generate a base for a mattepainting. Basically at the end I want a set cards as shown in http://www.fxshare.com/nuke/downloads/gizm...een.php?id=4128 to know, based on a matchmoved camera, which dimensions my final mattepainting will have the be done in.

• I installed Projector.gizmo, createProjectorEnv.tcl and RangeToListSimple.tcl into the plugins directory as needed
• I started Nuke, loaded Projector.gizmo
• I imported a camera *.chan file, which went ok, since it came out of maya I corrected the rotation order from zxy to xyz inside the group of the gizmo for every camera (to open groups use ctrl+enter)
• Now, when I'm ready to generate the dome I get the error msg "Nothing is named parent.use_input"
• I also tried not to import the matchmoved cam directly into the gizmo, instead I generated an independent camera, imported the chan file there and then used this cam as an input for the projector.gizmo --> same error

I checked the gizmo in a text editor and noticed "parent.use_input" has something to do with the switches 2 and 3 but as I'm pretty new to nuke thats just as far as I could go ... any idea how to solve this issue? Frank? Are you reading?

Any help would be appreciated ... maybe anybody has other suggestions for creating a base for a mattepainting based on an already solved camera? I really would love to know alternative workflows.

Best regards ... A nuke n00b!

[user_deleted]

The error pretty much says that there is no knob in the group interface called "use_input" which the Switch nodes should be linked to.
I'll look into it in a moment (haven't used it myself for ages).

[doublecee]

I'm thrilled because of the fast reaction ... thx alot for your time ... as a student I'm really glad to find help on this issue

                      ... still thinking a about a better nick ^\_^

[user_deleted]

no worries. I should probably update the entire thing as a lot of stuff has changed in Nuke's 3D system and this is just old and prone to be unreliable.
Will get back to you in a bit.

[user_deleted]

this is odd. I checked it here and all works well.
which version of nuke are you using?
can you see the "use input" checkbox in the Projector panel?
If so, right click in the panel and go to "Manage User Knobs...". In the list, find the "use input" item and check the actual name of it (it's to the right of the label and should read 'use_input', with an underscore).

If that is the case, go into the group (hit the 'show' button in the Projector panel or use ctrl+enter in the DAG with the node selected). Find the Switch nodes and check the expression inside their switch knob (right click and chose 'Edit/Expression').
They should read 'parent.use_input' and the output value on the right should not be ''.

IF all of the above is correct but you do get an error i those expressions than something is very fishy.

[doublecee]

Hey,

ok, so I tried the Nuke Version 4.7v2 and 4.7v5 under WinXP32 and Vista64 (both OS'es on 2 different machines, a laptop and a workstation) always with the same result. Here I included some screens to show what happens. After I setup'ed everything like described in my initial post the workspace looks like that

http://bouldercrap.com/NukeProjectorProblem01.jpg

(don't worry about the strange graphs at frame 140, gimbal lock problem where the cam flips, solved by setting the rotation order of all cams to xyz)

the script and chan file can be found here
http://bouldercrap.com/ProjectorTest.zip

now I click the 'generate dome' button and get

http://bouldercrap.com/NukeProjectorProblem02.jpg
with a 'more' description of
http://bouldercrap.com/NukeProjectorProblem03.jpg

I checked the "use input" item via 'manage user knobs'
http://bouldercrap.com/NukeProjectorProblem04.jpg

and everything seems to be fine

I also checked the switch node expressions
http://bouldercrap.com/NukeProjectorProblem05.jpg
http://bouldercrap.com/NukeProjectorProblem06.jpg
http://bouldercrap.com/NukeProjectorProblem07.jpg

and the output values were never 'error' ... they are 0 or 1 which seems to be ok

soooooooo, is it the version of Nuke? Maybe I can check it with an old 4.5.14, before TheFoundry Version but only on Windows ... we don't have Linux boxes around at the moment.

...out of ideas

         best regards....me

[user_deleted]

I will look into this when I'm at work. I tried it on linux and nuke 4.8 (beta) yesterday but I wrote this thing almost two ywars ago so it would have been there and working for earlier versions. Anyway, I'll give you a yell soon

[doublecee]

Thx alot, I just hope I'm not wasting anyones time ... could of course also be a user error by me.

... cu

[user_deleted]

naa, that sounds like I screwed up something and was lucky enough to stumble across it myself.