Houdini Main Changelogs
 |
6.0.284 | Fixed crash when giving insufficient number of arguments to the "opparm -c" hscript command. |
Mon. April 28, 2003 |
|
6.0.284 | Fixed crash when giving insufficient number of arguments to the "opparm -c" hscript command. |
Mon. April 28, 2003 |
|
6.0.284 | Fixed crash when giving insufficient number of arguments to the "opparm -c" hscript command. |
Mon. April 28, 2003 |
|
6.0.284 | Fixed crash when giving insufficient number of arguments to the "opparm -c" hscript command. |
Mon. April 28, 2003 |
 |
6.0.284 | As the title says: Houdini 6.0 to 6.5 Compatiblity above this line | Mon. April 28, 2003 |
|
6.0.284 | As the title says: Houdini 6.0 to 6.5 Compatiblity above this line | Mon. April 28, 2003 |
|
6.0.284 | As the title says: Houdini 6.0 to 6.5 Compatiblity above this line | Mon. April 28, 2003 |
|
6.0.284 | As the title says: Houdini 6.0 to 6.5 Compatiblity above this line | Mon. April 28, 2003 |
|
6.0.284 | As the title says: Houdini 6.0 to 6.5 Compatiblity above this line | Mon. April 28, 2003 |
 |
6.0.284 | Sampling generation in mantra was changed slightly. This means that mantra will not generate exactly the same images as before. There will be fewer stochastic artifacts with arbitrary bucket sizes. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling generation in mantra was changed slightly. This means that mantra will not generate exactly the same images as before. There will be fewer stochastic artifacts with arbitrary bucket sizes. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling generation in mantra was changed slightly. This means that mantra will not generate exactly the same images as before. There will be fewer stochastic artifacts with arbitrary bucket sizes. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling generation in mantra was changed slightly. This means that mantra will not generate exactly the same images as before. There will be fewer stochastic artifacts with arbitrary bucket sizes. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling generation in mantra was changed slightly. This means that mantra will not generate exactly the same images as before. There will be fewer stochastic artifacts with arbitrary bucket sizes. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling artifacts due to bias in a random number generator in mantra have been lessened. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling artifacts due to bias in a random number generator in mantra have been lessened. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling artifacts due to bias in a random number generator in mantra have been lessened. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling artifacts due to bias in a random number generator in mantra have been lessened. |
Mon. April 28, 2003 |
|
6.0.284 | Sampling artifacts due to bias in a random number generator in mantra have been lessened. |
Mon. April 28, 2003 |
|
6.0.284 | The VEX functions otransform(), ltransform() and ftransform() no longer require the full path name for the object in question. In other words, it's now possible to run otransform("geo1") to get the transform for /obj/geo1. |
Mon. April 28, 2003 |
|
6.0.284 | The VEX functions otransform(), ltransform() and ftransform() no longer require the full path name for the object in question. In other words, it's now possible to run otransform("geo1") to get the transform for /obj/geo1. |
Mon. April 28, 2003 |
|
6.0.284 | The VEX functions otransform(), ltransform() and ftransform() no longer require the full path name for the object in question. In other words, it's now possible to run otransform("geo1") to get the transform for /obj/geo1. |
Mon. April 28, 2003 |
|
6.0.284 | The VEX functions otransform(), ltransform() and ftransform() no longer require the full path name for the object in question. In other words, it's now possible to run otransform("geo1") to get the transform for /obj/geo1. |
Mon. April 28, 2003 |
|
6.0.284 | The VEX functions otransform(), ltransform() and ftransform() no longer require the full path name for the object in question. In other words, it's now possible to run otransform("geo1") to get the transform for /obj/geo1. |
Mon. April 28, 2003 |
 |
6.0.281 | MPlay now defaults to using all the phyical memory on a system minus 64Mb. If the physical memory reported is less than 128Mb, Mplay will use half instead. This is only the default, and can be user-configured. |
Fri. April 25, 2003 |