misterbk

Thanks! Taking a look.

What does the “Index Param Name” parameter actually do in the cache SOP?

The only documentation I can find is the phrase, “A stampable parameter set to the index during caching.”

It defaults to the letter i. I tried changing “Index Param Name” to ‘q’ and to “I_like_pizza”, and nothing seemed to change.

I've got a cache node with a stamped value for ‘Index’ that is working as far as I can tell.

Is this so that other nodes can stamp in the current index the cache is looking up, or something?

Another long shot question, just in case someone has an answer…

I have a (manually created and positioned) point P that is next to some geometry GEO. I transfer the normals from GEO onto P, and then use a copy sop to stamp some INST geo on to P.

I want to have a manipulator handle on P that lets the user apply an additional tweak rotation to INST, after it has been stamped on P. That's all well and good, I've created a persistent xform handle and linked its (rx, ry, rz) to a transform node that rotates INST before it gets stamped.

My problem is I can't figure out how to set the xform handle's (rprex, rprey, rprez) so that the rotation handle is correctly lined up to where the user sees the geometry. Is there a nice ‘Houdini’ way to do this, or do I just need to keep bashing my head against writing some horrid attribute scripts to try and convert N into Euler angles the same way that the copy sop does, and feed them into the xform's (rprex, rprey, rprez)?

———————————————-

For a visual example, say INST is a nail and it's being stamped several times (in a specific static way, not scattered) on GEO which is a tree. After being aligned to N during stamping, I want there to be rotation manipulators so the user can tweak the orientation of each nail.