CardtoTrack v8.0

This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Alexey Kuchinski & Helge Stang
Finding position in 3D space based on Geometry,World position pass, Deep or manual method. Reconcile 3D position to CornerPin, Transform and Roto nodes.
13.1, 13.0, 12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11 or later
Linux, Mac, Windows
22 Jan 2022

how to: (a bit outdated but you will get an idea)



  • New features:
    • Nuke 13 ready
    • The default calculation length is now taken from Camera first and last animated frames.
    • moved all python code to separated .py file (please add it to your plugin directory as well)
    • important - i had limited time to test it, so will be glad to.
    • 'knobChange' callbacks moved inside of the group to avoid trigering. 


  • New features:
    • Possible to export transform node only 
    • Transform node is replaced with Tproject gizmo in similar to Cproject.
    • Possible to choose which which nodes you would like to ceate
  • Fixed Bugs:
    • If user was standing on frame outside of the comp frame range, error was risen since tool was trying to use this frame as a ref frame, now first frame of animation will be used instead



  • New features:
    • CardToTrack Gizmo - Highpass mode added to Stabilize mode
    • CProject Gizmo - added option to manually set reference frame
  • Fixed Bugs:
    • If Camera had no animation error was risen
    • If pixel aspect ration was not 1 wrong resolution was output from CProject


  • CProject Gizmo added option to Soft/Hard crop or not crop at all, default is hard crop(concatenation preserved). In previous version concatenation was broken by crop.
  • BUG fixed, in Geometry and Card modes there was mossing Wireframe preview.


  • added possibility to calculate from Axis or chain of Axises *
  • added possibility to calculate from Deep *
  • UI changes to provide more user friendly experience*
  • Default frame range is taken from Camera animation and not from project frame range
  • Some stability improvements(hope no new bugs introduced)

*Calculation from an Axis: Many times we provided with an animated Axis, in previous version i was copying values from an Axis to the card and calculating, the problem is that if by default an axis had unfortunate rotation like 90 degrees to the camera it was imposible to adjust it. With and Axis option you can connect few Axises together and Card to track will calculate the animation from the workd matrix of the Axis you connected to with CardToTrack.(Supports animated Axises)

*Calculation from Deep: Connect your Deep footage to the Extra input. (The position sampled on the reference frame and can not be animated)

*UI changes: Knob Groups are presented only if they are relevant.

 Thanks to Adrian Pueyo for support!


Extract files into your plugin directory.

Paste those lines to your please:

r.addCommand('CardToTrack gizmo', 'nuke.createNode(\'CardToTrack\')',icon='my.png')




Older versions:


  • fixed broken connection in CardToTrack Gizmo


  • scene size added
  • grid hue/opacity added
  • stabilization function added
  • improved estimation for card passing the Camera origin
  • CProject Gizmo reworked
  • BUG fixes(and probably few new added :))



          added aditional input to the Gizmo 'Extra' and pulldown choice:

  1. Geometry - if you have a Geometry of the scene you can pick the exact position in one click
  2. Wpos pass - if you have a World position pass you can pick the exact position in one click. (it has to match Nuke World xyz, shuffled to 'rgb')
  3. Card - now it is possible to connect external Card to the gizmo and run the calculation (supports animated and static cards)

          fixed BUG causing colorization of the viewer if the scene is huge

          grid look is changed, added Green external grid to mark the position in huge scene, the size of the card is the size of the white grid with the magenta center

          CardToTrack command is sitting now in the Gizmo itself and there no need to inport it separately


          now compatible to Nuke9.08 and higher

          help and tooltips added

          grid color adjustment added


           fixed Roto animation update, thanks Magno!


           fixed CardToTrack gizmo error, thanks Mike!


CardToTrack command(not exist anymore as a separated command and included in the gizmo it self v6.5)

allows you to extract 2D tracking data from position of your card in 3D space of Nuke, it use Reconcile3D as a basis but in addition to 2d position you will have also rotation and scale.As a result you can have a CornerPin, CornerPin(extra matrix), tracked Roto node(extra_matrix). You can extract from static and moving cards. Can be used within CardToTrack gizmo or standalone.

CardTroTrack gizmo

helps you to find position of the object in 3D space and including CardToTrack command as well.

CProject gizmo - replacing CornerPin, added more user friendly interface

V 06.0

