There is now an environment variable which can be used to set the default color for missing texture maps: % setenv HOUDINI_TEXTURE_DEFAULT_COLOR "red green blue alpha" will cause missing texture maps to return the color specified when accessed in VEX.

The commands for creating the default scene in 123.cmd has been split into its own file, defaultscene.cmd. The file 123.cmd is loaded whenever Houdini starts up and from within 123.cmd, defaultscene.cmd is sourced.

The commands for creating the default scene in 123.cmd has been split into its own file, defaultscene.cmd. The file 123.cmd is loaded whenever Houdini starts up and from within 123.cmd, defaultscene.cmd is sourced.

The commands for creating the default scene in 123.cmd has been split into its own file, defaultscene.cmd. The file 123.cmd is loaded whenever Houdini starts up and from within 123.cmd, defaultscene.cmd is sourced.

The commands for creating the default scene in 123.cmd has been split into its own file, defaultscene.cmd. The file 123.cmd is loaded whenever Houdini starts up and from within 123.cmd, defaultscene.cmd is sourced.

The commands for creating the default scene in 123.cmd has been split into its own file, defaultscene.cmd. The file 123.cmd is loaded whenever Houdini starts up and from within 123.cmd, defaultscene.cmd is sourced.

Old change that should have been noted back in Houdini 4.9.337:

There is an option to specify the maximum memory usage for the undo manager under the "Preferences..." menu option. It is set to 1000 Kb by default in Houdini 4.9. In Houdini 4.1, it was fixed at a size of 100 Kb.

Old change that should have been noted back in Houdini 4.9.337:

There is an option to specify the maximum memory usage for the undo manager under the "Preferences..." menu option. It is set to 1000 Kb by default in Houdini 4.9. In Houdini 4.1, it was fixed at a size of 100 Kb.

Old change that should have been noted back in Houdini 4.9.337:

There is an option to specify the maximum memory usage for the undo manager under the "Preferences..." menu option. It is set to 1000 Kb by default in Houdini 4.9. In Houdini 4.1, it was fixed at a size of 100 Kb.

Old change that should have been noted back in Houdini 4.9.337:

There is an option to specify the maximum memory usage for the undo manager under the "Preferences..." menu option. It is set to 1000 Kb by default in Houdini 4.9. In Houdini 4.1, it was fixed at a size of 100 Kb.

Old change that should have been noted back in Houdini 4.9.337:

There is an option to specify the maximum memory usage for the undo manager under the "Preferences..." menu option. It is set to 1000 Kb by default in Houdini 4.9. In Houdini 4.1, it was fixed at a size of 100 Kb.

Miscellaneous fixes to 3d texture code:

• Fix to shadow integration artifacting
• Fixes to generation of files
• Addition of anti-aliasing of maps during generation
• Addition of forpoints() loop in image3d VEX context
• isbound() works properly (as best it can) in image3d
• Default shaders distributed for:

a) Fog context (including adaptive step integration) b) Surface context (ditto) c) Image3d context.

• Access to image3d context shaders via SHOPs is implemented
• There is an output driver which will generate texture mapsby calling i3dgen for the user.
• etc.

Miscellaneous fixes to 3d texture code:

• Fix to shadow integration artifacting
• Fixes to generation of files
• Addition of anti-aliasing of maps during generation
• Addition of forpoints() loop in image3d VEX context
• isbound() works properly (as best it can) in image3d
• Default shaders distributed for:

a) Fog context (including adaptive step integration) b) Surface context (ditto) c) Image3d context.

• Access to image3d context shaders via SHOPs is implemented
• There is an output driver which will generate texture mapsby calling i3dgen for the user.
• etc.

Miscellaneous fixes to 3d texture code:

• Fix to shadow integration artifacting
• Fixes to generation of files
• Addition of anti-aliasing of maps during generation
• Addition of forpoints() loop in image3d VEX context
• isbound() works properly (as best it can) in image3d
• Default shaders distributed for:

a) Fog context (including adaptive step integration) b) Surface context (ditto) c) Image3d context.

• Access to image3d context shaders via SHOPs is implemented
• There is an output driver which will generate texture mapsby calling i3dgen for the user.
• etc.

