I want to make a digital asset with chop network inside it. There is a ForEach CHOP in this chop network. Inside ForEach CHOP there is Foreach_Iteration. I can't change Export Prefix on that CHOP, cause it is inactive (and other params too).
When I'm trying to create DA, it says /obj/../foreach1/Foreach_Iterarion is outside the network being saved. HOW I can change parameters on Foreach_Iteration CHOP (or make them active) to create a DA ?
can't create DA with ForEach CHOP
4074 10 2- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
- old_school
- Staff
- 2540 posts
- Joined: July 2005
- Offline
ForEach SOP using the “Each Number” range option.
VEX is all about SIMDI execution of data. One point at a time.
If you really need to do this in VOPs, then the best approach is to construct a point cloud to iterate over several times but even that won't be nearly as efficient as using a trivial ForEach SOP.
>>> Sorry for the confusion. Yes you said CHOP…
VEX is all about SIMDI execution of data. One point at a time.
If you really need to do this in VOPs, then the best approach is to construct a point cloud to iterate over several times but even that won't be nearly as efficient as using a trivial ForEach SOP.
>>> Sorry for the confusion. Yes you said CHOP…
Edited by - March 26, 2012 14:38:45
There's at least one school like the old school!
- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
- zarti
- Member
- 330 posts
- Joined: July 2007
- Offline
morzh
I want to make a digital asset with chop network inside it. There is a ForEach CHOP in this chop network. Inside ForEach CHOP there is Foreach_Iteration. I can't change Export Prefix on that CHOP, cause it is inactive (and other params too).
When I'm trying to create DA, it says /obj/../foreach1/Foreach_Iterarion is outside the network being saved. HOW I can change parameters on Foreach_Iteration CHOP (or make them active) to create a DA ?
hi ,
just reading from your first post ..
maybe it is better to keep all you references in expressions relative and within your DA .
a path starting with /obj is an absolute one .
i could be wrong ..
except the things that cannot be seen , nothing is like it seems .
- old_school
- Staff
- 2540 posts
- Joined: July 2005
- Offline
OK.
Head screwed on correctly and again sorry about the mistake above.
I had a forum post last week where I commented on the use of opls -al to do a long listing on a node and that you could change permissions on nodes.
Well guess what? That is exactly what is happening with the For SOP inside the ForEach SOP.
You can query the state of the nodes inside the ForEach SOP in a textport:
-> cd /obj/geo1/chopnet1/foreach1
-> opls -al
-r–e-cs Foreach_Iteration Apr 1 16:17 Jeff
d—e— Output Mar 26 14:27 Jeff
—-e— jiggle1 Mar 26 14:29 Omid
—-e— jiggle2 Mar 26 14:30 Omid
As you can see, the read, write and execute permissions for this node have been turned off.
To enable this SOP to be edited, in the textport type:
-> opchmod 777 Foreach_Iteration
now confirm with:
-> opls -al
-r–e-cs Foreach_Iteration Apr 1 16:41 Jeff
Make your change in your asset and test that it works. In this case, change the Export Prefix from ../../../.. to ../.. or make it blank. That should do it.
Finally to lock the node back up (as it was intended to as you really shouldn't edit it), do a:
-> opchmod 000 Foreach_Iteration
and a final check:
-> opls -al
-r–e-cs Foreach_Iteration Apr 1 17:05 Jeff
As I mentioned last week, this catches out even hard core Houdini users and is a great technique to make a node non-editable upon delivery to the end user. I use this technique in my HDA's as it works like a charm.
Head screwed on correctly and again sorry about the mistake above.
I had a forum post last week where I commented on the use of opls -al to do a long listing on a node and that you could change permissions on nodes.
Well guess what? That is exactly what is happening with the For SOP inside the ForEach SOP.
You can query the state of the nodes inside the ForEach SOP in a textport:
-> cd /obj/geo1/chopnet1/foreach1
-> opls -al
-r–e-cs Foreach_Iteration Apr 1 16:17 Jeff
d—e— Output Mar 26 14:27 Jeff
—-e— jiggle1 Mar 26 14:29 Omid
—-e— jiggle2 Mar 26 14:30 Omid
As you can see, the read, write and execute permissions for this node have been turned off.
To enable this SOP to be edited, in the textport type:
-> opchmod 777 Foreach_Iteration
now confirm with:
-> opls -al
-r–e-cs Foreach_Iteration Apr 1 16:41 Jeff
Make your change in your asset and test that it works. In this case, change the Export Prefix from ../../../.. to ../.. or make it blank. That should do it.
Finally to lock the node back up (as it was intended to as you really shouldn't edit it), do a:
-> opchmod 000 Foreach_Iteration
and a final check:
-> opls -al
-r–e-cs Foreach_Iteration Apr 1 17:05 Jeff
As I mentioned last week, this catches out even hard core Houdini users and is a great technique to make a node non-editable upon delivery to the end user. I use this technique in my HDA's as it works like a charm.
There's at least one school like the old school!
- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
- Alejandro Echeverry
- Member
- 691 posts
- Joined: June 2006
- Offline
Thanks Jeff!!!
Feel The Knowledge, Kiss The Goat!!!
http://www.linkedin.com/in/alejandroecheverry [linkedin.com]
http://vimeo.com/lordpazuzu/videos [vimeo.com]
http://www.linkedin.com/in/alejandroecheverry [linkedin.com]
http://vimeo.com/lordpazuzu/videos [vimeo.com]
- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
- morzh
- Member
- 66 posts
- Joined: Oct. 2008
- Offline
-
- Quick Links