Elliot Stronge
The custom file path option for saving recipes seems absolutely broken. I tried saving a recipe to a network location (i.e. "//something/goes/here/recipe.hda") and for some scuffed reason it appended "C:\User\username" to the front. When I try manually type the location I cannot delete the "C:\" part without it automatically refilling "C:\User\username" again so I can never fully clear the field. What on earth is up with that? Such incredibly frustrating design.

What is the intended design here? I just want to save a recipe to a common location (i.e. with HOUDINI_PATH or HOUDINI_OTLSCAN_PATH) so other artists can use them.

Thomas M
Hi everyone,

I’m trying to load my Houdini recipes from a custom Google Drive folder, but I can’t tell if Houdini is recognizing the setup. The Mops.json file in the packages folder is working fine; it’s just this custom directory that’s giving me trouble.

Here’s what I’m using:

json
Copy code
{
"HOUDINI_PATH": "j:/My Drive/Houdini_Recipes",
"env": [
{"HOUDINI_CUSTOM_RECIPE_DIR": "j:/My Drive/Houdini_Recipes"},
{"HOUDINI_CUSTOM_RECIPE_LIBRARY": "myrecipe"}
]
}
I’ve tried adjusting to forward slashes, but still no luck. Does anyone know if HOUDINI_CUSTOM_RECIPE_DIR is valid for loading recipes, or have advice on getting custom paths to work?

Thanks!

vla
Possible solution, while we wait for an option to disable the HUD sliders

Rifs

mabelzile
{
"hpath": "/var/tmp/myrecipes",
"env" : [
{"HOUDINI_CUSTOM_RECIPE_DIR": "/var/tmp/myrecipes"},
{"HOUDINI_CUSTOM_RECIPE_LIBRARY": "myrecipe"}
]
}

how do you set it up, pretty boob here. Do you mind giving more detail like what file goes where?
and also what if I want to save on D: drive (D/lib/houdini)?

folpatte
That is something that I would be interested in too. Being able to save recipies in a custom directory, and set a custom path to load them, so that they would be installed on startup, just to be able to store recipies for upcoming versions of Houdini.
Would be great !

{
   "hpath": "/var/tmp/myrecipes"
}

/var/tmp/myrecipes/otls/myrecipe.hda

{
   "hpath": "/var/tmp/myrecipes",
    "env" : [
        {"HOUDINI_CUSTOM_RECIPE_DIR": "/var/tmp/myrecipes"},
        {"HOUDINI_CUSTOM_RECIPE_LIBRARY": "myrecipe"}
    ]
}

RGaal
the settings panel, Ctrl + Shift + Wheel still does not work

RGaal
Hooray, guys! The HUD has become a little useful in 321! Now the mouse wheel in the numbers window changes tenths, Shift + wheel - hundredths and Ctrl + wheel - thousandths! Excellent!
Thanks, mabelzile, this is just an amazing speed of improvements! Let's like it, guys, don't be lazy, applause to the developers for caring about our convenience!
And now let me talk a little about the remaining shortcomings.
1) The sliders are still useless, they just take up space, I would prefer to remove them. Shift and Ctrl do not work on the sliders, so their "precision" makes them useless and clutters the screen. Try to make a polyexestrude and adjust something with a slider - it's pointless. I can adjust the mouse wheel much faster and much more accurately. Sliders are not needed in this form.
2) The traditional lack of unification of the interface, shocking beginners. Ctrl + wheel on the slider in the parameters shifts by 0.1, on the slider in the viewport - nothing. Ctrl on the number in the parameters shifts the whole number, in the viewport shifts the thousandth part.
Personally, I am not afraid of this, but for beginners......
In any case, for adjusting the numbers with the wheel - a huge thank you!
If you also pushed the change of numbers with the wheel in the drop-down list 0.0001 - 100, which is used in all inputs - that would be just super!

quack_

mabelzile

quack_
another little bug I noticed that may or may not be related is this:

you can make the hud handle not appear for a certain node by quickly selecting another node.
in my case there is a small but noticeable delay when selecting a node before the hud handles appear.

steps to reproduce:

enter show handle mode (enter)
select node A (grid)
in the small delay it takes the handle to appear, quickly box select another node B (poly extrude)
before the handle for node B appears, quickly select node A again

the handle for node A will now never show up while you have that node selected

this hasn't caused the fully cursed state so far but may be related to the original bug since I do have a habit of spamming box selections around nodes while working and this seems to cause something going wrong with the handles

Thank you
Which build version are you using ?

apologies, forgot to mention.

20.5.312

dxdiag attached

RGaal
For the staff.
Guys, one of the reasons why HUDs are of little use is that using shift for a small step does not work on sliders, there is not enough precision, and scrolling with the mouse wheel does not change the numbers in the input field. So for accurate changes it is more convenient to go to the parameters and adjust there.

And by the way, it would be much more convenient than any HUD for everything to change the numbers with the mouse wheel in the drop-down list (0.001 - 100). So often you just need to add/reduce one step at some level, but carefully moving the mouse a little for this is already inconvenient and stressful.

quack_

mabelzile

quack_
another little bug I noticed that may or may not be related is this:

you can make the hud handle not appear for a certain node by quickly selecting another node.
in my case there is a small but noticeable delay when selecting a node before the hud handles appear.

steps to reproduce:

enter show handle mode (enter)
select node A (grid)
in the small delay it takes the handle to appear, quickly box select another node B (poly extrude)
before the handle for node B appears, quickly select node A again

the handle for node A will now never show up while you have that node selected

this hasn't caused the fully cursed state so far but may be related to the original bug since I do have a habit of spamming box selections around nodes while working and this seems to cause something going wrong with the handles

Thank you
Which build version are you using ?

apologies, forgot to mention.

20.5.312

dxdiag attached

quack_
another little bug I noticed that may or may not be related is this:

you can make the hud handle not appear for a certain node by quickly selecting another node.
in my case there is a small but noticeable delay when selecting a node before the hud handles appear.

steps to reproduce:

enter show handle mode (enter)
select node A (grid)
in the small delay it takes the handle to appear, quickly box select another node B (poly extrude)
before the handle for node B appears, quickly select node A again

the handle for node A will now never show up while you have that node selected

this hasn't caused the fully cursed state so far but may be related to the original bug since I do have a habit of spamming box selections around nodes while working and this seems to cause something going wrong with the handles