olliRJL

Thanks guys!

Kinda what I was expecting to hear. Hosting these on network drive surely is a factor but I'd also imagine that they get cached pretty well (atleast on linux) for subsequent launches.

Good thing is that I also managed to resolve those couple of hotl breaking cases - it was just a matter of touching the assets in them with a more recent version of Houdini - doh. Would be nice though that hotl actually gave some more informative error messages.

Cheers!

Is anyone doing this?

My initial intention was to "pack" the otls at release time using the hotl tool but in my testing I pretty much immediately encountered a couple of otls that "unpacked" fine but errored out when "packing" back. And there is no useful error information from the hotl tool. The weird thing is that those same otls unpack and pack just fine when using the asset manager gui inside Houdini.

Hi,

If I "unpack" OTLs to the git friendly folder structure form and use them like that is there some expected file IO or scanning performance loss compared to regular "packed" libraries in an environment with hundreds of OTLs?

Tnx!
o.