Miscellaneous fixes to 3d texture code:

• Fix to shadow integration artifacting
• Fixes to generation of files
• Addition of anti-aliasing of maps during generation
• Addition of forpoints() loop in image3d VEX context
• isbound() works properly (as best it can) in image3d
• Default shaders distributed for:

a) Fog context (including adaptive step integration) b) Surface context (ditto) c) Image3d context.

• Access to image3d context shaders via SHOPs is implemented
• There is an output driver which will generate texture mapsby calling i3dgen for the user.
• etc.

Miscellaneous fixes to 3d texture code:

• Fix to shadow integration artifacting
• Fixes to generation of files
• Addition of anti-aliasing of maps during generation
• Addition of forpoints() loop in image3d VEX context
• isbound() works properly (as best it can) in image3d
• Default shaders distributed for:

a) Fog context (including adaptive step integration) b) Surface context (ditto) c) Image3d context.

• Access to image3d context shaders via SHOPs is implemented
• There is an output driver which will generate texture mapsby calling i3dgen for the user.
• etc.

The Bones State's joint handle can now be switched to a rotate handle via the 'r' key or the right-click menu of the handle. This gives full control over the orientation of the bone.

Similarly, the default bone object handle has been updated to use the new bone rotate handle.

The orientation of the translate handle in the Bones State no longer loses its orientation when you tumble.

FK end affectors in the Bones State now align themselves to their associated bones when you move the position of a joint via the joint handles.

The Bones State's joint handle can now be switched to a rotate handle via the 'r' key or the right-click menu of the handle. This gives full control over the orientation of the bone.

Similarly, the default bone object handle has been updated to use the new bone rotate handle.

The orientation of the translate handle in the Bones State no longer loses its orientation when you tumble.

FK end affectors in the Bones State now align themselves to their associated bones when you move the position of a joint via the joint handles.

The Bones State's joint handle can now be switched to a rotate handle via the 'r' key or the right-click menu of the handle. This gives full control over the orientation of the bone.

Similarly, the default bone object handle has been updated to use the new bone rotate handle.

The orientation of the translate handle in the Bones State no longer loses its orientation when you tumble.

FK end affectors in the Bones State now align themselves to their associated bones when you move the position of a joint via the joint handles.

The Bones State's joint handle can now be switched to a rotate handle via the 'r' key or the right-click menu of the handle. This gives full control over the orientation of the bone.

Similarly, the default bone object handle has been updated to use the new bone rotate handle.

The orientation of the translate handle in the Bones State no longer loses its orientation when you tumble.

FK end affectors in the Bones State now align themselves to their associated bones when you move the position of a joint via the joint handles.

The Bones State's joint handle can now be switched to a rotate handle via the 'r' key or the right-click menu of the handle. This gives full control over the orientation of the bone.

Similarly, the default bone object handle has been updated to use the new bone rotate handle.

The orientation of the translate handle in the Bones State no longer loses its orientation when you tumble.

FK end affectors in the Bones State now align themselves to their associated bones when you move the position of a joint via the joint handles.

Tolerance sliders in SOPs, such as those for project, cookie, etc, are now logarithmic. This means that if you slide it one unit to the right, the number becomes ten times larger, and if you slide it one unit to the left, the number ten times smaller. This is more in line with the sort of changes one wants to make with tolerance values.

Tolerance sliders in SOPs, such as those for project, cookie, etc, are now logarithmic. This means that if you slide it one unit to the right, the number becomes ten times larger, and if you slide it one unit to the left, the number ten times smaller. This is more in line with the sort of changes one wants to make with tolerance values.

Tolerance sliders in SOPs, such as those for project, cookie, etc, are now logarithmic. This means that if you slide it one unit to the right, the number becomes ten times larger, and if you slide it one unit to the left, the number ten times smaller. This is more in line with the sort of changes one wants to make with tolerance values.

Tolerance sliders in SOPs, such as those for project, cookie, etc, are now logarithmic. This means that if you slide it one unit to the right, the number becomes ten times larger, and if you slide it one unit to the left, the number ten times smaller. This is more in line with the sort of changes one wants to make with tolerance values.