There is now a local variable defined for objects which is used when performing point instancing for renderers. The $IPT variable will be set to the point number where the geometry is being instanced. If no instancing is being performed this variable will be set to -1.

For example, if a light has point instancing turned on in its render tab, the $IPT variable can be used to "switch" parameters based on the point which the light is being instanced at. For example, the shadow map might be set to '$HOUDINI_TEMP_DIR/$OS.$IPT.pic' which would be expanded to something like '/tmp/light1.2.pic' (for the instance on point number 2 of the instance geometry).

The $IPT variable can also be used when performing geometry instancing (the $IPT variable is defined on parameters of the geometry object which has point instancing turned on, not the geometry objects being instanced).

There is now a local variable defined for objects which is used when performing point instancing for renderers. The $IPT variable will be set to the point number where the geometry is being instanced. If no instancing is being performed this variable will be set to -1.

For example, if a light has point instancing turned on in its render tab, the $IPT variable can be used to "switch" parameters based on the point which the light is being instanced at. For example, the shadow map might be set to '$HOUDINI_TEMP_DIR/$OS.$IPT.pic' which would be expanded to something like '/tmp/light1.2.pic' (for the instance on point number 2 of the instance geometry).

The $IPT variable can also be used when performing geometry instancing (the $IPT variable is defined on parameters of the geometry object which has point instancing turned on, not the geometry objects being instanced).

There is now a local variable defined for objects which is used when performing point instancing for renderers. The $IPT variable will be set to the point number where the geometry is being instanced. If no instancing is being performed this variable will be set to -1.

For example, if a light has point instancing turned on in its render tab, the $IPT variable can be used to "switch" parameters based on the point which the light is being instanced at. For example, the shadow map might be set to '$HOUDINI_TEMP_DIR/$OS.$IPT.pic' which would be expanded to something like '/tmp/light1.2.pic' (for the instance on point number 2 of the instance geometry).

The $IPT variable can also be used when performing geometry instancing (the $IPT variable is defined on parameters of the geometry object which has point instancing turned on, not the geometry objects being instanced).

The Light and Camera Orientation handles now have the ability to auto-resize themselves so that they stay visible in a large scale scene. The handles will resist overlapping one another and thus must have the focus point and camera origin far enough apart.

The Light and Camera Orientation handles now have the ability to auto-resize themselves so that they stay visible in a large scale scene. The handles will resist overlapping one another and thus must have the focus point and camera origin far enough apart.

The Light and Camera Orientation handles now have the ability to auto-resize themselves so that they stay visible in a large scale scene. The handles will resist overlapping one another and thus must have the focus point and camera origin far enough apart.

The Light and Camera Orientation handles now have the ability to auto-resize themselves so that they stay visible in a large scale scene. The handles will resist overlapping one another and thus must have the focus point and camera origin far enough apart.

The Light and Camera Orientation handles now have the ability to auto-resize themselves so that they stay visible in a large scale scene. The handles will resist overlapping one another and thus must have the focus point and camera origin far enough apart.

When building custom HDK objects, the code to handle template construction has changed. Please see sample code OBJ_Shake.C for the new method for inheriting templates.

When building custom HDK objects, the code to handle template construction has changed. Please see sample code OBJ_Shake.C for the new method for inheriting templates.

When building custom HDK objects, the code to handle template construction has changed. Please see sample code OBJ_Shake.C for the new method for inheriting templates.

When building custom HDK objects, the code to handle template construction has changed. Please see sample code OBJ_Shake.C for the new method for inheriting templates.

When building custom HDK objects, the code to handle template construction has changed. Please see sample code OBJ_Shake.C for the new method for inheriting templates.

When loading a hip file, if an error occurs during the synchronization of a locked operator type, that error is propogated up so that a warning dialog appears. This also occurs when creating a new instance of a locked subnet operator type which contains other locked subnet operators.

When loading a hip file, if an error occurs during the synchronization of a locked operator type, that error is propogated up so that a warning dialog appears. This also occurs when creating a new instance of a locked subnet operator type which contains other locked subnet operators.

When loading a hip file, if an error occurs during the synchronization of a locked operator type, that error is propogated up so that a warning dialog appears. This also occurs when creating a new instance of a locked subnet operator type which contains other locked subnet operators.

When loading a hip file, if an error occurs during the synchronization of a locked operator type, that error is propogated up so that a warning dialog appears. This also occurs when creating a new instance of a locked subnet operator type which contains other locked subnet operators.

When loading a hip file, if an error occurs during the synchronization of a locked operator type, that error is propogated up so that a warning dialog appears. This also occurs when creating a new instance of a locked subnet operator type which contains other locked subnet operators.

All Event scripts (see the Events page of the Type Properties dialog) now are passed take an additional argument which is the class and name of the operator type for which the script is being run.

All Event scripts (see the Events page of the Type Properties dialog) now are passed take an additional argument which is the class and name of the operator type for which the script is being run.

All Event scripts (see the Events page of the Type Properties dialog) now are passed take an additional argument which is the class and name of the operator type for which the script is being run.

All Event scripts (see the Events page of the Type Properties dialog) now are passed take an additional argument which is the class and name of the operator type for which the script is being run.

All Event scripts (see the Events page of the Type Properties dialog) now are passed take an additional argument which is the class and name of the operator type for which the script is being run.

Fixed pathcv object again so that it doesn't give warnings when loading.

Fixed pathcv object again so that it doesn't give warnings when loading.