Timeline for Accumulate field and for each loop
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18 at 17:41 | comment | added | Markus von Broady | @DanielMöller I've done that plenty of times. You can for example pass "Index" to "Separate Geometry", with only the first index implicitly converting to FALSE boolean. So you can keep removing the first element, modifying it, and joining with already processed elements. BTW, I recently converted this to use the new for each zone and... It got 22 times slower... The algorithm wasn't ideal to showcase "for each" zone capability however... | |
| Oct 18 at 17:29 | comment | added | Daniel Möller | @MarkusvonBroady, can we really do a foreach "element" using the repeat zone? | |
| Oct 10 at 16:46 | comment | added | Markus von Broady | @DanielMöller Yes I think this is the only real code flow element that is missing, You can kind of emulate a while loop (repeat zones are slow, and that one is much slower) using this workaround: blender.stackexchange.com/q/320815/60486 | |
| Oct 10 at 15:04 | comment | added | Daniel Möller | Probably faster, but even though it's not, it still saves lots of edit time, so..... What i'd love to see is a "loop while" node. | |
| Oct 10 at 14:35 | comment | added | Markus von Broady | Someone should benchmark and see if the foreach solution is faster, hopefully a lot faster, otherwise it's just a small QoL feature... | |
| Oct 10 at 13:56 | comment | added | cjorssen | Thanks for your time (+1). Your alternative seems to work as well. | |
| Oct 10 at 13:48 | history | answered | Daniel Möller | CC BY-SA 4.0 |
