• Page
• Discussion
• View source
• History

From Odwiki

What are they?

An index file provides a way to define custom operators for Houdini. This method as been obsoleted by OTLs, but is still supported by Houdini.

There are several index files supported by Houdini

• SHOPsurface, SHOPdisplace,SHOPfog, etc
• VEXsop, VEXpop, etc

The file in the same location called VEXdso is not a regular index file although it looks like one. It's a file that get read by Houdini programs to attach VEX custom DSOs written in C++ with the HoudiniDevelopmentKit. This file must be in a directory in the compound path "HOUDINI_VEX_PATH".

Whats in an Index File?

An index file contains lines of the form:

 op_name  path_to_dialog_script   -label "Operator Label" [other options]

Where other options include:

• -mininputs
• -maxinputs
• -inputs
• -icon

The path_to_dialog_script is a reference to an external DialogueScript. The path is searched using the HOUDINI_PATH, so it's possible to specify a partial path. For example:

 v_lensflare   vex/Fog/lensflare.ds  -label "VEX Lens Flare"

This example would search the HOUDINI_PATH for the first dialog named vex/Fog/lensflare.ds. So, for example, Houdini might search for

1. $HFS/houdini/vex/Fog/lensflare.ds
2. $HOME/houdini6.0/vex/Fog/lensflare.ds
3. etc.

depending on what the HOUDINI_PATH was set to.