Martin Brattensborg

Ended up figuring this out with some help from a kind stranger over on Discord.

My problem was two-fold:
1. I wasn't specifying a file extension in the third argument of the hou.data.saveNodePresetRecipe function, meaning that the file was created on disk as a blank file. On Linux this file was just interpreted as a folder with multiple other files inside (a .json file and a few other files). This made the recipe work in the Houdini session it was created (maybe the command adds the recipe to memory while Houdini is open?) but did not end up loading it when Houdini was re-launched. Instead, the recipes should be stored as a .hda file, which I should have been able to infer.
2. I was storing the recipes in the C:/users/my_user/Documents/houdini20.5/Presets folder instead of the C:/users/my_user/Documents/houdini20.5/otls folder. This also causes the recipe to only be available in the Houdini session it was created in, even if the file is saved on disk as a .hda file. When I switched to use the otls folder and saved the recipe as a .hda file everything worked immediately as expected.

Hi all!

I've recently been looking into the new recipe system in Houdini and have been trying to create new recipes through the Python API using commands like hou.data.saveNodePresetRecipe(). However, I've hit a little snag, I am able to write out files to disk and the recipe does immediately appear on the intended node, but after a restart of Houdini, the recipe is gone from the overview, even though it is still on disk. If I try saving a recipe with the built-in tools I do not get this behavior, also, the built-in tools store the recipes inside a .hda file, while this command seems to give a more raw output, instead, creating a folder on disk with a .json file containing all the parameters and options for the recipe with some other supporting text files.

So far, I have only tried to store these custom recipes either inside the oils folder or the Presets folder of my prefs folder. I am not sure if there is another directory I should store them in or if I have to specify a directory as an environment variable in the .env file so that Houdini knows where to find them.

If anyone knows why the recipes created by this command are only visible while I keep Houdini open and are lost when I restart, I'd be very grateful if you could share your knowledge. Is this command only intended to be used alongside the hou.data.applyNodePresetRecipe() command to recreate the recipes?


Thanks for the read!

Hello!
I'm kind of new to Karma, Solaris and the whole LOP context so please forgive any lack of knowledge.
I'm trying to transition from using Mantra to Karma and stage on a project I am working on and I've come across the first hurdle I haven't been able to solve by reading up on the documentation. I am rendering very thin curve geometry and I was looking for a setting in Karma that would be equivalent to the "vm_geometryfilterwidth" parameter you can add for Mantra so that when geometry approaches sub-pixel the renderer always keeps the geometry x amount of pixel in width but compensates by lowering the alpha value instead. Doing this so that I won't have to increase the pixel samples to un-godly amounts just to cleanly render a constant shaded spline without having the thinnest parts flicker in and out of existence.

Any advice on this is greatly appreciated, thank you so much for the read!