When creating an HDA that uses multiparms, I have noticed that versioning-up that digital asset causes the parameter names to change, typically adding a "_2" to the end of the name.

So for instance, on an HDA here I have some multiparms:


When I use the Digital Asset --> Save As... command to version up the asset, they all get a digit added to the end of them:


Is this a bug? Or is there a behavior I'm not understanding? It's not hard to go through and fix them but it does add an element of danger to regular maintenance on HDAs with a lot of multiparms...

It might be a bug, better if you report it to the Support

Thanks -- I submitted it and this has been logged as a bug by support.

Finally, someone else encountered this! I've submitted the bug twice and it's killing me. The workaround is just using Houdini 19.0 for saving the HDA because it doesn't have that problem.

EJaworenko
Finally, someone else encountered this! I've submitted the bug twice and it's killing me. The workaround is just using Houdini 19.0 for saving the HDA because it doesn't have that problem.

Oof, that’s a rough workaround.

A lot of my high-level tools rely heavily on multiparms and those break the hardest due to this bug. It has driven me to start developing a Python build system for all the high level HDAs because they are unmaintainable by hand. That’s probably better in the long run anyway, but it’s been a lot of work to set up and really slows down the prototyping.

jedmitchell

EJaworenko
Finally, someone else encountered this! I've submitted the bug twice and it's killing me. The workaround is just using Houdini 19.0 for saving the HDA because it doesn't have that problem.

Oof, that’s a rough workaround.

A lot of my high-level tools rely heavily on multiparms and those break the hardest due to this bug. It has driven me to start developing a Python build system for all the high level HDAs because they are unmaintainable by hand. That’s probably better in the long run anyway, but it’s been a lot of work to set up and really slows down the prototyping.

Would you mind detailing this a bit more? I've been curious about doing something similar but haven't gotten to this yet and am curious to at least the steps involved.