Search the Community
Showing results for tags 'How to deal with otl versions'.
Found 1 result
-
I have several otl versions of some assets and probably I will get more during the production and I'm looking for a way to manage them. The behavior I would prefere is that I start with a new houdini and with the otl scan path set to my otl directory where all version are saved. when I drop in a node of that definition it uses the latest one. when i open the scene it uses the one that was originally active when it was saved. The workflow is not that clear right now, cause there is the possibility to do it by several otl files on disc,all with same operator name. houdini scans in the otls and uses one. now the user can select the a older definition if he wants another way is with namespaces and versions. not to forget the version parameter in the operator type property window, it seems not to have a real effect what is the way to go for this? MartinPS: and how can I force a definition when several otls are visible in the operator type manager with python, I could not find a hou method for getting a list of installs of a operator that is not used in the scene, yet and how to set one as active
