Houdini Main Changelogs
 |
6.0.193 | Default cone angle parmeter in Light objects has been changed from 180 to 45. |
Mon. January 27, 2003 |
|
6.0.193 | Default cone angle parmeter in Light objects has been changed from 180 to 45. |
Mon. January 27, 2003 |
|
6.0.193 | Default cone angle parmeter in Light objects has been changed from 180 to 45. |
Mon. January 27, 2003 |
|
6.0.193 | Added new parameter to light object "Use Far Clipping Plane as Active Radius". This parameter, not yet implemented in mantra, will limit the light's effect beyond a certain radius. |
Mon. January 27, 2003 |
|
6.0.193 | Added new parameter to light object "Use Far Clipping Plane as Active Radius". This parameter, not yet implemented in mantra, will limit the light's effect beyond a certain radius. |
Mon. January 27, 2003 |
|
6.0.193 | Added new parameter to light object "Use Far Clipping Plane as Active Radius". This parameter, not yet implemented in mantra, will limit the light's effect beyond a certain radius. |
Mon. January 27, 2003 |
|
6.0.193 | Added new parameter to light object "Use Far Clipping Plane as Active Radius". This parameter, not yet implemented in mantra, will limit the light's effect beyond a certain radius. |
Mon. January 27, 2003 |
|
6.0.193 | Added new parameter to light object "Use Far Clipping Plane as Active Radius". This parameter, not yet implemented in mantra, will limit the light's effect beyond a certain radius. |
Mon. January 27, 2003 |
 |
6.0.190 | Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools". |
Fri. January 24, 2003 |
|
6.0.190 | Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools". |
Fri. January 24, 2003 |
|
6.0.190 | Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools". |
Fri. January 24, 2003 |
|
6.0.190 | Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools". |
Fri. January 24, 2003 |
|
6.0.190 | Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools". |
Fri. January 24, 2003 |
|
6.0.190 | When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging. |
Fri. January 24, 2003 |
|
6.0.190 | When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging. |
Fri. January 24, 2003 |
|
6.0.190 | When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging. |
Fri. January 24, 2003 |
|
6.0.190 | When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging. |
Fri. January 24, 2003 |
|
6.0.190 | When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging. |
Fri. January 24, 2003 |
 |
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. This means that some scripts may have to be adjusted to work correctly. |
Fri. January 24, 2003 |
|
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. This means that some scripts may have to be adjusted to work correctly. |
Fri. January 24, 2003 |
|
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. This means that some scripts may have to be adjusted to work correctly. |
Fri. January 24, 2003 |
|
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. This means that some scripts may have to be adjusted to work correctly. |
Fri. January 24, 2003 |
|
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. This means that some scripts may have to be adjusted to work correctly. |
Fri. January 24, 2003 |
|
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. |
Fri. January 24, 2003 |
|
6.0.190 | The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example: # # hscript quit command # set RESPONSE = yes quit $RESPONSE If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation. |
Fri. January 24, 2003 |