Getting Started with Recipes | Houdini 20.5

Unlock the potential of Houdini 20.5's new recipe system. Learn how to create and use presets and tools to enhance your workflow. Recipes are a perfect way for artists to maximize efficiency and speed up their workflow in Houdini.
Support me on Patreon:
/ insidethemind
Speed up your renders using AI (affiliate link)-
www.topazlabs....
Join this channel to get access to perks:
/ @insidethemindspace
Join my Discord here:
/ discord
Leave a like and a favorite if you enjoyed. Subscribe if you want to.
Please let me know what you thought of the video.
Follow me-
insidethemind....
/ stormz3d
/ insidethemindspace
www.artstation...
#houdini #houdinifx #houdinitutorial

[@HoudinifxAlfredosanmartin]

How interesting, I really like it because I don’t have to look for the tools in my paper notes anymore. I’ve lost count of everything I’ve been noting down for years. I think it’s an excellent time saver and very convenient. Thank you.

[@InsideTheMindSpace]

Definitely. The other good thing that I didn't realize was that it saves as am HDA so it should be really easy to move your recipes around as you need

[@guitoma109]

Thanks for share those updates. It will help a lot to create kind of quick templates for my scenes. I am following your Intro to COP serie and I will complement with USD Solaris stuff to improve my Lookdev. See you in the next videos.

[@osmanertasdiken]

Great stuff! Thanks for keeping us updated

[@InsideTheMindSpace]

Glad you're finding everything useful!

[@Igrom_Gamedev]

Отличный гайд! Спасибо.

[@workflowinmind]

What does tool does over dragging it to the shelf? Just the menu ?

[@ivanchernyshev2646]

is it the same as HDA, but not packaged into a subnet?

[@InsideTheMindSpace]

Basically yes. You don't get to expose parameters or anything unless you built that into a control node I guess. It does save any parameters you set

[@julesRuk]

why my houdini 20.5 geometry in shades are invisible but in wire is visible😢😢😢😢😢

[@fahimjaowad8717]

How do I Edit these, eg: from recipe manager I want to remove one node.

[@mab]

select recipe, Edit button

[@vytasrauckis6703]

I noticed that when I created the node tree I already had a camera in another tree and the camera was named camera1 in the tree. When I saved the recipe, camera1 was specified in the recipe. SO, when I loaded the recipe, the camera in new node tree was named camera2 ( because camera1 still existed). This made karmarendersettings to warn me that camera1 was being used when camera2 was actually the camera.

[@ati7900]

This is an unfortunate drawback. When nodes are placed from the recipe, the newly placed nodes automatically renamed out of the way to avoid any name collision with existing nodes. However when you just specify 'camera1' as a literal for a parameter, that is the literal value that the recipe will apply to that parameter. At the moment there is no obvious solution for this issue, other then making your parameter reference the Primitive Path parameter on the camera node, something like this: `chs("../camera1/primpath")` And make sure that Primitive Path has $OS variable in there. Doing that, houdini will resolve references according to how the nodes were renamed upon creation.

[@ati7900]

Decoration recipes are based on the concept that you can dedicate a central node which then generates various setups around itself. When you apply a tool recipe to a node, that node will take the place of your central node (the central node that was selected when the recipe was created). Any references that were pointing to your central node at recording, will be all redirected to point towards your node that replaces the central node upon creation.

[@ati7900]

In your demo, changing the pattern therefore can cause unexpected results, because your decoration tool was really designed to be used with the domelight and not other nodes. The pattern in this case could be useful when you have multiple versions of the same asset (in a studio environment for example) and then you can edit the pattern to show for all the versions of the same asset.

[@ati7900]

Or another example: it would make sense to edit the pattern so that all lights are able to generate the recipe.