[Sidefx-houdini-list] Recursive OTL search paths in h9?
larry at gcreativestudios.com
Mon Jan 7 10:15:54 EST 2008
Hey Peter, just curious here ....... but where did you find that info
referring to OPlibraries file being ignored in H9??
I had the same confusion as Rangi, but couldn't quite
find a clear explanation of what was going on.
I had the same issue recently when trying to search the docs
for certain Environment Variables ......... only to find
out ( from support ) that they are no longer listed in help
but are only available by typing hconfig -H in a shell.
I guess the reason I'm asking is because I've hit this
type of issue a few times while migrating to H9. Sometimes
things aren't where they used to be ( which is fine and expected)
but then I seem to have trouble finding direct information about the
change ........... or at least it seems a bit tougher to track down
than you might expect. However, I could just be looking in the wrong
Anyway, thanks. I've let this OPlibraries issue sit for a while,
but now I have some useful info to attempt to clean it up.
On Jan 7, 2008, at 3:20 AM, Peter Bowmar wrote:
> 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....
>> #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
>> 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
>> Am I doing this wrong?
>> 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
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list