Rhino WIP Feature: ScaleEach

[piac (Giulio Piacentino)]

What is ScaleEach?

ScaleEach is a new command in Rhino WIP. This command makes it simpler to change the size of multiple objects at one time.

Why ScaleEach?

ScaleEach allows varied methods of scaling multiple objects at once. Prompting is similar to the standard Scale command but with more options for the origin point and scale factor and style. Use cases could include: adding randomness to a landscaping scene, patternmaking for shoes or grillwork, or blending object sizes over a user customizable distance.

How It works:

Scale mode can be set to:

• Random factor - Scale each object randomly within a range of scales
• Gradient factor - Progressively scale each object to a different scale factor.
• Uniform factor - Set one scale for every object.
• Selection Order - Scale progressively based on selection order of objects.
• Attractor - Scale progressively out from a single point attractor

Random can be used in cases to create a more natural look of duplicate objects:

Gradient can be used to create a progressive pattern from objects:

It applies a scale transformation to each object independently, using an "origin point” that is generated from each object. Origin points can be set to:

• Centroid of objects
• Bounding box middle center
• Bounding Box Bottom center
• Any point relative to the bounding box
• Gumball anchor point

In addition the Scale axis can be set to be non uniform. select the Single or combined axis of scaling (ie. X Axis only, Y axis only, XY Axis only, etc…)

Below show the different ways scaling modes work with the a set of objects.

Uniform applies the same scale factor to all objects.

Gradient transitions from the smallest to the largest values,

Random creates a list of values and assigns these as scale factors to the objects in random order.

Attractor transitions from a radial point outwards.

Selection Order creates a numerically ordered list based on the order in which the geometry is selected.

Try It:

1. Download and open

   ScaleEach-Array.3dm (184.7 KB) in Rhino WIP.

   

2. Run the ScaleEach command

3. Select the all the circles.

4. Select Factor in the command line, set it to Gradient

5. Click the slider handle and drag the slider to reposition it.
   

   

6. Adjust the sliders’ values.
   

   

7. Press Enter or the space bar to complete the command and confirm the result.

8. Experiment with the other scale styles, uniform, selection order, random, gradient, and attractor.

Download the Rhino WIP…

[theoutside (Kyle Houchens)]

cool!

would be great if this worked on subobject selected subd faces-

[piac (Giulio Piacentino)]

@theoutside

great if this worked on subobject selected subd faces

@theoutside I agree. Can you make a YT issue and assign it to me?

[JosephML]

I have been waiting for this since Rhino 4! Illustrator has been doing it for a long while and I find it so useful to my work flow. Posted about it many years ago and I am so excited to see it being implemented!

[Jarek]

@piac

Special points can be centroids, bounding box centers, a particular location of the bounding box, or the gumball anchor point

This is great Giulio! Just from reading this I wanted to request block instance base point as another “special point” to add. I guess it would need to be a boolean since if you have mix of objects, non-blocks still need another special point defined.

How is the gradient defined? I did not have a chance to try but I imaging along X,Y,Z or maybe even along directional curve?

Another wish: random option but only from user-defined set of values (0.2, 0.4, 0.6, 0.8, 1 for example)

Also, why limit yourself just to Scale? The same can be very useful for other transforms (Move,Rotate). Not sure if you can combine all in one command or these are future commands. But if one command, they could be combined at once making it very powerful, like BoxEdit on steroids (big thing missing from BoxEdit was random option).

–jarek

[davidcockey]

ScaleNUEach is a logical next step.

[Daani (Dani)]

Looks awesome!

I’ve been using ''Box Edit" panel with the “transform individual objects” option checked to come around this feature.
Following the same logic, it would be nice to also have something like “Rotate each”.

Keep up the good work!!

[can.aysan (ACAN)]

In 3DS Max you can choose to apply transformations to the whole selection (as the whole group of object’s “pivot point/gumball”) or to individual objects “pivot points/gumball”. That way you can just select what you need and apply the transformation to the selected group of objects. Works quite well

How to Rotate Multiple Objects Around Their Pivots in 3Ds Max | Quick Tutorial #shorts #3dsmax

[piac (Giulio Piacentino)]

@JosephML

Posted about it many years ago and I am so excited to see it being implemented!

Thank you for posting this. Please feel free to let us know if you find any problems or have some requests.

@Jarek

block instance base point as another “special point” to add

Yes it might be nice to add “Peculiar points” for objects, where these are not coincident with centroids. Our goal is to make this accurate. Gumball anchor points can help, but only at times. Block insertion points are some of these; curve start/end points, object minimae/maximae (if single and obtainable) might come in the future? Probably these will be added based on popular demand.

@Jarek

How is the gradient defined?