1 huge improvement in a speed, you will get the calculation almost instantly (thanks to Helge Stang) 

2 including CardToTrack group for easy finding position in 3D space

3 new node created instead of the CornerPin (CProject), with additional features. if CProject is not installed - a CornerPin will be generated.


Known BUG v6.00, fixed in v6.03:

Right after creation of Roto you have to click on the Root layer of freshly created Roto node, so something will be update there and it will remember the animation. Working on solving the problem.


Do not cross the Camera origin, calculation will fail in this case, to avoid - keep your card small. In the end result it is not important how big your card was.




Short explanation about how to use it ( sorry for my terrible English :) :


In V.03    --It is possible extract also a corner pin.

In V 03.1  --fixed BUG. Reconcile was not always connected to BG Image.

                  --Added check box 'Translation only' - if checked - will calculate only 2D position (exactly as Reconcile do) - as result you willl have a Tracker node.

In V 03.2  --2D position of corners in corner pin will exactly match corners of the card in 3D space.

In V 04.0  --It is possible extract CornerPin with transformation animated in 'extra matrix'. (can be used later in Roto or GridWarp matrix).

In V 04.1   --fixed BUG. If a Card had an Animation it was not tracked properly.

In V04.2   --fixef BUG. In some cases tracking points were not positioned on corners of the Card.

In V05.1   --possible to create tracked Roto node (extra_matrix)

in V05.2   -- hopely final cleanups of the code :) . No need anymore to connect a texture to the Card (before Nuke was rising an error if a Card had no texture)



Please login in order to download these files.


0 # Alexey Kuchinski 2012-04-25 04:10
upps, found some mistake in v1.0, fixing now, will upload soon v2.0
Sorry for that
0 # Diego Ramos 2012-12-10 10:52
I think this great, but I dont know how this works..could you make a tutorial? :-)
0 # Alexey Kuchinski 2012-12-10 11:46
Hi Diego, i definitely will, just do not have time right now. Generally you need to position your card in the right place, than select your camera + select your BG + select this card and run the script. this works exactly as Reconcile3D node, just instead of axis you have a card.
It also will support moving/scaling/ rotation of the card (but will not work with card connected to Transform node or with animation in Extra matrix)
Hope it is enough for now, soon (hopefully) will post Tutorial :-)
0 # Alexey Kuchinski 2012-12-10 15:05
Here we go :-)
Hope my English is good enough
0 # Julian Lojek 2012-12-12 01:44
So this is what you do at night. :-) Thanks, will come in handy. Good work!
+1 # Falk Hofmann 2012-12-12 05:35
nice one Alexey!
seems to be much faster than using cards with a scanline render.
0 # kim sihyun 2012-12-13 02:06
this is super useful scripts
0 # li zhaohui 2012-12-22 11:07
I'm interested in your nuke plugin package, especially MassivePanel, whether it can be shared.My English is very bad....
Thank you!
0 # Patrick David 2013-01-04 08:56
This is amazing, however is it just me or does Nuke's motionblur not seem to work properly on matrix transformations ?
0 # Alexey Kuchinski 2016-02-28 08:59
Hi Patrick, Sorry for the late answer, it should work, sometimes the re some kind of Gimble lock and the animation flipps. Happenning if you rotating to the point behind tracked card(more than 180 degrees), or if you passing the card with the Camera.
0 # Alexey Kuchinski 2016-02-28 09:01
New Version (v6.0) finally have got what was missing all the time - SPEED!!!
the calculation happening almost instantly.
Huge thanks to Helge Stang for this improvement.
0 # Mike Connolly 2016-02-29 00:28
Brilliant mand, thank you.

But with CardToTrackGizm o I get:

unable to sample node at given location (1496.4, 1014.8) for the current context (may be zoomed in or have a ROI set)

I'm either all zoomed out, or zoomed in with viewer (as per the video), I don't have an ROI, base size is same as image.

Please advise

NukeX 9.0v8 OSX
0 # Alexey Kuchinski 2016-02-29 03:46
Hi, Mike.

Never had this error before, can you please send me a script please? maybe i will be able to recreate that.

exchange plate to constant if cant send the video.
thank you.
0 # Alexey Kuchinski 2016-02-29 04:03
OOO Crap!!!
just downloaded my own upload. the gizmo had disconnected camera inside, will re-upload...... now
0 # Magno Borgo 2016-02-29 20:53
The roto "bug" can be solved using:


