HDA version resolution vs HOUDINI_OTLSCAN_PATH

   349   0   0
User Avatar
Member
35 posts
Joined: April 2015
Offline
We are in a situation where we have a SOP HDA, say foo.hda, that exists without any versions. However that same foo.hda exists in our HOUDINI_OTLSCAN_PATH in a lower priority path location where it happens to have a foo.hda::2 version which is significantly different from the foo.hda definition in the priority scan path location. As a result whenever we TAB create this SOP HDA in a houdini session using this HOUDIN_OTLSCAN_PATH we get the foo.hda::2 defined in the lower priority location... And if we then switch the asset definition to the foo.hda version it does appear to switch to the priority source location for the .hda file, however it continues to display the parameter interface that was defined in the foo.hda::2 definition which makes things very confusing.

Is there any way to get houdini to correctly resolve to the foo.hda definition (including parameter interface) that is defined in the first folder of the HOUDINI_OTLSCAN_PATH?
  • Quick Links