Procedural surface complexity for CG integration.

Watch on YouTube

0:00
0:00

Get it

Download on GitHub
  1. Download the aeTools repository from GitHub as a ZIP, or clone it. One download brings every tool.
  2. Copy the Aitor_Echeveste folder into your .nuke folder.
  3. Add nuke.pluginAddPath("./Aitor_Echeveste") to .nuke/init.py and restart Nuke.

In the gizmo

  • Procedural noise generation
  • Multiple independently adjustable noise patterns
  • Colour and luminance variation
  • Position-based workflow
  • Deep workflow
  • Motion blur support
  • Noise preview outputs
  • Dedicated precomp/output modes

The quickest way to make a CG element look less sterile is to add imperfections. The quickest way to give the trick away is to attach those imperfections to the screen instead of the object. As soon as the camera moves, screen-space noise swims across the surface, and the eye reads it as a filter rather than dirt.

Procedural breakup added to a clean CG render, driven by position data.

Noise needs an address

Procedural noise is a function you sample at a coordinate. Sample it at screen coordinates and it stays with the frame; sample it at a position on the object and it stays with the object. aeDirtCG reads position data, from an image position pass or from Deep, so each pattern is evaluated where the surface is, not where the pixel is.

The noise stays on the object as it moves, because it's sampled in 3D space, not on the screen.

P or Pref?

A position pass (P) records, for each visible pixel, where that point is on this frame, in whatever space the renderer wrote it, usually world space. A reference position (Pref) records where the same point was at a chosen rest state. For a rigid object that only moves, the two behave alike once the motion is accounted for; on a deforming one, noise driven by P stretches and slides as the shape changes, while noise driven by Pref follows the surface, as long as the reference was generated consistently for that geometry. They are not interchangeable, and Pref is position data, not metadata.

Check which space your passes are in before tuning anything: the noise is only as stable as the coordinates it reads.

One noise is not a material

Real wear varies at several scales and changes different properties. aeDirtCG keeps them separate: patterns for luminance, contrast, saturation and an alpha mask, each with its own size and mix, so you can preview each contribution on its own. Subtlety is the point; stack them all at full strength and it reads as procedural.

When the noise misbehaves

Image position pass or Deep?
Both are supported. In the creator's experience Deep can give fewer artefacts, provided the camera and data are set up correctly; it isn't a guarantee for every shot.
It's getting slow. What can I do?
Motion blur and several noise layers add up. Precomp the noise once the look is set.

Goes well withaeUVChart + aePrefMakeraeShadows