after you create everything, it will force it to update the node ui
0 # Alexey Kuchinski 2016-03-01 07:54
Huge thanks!
will try this one and update the submission.
Thanks again Magno!
0 # Alexey Kuchinski 2016-03-01 17:47
Did anybody else expierence problem Mike had with CardToTrack gizmo?

unable to sample node at given location (1496.4, 1014.8) for the current context (may be zoomed in or have a ROI set)

trying to solve it but can not recreate the error, would like to know if it is some local problem or a gizmo is not working for other people as well.
thank you
0 # Alexey Kuchinski 2016-03-05 09:20
Hi there, seems like Foundry did change some TCL rules from version 9.08 and higher, so i am expecting you will have issues with CardTo Track gizmo, will fix the problem as soon as will have 9.v08
sorry for inconvinience
(it should run fine on lower versions though)
FIXED in version 6.04
if your viewer is looking redish - go inside of gizmo and put clamp after blue NoOp node - it is just preview issue, FIXED in version 6.05
0 # Travis Button 2016-05-28 20:37
Hey Alexey. Came across this thread because of a recent issue I started having on the "Magic Carpet" 4 point multi-gradient gizmo I've been using from Nukepedia for years. I have made a few adjustments over time to make it better but apparently this same bug was introduced via Nuke 9.0v8 for that gizmo as well. What exactly was your fix? The bug is producing really odd terminal errors and sporadically working/not working in the gui. My error is from a TCL expression pulling rgb values from a Crop node. Example: [sample Crop4 red 10 10 8 8]. I have tried a number of things to fix it to no avail. Any ideas?
0 # Alexey Kuchinski 2016-05-29 07:42
Hi Travis, not sure if it is connected to your problem, what happened in my Gizmo is that i was sampling the rgb value of certain node using python command inside of NoOp node.
the output of NoOp node was not connected to nothing
That was okay till Nuke 9.08, in Nuke 9.08 as turned out to be - if node is not connected to the main tree of the gizmo it is not evaluated (at least for me the solution was just to connect the bloody node to the tree with a merge node and set the mix value to zero)

maybe you can send me a group that errors and i will have a look
0 # Travis Button 2016-05-29 16:54
Thanks for the reply, Alexey. In a roundabout way, it does sound like the same problem. I have a crop node that is feeding values to a constant and half the time (depending on which node you're viewing) the constant gets the value it is supposed to and the other half of the time it returns 0. Like yours, it's pulling RGB values, in my case from a crop node using TCL. I can literally open them up sideXside Nuke9v6 it works fine and Nuke 9v8 it's broken the same way you report. I tried your fix with the merge node as well as a shufflecopy to get it connected to the main tree and it worked for a second and then it didn't. Extremely buggy. I reported this to the foundry and sent sample script so hopefully I'll hear from them tomorrow. I can send you the script/group if you give me your email. Thanks again!
0 # Alexey Kuchinski 2016-05-29 17:00
have to say that i also had a plenty errors with nuke expressions
inside of groups and funny enough too frequently i was solving the problem without fully understanding why for example : the simple line as input1.translat e.x is just refusing to work from time to time
(many times solution was to turn the expression into python)
my mail is
0 # Marco Masotti 2017-02-14 15:51
Hi, Alexey!
I can't use this gizmo on Nuke 10.0v5 (unknown command type when I click on the tab on top).
Anyway after a Copy and Paste it works but when I click "go" it doesn't export correctly the CProject. I only get a normal corner pin. Of course would be the same add some framehold or other but your CProject was very good. Can you help me in this case?
Thank you very much! Awesome job!
+1 # Alexey Kuchinski 2017-02-14 16:20
Hi Marco, thank you.
i do not work with Nuke 10, still on 9.
But i did run a simple test on 10,0v3 and everything went just fine.
Did you just download the gizmo or you used it before on lower version?
are you sure your CProject gizmo is in your plugin folder?

can not check for Nuke 10,0v5 since i do not have an access to it right now, sorry.
0 # Marco Masotti 2017-02-14 16:56
Thanks, Alexey,
It's the first time that I use it.
I've placed the folder inside .nuke and I've also put the lines into
+1 # Alexey Kuchinski 2017-02-14 17:46
please dive inside of CartToTrack gizmo, check if StabSwitch1 is connected to ScanlineRender1 Camera input, if not - reconnect please.
maybe the Gizmo was corrupted on Upload, checking it now, if yes, will re upload ASAP.
thank you
0 # Alexey Kuchinski 2017-02-14 19:03
Hi Marco,
re uploaded newer version, hope that will fix the problem.
worked on Nuke 10.0v03.
Thank you for reporting!
0 # Marco Masotti 2017-02-15 09:24
Hi, Alexey!
Thanks for the support!
Unfortunately, it's still not working :-|
There's always the CardToTrack: Unknown command error message.
+1 # Alexey Kuchinski 2017-02-15 10:04
Hi, good morning,
Which tab are you clicking?
are you talking about the CardToTrack menu?
if yes, press "x" , type CardToTrack - it should bring the node.
if you managing to bring the node probably something in your went wrong check if you did mistype something.
running out of ideas :D
0 # Marco Masotti 2017-02-15 10:36
Good morning!
I was talking about the button on the bar on top (near to "help").
also trying to execute with "x" and typing CardToTrack, nothing.
I just copied and paste the three lines above in the :D
maybe there's something strange with this nuke version.
I will keep you updated about it!
I hope the problem is just me 8)
+1 # Alexey Kuchinski 2017-02-16 07:21
Hi, it seems that Nuke is not loading the CardToTrack gizmo on startup, do you have some other ........ stop stop stop!!!!
just re read your first post: I've placed the folder inside .nuke

