Houdini Main Changelogs
4.9.408 | Added an option to vmantra output driver to output camera transform separately instead of combining it with object transform. |
Fri. June 29, 2001 | |
4.9.408 | Added new construction plane handle. Still very much a work-in-progress. |
Fri. June 29, 2001 | |
4.9.408 | Added new construction plane handle. Still very much a work-in-progress. |
Fri. June 29, 2001 | |
4.9.408 | Added new construction plane handle. Still very much a work-in-progress. |
Fri. June 29, 2001 | |
4.9.408 | Added new construction plane handle. Still very much a work-in-progress. |
Fri. June 29, 2001 | |
4.9.408 | Added new construction plane handle. Still very much a work-in-progress. |
Fri. June 29, 2001 | |
4.9.407 | Fixed two bugs in PolyKnit. The first one had to do with knitting connected geometry, where we would sometimes not pick up a meta edges on quad because some method was making an assumption about information it didn't have. The other was a display bug when reading back from the SOP parameters when you had flipped a meta quad to a meta edge. |
Thu. June 28, 2001 | |
4.9.407 | Fixed two bugs in PolyKnit. The first one had to do with knitting connected geometry, where we would sometimes not pick up a meta edges on quad because some method was making an assumption about information it didn't have. The other was a display bug when reading back from the SOP parameters when you had flipped a meta quad to a meta edge. |
Thu. June 28, 2001 | |
4.9.407 | Fixed two bugs in PolyKnit. The first one had to do with knitting connected geometry, where we would sometimes not pick up a meta edges on quad because some method was making an assumption about information it didn't have. The other was a display bug when reading back from the SOP parameters when you had flipped a meta quad to a meta edge. |
Thu. June 28, 2001 | |
4.9.407 | Fixed two bugs in PolyKnit. The first one had to do with knitting connected geometry, where we would sometimes not pick up a meta edges on quad because some method was making an assumption about information it didn't have. The other was a display bug when reading back from the SOP parameters when you had flipped a meta quad to a meta edge. |
Thu. June 28, 2001 | |
4.9.407 | Fixed two bugs in PolyKnit. The first one had to do with knitting connected geometry, where we would sometimes not pick up a meta edges on quad because some method was making an assumption about information it didn't have. The other was a display bug when reading back from the SOP parameters when you had flipped a meta quad to a meta edge. |
Thu. June 28, 2001 | |
4.9.407 | The brush SOPs (comb, paint, sculpt) all now have an "Orient to Surface" toggle in the stroke tab. This will switch from using the surface normal for the brush direction and the view direction. View direction is preferable for bumpy surfaces. |
Thu. June 28, 2001 | |
4.9.407 | The brush SOPs (comb, paint, sculpt) all now have an "Orient to Surface" toggle in the stroke tab. This will switch from using the surface normal for the brush direction and the view direction. View direction is preferable for bumpy surfaces. |
Thu. June 28, 2001 | |
4.9.407 | The brush SOPs (comb, paint, sculpt) all now have an "Orient to Surface" toggle in the stroke tab. This will switch from using the surface normal for the brush direction and the view direction. View direction is preferable for bumpy surfaces. |
Thu. June 28, 2001 | |
4.9.407 | The brush SOPs (comb, paint, sculpt) all now have an "Orient to Surface" toggle in the stroke tab. This will switch from using the surface normal for the brush direction and the view direction. View direction is preferable for bumpy surfaces. |
Thu. June 28, 2001 | |
4.9.407 | The brush SOPs (comb, paint, sculpt) all now have an "Orient to Surface" toggle in the stroke tab. This will switch from using the surface normal for the brush direction and the view direction. View direction is preferable for bumpy surfaces. |
Thu. June 28, 2001 | |
4.9.407 | There is a new SOP, the Layer SOP, which is designed to work with multipass textures. By changing your current layer, you change which attributes color, texture, etc, map to. On layer 5, for example, color is "Cd5" and texture coordiantes are "uv5". You see in the viewport what your current layer's values are - unless you have multipass texturing turned on in the display options. Then you get the effect of drawing each layer in order from the first to the max layers specified in this SOP. Each layer is drawn on top of one another with the Blend mode by default. However, you can override the blend control with any standard OpenGL modes using the SOP. |
Thu. June 28, 2001 | |
4.9.407 | There is a new SOP, the Layer SOP, which is designed to work with multipass textures. By changing your current layer, you change which attributes color, texture, etc, map to. On layer 5, for example, color is "Cd5" and texture coordiantes are "uv5". You see in the viewport what your current layer's values are - unless you have multipass texturing turned on in the display options. Then you get the effect of drawing each layer in order from the first to the max layers specified in this SOP. Each layer is drawn on top of one another with the Blend mode by default. However, you can override the blend control with any standard OpenGL modes using the SOP. |
Thu. June 28, 2001 | |
4.9.407 | There is a new SOP, the Layer SOP, which is designed to work with multipass textures. By changing your current layer, you change which attributes color, texture, etc, map to. On layer 5, for example, color is "Cd5" and texture coordiantes are "uv5". You see in the viewport what your current layer's values are - unless you have multipass texturing turned on in the display options. Then you get the effect of drawing each layer in order from the first to the max layers specified in this SOP. Each layer is drawn on top of one another with the Blend mode by default. However, you can override the blend control with any standard OpenGL modes using the SOP. |
Thu. June 28, 2001 | |
4.9.407 | There is a new SOP, the Layer SOP, which is designed to work with multipass textures. By changing your current layer, you change which attributes color, texture, etc, map to. On layer 5, for example, color is "Cd5" and texture coordiantes are "uv5". You see in the viewport what your current layer's values are - unless you have multipass texturing turned on in the display options. Then you get the effect of drawing each layer in order from the first to the max layers specified in this SOP. Each layer is drawn on top of one another with the Blend mode by default. However, you can override the blend control with any standard OpenGL modes using the SOP. |
Thu. June 28, 2001 | |
4.9.407 | There is a new SOP, the Layer SOP, which is designed to work with multipass textures. By changing your current layer, you change which attributes color, texture, etc, map to. On layer 5, for example, color is "Cd5" and texture coordiantes are "uv5". You see in the viewport what your current layer's values are - unless you have multipass texturing turned on in the display options. Then you get the effect of drawing each layer in order from the first to the max layers specified in this SOP. Each layer is drawn on top of one another with the Blend mode by default. However, you can override the blend control with any standard OpenGL modes using the SOP. |
Thu. June 28, 2001 | |
4.9.407 | vmantra output driver can now output null surface shaders instead of the real ones during shadow map generation stage. This behaviour is controlled by the "Null Surface" option. |
Thu. June 28, 2001 | |
4.9.407 | vmantra output driver can now output null surface shaders instead of the real ones during shadow map generation stage. This behaviour is controlled by the "Null Surface" option. |
Thu. June 28, 2001 | |
4.9.407 | vmantra output driver can now output null surface shaders instead of the real ones during shadow map generation stage. This behaviour is controlled by the "Null Surface" option. |
Thu. June 28, 2001 | |
4.9.407 | vmantra output driver can now output null surface shaders instead of the real ones during shadow map generation stage. This behaviour is controlled by the "Null Surface" option. |
Thu. June 28, 2001 |