Jump to content
hopbin9

Copy stamp a string value?

Recommended Posts

@Edward: I would watch it. Also if you put some cool anims demonstrating things, I am sure it wouldn't be as sleep-inducing :)

Share this post


Link to post
Share on other sites

Edward, I'm sure that if you present it in way that is not too littered with hardcore coding language we non-c++ people can get at least something from it. Sometimes just catching a concept or an idea is enough to nudge somebody's way of thinking and only good will come from it.

Edited by Macha

Share this post


Link to post
Share on other sites

Some info in this mailing list post as well:

http://www.sidefx.co...=20&revdate=off

PS. I've been thinking that I should do an advanced presentation on cooking and dependencies in general after H12 releases. However, I'm not sure that anyone would care for it as I imagine it only being useful for (advanced) HDK users. However, I guess non-HDK users who want to really understand how the internals work would find it useful (at the cost of yawning through it all).

I too would like to know more about correct evaluation order. Considering how badly "feedback node" confuses me.

Who knows, beginners now will become advanced users may be after 10 years. :)

For sure your presentation will be remembered.

Cheers,

EDIT - Thanks Hop, Nice one.

Edited by vectorblur

Share this post


Link to post
Share on other sites

Who knows, beginners now will become advanced users may be after 10 years. :)

Well, if people shared more tutorials on the subject. It won't take 10 years ;)

Share this post


Link to post
Share on other sites

GOD I love this forum :D

I had this same problem trying to copy some string info from the template points...

Thanks hopbin9 and everybody else for providing the examples.. extremely helpful and educative :D!

Share this post


Link to post
Share on other sites

Don't forget that Houdini has to resolve all dependencies for an operator on a first-come first-serve basis that is invariably determined by the node creation order. This means that the links in SOPs only represent data flow from one operator to the next but given the complexity of channel references, other nodes pulling geometry from any node anywhere in the network, the only way to really tell how the network is evaluating is to use the old H11 performance monitor or to use the new Performance Monitor set up to Event Log View and toggle the Enable Output toggle. This lists the exact order in which Houdini evaluated every node and will answer all your questions wrt dependencies that had to be resolved for the changes occurred that marked nodes "dirty" forcing dependencies to be resolved in the current cook.

You can RMB on any node and view the dependents via the View Dependencies... option and references at the current time/frame as well.

You can display external references/dependencies for the network by opening the display options for the network pane (D hotkey) and in the Dependency tab, enable the drawing of the various widgets to indicate dependencies.

Do users need to know this? Sure, if they are using Houdini daily to earn an income and have a desire to get even better.

Should users need to care about this. 99.9% of the time, no. Houdini takes care of this for you and with the aid of the Performance Monitor, you can find out where the slow-downs are and tweak the performance of your network.

On the very odd occasion and more in the older releases of Houdini, when a file would't evaluate properly, simply cutting and pasting a node that was first in line to be last in line in order of creation (determined by the Performance Monitor) has worked around many an evaluation dependency cook error/bug.

  • Like 1

Share this post


Link to post
Share on other sites

Hi.. 3 years later and I've come across a similar question.

 

Good examples and effective solutions, but perhaps,

 

chs("../node/stringparm#") BECOMES

 

chs("../node/stringparm"+stamp("../copystamp","copy",0))

 

This will allow stamping of string parameters using the copy SOP, with one variable in the copy SOP called "copy" with a value of "$CY+1" (or whichever variance you wish to stamp by)

Share this post


Link to post
Share on other sites

stamping of string attribs is already supported within Copy SOP (since H13) through Attribute Stamps parm

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×