X_Aton v1.1


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Xavier Martín
Website: www.xaviermartinvfx.com
This tool is an advanced variation on the God Rays node. It creates volumetric lighting effects with more realism. It supports soft and diffused light rays created by area lights and volumetric lights. It supports Nuke 3D Cameras, Point Lights and Axis to have a better control of the direction of the illumination.
Requirements:
11.0, 10.5, 9.0 or later
Linux, Windows
14 Nov 2017
5170
 Settings

X_Aton

This tool is an advanced variation on the God Rays node. It creates volumetric lighting effects with more realism. It supports soft and diffused light rays created by area lights and volumetric lights.

It supports Nuke 3D Cameras, Point Lights and Axis to have a better control of the direction of the illumination. The tool can also be used as a simple screen-space extruder, to create apparent 3D texts or extruded shapes. Now you can do WordArt from the 90s inside of Nuke!

All of this using the power of the GPU to speed up the calculations.

More documentation on my website.

Nukepedia BAr

Aton Rays-min-minFog Rays-min

Please login in order to download these files.

Comments   

 
+1 # Frank Rueter 2017-11-09 03:55
nice. It seems to crop to the incoming bounding box though.
 
 
+1 # Xavier Martín 2017-11-09 10:15
Oh, thanks for letting me know! Will fix it and upload a new version ASAP! :D
 
 
0 # Xavier Martín 2017-11-14 21:46
This issue has been resolved in version 1.1!
 
 
+1 # Erwan Leroy 2017-11-21 22:48
I'm still having bounding box issues with 1.1.
I'm just doing a text and X_Aton right after. and only diffuse mode changes the BBox, and not really the right way.
 
 
0 # Erwan Leroy 2017-11-21 22:52
Also, not working in Proxy mode, which is common with blinkscripts as they are not aware that Proxy has been turned on, have to catch it with a nuke expression on an extra property.
 
 
0 # Xavier Martín 2017-11-22 00:34
Hi Erwan.

Can you be more specific so I can locate the problem?
The kernel is only executed within your bbox bounds. If I resized them automatically to fit the whole effect you could easily get infinite bounding boxes if a light gets too close from the camera and that could cause Nuke to crash.

Therefore:
- Regular, Brightest and Darkest modes shouldn't affect the bounding box.
- Diffuse mode might slightly increase your bouding box to account for the light scattering, but that's it.

If you are applying the effect to a text, make sure the bounding box covers the whole frame you want to render.

This is to ensure maximum performance and minimum memory usage. :)

The file comes with an examples.nk where you will find a shiny text example. If you think your issue is something different, feel free to describe it and I'll try and recreate it to fix the issue.
 
 
0 # Erwan Leroy 2017-11-24 16:27
Hey Xavier,

I edited the gizmo to show you what I meant with the BBox.
I also added support for proxy mode (only in the first blink script, and only in mode == 0). It's not perfect proxy support either since it only takes the proxy scale in X into account, but I never used non uniform proxies so I think it's acceptable.
See it here: https://pastebin.com/tamCQybS
 
 
0 # Xavier Martín 2017-11-24 19:14
Hi Erwan,
Thanks so much for your example! I will definitely try and implement that option in the next release!
;-)
 
 
+1 # Paul Loop 2017-11-09 21:54
Oh, thank You very much, Xavier. It has been always pain in ass to achieve such effect in nuke before.
 
 
0 # Paul Loop 2017-11-10 10:46
Also it would be great to be able to get the efect itself, like in glow node, without original image
 
 
0 # Mike Connolly 2017-11-12 22:52
Javier, not being sure whether it's my lack of modern hardware/GPU power on my laptop, the scale of my scene or whatever, I have a camera, an object in front, and a light thing towards me, but whatever I twiddle, nothing happens... do you have a example script for a simple setup please? Apart from not working, it's exactly what I need at the mo... thankyou.
 
 
0 # Xavier Martín 2017-11-12 23:24
Hi Mike! I've set up a quick example for you.
https://pastebin.com/uSth3X89
Great idea! I will include all the .nk files of the examples I have on my website so people can quickly learn how to use the tool. Let me know if you got it to work. :)
 
 
0 # Mike Connolly 2017-11-13 14:03
Quoting Xavier Martín:
Hi Mike! I've set up a quick example for you.
https://pastebin.com/uSth3X89
Great idea! I will include all the .nk files of the examples I have on my website so people can quickly learn how to use the tool. Let me know if you got it to work. :)

