Hi all,
I have a little HDA that manages some preview renders in my project, it has TOP nodes inside the HDA.
When I run the TOP nets with a button wired up through the python module, the HDA unlocks itself.
Is there a way to avoid that? Having unlocked HDAs around the place is trouble :o.
Thanks,
Pete
Full Version: Running TOPS nodes inside HDA unlocks the HDA.
TOPs doesn't unlock HDAs in the general case.
Does your HDA contain ROP Fetch nodes that cook in process and also point to a ROP in the HDA itself, for example a ROP Geometry? The ROP Fetch will unlock the HDA that contains the ROP being cooked, because it often needs to set parameters on that ROP. You can disable that behavior using the "Unlock Target ROP Node" as described in the documentation: https://www.sidefx.com/docs/houdini/nodes/top/ropfetch.html#unlocktargetrop [www.sidefx.com]
Does your HDA contain ROP Fetch nodes that cook in process and also point to a ROP in the HDA itself, for example a ROP Geometry? The ROP Fetch will unlock the HDA that contains the ROP being cooked, because it often needs to set parameters on that ROP. You can disable that behavior using the "Unlock Target ROP Node" as described in the documentation: https://www.sidefx.com/docs/houdini/nodes/top/ropfetch.html#unlocktargetrop [www.sidefx.com]
Hey that was it! Thanks for pointing me in the right direction there. My HDA is working great again 
P.
P.