Render Passes

Rendering means taking the elements of a scene, including the lighting, camera position, and the geometry of the objects in the scene, and using those to compute an image. After the initial pass, we can perform additional render passes to create postprocessing effects. These passes can use the initial image output, along with intermediary structures computed during the previous pass—for example the depth buffer—to produce another image. Depth of field is a classic example of a postprocessing effect, using the depth buffer to apply a blur proportional to the distance from the camera. Multiple passes can be chained together to produce complex effects.

Using jit.gl.pass

The jit.gl.pass object provides a high-level, text-based way to describe a render pass. Working with a pass description file (a .jxp file), you can combine Jitter shaders defined in text (.jxs files) with Gen-based Jitter shaders (.genjit files) to create a final, complex shader with multiple stages.

Because a jit.gl.pass object works with intermediate render targets like the depth buffer, it works differently from objects like jit.gl.slab or jit.gl.pix, which can work as simple video effects. The jit.gl.pass object always works with a jit.gl.node object, even if it's the internal jit.gl.node object in a jit.world object.

The typical use pattern for jit.gl.pass is to bind jit.gl.pass to a jit.gl.node object with the same name. Multiple jit.gl.pass objects can be connected together to create complex effects. Finally, the texture output of the last jit.gl.pass object is connected to a jit.gl.layer object to be displayed in the root rendering context.

The JXP File Format

To determine its behavior, a jit.gl.pass object loads a Jitter Pass file: a specially-formatted XML file that defines one or more render passes. Every JXP file has a <jitterpass> node as its root.

<jitterpass>
    <!-- Pass definitions go here -->
</jitterpass>

The <pass> tag

The <jitterpass> tag can contain multiple <pass> tags, each of which defines one pass.

<jitterpass>
  <pass name="passname">
    <!-- Pass definition here -->
  </pass>
</jitterpass>

Each <pass> must have a name attribute, which is the identifier that a jit.gl.pass will use with the @fxname attribute to load the pass definition. For built-in pass definitions, the @fxname attribute is sufficient to select the pass. To load a custom pass definition, use the @file attribute to load the custom pass file, followed by @fxname to load the specific pass.

The <bind> tag

At the top of a <pass> tag, you can can use the <bind> tag to create a binding between Max attributes and shader parameters. Use the name attribute to define the name of the attribute as it will appear in Max. The param attribute will specify which shader parameter to bind to. The param attribute will bind to the first shader parameter among <subpass> tags with a matching name.

The <subpass> tag

Each <pass> tag contains one or more <subpass> tags. These <subpass> tags define which shader program to load, as well as how that shader should connect to the various input sources available (see subpass sources). To load a shader, set the file attribute to load a Jitter shader (a .jxs file), or set the gen attribute to load a jit.gl.pix shader (a .genjit file).

<jitterpass>
  <pass name="passname">
    <subpass file="cf.radialblur.jxs">
      <!-- subpass inputs -->
    </subpass>
    <subpass gen="kaleido.genjit">
      <!-- subpass inputs -->
    </subpass>
  </pass>
</jitterpass>

A <subpass> tag can also have a name, allowing it to be referred to as an input by other subpasses. Finally, a subpass can also use the dimscale attribute to scale the size of any dimension of the output texture, and the rect attribute to adjust or invert the subpass texture coordinates. See the object reference for jit.gl.pix for more.

<jitterpass>
  <pass name="passname">
    <!-- a named subpass can be referred to by other subpasses -->
    <subpass file="cf.radialblur.jxs" name="subpass_name">
    </subpass>

    <!-- here dimscale will downsample (shrink) the output texture -->
    <subpass file="cf.radialblur.jxs" dimscale="0.5 0.5">
    </subpass>

    <!-- rect defines normalized texture coordinates, left-bottom-right-top -->
    <!-- used in this way, we could mirror the texture left to right-->
    <subpass file="cf.radialblur.jxs" rect="1 0 0 1">
    </subpass>

    <!-- >
  </pass>
</jitterpass>

Subpass sources

The number of texture inputs to a subpass will depend on the number of texture inputs of its loaded shader. You can connect each input to a different source using the <input> child tag. The input to a subpass can be a named texture, another named subpass, or one of several special sources.

Named texture input

Use the name attribute to specify a named texture as input.

<jitterpass>
  <pass name="passname">
    <subpass file="cf.radialblur.jxs">
      <input name="named_texture" />
    </subpass>
  </pass>
</jitterpass>

Source input

The source tag can get input from any of several special sources.

<jitterpass>
  <pass name="passname">
    <subpass file="hdr.bloom.jxs">
      <input source="VELOCITY" />
    </subpass>
  </pass>
</jitterpass>

Subpass input

Use the subpass attribute to specify another subpass to use as input.

<jitterpass>
  <pass name="passname">
    <subpass file="cf.laplace.jxs" name="laplace">
      <input source="COLOR" />
    </subpass>
    <subpass file="hdr.bloom.jxs">
      <input subpass="laplace" />
    </subpass>
  </pass>
</jitterpass>

The output index of a multi-output subpass input type is specified using an "output" attribute and 0-based indexing. The previous frame of subpass input types can be requested using the history keyword and setting it to 1. For example to set second output of the previous frame as the input.

<input subpass="mysubpass" output="1" history="1" />