you have to put only files inside of .nuke folder, not a folder with files inside!!! nuke will not access the folder you pasted in, nuke will look into .nuke folder only
i think we are done here :)
0 # Marco Masotti 2017-02-16 09:18
Hi, Alexey!
Wow, I feel so dumb :o other gizmos I have are working inside their folder. Sorry for the waste of time :D
Thanks again! You did a great and useful gizmo!
0 # Alexey Kuchinski 2017-02-16 11:49
Hi Marco, glad we solved it!
0 # Sven Akelian 2017-10-02 12:22
Thanks Alexey,
Can you elaborate on using the now builtin Card2Track Command ?

I'm connection my card to the extra slot, setting the gizmo to "I have a card", but this does not work :(
0 # Alexey Kuchinski 2017-10-02 12:32
hi Sven.
are you getting some error message?
is your camera connected
do you have animation in your camera
frame range.......
too many things can go wrong
havw you seen tutorial?
you can send me script as well
0 # Alexey Kuchinski 2017-10-02 12:32
hi Sven.
are you getting some error message?
is your camera connected
do you have animation in your camera
frame range.......
too many things can go wrong
havw you seen tutorial?
you can send me script as well
0 # piotr hurny 2018-01-30 15:56
Hello Alexey, long time no see.

I have an issue with you script.

I am using Nuke 10.5v2 on windows 7.

The gizmo freezes nuke when I press GO!

Its not responding and I wonder why.

I am not using any undistort nodes for the BG.

Can you help me or explain why does it freeze up ?


0 # piotr hurny 2018-01-30 16:01
Quoting piotr hurny:
Hello Alexey, long time no see.

I have an issue with you script.

I am using Nuke 10.5v2 on windows 7.

The gizmo freezes nuke when I press GO!

Its not responding and I wonder why.

I am not using any undistort nodes for the BG.

Can you help me or explain why does it freeze up ?



Never mind its just very slow. Took about 5 mins but it works! :)
0 # Bernd M 2018-04-01 01:15
It's one of the greatest gizmos!!!
0 # Adrian Rivera 2018-05-03 18:26
Hi, love your gizmo!

I was wondering if you could add another feature in your next version, information that comes in the corner pins and roto node come from undistorted sources due 3d camera and reconcile3d information, would there be a way to also export position information already distorted, say as if there would be an undistorted lensdistortion node in the BG input after the plate, so the gizmo could take that information, copy it and then apply a the distortion into the information, it would would be great specially for the roto node since you normally roto in the distorted plate
0 # Alexey Kuchinski 2018-05-03 21:00
Hi Adrian, thank you for your comment.
a corner pin has points and it is theoretically possible to calculate
their position affected by some lens distortion.
Problem 1 : it is complicated from numerous reasons.
Problem 2: everything between points will be not properly distorted since it will be linearly interpolated between points and will not correspond to the lens distortion.

