Ohh, I like this idea…
I often array gems as block instances, then I can add prongs to the block - but this doesn’t account for curvature of the surface it’s orienting to. So this ‘between’ option would solve that nicely!
Hi, it works well in the latest version, but the Expand/Collapse state isn’t saved; it resets to ‘Expand’ when restarting the command. Thanks..
That was intentional as hiding things from users is tricky for us as they often forget how to get back to where they were and call support and this command requires clicks in different panel sections to go.
Let’s see how this condition plays out and we can go from there. It’s not hard to make it remember for the session if its a wide spread issue. I made a pass through today and pulled out a bunch of padding and freed about about another 100 pixels vertically. That will roll out in the next wip.
Thank you for preserving the old method, and please don’t remove it in future releases! I see how the new tool is useful, but it is also overly complex in some use cases. I just wasted significant time trying to array an object, and the tool defaulted to rotating them rather than preserving the original object’s orientation. My guess is that it was following the World orientation rather than the C Plane orientation. Being able to specify this would be very useful when working on projects that are not set to the standard World XYZ.
+1 for an additional option that would allow you (in the new UI) to set a base point and orientation in the world that’s not the bounding box center – some way to “start off” with the old behavior and then still get to use all the fancy new features =)
Hi all, I’m struggling with a mysterious bug (or behavior) in the new ArrayCrv. I get all the way through the settings, but when I hit apply, the dialog disappears and no objects are generated. After some experimenting, I’m realizing I can’t get it to “bake” any objects at all. Anyone else seen this?
Here are some screenshots of the geometry, the dialog, and the command history after I hit “apply.” I’ll also attach the rhino file for good measure, but it’s literally just a box and a line.
What am I missing here?
arraycrv-doc.3dm (99.5 KB)
The original ArrayCrv is back! The familiar workflow from Rhino 8 has been reinstated in the Rhino WIP, and the new command can now be accessed by using ArrayCrvAdvanced.
Several new changes to ArrayCrvAdvanced in this weeks WIP.
Double clicking an existing collection of array objects triggers the command to edit mode (re-runs arraycrvAdvanced)
Double clicking the viewport grips now gives you an input box.
Hitting ESC can now exit the command if you manage to overwhelm your pc with a complex request.
History is now playing by the rules and pushed pretty far into and beyond the limits.
Editing the parent array objects attributes now triggers a history replay on the array objects.
Object Edges are now valid inputs for drive curves
Match button can now match an existing array or a current array to new curves or edges. Matched layouts are individually editable after completing a layout.
A new “Between” orientation mode lets you select an existing array of objects to place objects between (eg fence post - fence panel - fence post - fence panel or prong - gem - prong). Betweens try to retain history link to their parent array.
That’s amazing ! 
Jaw dropped.
Ecellent!
Ahh, yes the original ArrayCrv isnt going to hold uniform spacing on curvature. The new command does but doesnt support a No Rotation option. We can see about adding No Rotation in the future.
RH-96473 ArrayCrvAdvacned - No Rotation option