Houdini Main Changelogs
4.9.486 | Field COP now does Pulldown and Pushup on arbitrary film and video rates. |
Fri. September 28, 2001 | |
4.9.486 | Field COP now does Pulldown and Pushup on arbitrary film and video rates. |
Fri. September 28, 2001 | |
4.9.486 | Field COP now does Pulldown and Pushup on arbitrary film and video rates. |
Fri. September 28, 2001 | |
4.9.486 | Field COP now does Pulldown and Pushup on arbitrary film and video rates. |
Fri. September 28, 2001 | |
4.9.486 | New COPs:
|
Fri. September 28, 2001 | |
4.9.486 | New COPs:
|
Fri. September 28, 2001 | |
4.9.486 | New COPs:
|
Fri. September 28, 2001 | |
4.9.486 | New COPs:
|
Fri. September 28, 2001 | |
4.9.486 | New COPs:
|
Fri. September 28, 2001 | |
4.9.486 | A preliminary version of a texture baker has been added to vmantra. The -u option can be used to render the 0-1 texture space for an object. Instead of rendering using the point positions, the attribute specified (defaulting to "uv") is projected into NDC screen space and rendered. All shading for the object specified still occurs in world space (with proper object/shader transforms). The result of a texture baked render will be a texture map which captures the VEX procedural shaders and diffuse lighting information (including shadows if they exist) which can be re-mapped onto the rendered object. Ideally, each polygon should map to a unique space in the 0-1 texture grid. Overlapping polygons are not handled properly and will result in bad texture map generation. The texture baker rendering has the following limitations:
It is possible to render deep rasters outputting arbitrary VEX variables when texture baking. This will generate multiple texture maps simultaneously (or a single deep raster Houdini .pic file). For example: vmantra < foo.ifd -u logo:uv x.pic |
Fri. September 28, 2001 | |
4.9.486 | A preliminary version of a texture baker has been added to vmantra. The -u option can be used to render the 0-1 texture space for an object. Instead of rendering using the point positions, the attribute specified (defaulting to "uv") is projected into NDC screen space and rendered. All shading for the object specified still occurs in world space (with proper object/shader transforms). The result of a texture baked render will be a texture map which captures the VEX procedural shaders and diffuse lighting information (including shadows if they exist) which can be re-mapped onto the rendered object. Ideally, each polygon should map to a unique space in the 0-1 texture grid. Overlapping polygons are not handled properly and will result in bad texture map generation. The texture baker rendering has the following limitations:
It is possible to render deep rasters outputting arbitrary VEX variables when texture baking. This will generate multiple texture maps simultaneously (or a single deep raster Houdini .pic file). For example: vmantra < foo.ifd -u logo:uv x.pic |
Fri. September 28, 2001 | |
4.9.486 | A preliminary version of a texture baker has been added to vmantra. The -u option can be used to render the 0-1 texture space for an object. Instead of rendering using the point positions, the attribute specified (defaulting to "uv") is projected into NDC screen space and rendered. All shading for the object specified still occurs in world space (with proper object/shader transforms). The result of a texture baked render will be a texture map which captures the VEX procedural shaders and diffuse lighting information (including shadows if they exist) which can be re-mapped onto the rendered object. Ideally, each polygon should map to a unique space in the 0-1 texture grid. Overlapping polygons are not handled properly and will result in bad texture map generation. The texture baker rendering has the following limitations:
It is possible to render deep rasters outputting arbitrary VEX variables when texture baking. This will generate multiple texture maps simultaneously (or a single deep raster Houdini .pic file). For example: vmantra < foo.ifd -u logo:uv x.pic |
Fri. September 28, 2001 | |
4.9.486 | A preliminary version of a texture baker has been added to vmantra. The -u option can be used to render the 0-1 texture space for an object. Instead of rendering using the point positions, the attribute specified (defaulting to "uv") is projected into NDC screen space and rendered. All shading for the object specified still occurs in world space (with proper object/shader transforms). The result of a texture baked render will be a texture map which captures the VEX procedural shaders and diffuse lighting information (including shadows if they exist) which can be re-mapped onto the rendered object. Ideally, each polygon should map to a unique space in the 0-1 texture grid. Overlapping polygons are not handled properly and will result in bad texture map generation. The texture baker rendering has the following limitations:
It is possible to render deep rasters outputting arbitrary VEX variables when texture baking. This will generate multiple texture maps simultaneously (or a single deep raster Houdini .pic file). For example: vmantra < foo.ifd -u logo:uv x.pic |
Fri. September 28, 2001 | |
4.9.486 | A preliminary version of a texture baker has been added to vmantra. The -u option can be used to render the 0-1 texture space for an object. Instead of rendering using the point positions, the attribute specified (defaulting to "uv") is projected into NDC screen space and rendered. All shading for the object specified still occurs in world space (with proper object/shader transforms). The result of a texture baked render will be a texture map which captures the VEX procedural shaders and diffuse lighting information (including shadows if they exist) which can be re-mapped onto the rendered object. Ideally, each polygon should map to a unique space in the 0-1 texture grid. Overlapping polygons are not handled properly and will result in bad texture map generation. The texture baker rendering has the following limitations:
It is possible to render deep rasters outputting arbitrary VEX variables when texture baking. This will generate multiple texture maps simultaneously (or a single deep raster Houdini .pic file). For example: vmantra < foo.ifd -u logo:uv x.pic |
Fri. September 28, 2001 | |
4.9.486 | There are new pragmas to bind default handles/selectors for VEX Ops. Please see online VEX docs for further details. |
Fri. September 28, 2001 | |
4.9.486 | There are new pragmas to bind default handles/selectors for VEX Ops. Please see online VEX docs for further details. |
Fri. September 28, 2001 | |
4.9.486 | There are new pragmas to bind default handles/selectors for VEX Ops. Please see online VEX docs for further details. |
Fri. September 28, 2001 | |
4.9.486 | There are new pragmas to bind default handles/selectors for VEX Ops. Please see online VEX docs for further details. |
Fri. September 28, 2001 | |
4.9.486 | There are new pragmas to bind default handles/selectors for VEX Ops. Please see online VEX docs for further details. |
Fri. September 28, 2001 | |
4.9.486 | UV Project PI bound to the UV Project SOP which also shows what in the past would have been the guide geometry. |
Fri. September 28, 2001 | |
4.9.486 | UV Project PI bound to the UV Project SOP which also shows what in the past would have been the guide geometry. |
Fri. September 28, 2001 | |
4.9.486 | UV Project PI bound to the UV Project SOP which also shows what in the past would have been the guide geometry. |
Fri. September 28, 2001 | |
4.9.486 | UV Project PI bound to the UV Project SOP which also shows what in the past would have been the guide geometry. |
Fri. September 28, 2001 | |
4.9.486 | UV Project PI bound to the UV Project SOP which also shows what in the past would have been the guide geometry. |
Fri. September 28, 2001 | |
4.9.486 | The smooth sop now allows the user to specify Texture UV or Color as target. In this way we apply the smoothing to the current layer. The user still has the option to specify the attribute name. Also we now use vertex attributes by default, and if not found, then we try for a point attribute. |
Fri. September 28, 2001 |