- over 1,000 free tools for The Foundry's Nuke
HeatWave v4.0
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Damian Binder
HeatWave simulates heat distortion often seen around fire or other sources of heat.
Requirements:
12.0, 11.0, 10.5, 10.0 or later
Linux, Mac, Windows
12.0, 11.0, 10.5, 10.0 or later
Linux, Mac, Windows
17 Oct 2020
11411
This update focuses on making this tool more production friendly, functional and efficient.
HeatWave v4.0 is presented with two points, POS and WIND, which are overlayed in the viewer.
POS represents the initial position of the heat source. Moving this point affects the translation of the distortion. If a plate's heat source moves over time, POS can be animated to match its position.
WIND represents the angle at which the distortion travels. Moving this point around POS will only affect its angle, not its strength. Wind angle can also be animated and controlled either with a point or with a slider.
How to install:
- Place the “Damian_Binder” folder inside your .nuke folder.
- Add this to your init.py file located in your .nuke folder:
# DAMIAN BINDER TOOLS
nuke.pluginAddPath('./Damian_Binder')
nuke.pluginAddPath('./Damian_Binder/HeatWave')
- Add this to your menu.py file also located in your .nuke folder:
# DAMIAN BINDER TOOLS
toolbar = nuke.toolbar('Nodes')
m = toolbar.addMenu('DamianBinder', icon='DamianBinderNukeLogo.png')
m.addCommand('HeatWave', 'nuke.createNode(\'HeatWave\')', icon='HeatWave_Icon.png')
*** If you don't have init.py and menu.py files inside your .nuke folder, use the ones provided.
*** If the folder “Damian_Binder” already exists in your .nuke folder (because of already installed tools by Damian Binder like DefocusPlus or Looper for example), move the “HeatWave” folder (located inside the downloaded “Damian_Binder” folder) to the already installed “Damian_Binder” folder.
*** If you have older versions of HeatWave installed (like v3.0), take into consideration that HeatWave v4.0 now has its own dedicated folder inside the “Damian_Binder” folder. Older versions had two separate folders (Gizmos and Icons) which should be removed to ensure that the latest version is being loaded correctly.
Please login in order to download these files.
Comments
Thanks!
addUserKnob {52 CREDITS T "nuke.thisNode( ).knob(\"Credit s\").setValue(\ "\"%(nuke.plugi nPath()[[i for i, s in enumerate(nuke. pluginPath()) if '/Damian_Binder /icons' in s.replace(nuke. os.sep,'/')][0] ]+'/HeatWave_cr edits.png'))" +STARTLINE}
edit:
nukepedia screws up the spacing in the text above, so copy from here instead: https://pastebin.com/raw/JWrVMJik
It's a bit weird since i've tested it on Windows too and it was working fine. I might just remove the header completely in future updates since it takes a lot of space and it is not really practical. Will see. I hope that at least the rest of the tool is working fine for you!
I switched the if statement to:
Quote: and it took care of the issue :)
p0 disabled , so how can I enable it like your doing .
works perfectly fine with nuke 10.0v2
First of all, love the tool! But I keep getting some strange results.
I sometimes noticed the heatwave "image" and "mask" input keeps connecting to random nodes after saving and reopening.
Any chance you might know what could cause this issue?
quote name="Remco Consten"]Hi Damian,
First of all, love the tool! But I keep getting some strange results.
I sometimes noticed the heatwave "image" and "mask" input keeps connecting to random nodes after saving and reopening.
Any chance you might know what could cause this issue?
Aldo this has never happened to me personally, I had some users telling me that they were having the same issue. I have the suspicion that it might be an onCreate callback which nuke doesn't seem to handle very well. Here is something you could try:
1. Convert the gizmo to a group.
2. Copy the group and paste it in a text editor.
3. Look for this line near the start and delete it:
onCreate "node = nuke.thisNode() \n\nw = node.width()/2\ n\nh = node.height()/2 +300\n\nif not node.knob('firs tCreation').val ue():\n\n node.knob('p1') .setValue((w,h) )\n\n node.knob('firstCreation').setValue(True)"
4. Select all the text and copy/paste it back to nuke.
Let me know if this fixes it so I can keep it in mind for future updates.
I had the same problem as Remco, when opening saved comp, mask inputs were randomly disconnected (Nuke 12.0 in Linux). Deleting this line from gizmo seems to have fixed it.
I tried the fix above but it didn't work
https://drive.google.com/file/d/1At3TER1bdJXdnt20p56WwtfjWZ1lWUX_/view?usp=sharingRSS feed for comments to this post