Houdini Main Changelogs

6.0.131

The run() and execute() expression functions have changed their behaviour. Now, trailing new-lines will be stripped from the result of the run(). As well, all embedded new-lines and tabs in the result are converted to space characters.

Tue. November 26, 2002
6.0.131

Fixed bug where Houdini would hang if you tried to drag a zero length channel segment backwards using a time group in the channel graph editor.

Tue. November 26, 2002
6.0.131

Fixed bug where Houdini would hang if you tried to drag a zero length channel segment backwards using a time group in the channel graph editor.

Tue. November 26, 2002
6.0.131

Fixed bug where Houdini would hang if you tried to drag a zero length channel segment backwards using a time group in the channel graph editor.

Tue. November 26, 2002
6.0.131

Fixed bug where Houdini would hang if you tried to drag a zero length channel segment backwards using a time group in the channel graph editor.

Tue. November 26, 2002
6.0.131

Fixed bug where Houdini would hang if you tried to drag a zero length channel segment backwards using a time group in the channel graph editor.

Tue. November 26, 2002
6.0.131

Added new local variable SLIDING, which is used to query the sliding state of the particle. Parameters have also been added to the State pop to control this state flag.

Tue. November 26, 2002
6.0.131

Added new local variable SLIDING, which is used to query the sliding state of the particle. Parameters have also been added to the State pop to control this state flag.

Tue. November 26, 2002
6.0.131

Added new local variable SLIDING, which is used to query the sliding state of the particle. Parameters have also been added to the State pop to control this state flag.

Tue. November 26, 2002
6.0.131

Added new local variable SLIDING, which is used to query the sliding state of the particle. Parameters have also been added to the State pop to control this state flag.

Tue. November 26, 2002
6.0.131

Added new local variable SLIDING, which is used to query the sliding state of the particle. Parameters have also been added to the State pop to control this state flag.

Tue. November 26, 2002
6.0.131

Previously, when ray-tracing was turned off in mantra (i.e. -q 4), shadow shaders would not be run on lights. This was incorrect behaviour and is now corrected. However, if the shadow shader makes ray-tracing calls (i.e. fastshadow()), these calls will still "fail" in that no rays will be cast.

Tue. November 26, 2002
6.0.131

Previously, when ray-tracing was turned off in mantra (i.e. -q 4), shadow shaders would not be run on lights. This was incorrect behaviour and is now corrected. However, if the shadow shader makes ray-tracing calls (i.e. fastshadow()), these calls will still "fail" in that no rays will be cast.

Tue. November 26, 2002
6.0.131

Previously, when ray-tracing was turned off in mantra (i.e. -q 4), shadow shaders would not be run on lights. This was incorrect behaviour and is now corrected. However, if the shadow shader makes ray-tracing calls (i.e. fastshadow()), these calls will still "fail" in that no rays will be cast.

Tue. November 26, 2002
6.0.131

Previously, when ray-tracing was turned off in mantra (i.e. -q 4), shadow shaders would not be run on lights. This was incorrect behaviour and is now corrected. However, if the shadow shader makes ray-tracing calls (i.e. fastshadow()), these calls will still "fail" in that no rays will be cast.

Tue. November 26, 2002
6.0.131

Previously, when ray-tracing was turned off in mantra (i.e. -q 4), shadow shaders would not be run on lights. This was incorrect behaviour and is now corrected. However, if the shadow shader makes ray-tracing calls (i.e. fastshadow()), these calls will still "fail" in that no rays will be cast.

Tue. November 26, 2002
6.0.130

The system() expression has changed its behaviour with every long lines. It would previously insert an extra " " every 1k lines, and stop after 16k lines. It now only inserts " " at line ends in the source, and can handle arbitrarily long lines.

Mon. November 25, 2002
6.0.130

The system() expression has changed its behaviour with every long lines. It would previously insert an extra " " every 1k lines, and stop after 16k lines. It now only inserts " " at line ends in the source, and can handle arbitrarily long lines.

Mon. November 25, 2002
6.0.130

The system() expression has changed its behaviour with every long lines. It would previously insert an extra " " every 1k lines, and stop after 16k lines. It now only inserts " " at line ends in the source, and can handle arbitrarily long lines.

Mon. November 25, 2002
6.0.130

The system() expression has changed its behaviour with every long lines. It would previously insert an extra " " every 1k lines, and stop after 16k lines. It now only inserts " " at line ends in the source, and can handle arbitrarily long lines.

Mon. November 25, 2002
6.0.130

The system() expression has changed its behaviour with every long lines. It would previously insert an extra " " every 1k lines, and stop after 16k lines. It now only inserts " " at line ends in the source, and can handle arbitrarily long lines.

Mon. November 25, 2002
6.0.130

The chls command has a new option, -v, which can be used with the -l option. This will cause it to print verbose information about the keyframe, listing the incoming and outgoing values, slopes, and accelerations, along with the tie status of the keyframe.

Mon. November 25, 2002
6.0.130

The chls command has a new option, -v, which can be used with the -l option. This will cause it to print verbose information about the keyframe, listing the incoming and outgoing values, slopes, and accelerations, along with the tie status of the keyframe.

Mon. November 25, 2002
6.0.130

The chls command has a new option, -v, which can be used with the -l option. This will cause it to print verbose information about the keyframe, listing the incoming and outgoing values, slopes, and accelerations, along with the tie status of the keyframe.

Mon. November 25, 2002
6.0.130

The chls command has a new option, -v, which can be used with the -l option. This will cause it to print verbose information about the keyframe, listing the incoming and outgoing values, slopes, and accelerations, along with the tie status of the keyframe.

Mon. November 25, 2002