Specifies whether the node is a shader; otherwise it’s a building block.

Specifies the mask for the renderers the shader node belongs to. Used for finding a USD shader translator for the shader node.

Specifies the name of the render context (renderer) the shader node applies to. Used for USD material primitive output name namespace identifying the terminal shader primitive.

Specifies the shader name. Used for an asset or an ID attribute of the USD shader primitive.

Specifies the interpretation and meaning of the shader name string returned by a VOP node. Values are 'id', 'asset', or 'code'.

Identifies the type of shader source. Eg 'glsl', 'osl', 'vex' (effectively, the name of the shader’s language).

Specifies the USD path of a shader, material, or graph primitive to author. Useful for creating graph primitives outside of the implied material to drive its inputs.

Specifies the USD pritive type (i.e. schema name) for the USD primitive to author. The names should match schema names, eg 'Material', 'NodeGraph', or 'Shader'. Useful for forcing the translation of a node into a particular USD primitive type, e.g., NodeGraph instead of a Material).

Specifies the USD shader primitive name for this shader.

Specifies the USD material parent primitive name for this shader.

Specifies the USD pritive type (i.e. schema name) for the USD material primitive to author. The names should match schema names, eg 'Material' or 'NodeGraph'. Useful for forcing the translation of a node into a particular USD primitive type, e.g., NodeGraph instead of a Material).

#hprop shader_forceterminaloutput

Make sure the material primitive has a terminal shader output."

#hprop shader_skipdefvalparms

Determines whether to output (or author) only parameters that have non-default values.

#hprop shader_useallparms

Designates all node parameters as shader parms (or not), unless they have an explicit 'shader_isparm' tag that inidcates otherwise.

When true, the shader node is translated into USD Material sibling primitive, rather than as a child (or descendent).

When VOP subnet HDAs reference an existing USD material (thru 'shader_baseprimpath'), their children don’t need to be translated, because the base primitive already has children. However, when this property is set to true, shader translators will translate them anyway.

#hprop shader_referencetype

Specifies whether the translated USD material should reference an existing primitive, and if so, then how.

#hprop shader_baseassetpath

Specifies the file path to the asset that contains a material to reference, when translating the node into a new USD material primitive.

#hprop shader_baseprimpath

Specifies the USD path of a material to be referenced, inherited from, or specialized, when translating the node into a new USD material primitive.

#hprop shader_importbaseparms

Creates spare parameters that correspond to input attributes of the material specified in the 'Base Primitive Path'.

#hprop vop_shader_name

Specifies an explicit shader name for the VOP node.

#hprop vop_force_code_context

Marks the VOP as one of the terminal nodes in the shader of the specified context. This node and its input chains will contribute to the generated shader code.

#hprop vop_shaderlayerexports_inputs

Lists the inputs whose shader layer exports tag should be copied to the output tag.

#hprop vop_shaderlayerexports_add

Lists the shader parameter names that should be added to the shader layer exports output tag. Eg, 'f@vex_export_parm_foo v@bar'.

The prefix is prepended to the names of any parameters promoted to the owner network’s parameter interface. The prefix is live so changes to it are auto-propagated to the promoted parameters.

#hprop vopui_parmpostfix

The postfix is appended to the names of any parameters promoted to the owner network’s parameter interface. The postfix is live so changes to it are auto-propagated to the promoted parameters.

#hprop vopui_infolder

The folder that contains the promoted parameters on the owner network’s parameter interface. Set this parameter to blank to move the promoted parameters to the top-level of the parameter interface. The in-folder parameter is not live so changes to it are not auto-propagated. Click on the 'Move Promoted Parameters' button for in-folder changes to take effect on the owner network’s parameter interface.

#hprop vopui_infolder_update

Move promoted parameters to the folder specified by the 'In-Folder' parameter on the owning network’s parameter interface. The folder is automatically created if it does not yet exist.