← All ideas
  • Published 16 Apr 2019

move all duplication techniques to an improved array modifier

The duplication of objects is a bit convoluted at the moment, some methods use the objects tab's duplication panel (frames, verts, faces, group), some methods use the array modifier, some methods need constraints to work etc.

It would be much better if all this could be consolidated into two array modifiers:

1, Array modifier = modifier that enables deformation and merging (results in a single mesh)

2, Array modifier (non deforming) = modifier that can array an object without merging/deforming (results in an array of instances for better memory usage.

Both arrays should have options to choose a curve (preferably without having a curve modifier in the stack), and the non deforming version should have options for instance rotation, translation and scale, and follow curve/path. as well as allowing to choose an object to array along with the standard options which are currently in the object panels duplication panel (faces, verts etc). Both modifiers should still have the option to choose an empty as an offset option.

if the non deforming modifier could have an option for child modifiers too, this would mean that a modifier could be applied to each instance, and each child modifier could base it's values on the array count, or perhaps the curvature of the selected curve (allowing for a bend modifier to deform each instance individually for a close emulation of the normal array modifier, but with better memory usage).

92%

Development Status: Open

Upvote 23 Downvote 2
3di
16 Apr 2019

3 Comments

4dezigner

A blender will never be an adult simulation package without a powerful cloning tool.

jason

The difficulty here (well, one of them) is that modifiers always, always generate a derivative mesh and never generate instances. To have modifiers support instances would not only require a massive (I believe) re-thinking of the modifier stack beyond even what's planned for Everything Nodes, but it would also present quite a few user interface challenges because of inconsistency and lack of predictability in how modifiers behave. You could no longer assume that the modifier is generating actual geometry... as a user, you'd need other mechanisms of feedback to make that clear.

zuorion

I don't think that instancer modifier will be made, while everything nodes that include modifier nodes are in development.