I will recommend to you to do your masks on undistorted footage and apply the distortion to mask later on.

or, and frankly that is my preferred way : just mask the distorted footage and add 2-3 additional keyframes fo fix possible drift.It will do in the most cases.
0 # Adrian Rivera 2018-05-03 21:27
I see, thank you for the quick response! :)
0 # Alexey Kuchinski 2019-06-21 20:06
Hi Folks, sorry for the spam , new version is available, check it out!

added possibility to calculate from Axis or chain of Axises *
added possibility to calculate from Deep *
UI changes to provide more user friendly experience*
Default frame range is taken from Camera animation and not from project frame range
Some stability improvements(ho pe no new bugs introduced)
0 # MARK PINHEIRO 2019-06-24 14:00
Thanks ;-)
0 # Roman Antonjuk 2019-07-31 00:25
global name "first_frame_v' is not defined
help me please :)
0 # Alexey Kuchinski 2019-07-31 05:18
Hi Roman.
This happens when you have no keyframes in your Camera animation, .... probably. is this a case?

sometimes it is not working when you standing outside of the comp range on the timeline as well .

If none of this, send me the script so i will be able to debug the issue. no material needed, just a camera and the constant with proper resolution instead of the plate.
Will release new version with additional fixes soon.

0 # Alexey Kuchinski 2019-07-31 08:45
funny enough, just came to work and my collegiate greeted me with same error, the reason in his case was that his camera has linked transformations to camera tracker.
we baked the animation and all worked
0 # Alexey Kuchinski 2019-07-31 08:45
funny enough, just came to work and my collegiate greeted me with same error, the reason in his case was that his camera has linked transformations to camera tracker.
we baked the animation and all worked
0 # bang meng 2019-08-09 10:44
Great, can you make a choice when you create it? Instead of only creating all and card
Thank you very much for sharing.
0 # Alexey Kuchinski 2019-08-09 10:54
Hi man, this is on my list but with very little priority, have not much time lately.
So no promises :). one day one day.
0 # Brian Sales 2019-11-21 07:47
I love CardToTrack, but tried it using a card today on an anamorphic shot and it seemed to place the pins in the wrong spots. Went back to an early version and it worked fine. Was it something I did or is that functionality broken in the newer versions of the Gizmo?
0 # Alexey Kuchinski 2019-11-21 08:54
Hi Brian, will check it out, thank you for pointing out.
Will upload next week with some additional features and fixes.
Hope will fix anamorphic issue (if will find one)
0 # Alexey Kuchinski 2019-11-21 08:54
0 # Alexey Kuchinski 2019-11-28 14:13
the problem was that the reformat in CProject gizmo was not getting the pixel aspect from input,
thank you for pointing out.
fixed, reuploaded!
0 # Brian Sales 2019-12-03 06:55
Alexey, thanks for looking into it and for your quick fix. I've been out of the office, but will explore the latest version this week.
0 # Matthias Backmann 2020-02-12 16:49
The Node is awesome and keeps getting better and better!
Is it perhaps possible to also export a Tracker-Node with the cornerpin-Data? That would complete the package you get.
0 # Alexey Kuchinski 2020-02-15 15:43
Hi Mtthias, thank you for your kind words,
Regarding Tracker export - i see Corner pin superior to Tracker in most of aspects - that why i choose to export cornr pin and not tracker.
To export both can be an option, but it will add more weight to script and i saw it as not big necessity so decided not to go this way.

The proper solution will be i guess to let user to decide what he/she would like to .... ideas ideas ideas.

Cant promise anything but i guess i will put it on my list.

And btw - why you will prefer tracker over corner pin?
0 # Ruairi Twohig 2020-02-13 18:01
This is amazing, used to use a script that did something similar but it was a lot more limited. Awesome work!
0 # Alexey Kuchinski 2020-02-15 15:29
Thank you Ruairi
0 # Min Tesch 2020-04-15 08:25
hi Alex,
your tool is gréat. i use it in nuke 12.1v1
when i fire it up i get the error CardToTrack.loo k_at_Axis.rotat e: Nothing is named "Nothing". the imported track is from 3de and has an axis attachet do the cam. han theis be the problem?
whem i try to track from a card i get the error line 39, in
AttributeError: 'NoneType' object has no attribute 'setSelected'
is this because of nuke 12 or am i doing something wrong?
0 # Alexey Kuchinski 2020-06-11 08:34
Hi Min, thank you.

