damian
If you update to the latest commit you might have to wait a bit for the daily build to finish that day.

For older commits, try to stick to the commits that have the same version as the current production build.

Also, if you are just a few builds apart, especially in 15.5 and older Houdini versions, you can usually get away with manually changing the version numbers in your local repo to what you can still download from the Daily Builds.

We are working an a better solution to this for the future but I can't promise anything soon.

ttvdsfx
Hello!

I am sorry to say, but we have not started this work yet. So baking separate meshes and then assembling them into a single destructible mesh is the only option at the moment. Having said that, we have a big interest from several clients and this RFE came up several times and it is quite likely we will start work on this feature soon.

awong
The path that I wrote was for 14.0.365 environment. Since it looks like you're using 14.0.362, you should try:
putenv PATH (“CProgram Files/Side Effects Software/Houdini 14.0.362/bin; ” + `getenv PATH`);

awong

Trent Polack
I'm running into the same problem with 2016 as was discussed here (and I tried all the solutions to no avail): https://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=38166 [sidefx.com]

Are you now getting the error “The specified module could not be found” ? If so, have you tried putting the Houdini's bin directory at the beginning of the PATH environment? You could do this in MEL before loading the plugin:
putenv PATH (“CProgram Files/Side Effects Software/Houdini 14.0.365/bin; ” + `getenv PATH`)