[Sidefx-houdini-list] Recursive OTL search paths in h9?

Peter Bowmar pbowmar at gmail.com
Mon Jan 7 03:20:25 EST 2008

Hey Rangi,

The default in 9 is to ignore the OPlibraries file, but you can use
the option in the Optype Manager to turn the old, and still very
useful IMO, behaviour back on. So, when ignored, you'd have to add all
your subdirs to the OTL_PATH path. This is perhaps more flexible
because you could dynamically build the path on launch, and not have
to edit OPlibraries files anymore.


Peter B

On 07/01/2008, Rangi Sutton <rangi at kanuka.com.au> wrote:
> Hey folks,
> I used to use HOUDINI_OTL_PATH in h8 to reference an assets directory
> that had nested directories full of .otls, where  the base directory had
> an OPlibraries file #including the subdirectories where the actual .otl
> files lived....
> /job/assets/OPlibraries
> --------------
> #include "system_otls/OPlibraries"
> #include "part_otls/OPlibraries"
> #include "shot_otls/OPlibraries"
> Now in h9 the HOUDINI_OTL_PATH doesn't seem to be being respected. I try
> the HOUDINI_OTLSCAN_PATH and that will work, but ignores the OPlibraries
> files and doesn't scan recursively. Is there a solution to this that
> doesn't require me to put in all the sub-directories into the scan path?
> Am I doing this wrong?
> Cheers,
> r.
> --
> Rangi Sutton                      Kanuka Studio Pty Ltd
> rangi at kanuka.com.au               http://www.kanuka.com.au/
> Studio +61 (0)7 3139 1040         35 Dover St. Albion
> Mobile +61 (0)4 1521 1280         QLD 4010 Australia
> _______________________________________________
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
> https://lists.sidefx.com:443/mailman/listinfo/sidefx-houdini-list

More information about the Sidefx-houdini-list mailing list