i do not think you can use and axis attached to camera, the tool is not collecting data from the camera matrix.

you will have to copy data directly to the camera.

sorry for a late reply
0 # Bernd M 2020-06-10 22:38
Same here... when I click on Happy I receive this:

ERROR: _data.xform_ord er: Nothing is named "Nothing"
[ 0:25.55] ERROR: _data.rot_order : Nothing is named "Nothing"
[ 0:27.40] ERROR: CardToTrack1.lo ok_at_Axis.rota te: Nothing is named "Nothing"
0 # Alexey Kuchinski 2020-06-11 08:34
Hi Blic, did you use an Axis connected to Camera as well?
0 # Bernd M 2020-06-11 08:57
Hey Alexey,
nope, nothing attached. Plain camera, baked animation (ticked off read from file); Input is set to grat matchmove; the gizmo also shows a "0" inside the switch for the axis.. so should be set to placeholder axis
Do you have one of the older versions still on your machine? Maybe I can test it with a version prior to the latest here?
Or vice versa I can send you the cam/geo (dont think you need the image? - checkerboard as input?)
0 # Bernd M 2020-06-18 10:32
Hey Alexey,

i've found my issue... it happened, that... no idea why, my framerange had been extended instead from 1001-1195 to 1001 - 16700... This obviously takes some time to calculate.
Also I think the calculation takes longer, when the gizmo cannot find any camera keyframes anymore (which is the case from frame 1196 on...).
For testing purpose I extended everything to frame 2000 and repeated the creation process and indeed instead of some second it takes 15-20 seconds to calculate... or just crashes as it happened before...

I still get those error messages, though, although it doesn't affect the result.
0 # Alexey Kuchinski 2020-06-29 20:01
Ha ha , you have no idea how many times I have furious composition rushing towards my desk with 'this stupid Gizmo is not working!!!!!'
But yes it usually someone forgot to connect the camera, or used wrong camera or wrong frame range or some other funny thing.

Regarding calculating 1000 frames - it does make sense that it will take 15 seconds, it is not the fastest tool out there, I am aware of that and maybe one day I will finally rewrite it, but not today ,
Have a nice day
0 # Alexey Kuchinski 2020-06-29 20:07
And regarding error message, I think actually in have it fixed in my latest version, will check later this week, ...
0 # Dmitrii V 2021-08-08 01:29
Great tool, Alexey! Btw, dont forget to dettach axis from camera. Some times camera tracked scene got it by default. It just will not work.
0 # Alexey Kuchinski 2021-08-09 10:49
Thank you Dmitrii, i will try to solve this when i will get into rewriting the code for Python3.
0 # Ella P 2021-12-30 11:58
Hi! I get this error message when trying to set the reference frame (I have a camera and a card): "inconsistent use of tabs and spaces in indentation (, line 9)". Don't quite understand what it means
0 # Alexey Kuchinski 2021-12-31 10:31
Hi Ella,
the error it self is pretty trivial
It happens when tabs and spaces are mixed in a code.
I did not have this problem so far but i will re-check the code.
Thank you.
0 # Ella P 2021-12-31 11:25
Right okay. Something is off tho. I continue after setting the reference frame and I get the grid. However nothing happens when I try to adjust the Z knob. And then when pressing Go! I get this: "Did you mean print('no dialog, use auto-created input values')? (, line 237)". I get no nodes at all. I'm using Nuke13.v1 btw. The older version of this gizmo used to work fine for me but now I just can't get it to work. It's a great gizmo but I just don't understand what goes wrong... Thank you for taking your time answering me
0 # Alexey Kuchinski 2021-12-31 14:05
Nuke13 :)
It uses different Python version (3) and current is written in (2.7)
I will upload next week version compatible with Nuke 13.
Till then stay strong and have some holidays!
(you still can use Card To Track in previous version and copy resulted nodes to Nuke13 )
0 # Ella P 2021-12-31 14:48
Ah, well that could explain it! I was too eager to use the gizmo to see what the issue might be. Hopefully the new version update works. Happy New Year!
0 # Alexey Kuchinski 2022-01-22 21:27
Sorry for the delay, uploaded new version.

Important - had no time to test it in production but seems to work on both Nuke 12 and 13 now.

There is no CProject and Tproject in this update as they should work from previous versions.

