Fixed a bug where deleting a vopnet could end up effectively de-registering unrelated viewer states with the same name.

Fixed a bug where deleting a vopnet could end up effectively de-registering unrelated viewer states with the same name.

Fixed a bug where deleting a vopnet could end up effectively de-registering unrelated viewer states with the same name.

Fixed a bug where deleting a vopnet could end up effectively de-registering unrelated viewer states with the same name.

Added support for python startup and post load scripts, 123.py and 456.py. Place these files in $HOME/houdini9.0/scripts if you want them executed instead of Houdini's default scripts. Optionally, you can set the environment variable, HOUDINI_SCRIPT_PATH, to include the directory which contain your scripts.

As a note, if you have 123.py and 123.cmd in the same directory, 123.py will take precendence and be run by Houdini (same goes for 456.py).

Added support for python startup and post load scripts, 123.py and 456.py. Place these files in $HOME/houdini9.0/scripts if you want them executed instead of Houdini's default scripts. Optionally, you can set the environment variable, HOUDINI_SCRIPT_PATH, to include the directory which contain your scripts.

As a note, if you have 123.py and 123.cmd in the same directory, 123.py will take precendence and be run by Houdini (same goes for 456.py).

Added support for python startup and post load scripts, 123.py and 456.py. Place these files in $HOME/houdini9.0/scripts if you want them executed instead of Houdini's default scripts. Optionally, you can set the environment variable, HOUDINI_SCRIPT_PATH, to include the directory which contain your scripts.

As a note, if you have 123.py and 123.cmd in the same directory, 123.py will take precendence and be run by Houdini (same goes for 456.py).

Added support for python startup and post load scripts, 123.py and 456.py. Place these files in $HOME/houdini9.0/scripts if you want them executed instead of Houdini's default scripts. Optionally, you can set the environment variable, HOUDINI_SCRIPT_PATH, to include the directory which contain your scripts.

As a note, if you have 123.py and 123.cmd in the same directory, 123.py will take precendence and be run by Houdini (same goes for 456.py).

Added support for python startup and post load scripts, 123.py and 456.py. Place these files in $HOME/houdini9.0/scripts if you want them executed instead of Houdini's default scripts. Optionally, you can set the environment variable, HOUDINI_SCRIPT_PATH, to include the directory which contain your scripts.

As a note, if you have 123.py and 123.cmd in the same directory, 123.py will take precendence and be run by Houdini (same goes for 456.py).

When specifying image data types (i.e. the -b option to mantra, the -d option on iconvert), it's now possible to specify the format as an integer with either an i or f suffix. For example, 16f (16 bit float), 32f (32 bit float), 16i (16 bit integer), 8i (8 bit integer).

When specifying image data types (i.e. the -b option to mantra, the -d option on iconvert), it's now possible to specify the format as an integer with either an i or f suffix. For example, 16f (16 bit float), 32f (32 bit float), 16i (16 bit integer), 8i (8 bit integer).

When specifying image data types (i.e. the -b option to mantra, the -d option on iconvert), it's now possible to specify the format as an integer with either an i or f suffix. For example, 16f (16 bit float), 32f (32 bit float), 16i (16 bit integer), 8i (8 bit integer).

When specifying image data types (i.e. the -b option to mantra, the -d option on iconvert), it's now possible to specify the format as an integer with either an i or f suffix. For example, 16f (16 bit float), 32f (32 bit float), 16i (16 bit integer), 8i (8 bit integer).

When specifying image data types (i.e. the -b option to mantra, the -d option on iconvert), it's now possible to specify the format as an integer with either an i or f suffix. For example, 16f (16 bit float), 32f (32 bit float), 16i (16 bit integer), 8i (8 bit integer).

Nodes' colours are now displayed again.

Nodes' colours are now displayed again.

Nodes' colours are now displayed again.

Nodes' colours are now displayed again.

Nodes' colours are now displayed again.

Dragging an operator path onto the Parameter Pane's path gadget now pins the pane.