First you say it's downstream
This really is a pipe with data pushed down through the nodes.
Then you suddenly say it's upstream
Well, the truth is, it's all about upstream, not downstream. Node with display/render flag asks for a geometry its input node and so one recursively. Does't matter. The theory is quite correct. CopySOP isn't any exception from that. That's why you have to use stamp(), which the only reason to exists is to ask downstream node for the attribute existing there
I would say Houdini is all about downstreambecause that's the only answer why there is something like detail() or stamp() necessary anyway. If it would be upstream these wouldn't be needed because the attribute/variable is created before it is evaluated and it everything is fine. So the upstream theory doesn't work out as well.
Now, back to Maya, the familiarity effect last two weeks, and then you end up with usability issues for the rest of the time. Adsk decision for mirroring MEL commands with Python was good only for people using ~15 commands casually. Anyone using scripting intensively curse Adsk. It's ironic you compare the worst Python implementation in business with one of the best saying how good is to actually break Python, lost its object oriented nature and mirror it with ancient and horrible dialect that no one really wants to use these days. Thank god ,the Foundry wasn't doing the same with TCL to Python transition in Nuke…I think we should get clear about the difference of Python as a scripting language and Python as an expression language. As a scripting language it should keep its object oriented structure but as a expression language this is like taking a sledgehammer to crack a nut.
You can actually use AttributeCopy there. Just use the attribute after you have copied it… Leave Line Sop alone, copy your attribute, add PointSOP for example, ad type in TY field the same expression with $PT multiplication:I have to copy the attribute and then I still would have to use detail() to get the attribute?
detail(“../attributecreate1”, “height”, 0) * $PT
This is more workaround then just using the expression on the line SOP or am I missing something?
You can, with AttributeCopyNo I can't. I can't shuffle that attribute in before the line SOP, so that it is utilizable there. I can only shuffle it in after the line SOP where it is basicly needless.