please update me if something is not working.

0 # Alexey Vaitvud 2022-02-10 13:13
Hey Alexey, thank you for the updated version!

Seems to be working fine, except for one small fix: ' ' needs to be renamed to ' ' before using.

Otherwise, it's a very handy tool! Thank you!
0 # Alexey Kuchinski 2022-02-11 07:18
Hi Alexey!
Thank you very much for the feedback, will fix the typo.
0 # Alexey Kuchinski 2022-02-11 07:29
Hi, i had a look and i am not sure where did you see the problem.
The group is calling and it works, It can not work with naming changed in the way you proposed.
0 # Alexey Vaitvud 2022-02-11 11:03
Well, I'm not an expert in Python, so I might come to a wrong conclusion, but here is how it works on my side:
0 # Alexey Kuchinski 2022-02-11 13:35
cool, thank you for the video.
I just downloaded the latest version and checked it:
this what is running when you press the 'Go' Button:

import cardToTrack

so i am not sure how you arrived to error you are getting.
mystery........ :-)
0 # Alexey Vaitvud 2022-02-11 13:58
F**k, it's my bad now, sorry!

At first, I just put the lines you suggest in the to make a Menu Command. And then it gave me: "CardToTrack: Unknown command" Error.

Then I went into troubleshooting , most likely replacing some lines by accident in the process in your .py file. So in the end I reported the wrong issue. :lol:

If I put your .nk in the Toolsets folder, just to avoid adding anything to, it works fine.

Thank you, for taking the time to figure it out!
0 # Alexey Kuchinski 2022-02-13 13:37
no worries, glad all is resolved, have fun!
0 # pancho lopez 2022-03-31 20:04
hello, could you teach me how to install please I'm a newbie
0 # Alexey Kuchinski 2022-04-10 08:34
Hey Pancho, sorry for a late reply, if you still did not manage - please watch Basic tutorials about
you will need it in future in any case.
From the moment you will understand the basic you will be able to install any python code or gizmo.
Good luck
0 # Edwin Mendieta Rueda 2022-04-05 16:25
inconsistent use of tabs and spaces in indentation (, line 9) PLEASE HELP!!
0 # Alexey Kuchinski 2022-04-10 08:31
Hi Edwin, i guess you have an issue with Nuke 13.
do you use the latest version?
It should work for Nuke 13 without issues
0 # Alexey Kuchinski 2022-04-10 08:31
Hi Edwin, i guess you have an issue with Nuke 13.
do you use the latest version?
It should work for Nuke 13 without issues
0 # Sindre Grimsrud 2022-11-09 13:17
I get the same message when I try to set reference frame. I am in Nuke 13.2v1.
0 # Topi O 2022-05-04 17:18
Hi! I need help installing this. I just cant wrap my head around this python thing so I'm lost. I don't have file or plugins folder in my .nuke-folder.
I'd really appreciate if someone could explain this step by step. Where are these files/folders suppose to go and is there something else that I need to do?
0 # Pal Tauszig 2022-06-12 17:42
please see this for instructions:
0 # ilies Carmona 2022-12-08 00:07
inconsistent use of tabs and spaces in indentation (, line 9) help
0 # Alexey Kuchinski 2022-12-08 17:58
Hi, are you sure you are using the latest version?
iI assume you are on the Nuke 13 but you are using the older version of CardToTrack. (not Python3 ready)

If you will download and replace with new one - you should be fine.
Correct me if i am wrong, please additionally send full error if possible.
Thank you!
0 # Gonzalo Gomez 2022-12-11 17:58
Hi, "knob near does not exist" pops up when I click Set. I downloaded the recent version of the gizmo and this still pops up.

Would appreciate some help.
0 # Alexey Kuchinski 2022-12-14 15:34
hi Gonzalo, did you connect the camera?
He is looking for the camera but can not find it from what i see.

do you have and axis connected to camera?

there is a chance it will not work in this case, do not remember for sure.
0 # Nicholas Hoyt 2023-05-17 17:50
Can you update the version and copyright code so we know what versions are floating around in the ethos. The nuke survival toolkit has one marked as v4.0 from 2017 and this latest one is also marked as v4.0 2017.

I can update it myself in the .nk file provided for my pipeline, but the bigger issue is its an unknown which versions are out there in other toolsets.

You have no rights to post comments

We have 2698 guests and 112 members online