Houdini Main Changelogs

Houdini 4.9.486 New COPs:
  • Geometry (rasterizes geometry)
  • Lookup (from LUT file and CHOPs)
  • System (renamed from UNIX, similar functionality)
  • Rename (renames planes)
  • Fetch
  • SubNet
  • Blend (blends between 2 sequences)
  • Bump (creates a bump map)
  • TimeScale (stretchs or changes the frame rate of a sequence)
  • Function (assorted mathematical functions)
Fri. September 28, 2001
Houdini 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:

  • The VEX function frontface(vector, vector) is a no-op. This requires models to be built with consistent normals. The form frontface(vector, vector, vector) is still enabled, and can be used as a work-around if required: frontface(N, I, Ng);
  • The VEX functions reflectlight(), refractlight() are disabled since both of these are view dependent. The trace() function is still active (as are all other ray-tracing functions) so if required, this can be worked around.
  • The specular(), phong(), blinn() and Oren-Nayar diffuse() functions which are view dependent are disabled. Illuminance loops can still compute specular light which may cause problems since specular light is largely view dependent and may result in bad textures (i.e. the brushed aluminum shader).
  • Only one image can be rendered in a single IFD. Users should turn off shadow map and reflection map generation.
  • The attribute specified must be a vertex attribute and be three floats large.

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
Houdini 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
Houdini 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
Houdini 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
Houdini 4.9.485 When rendering sequences of images from Houdini on Windows or Solaris (which support threaded UI), an interrupt dialog no longer pops up. Instead, the interrupt messages are sent to the main Houdini window. Thu. September 27, 2001
Houdini 4.9.485 Handles are now capable of remembering their settings. Per-op settings are saved to the hip file via a new "omparm" command. Also, starting a new operation will use the settings of the previous handle. For example, if you left the transform sop's handle in translate mode it will start up in translate mode the next time you put down another transform sop. Currently, the transform and edit sop handles are the only handles that remember their settings. Thu. September 27, 2001
Houdini 4.9.485 New UV Project sop which does best plane projection and automatic layout. Currently only works for vertex UVs. Still some work to be done. Thu. September 27, 2001
Houdini 4.9.484 There is a new command "shopvisible" which can hide operators for specific renderers in the toolbars. The operators still exist, but are not visible when adding new ops from the toolbar.

There is also a menu to control visibility of SHOPs in both the SHOP and Output Driver panes.

Please see the help for more information.

Wed. September 26, 2001
Houdini 4.9.484 Edge selection is now rendered in the UV viewport for vertex attributes. Wed. September 26, 2001
Houdini 4.9.484 When orthographic lights are sent to vmantra, the L variable is now initialized differently than for perspective lights. This will affect shading quite drastically for orthographic light sources. Please see on-line VEX documentation for further details. Wed. September 26, 2001
Houdini 4.9.484 Added nearpoint() expression that allows you to find the nearest point to a specified coordinate. Wed. September 26, 2001
Houdini 4.9.484 You can now toggle the display of the current display geometry. This is either the geometry with the display flag if your viewport is "Show display flag" or the selected SOP if "Show Selected". Wed. September 26, 2001
Houdini 4.9.484 There are new VEX functions in the SOP/POP contexts to add arbitrary attributes:

        addattribute(string name; int value);
        addattribute(string name; float value);
        addattribute(string name; vector value);
        addattribute(string name; vector4 value);
        addattribute(string name; matrix3 value);
        addattribute(string name; matrix4 value);
Wed. September 26, 2001
Houdini 4.9.484 There is now a menu in the VMantra output driver to allow users to choose the image format they would like to generate. This is only applicable to the final image (not shadow maps etc.) Wed. September 26, 2001
Houdini 4.9.484 The Edit Capture Weights state can now also do lasso and brush picking of points. Wed. September 26, 2001
Houdini 4.9.483 When picking objects, the full set of selection methods, box-picking, lasso, and brush are all now available. Tue. September 25, 2001
Houdini 4.9.483 When copy/pasting parameters, you can now paste a "relative reference" to the channel. This will paste a relative path to the copied parameter rather than the full path of the copied parameter. Tue. September 25, 2001
Houdini 4.9.483 The Smooth SOP no longer does anything if attributes are selected but the attribute name is left blank. Tue. September 25, 2001
Houdini 4.9.483 Houdini Select (hselect) is born. Tue. September 25, 2001
Houdini 4.9.483 If you have triangles with point normals, you can now convert them to Triangular Beziers. Tue. September 25, 2001
Houdini 4.9.483 Instead of being hard-coded within Houdini, the default op-handle and op-selector bindings are now stored in a text file called OPbindings. This file by default is in $HH, but is searched for using the HOUDINI_PATH, so placing an OPbindings file in $HOME will override the default file. This file can use the #include directive. There is also a new textport command, omwrite. This command writes all current binding information to a specified file (or $HOME/houdini/OPbindings if no file is specified). The output file is in the format required for the OPbindings file. Tue. September 25, 2001
Houdini 4.9.483 Added several new commands for dynamically modifying OP-selector bindings from the textport. These commands mirror the omXXX commands, and are: omsbind, omsbindinfo, omsls, omsunbind, and omswhere. The parameters are generally very similar to the parameters for the corresponding omXXX commands (except omsbind, which requires very different information). Tue. September 25, 2001
Houdini 4.9.483 The Clip SOP now has the opposite sense for "distance" than before. This is now the logical value - the distance along the given vector to start clipping at - rather than the negation of that. Tue. September 25, 2001
Houdini 4.9.483 When specifying geometry files for mantra to load (in the Render Tab of the geometry object), it is now possible to have an application which generates geometry. By prefixing the command with a pipe (|) symbol, mantra will open the command and read the geometry from stdout. For example,

        opparm logo detail_file ( '|gconvert somefile stdout.bgeo' )

will cause mantra to open gconvert as a pipe and read the geometry from the output of the application. It is suggested that bounding box information is also supplied so that mantra can defer opening the pipe until the object is actually required.

Tue. September 25, 2001