There are two new expression functions in Houdini: tex() and texni() which perform texture evaluation of disk files. These functions are similar to the pic() and picni() expression functions, but use the texture mapping code to allow for rasters which aren't 4 channel 8/16 bit data. These functions can minimize memory usage when accessing single or three channel images and can also provide access to high-dynamic range/high-precision data stored in floating point images.

There are two new expression functions in Houdini: tex() and texni() which perform texture evaluation of disk files. These functions are similar to the pic() and picni() expression functions, but use the texture mapping code to allow for rasters which aren't 4 channel 8/16 bit data. These functions can minimize memory usage when accessing single or three channel images and can also provide access to high-dynamic range/high-precision data stored in floating point images.

There are two new expression functions in Houdini: tex() and texni() which perform texture evaluation of disk files. These functions are similar to the pic() and picni() expression functions, but use the texture mapping code to allow for rasters which aren't 4 channel 8/16 bit data. These functions can minimize memory usage when accessing single or three channel images and can also provide access to high-dynamic range/high-precision data stored in floating point images.

There are two new expression functions in Houdini: tex() and texni() which perform texture evaluation of disk files. These functions are similar to the pic() and picni() expression functions, but use the texture mapping code to allow for rasters which aren't 4 channel 8/16 bit data. These functions can minimize memory usage when accessing single or three channel images and can also provide access to high-dynamic range/high-precision data stored in floating point images.

There are two new expression functions in Houdini: tex() and texni() which perform texture evaluation of disk files. These functions are similar to the pic() and picni() expression functions, but use the texture mapping code to allow for rasters which aren't 4 channel 8/16 bit data. These functions can minimize memory usage when accessing single or three channel images and can also provide access to high-dynamic range/high-precision data stored in floating point images.

The texture engine for sampling non-RAT textures was largely re-written. Aside from minor performance improvements, the texturing code now handles images consisting of 1, 3 or 4 channels of color data which can be 8-bit, 16-bit or floating point format. Previously all images loaded were converted to 4 channel 8-bit or 16-bit rasters internally.

Please note that RAT files still provide the best quality filtering and memory usage and should be used for all texture mapping (excepting bump-mapping and shadow maps where no filtering advantages are gained).

The texture engine for sampling non-RAT textures was largely re-written. Aside from minor performance improvements, the texturing code now handles images consisting of 1, 3 or 4 channels of color data which can be 8-bit, 16-bit or floating point format. Previously all images loaded were converted to 4 channel 8-bit or 16-bit rasters internally.

Please note that RAT files still provide the best quality filtering and memory usage and should be used for all texture mapping (excepting bump-mapping and shadow maps where no filtering advantages are gained).

The texture engine for sampling non-RAT textures was largely re-written. Aside from minor performance improvements, the texturing code now handles images consisting of 1, 3 or 4 channels of color data which can be 8-bit, 16-bit or floating point format. Previously all images loaded were converted to 4 channel 8-bit or 16-bit rasters internally.

Please note that RAT files still provide the best quality filtering and memory usage and should be used for all texture mapping (excepting bump-mapping and shadow maps where no filtering advantages are gained).

The texture engine for sampling non-RAT textures was largely re-written. Aside from minor performance improvements, the texturing code now handles images consisting of 1, 3 or 4 channels of color data which can be 8-bit, 16-bit or floating point format. Previously all images loaded were converted to 4 channel 8-bit or 16-bit rasters internally.

Please note that RAT files still provide the best quality filtering and memory usage and should be used for all texture mapping (excepting bump-mapping and shadow maps where no filtering advantages are gained).

The texture engine for sampling non-RAT textures was largely re-written. Aside from minor performance improvements, the texturing code now handles images consisting of 1, 3 or 4 channels of color data which can be 8-bit, 16-bit or floating point format. Previously all images loaded were converted to 4 channel 8-bit or 16-bit rasters internally.

Please note that RAT files still provide the best quality filtering and memory usage and should be used for all texture mapping (excepting bump-mapping and shadow maps where no filtering advantages are gained).

When secure selection is OFF in the world viewer, the selection buttons on the left-hand side of the viewer are now enabled.

When secure selection is OFF in the world viewer, the selection buttons on the left-hand side of the viewer are now enabled.

When secure selection is OFF in the world viewer, the selection buttons on the left-hand side of the viewer are now enabled.

When secure selection is OFF in the world viewer, the selection buttons on the left-hand side of the viewer are now enabled.

When secure selection is OFF in the world viewer, the selection buttons on the left-hand side of the viewer are now enabled.

Improved bone rotations (especially twisting) when converting mocap data.

Improved bone rotations (especially twisting) when converting mocap data.

Improved bone rotations (especially twisting) when converting mocap data.

Improved bone rotations (especially twisting) when converting mocap data.

Improved bone rotations (especially twisting) when converting mocap data.

Added "Merge Operation With All Footprints" to sop viewer menu. If anyone finds footprints confusing and does not for sure what is finally exported to the object, this option should put all confusion to rest because it merges everything visible into one SOP.

Added "Merge Operation With All Footprints" to sop viewer menu. If anyone finds footprints confusing and does not for sure what is finally exported to the object, this option should put all confusion to rest because it merges everything visible into one SOP.

Added "Merge Operation With All Footprints" to sop viewer menu. If anyone finds footprints confusing and does not for sure what is finally exported to the object, this option should put all confusion to rest because it merges everything visible into one SOP.

Added "Merge Operation With All Footprints" to sop viewer menu. If anyone finds footprints confusing and does not for sure what is finally exported to the object, this option should put all confusion to rest because it merges everything visible into one SOP.

Added "Merge Operation With All Footprints" to sop viewer menu. If anyone finds footprints confusing and does not for sure what is finally exported to the object, this option should put all confusion to rest because it merges everything visible into one SOP.