Basics
Configure Houdini
How to configure Houdini to match your project and workflow.
Overview
Choose a category from the Edit > Preferences submenu to open the main preferences window.
See also how to change the hotkeys and how to customize the shelf.
Common UI customizations
You can customize the UI for a particular workflow, project, or facility.
| To... | Do this |
|---|---|
|
Scale the Houdini UI |
Choose Edit > Preferences > General user interface and change the Global UI size option. You can also set the |
|
Adjust the UI colors |
Choose Edit > Color settings. |
|
Use Houdini 8-style pane coloring to show network type |
Choose Edit > Preferences > General user interface and turn on Color pane headers with network contexts. |
|
Add preset colors to palette in the color picker dialog |
|
Common viewer customizations
| To... | Do this |
|---|---|
|
Change the tumbling behavior |
|
|
Turn off multicolored handles |
With this option off, Houdini will draw handles all-red instead of coloring the axes red, green, and blue.
|
|
Use a black background in the 3D viewer |
|
|
Change the background color in a compositing viewer |
|
Common network editor customizations
| To... | Do this |
|---|---|
|
Choose whether to zoom in and out from the center or based on the mouse position |
|
|
Change how wires are drawn |
|
|
Automatically place new nodes instead of requiring a click |
|
Paths and locations
Houdini uses two types of environment variables for specifying directories: paths (lists of locations to check for files), and locations (paths of directories).
In a command line shell, run hconfig -ap to show the current path and location assignments, and instructions and shortcuts for setting the variables.
Locations
Locations, like $HSITE (directory of site-specific files) and $HIP (the directory containing the current .hip file), specify the directory in which to find files for various purposes.
Unlike a path, a location variable can’t have multiple directories; it’s simply used to avoid hard-coding locations, as in $HFS/geo/model.bgeo instead of /usr/joe/files/show/act1/scene1/geo/model.geo. This makes the .hip file much more portable between machines and operating systems.
You can set the $HSITE variable to a directory containing site-specific files. You can set the $JOB variable to a directory containing project-specific files. The two locations are included in the path, but not defined by default. So, if you define one or both, they will already be included in the path.
The $HSITE directory must contain a houdinix.y directory (such as houdini9.0). If no such directory exists, Houdini will not search in $HSITE.
Paths
Paths, like $HOUDINI_PATH, can have more than one location, and Houdini searches the locations in the path in the order they appear in the variable.
Houdini uses paths to search for various file types (for example, $HOUDINI_GEOMETRY_PATH for .geo files) when the file’s location is not absolute.
For example, the default $HOUDINI_GEOMETRY_PATH is:
./ $HOUDINI_PATH/geo/
If you add a location to the path:
./ $HIP/geo/ $HOUDINI_PATH/geo/
…then you can just use model.bgeo in a geometry file parameter and Houdini will find it if it exists in $HIP/geo/.
Some important Houdini paths:
|
|
Geometry ( |
|
|
Operator type library ( |
|
|
HScript ( |
|
|
Image files. |
|
|
Channel and audio files. |
|
|
Compiled VEX ( |
This not a full list of search paths. In a command shell, run hconfig -ap to see all available path variables.
Subtopics
-
HUD (Heads-up Display) sliders let you put controls for important parameters directly in the viewer pane, floating above the scene.