In case someone runs into the same problem: I had some troubles installing the Toolkit because the slashes were in the wrong direction, after I copied the path into the init.py! Thanks for putting this awesome Toolkit together, Tony!
Big Big Thank You!! This is the most amazing tool I ever had in Nuke! I just started to learn Comp these 2 years, and this tool is incredibly helpful and useful! I know you were doing this toolkit from Ben's Comp Newsletter, I was Ben's student from our comp class for 1 term. Incredible amazing!! I am so happy to learn how wonderful this community is! Thank you, Tony :)
Really cool! I hope one day can make gizmo that will behave like TripLanar mapping, when you plug texture and using World Position or Normal pass from CG render, it will place this texture on objects (similar to generating Noise form World Postion, but only with image input😅
This is an amazing resource! There is an error in the installation documentation: In the init.py you need the line `import nuke` before the nuke.pluginAddPath otherwise it will not work. Thanks for this resource and video!
@@JAYJAY_ So the way Python works is it loads up some basic stuff when it starts. But there are modules that extend this. There is "nuke" module contains all the code relevant to nuke. That includes nuke.pluginAddPath() (see it's "nuke" dot "pluginAddPath", so pluginAddPath is in the "nuke" module). If you run code from within Nuke itself, well that nuke module is already loaded. But the init.py runs BEFORE nuke loads. So it's vanilla Python code and ignorant of the various commands in the nuke module. The command "import nuke" loads all the commands so you can include them in your code. After that everything works as described in the video.
@@alg2398 second question, yes. Careful not to use a wordprocessor like Word or LibreOffice as it will add qeird stuff to your file. A plain text editor (even notepad on windows) is what you need. Have a look at Automate The Boring Stuff with Python for a really simple and useful guide to how Python works in general, then the Nuke docs are really good at explaining how it works within Nuke. Also on my website danielmarkmiller.uk I have some examples of python in nuke
If i may suggest a feature, having a way of easily enable or disable the loading of a gizmo would be nice. Cragl made something really clever for their tools (cragl connect). With a single menu you can choose only the tools you need, so you dont get overwhelmed with features you never really use
A very good idea! I’m not much of a coder and wish i knew how to do that! What you can do though is open up the menu.py file in the main folder in a text editor. It’s pretty organized, and just hashtag out or delete any lines of code that are adding tools you don’t need. That’s the poorboy solution for the moment! Haha maybe there will be others in the future to help make cool features like that possible. Thanks for the suggestion, very good one
Im a bit overwhelmed by my work right now, but i’d be glad to help. Ill get in touch as fast as i can to add this feature on your wonderful gizmo compilation ;)
Unrelated question to this video but I'm curious...have your keying methods changed since you released the Advanced Keying Breakdown series? Is there anything you'd do differently now?
ruclips.net/video/C8GX5gZ3dtQ/видео.html I was a guest on VFX for Filmmakers channel a few months ago and went over an updated version of the template, which is also found in the NST. But it’s up to date as far as how I approach things in this video. Matt has provided the source material and workfiles for you to download and investigate as well. Thanks for the question!
This must have taken serious effort and time to put together. Kudos for the gift we can all use. I'm sure people will bombard you with 'what about this tool'... but... Rainmaker (lens droplets) should be in there - it's under the particles menu on Nukepedia. I use it a tonne. Also in your documentation you have AutoFlare but - correct me if I'm wrong - it doesn't appear to be part of the toolkit download just fyi. Cheers dude
I’ll have a look at rainmaker! Thank you! And good spot on the autoflares. I had to take it out last minute because it has images with filepaths. I will have to figure out a way to basically replace a variable in the read filepath with the hardcoded filepath to the images. I am consulting some friends on ideas on how to do that. You could do it with a live variable that if you have the NST loaded it would show you, sort of like [value root.name] gives you the value of the script folder. But this doesnt work with renderfarms or other users who didnt load the NST, or if you want to share the script. Anyway long story short, i am hoping to work out a way around that in the future! Thank you for the heads up!
@@CompositingMentor Ahh makes sense no worries! Sounds like you got all under control. There are so many tools in here I had no idea about/ forgotten about after all these years, so it's been awesome to read the documentation and go through them all. Thanks again!
Me, An Intellectual, Installing this toolkit: nuke.pluginAddPath("Your/NukeSurvivalToolkit/C:\Users\user\Documents\survivaltoolkit\NukeSurvivalToolkit_publicRelease-1.1.1\NukeSurvivalToolkit") This video saved me lol Thank you!
@@user-xr1bw2ho1y I've gotten other gizmos and plugins to work before, but i think the error is with my python version not being able to read the .py files correctly
@@CompositingMentor Hey Tony. thanks for getting back to me so fast. I have 2.1.1 toolkit. i think thats the latest. I am running Nuke indy on a M1 pro Max MacBook. would that be the issue?
If you're in Nuke Indie, try this -- nuke.pluginAddPath("C:\\Users\\user\\.nuke\\NukeSurvivalToolkit") -- .... After some research, doubling the backslashes worked for me!
Unfortunately, it did not come in nuke plugins I do not know what the problem is .. I followed the instructions and the explanation in detail, but it did not appear in the list of Plugins I use the macOS High Sierra system, NukeX 12.2V4
Tony, good afternoon! Do you plan to write a tutorial on Morph_Dissolve ( In depth explain )? I'm sure many will be interested, because there is no such thing on RUclips yet. I'm talking about this: " Tony Lyons June 15, 2019 at 12:35 pm - Reply Using this combined with SmartVectors and a couple “clean frames” has revolutionized my paint workflow! especially if I have to cleanup or patch something over clothing. works awesome, thank you! "(c)
learn.foundry.com/nuke/8.0/content/user_guide/configuring_nuke/common_preferences.html This could help. I believe nuke takes into account .nuke folder by default, so just make sure you’re in the right folder
Pretty nice set, but how do you update these? Plus isn't nubrige a thing that would allow each artist to get the things they only need and use and keep it up to date? www.nukepedia.com/nubridge
I don't think I had a camera shake tutorial, maybe you are thinking of someone else? I do suggest trying ben mcewan's bm_cameraShake tool though, it's probably my favorite. If only using nuke's default camera shake tool, I recommend seperating different movements, a slower "hand held" one, and then under it, a more quick jittery one. You can layer as many as you want. Also you can use an external multiply node or any node with 0-1 mix to control the overall amount and expression link all the camera shakes. That way you can turn it on/off with just 1 overall slider.
@@PostolPost oh yes, i remember that. I didn't think the info was relevant any more. however that motionTile node is in the NST, i renamed it to MirrorBorder, I thought it was more descriptive than motionTile
It is working for me for nuke 13.1 on macOS, Which version of nuke are you using? Also are you using nukeX, indie, non-commercial? Does it give you an exact error? a lot of times in order to get a more detailed error you need to run the program from a terminal window, so when nuke fails/quits, it still gives a nice detailed error. It usually tells exactly where the python code failed, including the line of code it could not process. Are you using windows, mac, linux? I will assume windows. If so, try this website and follow instructions for how to run nuke from command line terminal to get the error: learn.foundry.com/nuke/9.0/content/getting_started/installation/launching_nuke_win.html?tocpath=Getting%20Started%7CInstallation%20and%20Licensing%7CWindows%7C_____2 I do not have windows, I have only access to mac, so maybe it's a windows thing, or maybe nuke 13.4 update changed something. But either way I'll need your help to let me know the exact error you are having to either fix it on my side or guide through any installation trouble you may have had. Thank you! Hopefully we can get it working
It is working for me for nuke 13.1 on macOS, Which version of nuke are you using? Also are you using nukeX, indie, non-commercial? Does it give you an exact error? a lot of times in order to get a more detailed error you need to run the program from a terminal window, so when nuke fails/quits, it still gives a nice detailed error. It usually tells exactly where the python code failed, including the line of code it could not process. Are you using windows, mac, linux? I will assume windows. If so, try this website and follow instructions for how to run nuke from command line terminal to get the error: learn.foundry.com/nuke/9.0/content/getting_started/installation/launching_nuke_win.html?tocpath=Getting%20Started%7CInstallation%20and%20Licensing%7CWindows%7C_____2 I do not have windows, I have only access to mac, so maybe it's a windows thing, or maybe nuke 13.4 update changed something. But either way I'll need your help to let me know the exact error you are having to either fix it on my side or guide through any installation trouble you may have had. Thank you! Hopefully we can get it working
If what @Oxlou suggested doesn't work, if you're in Nuke Indie, try this -- nuke.pluginAddPath("C:\\Users\\user\\.nuke\\NukeSurvivalToolkit") -- .... After some research, doubling the backslashes worked for me!
Hey! If you're in Nuke Indie or NC, try this .... nuke.pluginAddPath("C:\\Users\\user\\.nuke\\NukeSurvivalToolkit") .... After some research, doubling the backslashes worked for me! Thanks so much for this Toolkit!! Found it because @VFX Central!!
Finally found the SOLUTION,,,, the problem is dont use double quotation use single quotation so instead of ( "C:/Users/.nuke/NukeSurvivalToolkit" ) use ( 'C:/Users/.nuke/NukeSurvivalToolkit' )
In case someone runs into the same problem: I had some troubles installing the Toolkit because the slashes were in the wrong direction, after I copied the path into the init.py!
Thanks for putting this awesome Toolkit together, Tony!
THANKS!
thank you! Thought i was going mad :D
thanks, I thought this wont work on nuke 13
Thanks!
thanks! Tought I was just stupid for copy/paste files xd🧐🤣
Big Big Thank You!! This is the most amazing tool I ever had in Nuke! I just started to learn Comp these 2 years, and this tool is incredibly helpful and useful! I know you were doing this toolkit from Ben's Comp Newsletter, I was Ben's student from our comp class for 1 term. Incredible amazing!! I am so happy to learn how wonderful this community is! Thank you, Tony :)
Thank you!
Thanks Tony to you and all those great people who develop these tools and share them generously to the whole community.
Are you f**king kidding me? This is such a nice gift to the community! Bravo!!!!
You are the best. Thank you
Oh, this is a must-have gizmo set for every NukeX compositor! AWESOME!
This is pretty awesome! Thank you for contributing this to the community alone with all the gizmos/tools creators.
Really cool! I hope one day can make gizmo that will behave like TripLanar mapping, when you plug texture and using World Position or Normal pass from CG render, it will place this texture on objects (similar to generating Noise form World Postion, but only with image input😅
The legend keeps on legend-ing
Amazing Tony.... Master stroke .. Thank you so much for incredible work..
Nice, i really appreciate that artists get credited for their work !
you’re a gem, Tony! Kudos to you.
This is so generous. Now I just need a job to try them out.
Hello , is anybody have problem with the "init. py : error interpreting this plugin" warning on mac (using Nuke X 13.2v1)?
same problem. have you resolve it?
Legend
This is an amazing resource!
There is an error in the installation documentation: In the init.py you need the line `import nuke` before the nuke.pluginAddPath otherwise it will not work.
Thanks for this resource and video!
Please tell me more
@@JAYJAY_ So the way Python works is it loads up some basic stuff when it starts. But there are modules that extend this. There is "nuke" module contains all the code relevant to nuke. That includes nuke.pluginAddPath() (see it's "nuke" dot "pluginAddPath", so pluginAddPath is in the "nuke" module).
If you run code from within Nuke itself, well that nuke module is already loaded. But the init.py runs BEFORE nuke loads. So it's vanilla Python code and ignorant of the various commands in the nuke module. The command "import nuke" loads all the commands so you can include them in your code. After that everything works as described in the video.
like this? importnuke.pluginAddPath
I don't even know nothing about phyton, is it okay to create a text doc and name it with .py?
@@alg2398 So you would have "import nuke" on one line, after that nuke.pluginAddPath('path/to/add')
@@alg2398 second question, yes. Careful not to use a wordprocessor like Word or LibreOffice as it will add qeird stuff to your file. A plain text editor (even notepad on windows) is what you need. Have a look at Automate The Boring Stuff with Python for a really simple and useful guide to how Python works in general, then the Nuke docs are really good at explaining how it works within Nuke. Also on my website danielmarkmiller.uk I have some examples of python in nuke
Amazing as always, please keep this fantastic content coming :)
This is amazing, Tony, thank you so much.
If i may suggest a feature, having a way of easily enable or disable the loading of a gizmo would be nice.
Cragl made something really clever for their tools (cragl connect). With a single menu you can choose only the tools you need, so you dont get overwhelmed with features you never really use
A very good idea! I’m not much of a coder and wish i knew how to do that!
What you can do though is open up the menu.py file in the main folder in a text editor. It’s pretty organized, and just hashtag out or delete any lines of code that are adding tools you don’t need. That’s the poorboy solution for the moment! Haha maybe there will be others in the future to help make cool features like that possible. Thanks for the suggestion, very good one
Im a bit overwhelmed by my work right now, but i’d be glad to help. Ill get in touch as fast as i can to add this feature on your wonderful gizmo compilation ;)
not working for me, trying on win 11, did everything tried different methods , the ;plugin its not showing up
amazing stuff Tony. I basically learned keying from your videos.
I already tried both methods but the menu doesn't show up, the gizmos loads but the menu tool kit doesn't load. Any help will be welcome.
Amazing stuff, cheers for this mate.
Hi thank you but this method not working on nuke13 what should i write in init.py
downright incredible, thanks a bunch!
Thank very much for this gift, its amazing!
I love it!
Thank you Tony!
On Windows 10 no allow to save the folder as init.py, how can I solve this issue?
Unrelated question to this video but I'm curious...have your keying methods changed since you released the Advanced Keying Breakdown series? Is there anything you'd do differently now?
ruclips.net/video/C8GX5gZ3dtQ/видео.html
I was a guest on VFX for Filmmakers channel a few months ago and went over an updated version of the template, which is also found in the NST. But it’s up to date as far as how I approach things in this video. Matt has provided the source material and workfiles for you to download and investigate as well. Thanks for the question!
@@CompositingMentor Thank you so much, man! I'll definitely have a look :)
The instalation tutorial starts at 3:00 :)
Awesome, thanks brother.
Huge work man! Thanks a lot!
This is amazing!! Thank you so much!
Awesome Work Tony
This must have taken serious effort and time to put together. Kudos for the gift we can all use.
I'm sure people will bombard you with 'what about this tool'... but... Rainmaker (lens droplets) should be in there - it's under the particles menu on Nukepedia. I use it a tonne.
Also in your documentation you have AutoFlare but - correct me if I'm wrong - it doesn't appear to be part of the toolkit download just fyi.
Cheers dude
I’ll have a look at rainmaker! Thank you! And good spot on the autoflares. I had to take it out last minute because it has images with filepaths. I will have to figure out a way to basically replace a variable in the read filepath with the hardcoded filepath to the images. I am consulting some friends on ideas on how to do that. You could do it with a live variable that if you have the NST loaded it would show you, sort of like [value root.name] gives you the value of the script folder. But this doesnt work with renderfarms or other users who didnt load the NST, or if you want to share the script. Anyway long story short, i am hoping to work out a way around that in the future! Thank you for the heads up!
@@CompositingMentor Ahh makes sense no worries! Sounds like you got all under control. There are so many tools in here I had no idea about/ forgotten about after all these years, so it's been awesome to read the documentation and go through them all. Thanks again!
Is this compatible with Nuke 13?
感谢您为合成事业做出的贡献
thank you so much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Me, An Intellectual, Installing this toolkit: nuke.pluginAddPath("Your/NukeSurvivalToolkit/C:\Users\user\Documents\survivaltoolkit\NukeSurvivalToolkit_publicRelease-1.1.1\NukeSurvivalToolkit")
This video saved me lol Thank you!
did it work for you after fixing the path? i'm getting an error ;o;
@@Xgrl00fireX it does! Are you using non-commercial? Seems like most gizmos won't work in NC ㅠ_ㅠ
@@user-xr1bw2ho1y I've gotten other gizmos and plugins to work before, but i think the error is with my python version not being able to read the .py files correctly
If Nuke cannot initialize the path, change your "\" to "/" and magically, it will work. :D
Hey Tony I am getting a /.nuke/init.py : error interpreting this plugin. can you point me into the right direction to solve this.
Hi Joel, try updating it to the latest release version on github, maybe you have an older version
@@CompositingMentor Hey Tony. thanks for getting back to me so fast. I have 2.1.1 toolkit. i think thats the latest. I am running Nuke indy on a M1 pro Max MacBook. would that be the issue?
@@Mrjeschaeffer ya, indie cannot run python code, so it errors, thats the issue, sorry! Not much i can do about that limitation
@@CompositingMentor copy. shame. well thats is solved. thanks again.
If you're in Nuke Indie, try this -- nuke.pluginAddPath("C:\\Users\\user\\.nuke\\NukeSurvivalToolkit") -- .... After some research, doubling the backslashes worked for me!
Can this be done in windows 10? Thanks!
I couldn't get publicRelease-2.0.0 2 to load on 13 ... no problems with 12 though.
Thank you Tony!
Is it possible to use it in non-commerical version?
Great idea, thank you very much! :-)
the gizmo won't work on nuke 13 :(
I cannot create the .py file, it is placed in .rtf by default
Unfortunately, it did not come in nuke plugins
I do not know what the problem is .. I followed the instructions and the explanation in detail, but it did not appear in the list of Plugins
I use the macOS High Sierra system, NukeX 12.2V4
Do you think this will install on nuke indie ?
It does :)
thank you very much
Tony, good afternoon! Do you plan to write a tutorial on Morph_Dissolve ( In depth explain )? I'm sure many will be interested, because there is no such thing on RUclips yet. I'm talking about this:
" Tony Lyons June 15, 2019 at 12:35 pm - Reply
Using this combined with SmartVectors and a couple “clean frames” has revolutionized my paint workflow! especially if I have to cleanup or patch something over clothing. works awesome, thank you!
"(c)
is someone tested this to nuke 15? mine says that he canon turn on the plugin or something
You are amazing.
after editing init.py running nuke gives an error COULD NOT LOAD VECTORTRACKER.PY and nuke crashes
My .nuke folder doesn't seem to have any effect on my setup. Is there a way to make sure nuke is reading files from the .nuke folder?
learn.foundry.com/nuke/8.0/content/user_guide/configuring_nuke/common_preferences.html
This could help. I believe nuke takes into account .nuke folder by default, so just make sure you’re in the right folder
Sadly this is not working for me.I followed everything intact.
Facing error. Showing failed to interpret init.py
Awesome, please how to install on windows. i don't understand how you copy the tool kit as text. help
Thank you.
Pretty nice set, but how do you update these? Plus isn't nubrige a thing that would allow each artist to get the things they only need and use and keep it up to date? www.nukepedia.com/nubridge
I'm having trouble installing Nuke itself. Never used the software so really feel lost atm
Thank you!!!
God save the king
How can I add your w_hotbox to this?
Thank you...
Thanks.
thanks bro
it's not working in nuke 10
No more showreels?
did not work on nuke 14
Awesome! I can now be a little less scared of python
hi. did you deleted your "camerashake nuke torial" ?(
I don't think I had a camera shake tutorial, maybe you are thinking of someone else? I do suggest trying ben mcewan's bm_cameraShake tool though, it's probably my favorite. If only using nuke's default camera shake tool, I recommend seperating different movements, a slower "hand held" one, and then under it, a more quick jittery one. You can layer as many as you want. Also you can use an external multiply node or any node with 0-1 mix to control the overall amount and expression link all the camera shakes. That way you can turn it on/off with just 1 overall slider.
@@CompositingMentor You did. Its mostly about "motion tile gismo", and blogpost is still on your website, but video is unavalible :)
@@PostolPost oh yes, i remember that. I didn't think the info was relevant any more. however that motionTile node is in the NST, i renamed it to MirrorBorder, I thought it was more descriptive than motionTile
Great tutorial, I still can't get it to load unfortunately. :(
Epic
Please update it to be compatible with nuke 13 🙏
It is working for me for nuke 13.1 on macOS, Which version of nuke are you using? Also are you using nukeX, indie, non-commercial? Does it give you an exact error? a lot of times in order to get a more detailed error you need to run the program from a terminal window, so when nuke fails/quits, it still gives a nice detailed error. It usually tells exactly where the python code failed, including the line of code it could not process.
Are you using windows, mac, linux? I will assume windows. If so, try this website and follow instructions for how to run nuke from command line terminal to get the error:
learn.foundry.com/nuke/9.0/content/getting_started/installation/launching_nuke_win.html?tocpath=Getting%20Started%7CInstallation%20and%20Licensing%7CWindows%7C_____2
I do not have windows, I have only access to mac, so maybe it's a windows thing, or maybe nuke 13.4 update changed something. But either way I'll need your help to let me know the exact error you are having to either fix it on my side or guide through any installation trouble you may have had.
Thank you! Hopefully we can get it working
It is working for me for nuke 13.1 on macOS, Which version of nuke are you using? Also are you using nukeX, indie, non-commercial? Does it give you an exact error? a lot of times in order to get a more detailed error you need to run the program from a terminal window, so when nuke fails/quits, it still gives a nice detailed error. It usually tells exactly where the python code failed, including the line of code it could not process.
Are you using windows, mac, linux? I will assume windows. If so, try this website and follow instructions for how to run nuke from command line terminal to get the error:
learn.foundry.com/nuke/9.0/content/getting_started/installation/launching_nuke_win.html?tocpath=Getting%20Started%7CInstallation%20and%20Licensing%7CWindows%7C_____2
I do not have windows, I have only access to mac, so maybe it's a windows thing, or maybe nuke 13.4 update changed something. But either way I'll need your help to let me know the exact error you are having to either fix it on my side or guide through any installation trouble you may have had.
Thank you! Hopefully we can get it working
@@CompositingMentor Hi,I made it work, thanks, I just had an old version, now with latest version 2.1.1 its working properly inside NUKE 13v4 Thanks!
This message appears when I open the program and then closes.
"C:/Users/USER/.nuke/init.py : error interpreting this plugin"
please help.
Replace the " \ " with " / "
If what @Oxlou suggested doesn't work, if you're in Nuke Indie, try this -- nuke.pluginAddPath("C:\\Users\\user\\.nuke\\NukeSurvivalToolkit") -- .... After some research, doubling the backslashes worked for me!
Local User Installation: ruclips.net/video/MQq9GH3SekA/видео.html
Hey! If you're in Nuke Indie or NC, try this .... nuke.pluginAddPath("C:\\Users\\user\\.nuke\\NukeSurvivalToolkit") .... After some research, doubling the backslashes worked for me! Thanks so much for this Toolkit!! Found it because @VFX Central!!
Finally found the SOLUTION,,,, the problem is dont use double quotation use single quotation so instead of ( "C:/Users/.nuke/NukeSurvivalToolkit" ) use ( 'C:/Users/.nuke/NukeSurvivalToolkit' )
This is amazing, Tony, thank you so much.
Thank you so much!! This is amazing!
Amazing, Thanks a lot!
Thank you, Tony!!! This is amazing!
Thanks for this!