Houdini Main Changelogs
 |
9.0.235 | The textport menu is now availble from RMB and no longer requires holding down Ctrl. Panning in the textport using RMB has been disabled. |
Wed. May 17, 2006 |
|
9.0.235 | The textport menu is now availble from RMB and no longer requires holding down Ctrl. Panning in the textport using RMB has been disabled. |
Wed. May 17, 2006 |
|
9.0.235 | The textport menu is now availble from RMB and no longer requires holding down Ctrl. Panning in the textport using RMB has been disabled. |
Wed. May 17, 2006 |
|
9.0.235 | The textport menu is now availble from RMB and no longer requires holding down Ctrl. Panning in the textport using RMB has been disabled. |
Wed. May 17, 2006 |
 |
9.0.235 | Added two new options in Fuse SOP's Snap folder (using the distance snap): Snap Point Positions (controls whether points are actually moved together when snapped) and Snap Point Attributes (controls whether a list of specified point attributes are snapped together). This lets you snap together point attributes if the points are within a specified distance. |
Wed. May 17, 2006 |
|
9.0.235 | Added two new options in Fuse SOP's Snap folder (using the distance snap): Snap Point Positions (controls whether points are actually moved together when snapped) and Snap Point Attributes (controls whether a list of specified point attributes are snapped together). This lets you snap together point attributes if the points are within a specified distance. |
Wed. May 17, 2006 |
|
9.0.235 | Added two new options in Fuse SOP's Snap folder (using the distance snap): Snap Point Positions (controls whether points are actually moved together when snapped) and Snap Point Attributes (controls whether a list of specified point attributes are snapped together). This lets you snap together point attributes if the points are within a specified distance. |
Wed. May 17, 2006 |
|
9.0.235 | Added two new options in Fuse SOP's Snap folder (using the distance snap): Snap Point Positions (controls whether points are actually moved together when snapped) and Snap Point Attributes (controls whether a list of specified point attributes are snapped together). This lets you snap together point attributes if the points are within a specified distance. |
Wed. May 17, 2006 |
|
9.0.235 | Added two new options in Fuse SOP's Snap folder (using the distance snap): Snap Point Positions (controls whether points are actually moved together when snapped) and Snap Point Attributes (controls whether a list of specified point attributes are snapped together). This lets you snap together point attributes if the points are within a specified distance. |
Wed. May 17, 2006 |
 |
9.0.234 | Altered change introduced in 9.0.227 that would shift keys that were overlapped when loading channels. Instead, the keys are no longer altered and a warning is displayed with the frame at which overlapped keys were found. |
Tue. May 16, 2006 |
|
9.0.234 | Altered change introduced in 9.0.227 that would shift keys that were overlapped when loading channels. Instead, the keys are no longer altered and a warning is displayed with the frame at which overlapped keys were found. |
Tue. May 16, 2006 |
|
9.0.234 | Altered change introduced in 9.0.227 that would shift keys that were overlapped when loading channels. Instead, the keys are no longer altered and a warning is displayed with the frame at which overlapped keys were found. |
Tue. May 16, 2006 |
|
9.0.234 | Altered change introduced in 9.0.227 that would shift keys that were overlapped when loading channels. Instead, the keys are no longer altered and a warning is displayed with the frame at which overlapped keys were found. |
Tue. May 16, 2006 |
|
9.0.234 | Altered change introduced in 9.0.227 that would shift keys that were overlapped when loading channels. Instead, the keys are no longer altered and a warning is displayed with the frame at which overlapped keys were found. |
Tue. May 16, 2006 |
 |
9.0.234 | Added options to otload and otunload commands to stop them from trying to modify the OPlibraries file. |
Tue. May 16, 2006 |
|
9.0.234 | Added options to otload and otunload commands to stop them from trying to modify the OPlibraries file. |
Tue. May 16, 2006 |
|
9.0.234 | Added options to otload and otunload commands to stop them from trying to modify the OPlibraries file. |
Tue. May 16, 2006 |
|
9.0.234 | Added options to otload and otunload commands to stop them from trying to modify the OPlibraries file. |
Tue. May 16, 2006 |
|
9.0.234 | Added options to otload and otunload commands to stop them from trying to modify the OPlibraries file. |
Tue. May 16, 2006 |
 |
9.0.234 | The semantics of the frontface() function for shading have been changed slightly. The frontface() function takes an implicit argument of Ng (the geometric normal) which it uses for the comparison. The frontface() function now tests to see whether the geometric normal and the normal passed in are opposed. If this is the case, then the semantics are reversed. The VEX code for the frontface function is now: vector frontface(vector n, i) { if (dot(n, Ng) * dot(n, i) > 0) return -n; return n; } This means that if frontface() is called multiple times, the results will be more inline with what's expected, even if the normal is flipped on the first call. |
Tue. May 16, 2006 |
|
9.0.234 | The semantics of the frontface() function for shading have been changed slightly. The frontface() function takes an implicit argument of Ng (the geometric normal) which it uses for the comparison. The frontface() function now tests to see whether the geometric normal and the normal passed in are opposed. If this is the case, then the semantics are reversed. The VEX code for the frontface function is now: vector frontface(vector n, i) { if (dot(n, Ng) * dot(n, i) > 0) return -n; return n; } This means that if frontface() is called multiple times, the results will be more inline with what's expected, even if the normal is flipped on the first call. |
Tue. May 16, 2006 |
|
9.0.234 | The semantics of the frontface() function for shading have been changed slightly. The frontface() function takes an implicit argument of Ng (the geometric normal) which it uses for the comparison. The frontface() function now tests to see whether the geometric normal and the normal passed in are opposed. If this is the case, then the semantics are reversed. The VEX code for the frontface function is now: vector frontface(vector n, i) { if (dot(n, Ng) * dot(n, i) > 0) return -n; return n; } This means that if frontface() is called multiple times, the results will be more inline with what's expected, even if the normal is flipped on the first call. |
Tue. May 16, 2006 |
|
9.0.234 | The semantics of the frontface() function for shading have been changed slightly. The frontface() function takes an implicit argument of Ng (the geometric normal) which it uses for the comparison. The frontface() function now tests to see whether the geometric normal and the normal passed in are opposed. If this is the case, then the semantics are reversed. The VEX code for the frontface function is now: vector frontface(vector n, i) { if (dot(n, Ng) * dot(n, i) > 0) return -n; return n; } This means that if frontface() is called multiple times, the results will be more inline with what's expected, even if the normal is flipped on the first call. |
Tue. May 16, 2006 |
|
9.0.234 | The semantics of the frontface() function for shading have been changed slightly. The frontface() function takes an implicit argument of Ng (the geometric normal) which it uses for the comparison. The frontface() function now tests to see whether the geometric normal and the normal passed in are opposed. If this is the case, then the semantics are reversed. The VEX code for the frontface function is now: vector frontface(vector n, i) { if (dot(n, Ng) * dot(n, i) > 0) return -n; return n; } This means that if frontface() is called multiple times, the results will be more inline with what's expected, even if the normal is flipped on the first call. |
Tue. May 16, 2006 |
 |
9.0.233 | Fixed a bug in the Sharpen COP where negative values in the Effect parameter would cause a crash. Now it is clamped at zero. |
Mon. May 15, 2006 |