- #Houdini free lancework install
- #Houdini free lancework full
- #Houdini free lancework code
- #Houdini free lancework windows
Other than auto loading stuff from custom user directories, you can setup all sorts of low level system stuff here that can make your life easier and user experience more enjoyable: HOUDINI_VIEWER_STATE_VERBOSE got rid us of some annoying viewport verbosity (that might otherwise be useful for debugging I imagine), HOUDINI_ACCESS_METHOD deals with network permissions which turned out to be a critical little tweak, HOUDINI_ENABLE_EXR_TEXTURE made it possible to work directly with exr textures without having to constantly converting them to rat in lookdev stage, before they were ready to be rendered in shots. However, if you save your HDA to a default directory, you don’t have to add anything to the env file, as that path is scanned automatically. HOUDINI_OTLSCAN_PATH = $HOUDINI_PATH $MYHDA If you want to add your own HDA, and put it into a custom directory for any reason, you have to append it to the $HOUDINI_OTLSCAN_PATH list: MYHDA = C:/Users/David/Houdini17.5/Myhda
Mostly it’s just a path to the plugin, added to the existing $HOUDINI_PATH variable, as you can see at the example above.
#Houdini free lancework code
If you’re dealing with plugins like 3rd party renderers for instance, typically it comes with a short code that needs to be added to the env file. That is basically the whole essence you need to know.
#Houdini free lancework install
If you have a clean install there shouldn’t be much to see.
are saved.įind houdini.env file and open it in any text editing application.
#Houdini free lancework windows
So if you go to “your windows user folder/Documents/HoudiniXX”, you’ll see a bunch of files and folders where your preferences, OTLs, presets, desktops, etc.
#Houdini free lancework full
Other than that there is a number of variables that can alter some low level funtions, like turning on/off various GPU and CPU functions, altering how houdini is hadling textures, log files, color spaces, there are debuging options, graphical output options, network features, caching, and tons of other things.įor the full list of environment variables see this docs page: Very convenient if you want to have a shared network folder that collects that kind of things which you want everybody on a team to have an instant access to. Typical task that can be accomplished by modifying the env file is user defining paths to scan for plugins, HDAs, gallery files, toolbars, presets, etc. In this article I will explain how you can use it to setup some basic Houdini asset sharing across multiple workstations. Environment file is a simple text file located in your Windows user directory, that lets you define a number of variables and settings that can change how Houdini behaves and where it is looking for resources.