cruiserandmax
cruiserandmax
About Me
Connect
LOCATION
Not Specified
ウェブサイト
Houdini Engine
Availability
Not Specified
Recent Forum Posts
Shaded View Clipping Plane Nightmare (19.5) !? 2024年10月22日1:40
Has anyone noticed the auto-computed clipping plane values (Display Options -> Camera -> Homing Auto Adjusts -> Near & Far Clip Planes) in the shaded view (in H19.5) consistently fail to evaluate to whatever geometry you are trying to frame your view on?
It seems like a massive regression from h18.5.. There seems to be no rhyme or reason for when the dynamically calculated near/far clip will go wrong, so half the time I am having to set the near/far clip explicitly in Display Options which solves the problem temporarily while I am orbiting my view around a specific piece of geometry. But then when I try framing other things I need to either manually update the near/far values in Display Options, or set it back to Homing Auto Adjust Near & Far Clip Planes so it will frame geometry without clipping- but then as soon as I start orbiting the camera the geometry gets clipped or worse disappears due to incorrectly auto-computed clip planes...
This is in RHEL 9.4..
It seems like a massive regression from h18.5.. There seems to be no rhyme or reason for when the dynamically calculated near/far clip will go wrong, so half the time I am having to set the near/far clip explicitly in Display Options which solves the problem temporarily while I am orbiting my view around a specific piece of geometry. But then when I try framing other things I need to either manually update the near/far values in Display Options, or set it back to Homing Auto Adjust Near & Far Clip Planes so it will frame geometry without clipping- but then as soon as I start orbiting the camera the geometry gets clipped or worse disappears due to incorrectly auto-computed clip planes...
This is in RHEL 9.4..
Event handler specifically when an HDA is pasted? 2024年5月4日22:09
Is there any way to trigger a python script that is part of an HDA specifically when a copy of the HDA is pasted (only for the pasted copy)?
Neither On Created nor On Updated get triggered after the copy is pasted.
On Name Changed is triggered for both the copy and the source node after the paste.
On Loaded is triggered for just the pasted copy, but is also triggered for all node instances the next time the hip is loaded ...
Neither On Created nor On Updated get triggered after the copy is pasted.
On Name Changed is triggered for both the copy and the source node after the paste.
On Loaded is triggered for just the pasted copy, but is also triggered for all node instances the next time the hip is loaded ...
Example of using stroke meta data ? 2023年10月23日11:46
I'm interested in building a stroke tool that associates the frame number at which a stroke was drawn with the primitive of the stroke. It seems like stroke meta data maybe a good way to handle this, but following the docs it doesn't seem to work.
Does anyone have an example of setting custom data per stroke, and doing something with it after the stroke node inside the hda?
I have tried making an hda with just a stroke node inside, setting the hda Node Default State to stroke, dragging the Number of Strokes parameter from the parameters panel on the stroke node inside the hda to the Edit Operator Type Properties Parameters panel of the hda. Then adding a new parameter on the hda properties called something like stroke#_frame or stroke_frame#. According to the docs the Meta Data parameter on the stroke geometry node:
"Stores the values of all parameters whose names start with stroke_ from the top level node. These are copied into correspondingly named primitive attributes."
But the Meta Data always seem to contain just a list like
I can't figure out what I am doing wrong?
Does anyone have an example of setting custom data per stroke, and doing something with it after the stroke node inside the hda?
I have tried making an hda with just a stroke node inside, setting the hda Node Default State to stroke, dragging the Number of Strokes parameter from the parameters panel on the stroke node inside the hda to the Edit Operator Type Properties Parameters panel of the hda. Then adding a new parameter on the hda properties called something like stroke#_frame or stroke_frame#. According to the docs the Meta Data parameter on the stroke geometry node:
"Stores the values of all parameters whose names start with stroke_ from the top level node. These are copied into correspondingly named primitive attributes."
But the Meta Data always seem to contain just a list like
[ 0 ]
I can't figure out what I am doing wrong?