Hello,
I have a group of nodes that need to be run with a view and 3 lists.
Task #1 is to create a bounding box list.
Task #2 is to apply the list of crops to the given 3D view
Task #3 is to export the given 3D view as an image, once for each crop.
In the screen shot you can see the data I feed to the group.
Currently the images exported are all the same, they show the last crop only.
I tried lacing longest, on some of those nodes, but no luck.
Any suggestion / improvement?
Sometime ago I solved a similar issue using a custom node, which worked in executing the nodes through the lists of data, but I wish to avoid using custom nodes now.
Ah…
Dynamo runs all the way through and stops… So with some stuff you can’t get it to do X… then update to Y.
Unless… you set it to periodic… and step through each run.
So it runs for the first box… then runs for the second etc.
I’m not sure if exporting images would allow you to step through the process without using periodic… But the periodic method would work.
IF you can alter the scope box… then take a picture… then alter the scope box and take a new picture… you’d have to do that in a python loop I’d guess… or build one bunch of nodes per run.
You can set your run to automatic, manual or periodic.
If you added a counter to step through the indexes depending on time you could step though each bounding box.
You could try repeating the nodes so you set box at index zero, then take picture, set box at index 1 take picture… But I don’t think that’ll work.
Periodic lets dynamo run… then run again, then run again…
So it’s actually several runs, one for each index.
Also… if you’re only doing 5 views then periodic is fine… You can get it to run every 5 seconds easily. Even the worst computer can manage that surely!
That’s annoying. I’ve never had issues creating hundreds/thousands of views at once, even 3Ds. Is it feasible to break it down into chunks (e.g. max 300 views or something) where it won’t crash? Otherwise I think you’re stuck with having to use either custom node(s) or Python…
The one I sent to Jacob replaced the “View3D.SetSectionVBox” node with the OOTB “View.CropBox” which is just the view 2D crop, NOT the Section Box. That was my mistake.