Javier, thankyou for that - it all works, so it was the lump of flesh at my end that was the issue, not my hardware. v cool, just what I needed, thankyou!
 
 
0 # Xavier Martín 2017-11-14 21:47
Version 1.1 comes with a few example scenes to create backlit texts, holograms and even WordArt!
 
 
-1 # Mike Connolly 2017-11-14 22:39
Top banana! v cool, thanks.
 
 
+1 # R W 2018-01-26 19:29
Thanks for making this plugin. I just wanted to note that the latest download of the documentation seems to be incorrect.
When it says to add the line:
Quote:
nuke.pluginAddPath('./X_Tools/Gizmos')
It should read:
Quote:
nuke.pluginAddPath('./X_Tools/Tools')
To account for the folder structure in the downloaded plugin.
 
 
0 # Mladen Pajdic 2018-05-11 05:41
Sorry, I did everything by instruction, but I get an error:
X_ATON: UNKNOWN COMMAND
 
 
0 # Stefan Nguyen 2021-04-01 04:03
Quoting Mladen Pajdic:
Sorry, I did everything by instruction, but I get an error:
X_ATON: UNKNOWN COMMAND



When it says to add the line:

Quote:
nuke.pluginAddPath('./X_Tools/Gizmos')


It should read:

Quote:
nuke.pluginAddPath('./X_Tools/Tools')
 
 
0 # J R 2018-09-01 10:12
Hey Xavier, thanks for the great tool! We're noticing that it drops the location of the light for 1 frame, every 10 frames, when rendering on a farm. It might be that exposing and using the "create keyframes" button in the Reconcile3D node would fix this? We think it's when a new machine picks up the next batch of 10 frames, so baking that animation instead of keeping it live might help.

Cheers!
 
 
0 # Florian Dehmel 2019-09-25 09:22
Quoting J R:
Hey Xavier, thanks for the great tool! We're noticing that it drops the location of the light for 1 frame, every 10 frames, when rendering on a farm. It might be that exposing and using the "create keyframes" button in the Reconcile3D node would fix this? We think it's when a new machine picks up the next batch of 10 frames, so baking that animation instead of keeping it live might help.



Cheers!


Same here
 
 
+2 # darren coombes 2020-10-07 09:05
Getting these errors in Nuke 12.2v3 Mac OSX

Warning: X_Aton1.BlinkSc ript2.maxTileLi nes: no such knob
X_Aton1.BlinkScript2.100: no such knob
Warning: X_Aton1.BlinkSc ript1.maxTileLi nes: no such knob
X_Aton1.BlinkScript1.100: no such knob
Warning: X_Aton1.BlinkSc ript4.maxTileLi nes: no such knob
X_Aton1.BlinkScript4.100: no such knob
Warning: X_Aton1.BlinkSc ript3.maxTileLi nes: no such knob
X_Aton1.BlinkScript3.100: no such knob
ERROR: Text2.font: Font (impact.ttf:0) not available.
Warning: X_Aton2.BlinkSc ript2.maxTileLi nes: no such knob
X_Aton2.BlinkScript2.100: no such knob
Warning: X_Aton2.BlinkSc ript1.maxTileLi nes: no such knob
X_Aton2.BlinkScript1.100: no such knob
Warning: X_Aton2.BlinkSc ript4.maxTileLi nes: no such knob
X_Aton2.BlinkScript4.100: no such knob
Warning: X_Aton2.BlinkSc ript3.maxTileLi nes: no such knob
X_Aton2.BlinkScript3.100: no such knob
ERROR: Text3.font: Font (impact.ttf:0) not available.
Warning: X_Aton3.BlinkSc ript2.maxTileLi nes: no such knob
X_Aton3.BlinkScript2.100: no such knob
Warning: X_Aton3.BlinkSc ript1.maxTileLi nes: no such knob
X_Aton3.BlinkScript1.100: no such knob
Warning: X_Aton3.BlinkSc ript4.maxTileLi nes: no such knob
X_Aton3.BlinkScript4.100: no such knob
Warning: X_Aton3.BlinkSc ript3.maxTileLi nes: no such knob
X_Aton3.BlinkScript3.100: no such knob
Warning: X_Aton3.BlinkSc ript2.maxTileLi nes: no such knob
X_Aton3.BlinkScript2.100: no such knob
Warning: X_Aton3.BlinkSc ript1.maxTileLi nes: no such knob
X_Aton3.BlinkScript1.100: no such knob
Warning: X_Aton3.BlinkSc ript4.maxTileLi nes: no such knob
X_Aton3.BlinkScript4.100: no such knob
Warning: X_Aton3.BlinkSc ript3.maxTileLi nes: no such knob
X_Aton3.BlinkScript3.100: no such knob
 
 
0 # dean lewis 2020-10-19 21:38
same.
 
 
+1 # Kento Fukuda 2021-08-06 01:36
Probably because the BlinkScript node has changed a bit since nuke 12.1, some parameters have been removed. This parameter was intended to streamline the process, and since nuke 12.1, this process has been done automatically. Therefore, you can ignore this error.
(This may have been difficult to read due to the automatic translation...)
 

You have no rights to post comments

We have 2284 guests and 68 members online