Cant find a simple way to do with the new for workflow what I used to do with the old subnet for…
Cant make the new “for number of iterations” system to work as the okd one, the new one is accumulating everything inside the loop rather than to do it once at each iteration
I'v found a workaround wit copy / assemble adn foreach loop but its kind of cumbersome and I wonder if I'm missing something in the new for each…
See attatched hipfile.
By the way, when I use the new thing inside an attribute vop more than often the vop goes in error and i have to setup manualy the variable type for each output in the end block.
THANKS
new vs old foreach
2366 3 2- NAHASSIA
- Member
- 125 posts
- Joined: June 2008
- Offline
- jlait
- Staff
- 6224 posts
- Joined: July 2005
- Offline
I think we need to add another mode to the For-Begin SOP.
Currently it is
Fetch Feedback
Fetch Piece
Fetch Metadata
The problem is your network is set to Fetch Feedback. That is why it is grabbing the previous iteration and accumulating the transform.
The current solution is simple, if not obvious. Wire pointjitter1 directly to grid1. Do not pass through repeat_begin1.
If we added another mode,
Fetch Input
it might be easier to recognize this need.
Currently it is
Fetch Feedback
Fetch Piece
Fetch Metadata
The problem is your network is set to Fetch Feedback. That is why it is grabbing the previous iteration and accumulating the transform.
The current solution is simple, if not obvious. Wire pointjitter1 directly to grid1. Do not pass through repeat_begin1.
If we added another mode,
Fetch Input
it might be easier to recognize this need.
- NAHASSIA
- Member
- 125 posts
- Joined: June 2008
- Offline
- DASD
- Member
- 453 posts
- Joined: Feb. 2013
- Online
-
- Quick Links