ah and the above warning was resolved by commenting
#opalias Sop qLib::camera_frustum_ql::3 qLib::camera_frustrum_ql::3
inside
..\qLib-master\OPcustomize file

wlvl_gv
#opalias Sop qLib::camera_frustum_ql::3 qLib::camera_frustrum_ql::3

Should report a bug. Proably intended to alias some older node to the ::3 one.

Hey!

(all of this is my knowledge at the time of writing, not the truth, I might be super wrong!)

This post is pretty old but I thought that I should add my knowledge :
If you are using packages and HOUDINI_SCRIPT_PATH pointing to a shared location (such as a windows server for example), you will have a lot of calls to find OnInstall.py file at the same path for each HDA being added by your packages.

Oh boy, that's not easy to explain.

Basically, each time that you add an HDA, there is an event being called "OnInstall" by the API. This call exists on the HDA itself (think as embedded python) but this mecanism search as well for a file being named "ALL_HOUDINI_SCRIPT_PATHs/SOP/hdaName_onInstall.py". It searches this for each hda node in your install, multiplied by each HOUDINI_SCRIPT_PATH.

So that can be a lot.
I've done a quick test (and an email to support with it) with 10 packages with HOUDINI_SCRIPT_PATH pointing to nothing. My startup time went from 10s to 2 minutes.

You can see this using the process monitor on windows :


On our side we used RClone to sync some package content to each workstation. Moving to Rez might be better, but at least we now have a fix.

I hope that it helps someone !

This is something that I've been looking into recently. It should be much better in the next release.