Houdini Main Changelogs
 |
9.0.265 | The interface to the IMG_File class has changed. In particular, derived classes can no longer directly access the stream myIS. Most functionality is provided by new helper methods in IMG_File. |
Fri. June 16, 2006 |
|
9.0.265 | The interface to the IMG_File class has changed. In particular, derived classes can no longer directly access the stream myIS. Most functionality is provided by new helper methods in IMG_File. |
Fri. June 16, 2006 |
|
9.0.265 | The interface to the IMG_File class has changed. In particular, derived classes can no longer directly access the stream myIS. Most functionality is provided by new helper methods in IMG_File. |
Fri. June 16, 2006 |
|
9.0.265 | The interface to the IMG_File class has changed. In particular, derived classes can no longer directly access the stream myIS. Most functionality is provided by new helper methods in IMG_File. |
Fri. June 16, 2006 |
 |
9.0.265 | imgdispopt now applies all the values it sets in addition to merely setting the preference value. This will allow things like the background image to update correctly. |
Fri. June 16, 2006 |
|
9.0.265 | imgdispopt now applies all the values it sets in addition to merely setting the preference value. This will allow things like the background image to update correctly. |
Fri. June 16, 2006 |
|
9.0.265 | imgdispopt now applies all the values it sets in addition to merely setting the preference value. This will allow things like the background image to update correctly. |
Fri. June 16, 2006 |
|
9.0.265 | imgdispopt now applies all the values it sets in addition to merely setting the preference value. This will allow things like the background image to update correctly. |
Fri. June 16, 2006 |
|
9.0.265 | imgdispopt now applies all the values it sets in addition to merely setting the preference value. This will allow things like the background image to update correctly. |
Fri. June 16, 2006 |
|
9.0.265 | Fixed bug in mplay where changing the frame range would print out a harmless warning about the invalid command varchange. |
Fri. June 16, 2006 |
|
9.0.265 | Fixed bug in mplay where changing the frame range would print out a harmless warning about the invalid command varchange. |
Fri. June 16, 2006 |
|
9.0.265 | Fixed bug in mplay where changing the frame range would print out a harmless warning about the invalid command varchange. |
Fri. June 16, 2006 |
|
9.0.265 | Fixed bug in mplay where changing the frame range would print out a harmless warning about the invalid command varchange. |
Fri. June 16, 2006 |
|
9.0.265 | Fixed bug in mplay where changing the frame range would print out a harmless warning about the invalid command varchange. |
Fri. June 16, 2006 |
 |
9.0.265 | Added the ability to extract point attributes from the target primitive when using the Ray SOP to project rays. The attribute value is interpolated from the hit primitive. You can now extract modified normals, colors, UVs, etc. Also fixed a bug in the Median ray combiner option which would have resulted in hits being miscounted and sorted wrong. |
Fri. June 16, 2006 |
|
9.0.265 | Added the ability to extract point attributes from the target primitive when using the Ray SOP to project rays. The attribute value is interpolated from the hit primitive. You can now extract modified normals, colors, UVs, etc. Also fixed a bug in the Median ray combiner option which would have resulted in hits being miscounted and sorted wrong. |
Fri. June 16, 2006 |
|
9.0.265 | Added the ability to extract point attributes from the target primitive when using the Ray SOP to project rays. The attribute value is interpolated from the hit primitive. You can now extract modified normals, colors, UVs, etc. Also fixed a bug in the Median ray combiner option which would have resulted in hits being miscounted and sorted wrong. |
Fri. June 16, 2006 |
|
9.0.265 | Added the ability to extract point attributes from the target primitive when using the Ray SOP to project rays. The attribute value is interpolated from the hit primitive. You can now extract modified normals, colors, UVs, etc. Also fixed a bug in the Median ray combiner option which would have resulted in hits being miscounted and sorted wrong. |
Fri. June 16, 2006 |
|
9.0.265 | Added the ability to extract point attributes from the target primitive when using the Ray SOP to project rays. The attribute value is interpolated from the hit primitive. You can now extract modified normals, colors, UVs, etc. Also fixed a bug in the Median ray combiner option which would have resulted in hits being miscounted and sorted wrong. |
Fri. June 16, 2006 |
 |
9.0.265 | The houdini preprocessor used to prepend a single space in macro definitions (ie macros defined with #define directive). Also, the "#define SYMBOL" statement would initialize SYMBOL to "1" instead of "". Both of these behaviours were inconsistent with the standard preprocessors (cpp). Now, the macro definition will not contain any extra leading space and empty symbol will not be initialized to "1". For example: #define EXT .html "hdox://contents/geo.EXT" used to expand to "hdox://contents/geo. html" but now correctly expands to "hdox://contents/geo.html" This fix affects the Houdini resource files that used #define directive. |
Fri. June 16, 2006 |
|
9.0.265 | The houdini preprocessor used to prepend a single space in macro definitions (ie macros defined with #define directive). Also, the "#define SYMBOL" statement would initialize SYMBOL to "1" instead of "". Both of these behaviours were inconsistent with the standard preprocessors (cpp). Now, the macro definition will not contain any extra leading space and empty symbol will not be initialized to "1". For example: #define EXT .html "hdox://contents/geo.EXT" used to expand to "hdox://contents/geo. html" but now correctly expands to "hdox://contents/geo.html" This fix affects the Houdini resource files that used #define directive. |
Fri. June 16, 2006 |
|
9.0.265 | The houdini preprocessor used to prepend a single space in macro definitions (ie macros defined with #define directive). Also, the "#define SYMBOL" statement would initialize SYMBOL to "1" instead of "". Both of these behaviours were inconsistent with the standard preprocessors (cpp). Now, the macro definition will not contain any extra leading space and empty symbol will not be initialized to "1". For example: #define EXT .html "hdox://contents/geo.EXT" used to expand to "hdox://contents/geo. html" but now correctly expands to "hdox://contents/geo.html" This fix affects the Houdini resource files that used #define directive. |
Fri. June 16, 2006 |
|
9.0.265 | The houdini preprocessor used to prepend a single space in macro definitions (ie macros defined with #define directive). Also, the "#define SYMBOL" statement would initialize SYMBOL to "1" instead of "". Both of these behaviours were inconsistent with the standard preprocessors (cpp). Now, the macro definition will not contain any extra leading space and empty symbol will not be initialized to "1". For example: #define EXT .html "hdox://contents/geo.EXT" used to expand to "hdox://contents/geo. html" but now correctly expands to "hdox://contents/geo.html" This fix affects the Houdini resource files that used #define directive. |
Fri. June 16, 2006 |
|
9.0.265 | The houdini preprocessor used to prepend a single space in macro definitions (ie macros defined with #define directive). Also, the "#define SYMBOL" statement would initialize SYMBOL to "1" instead of "". Both of these behaviours were inconsistent with the standard preprocessors (cpp). Now, the macro definition will not contain any extra leading space and empty symbol will not be initialized to "1". For example: #define EXT .html "hdox://contents/geo.EXT" used to expand to "hdox://contents/geo. html" but now correctly expands to "hdox://contents/geo.html" This fix affects the Houdini resource files that used #define directive. |
Fri. June 16, 2006 |
 |
9.0.265 | The houdini preprocessor used to prepend a single space in macro definitions (ie macros defined with #define directive). This was inconsistent with the standard preprocessors, and now the macro definition will not contain an extra leading space. |
Fri. June 16, 2006 |