Currently, from a minimum to a maximum in order of selection.

@Jarek

random option but only from user-defined set of values (0.2, 0.4, 0.6, 0.8, 1 for example)

OK; I’ll add this.

@Jarek

The same can be very useful for other transforms (Move,Rotate)

@davidcockey

ScaleNUEach is a logical next step.

@Daani

something like “Rotate each

You guys are on fire!
About multiple axes, it’s a little different because each object needs a realignment plane, and this maybe could come from (axes of inertia?). I haven’t thought about this enough.
RotateEach will surely be added if there’s enough demand. I’d like to get some feedback from ScaleEach to understand the needs.

Thanks guys for all the feedback so far. Keep it coming!

Giulio
giulio@mcneel.com

[davidcockey]

@charles.ranken

May I ask if it could be possible to make a ‘Scale - Direction Extent - with an Item Count’ feature? Similar to this in MoI?

This looks like it is about creating copies of an object. ScaleEach is for scaling existing objects which do not have to be an array.

What does that method in MoI do which is not possible using Array in Rhino?

[davidcockey]

@piac

About multiple axes, it’s a little different because each object needs a realignment plane, and this maybe could come from (axes of inertia?).

@piac If this was in response to my request for ScaleNUEach then my request was misunderstood. I’m requesting ScaleNUEach to work similar to ScaleNU - separate scale factors in the x, y and z directions in either the World or Cplane coordinate system. NOT a different axis system for each object.

[charles.ranken]

Hi David,

On reflection I agree with you, Array and ScaleEach are more distinctly separate transform tools than I had previously thought. I will delete my post here and make a new thread.

(as an aside: In Rhino, ArrayLinear only offsets each arrayed curve from each other, with the second reference point being the distance between each arrayed curve. In MoI, you can also array multiple curves within a set distance or within a curve’s extents.)

[piac (Giulio Piacentino)]

@davidcockey

ScaleNUEach to work similar to ScaleNU - separate scale factors in the x, y and z directions in either the World or Cplane coordinate system

I see. Would it also be useful this way? Essentially, this would not need a new realignment plane, just a new base point for each object. Axes would not be changed. Correct?

May I ask, were would you use this workflow?

[davidcockey]

@piac

I see. Would it also be useful this way? Essentially, this would NOT need a new realignment plane, just a new base point for each object. Axes would not be changed. Correct?

Correct.

@piac

May I ask, were would you use this workflow?

Multiple section curves which will be used to create a surface, and need to change the proportions of each section curve relative to a corner of its bounding box but not the position of the section curve.

[piac (Giulio Piacentino)]

@davidcockey

Correct.

There’s a new “NUAxes” option now, that should make what you ask possible. I didn’t want to add a new “NU” version of the command. See if it’s any useful!

[davidcockey]

@piac Thank you for letting us know about the new option.

A) A WorldCoordinates= option is needed like in ScaleNU.

B) The ability to apply a different scale fractor for each coordinate direction in one application of the command, like in ScaleNU, would be very useful. The function of the this option in ScaleEach and the function of ScaleNU should be consistent.

C) There are several problems with the interface which hinder it’s use.

Scenario 1:
ScaleEach
Select multiple objects in response to prompt and Enter.
From= and NUAxes= options are no longer available.
Scaling is from object centroids with no other options available.
Scaling is uniform, not non-uniform.

Scenario 2:
Select multiple objects
ScaleEach
From= and NUAxes= options are not longer available.
Scaling is from object centroids with no other options available.
Scaling is uniform, not non-uniform.

[RhinoFabStudio (Andres Gonzalez)]

Very Nice …

[Ivar_Havåg_Bergseth]

The first thing I tried was setting the Gumball origin for each object to the point I wanted them to scale from.
That didn’t work or didnt seem to be implemented, but I can imagine situations where it would be useful. For example, if you’re scaling multiple columns in a building and you already know which corner of each column should stay anchored.

Ultimately, this kind of controlled, per-object behavior is something Grasshopper handles, since it starts to fall into the parametric realm.

If this was implemented I imagen it would be an option in the command line, “Scale from gubal origin”

[wim (Wim Dekeyser)]

Hei Ivar -

@Ivar_Havåg_Bergseth

For example, if you’re scaling multiple columns in a building and you already know which corner of each column should stay anchored.

Doesn’t the From=AnyBoundingBoxPoint setting let you do that?
-wim

[Normand (Jakob Normand)]

Hi @piac
Great addition - it’s something I’ve been doing with small scripts so far, which brings me my comment: Would it make sense to add similar “variations” for move and rotate commands, especially the “Random” option, eg. for placing trees, making hole patterns etc.
-Jakob

OK, so read through the whole thread, and see that this has already been mentioned - add my vote