Versioning Shader Compounds

 
 
 

As you create shader compounds, you'll find that you will probably want to create several versions of it, either for fixing bugs or for adding enhancements. You can have control over the versions of shader compounds in a manner that is similar to that of ICE compounds.

This section describes the only issues that are specific to shader compounds, but you can find basic information about versioning ICE compounds in Versioning Compounds.

These are the main differences between versioning ICE and shader compounds:

Modifying the Version of a Shader Compound

For complete control over a compound's version numbers, you need to modify the version numbers in the compound's properties and re-export it, as described below.

Shader compounds that already exist in a scene are not updated automatically even if new versions are available. However, you can update them using The Shader Version Manager.

  1. Open the compound's properties as described in Editing Shader Compound Properties.

  2. Increase the Version number as appropriate:

    • Update the major version for changes in functionality, such as additional nodes and exposed ports.

    • Update the minor version number for bug fixes.

  3. If desired, enter a Version Tag. This is a character string that you can use to describe this version.

  4. Export the compound as described in Exporting Compounds.

  5. After you update the shader compound version in a scene, you can right-click on a shader compound's node in the render tree, choose the Version menu, then select which of the compound's versions you want to use.

    You can also use the The Shader Version Manager to select which compound version to use.

Creative Commons License Except where otherwise noted, this work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License