no I don't, but perhaps I'll have to look into that for a future video!

you're probably not doing something "wrong" -- it's most likely just a small tweak that needs adjusting. I'm not entirely sure what your specific issue is, since I can't see your file. However, I'd just make sure on every frame, you have 4 rest points that have unique names, and then you have 4 corresponding points with the unique names that match the rest points. Lastly, make sure your packed geometry has the same 4 names as well. If all those line up, and your packed geometry is centered in the origin, you in theory should be good. Let me know if that works.

@@mrbennelson Thank you so much! I kept looking over and over, couldn't figure it out. When u said center the origin something clicked. I found it to be in the assamble node I had it set to centroid. Changed it to pivot location to origin and it worked!

@@MathewMaths thank you! I’ve made one so far - check out www.parameter3.com

right click on any sop node, and click "asset manager". Then click the "configuration" tab. At the bottom of that tab page you should see a drop down selection parameter called "Asset Definition Toolbar" -- set that to "Show Menu Always" and you should be good to go!

No one uses Blender willingly.

​@@xl000 *except for the ones who worship it

Thank you, I appreciate that! Very kind of you to say.

Actually, unless he changed it, it says add animation. It doesn’t say how to pose, or rig, or animate.

It can do things all three do plus more, but crucially it allows different types of matter to interact and mix seamlessly, like grains and fluid. It also can give much better results than vellum in situations like snow or mud being compressed and accumulating

🤣🤣 I can't ever keep up tbh

I personally think Houdini has needed to make workflows easier for a long time, while maintaining the current deep level of control. If pre made setups can be easier to manage and pass along I’m all for that.

Tbh I’m not sure yet. I’m excited to see their keynote and hear more about it

@@mrbennelson they are using machine learning into their nodes, ML deformer and ML wrinkles to get better visuals, like for cloth deformations and and skin deformations in rig without using simulations cache.

I've always seen HDA's as a way to make a generalized tool that Houdini doesn't already have built out, or something that's specific to your project or studio needs. For example, an HDA that generates procedural houses would be a specific project need. Recipes are a way to pass a collection of nodes that would probably be used for a specific shot, or numerous shots. For example, say a studio needs 10-15 fire shots on an interior of a house. You wouldn't really make an HDA for that, but you could have an artist create the unique fire effects as a setup, then copy that as a recipe to then pass to other artists.

@@mrbennelsonNice video! Basically, recipes are collections of node parameter values (parm preset) or group of nodes (i.e. tool/decoration) represented as a JSON dictionary and stored as data assets in an HDA.

@@mrbennelsonI guess you mean a recipe is a more like a template of nodes that can be edited afterward to adapt different situations , an Hda is an asset which is the same for everybody and less flexible.

@@sethart22 right... I mean everyone is going to use these a little different, but in my experience HDAs have been used as generalized tools, where as recipes could be specific setups, or just a playbook for not needed to redo a lot of work. I think there's some crossover for sure.

It’s daunting for sure! Glad you found it helpful

This is best I've come across.

lol yes! My inspiration! I love his stuff and feel like the 3D sector could use a bit of it.

@@mrbennelson Yeah I think thats a great call, I think you're right. Great idea.

I think if people are daunted by using Houdini, and VOPS helps bridge the gap, then eventually they will be able to tackle VEX and not be inhibited. I think it just comes down to learning preference and prior experience with 3D and coding.

yes definitely. adobe is so far behind there are already solutions better than substance like InstaMat.. give it a year or 2 and this is gonna make substance look like a toy. The full context round tripping and implementation of ML on top of it makes this not only poised to be a substance replacement but potentially a comfyUI replacement as well. very exciting stuff

you happy with adobe bending you over ?

Substance designer*

Does anyone still use Substance anymore since Adobe bought them? Adobe's latest TOS said they can steal all of your work and use it to train AI!

@@Create-The-Imaginable I always worked procedurally within Redshift. What tools would you recommend other than Substance? Thank you

Amazing! Thanks Tom, if you're interested, I'd love to hear your thoughts on what courses / tools / etc could be useful to you on the site. I'm trying to talk to as many people as possible to have a clearer picture on where the pain points are. You can find my email on the contact of this channel. No pressure though either way, glad to have you join!

That's totally fine to disagree, and I'd encourage it for discussion. I do feel like the COPs workflow will eventually balloon into more AI + ML image post processing, denoising, upscaling etc that would be very wise for Houdini to lean into. But I could be totally wrong. I think Houdini has a lot of great features such as USD and Solaris gaining traction.

Agreed, there’s a new ML node, it’s coming :)

Amazing! I’m gonna have to try that - will save more time and just be simpler! Thanks!

I think that’s great! As you progress with Houdini you’ll pick up on bits of information and code if you need to.