How to configure Houdini to match your project and workflow.
Common UI customizations
You can customize the UI for a particular workflow, project, or facility.
|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
|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
|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
$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
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.
$HSITE directory must contain a
directory (such as
houdini9.0). If no such directory exists,
Houdini will not search in
$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,
.geo files) when the file’s location
is not absolute.
For example, the default
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
Some important Houdini paths:
Operator type library (
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.
Houdini will search certain paths to build up the configuration when it launches. The main path is in the environment variable
HOUDINI_PATH. For different options, Houdini may find the first file it finds, or it may aggregate all files found in the path.
Execute the first startup scripts it finds (
456.cmd). See event scripts.
hopmanager.preffile (for OTL configuration). See Operator type manager.
OPmenufile (for customizing menu options of nodes).
FBresfile (for customizing the list of preset resolutions in pop-up menus on render nodes, lights, and cameras).
FBrenderfile (for customizing the list of preset sequence filename patterns in pop-up menus).
Most files under
$HH). You can copy these files into
$HOME/houdiniX.X(which is earlier on the
HOUDINI_PATH) and modify them to override the files in
Preference files (
.pref) that are outside of
$HOME/houdini must be suffixed
.nosave in order for them to be recognized, even if they occur earlier
Preventing user changes
If you are creating/copying
.deskfiles manually instead of using the graphical interface (for example, to enforce uniform layouts/preferences across all machines), you can usually append
.nosaveto the filename to prevent the files from being overwritten with user changes. The user can still change the settings in a session, but those changes will not be saved between sessions.
For desktop (pane layout) files, this is the same as turning on the “no save” option in the desktop editing interface.
The downside is that a preference file often contains many different preferences and you may not want to lock them all down. The
.nosavefeature is most useful to override
hopmanager.prefsettings to provide a consistent set of OTLs.
Make sure the
.nosaveversion of the file is higher in the
HOUDINI_PATHthan a regular version.