amilne

This has been very helpful! I've been trying to do something similar, but I've run into a few problems.

We want a site-wide setting to disable the “Open Help Browser at Startup”. This setting is in hcommon.pref I tried creating a hcommon.pref.nosave containing

#include “$HOME/houdini10.0/hcommon.pref”
startupHelp := 0;

And then I put the directory containing this hcommon.pref.nosave in the front of the HOUDINI_PATH. This all works fine, except that now if I change any of my preferences in Houdini which would go in the hcommon.pref file, it doesn't save them to my $HOME/houdini10.0/hcommon.pref anymore. This is no good if the user can't save any of their other preferences. Did you run into this?

Also, we wanted to change some display settings which are found in display.pref. This file seems to be a different format and I can't get it to work. I put the following in display.pref.nosave, but it never seems to get picked up:

#include “$HOME/houdini10.0/display.pref”
near ( 10 )
far ( 1000000 )
adjustlimits ( 0 )

I put the display.pref.nosave in the same location as the hcommon.pref.nosave, which does get picked up.

Thanks for your reply. Setting aside for the moment the issue of actually using the value of the parameter, what I really want to be able to do is to display a calculated value to the user. So, as they tweak some parameter, they can immediately see the effect on the calculated value instead of having to try to infer it from the way the output geometry changes.

I can use addMessage to display the value when the user middle-mouses over the node, but then it's not visible while they're tweaking the parameter; it requires some extra clicks. It would be so much more convenient if I could display the calculated value in the parameter editor right next to the parameter that affects it.

An example of what I'd like to do is the DOP Network. It has a timestep parameter which contains the expression ch(“timescale”)/(ch(“substep”)*$FPS) The user tweaks the timescale and substep attributes, and sees the effect on the timestep attribute, which is what the node actually uses internally. Additionally, if they really want to, they can delete this expression and set the timestep explicitly. However, my calculation is too complex to put in an expression (it involves reading some files off disk), so I can't do it this way.

It sound like the only correct way to do this is to use two nodes. The first calculates the value and puts it in a detail attribute. The downstream node can then display this value in a parameter using the “detail” expression function. Then I'd have to put both nodes in a subnetwork so that I could display both parameters to the user on a single node. But this is really cumbersome.

I'm writing a SOP which sets one of its parameters (call it “foo”) with setInt() when it cooks. I see the value update immediately in the parameter editor. However, if another parameter has an expression which references it (e.g., ch(“foo”) ), the display of the numeric value of the expression is not updated until I do something like change the frame. I have confirmed that the expression is actually evaluating to the correct value in my SOP, even though the display is incorrect. How do I make Houdini update the value of the expressions when I change the parameter?

Is having an “output parameter” like this not supported? If so, what is the correct way to achieve a similar effect? I tried a local variable, but it had the same update problem.