Remove/extend 1000 clone limit in Array modifier

[dswahn]

Yes, more than 1000 clones might seem like a lot for the Array modifier, but I have encountered situations where I need more than 1000 clones.

This hard coded limit of 1000 clones feels unnecessary and should be removed, or at least significantly increased.

Edit:

It seems like this clone limit applies to the modes Total Dimension and Relative Offset, which means using Fill mode as suggested by a user can provide a workaround since it allows for generating more than 1000 clones. However, in these modes the number of clones are determined by other factors than clone count, so setting a specific amount of clones can be tricky and tedious. It would be better if the other two modes had the clone limit extended or removed completely.  

Edit2:

I suggest that rather than having hard coded limits to spinners the Array modifier should have a Max Clones parameter similar to the Normalize Spline modifier has a Max Knots parameter that the user can change depending on needs. With the new "set default value" feature the user can specify any preferred default value, or just leave it to the factory default if the default value is enough for all situations.

[ads_delesdr]

The 1000 limit is just in the UI, probably to help prevent users from putting in a crazy high number, only to have the program hang which it tries to calculate the geometry.

To get past this for now, you can always set to your heart's delight through Maxscript or through a Trackview key (probably other sneaky ways too). You'll see the actual clone count at the bottom of the Distribution rollout.

Example (straight from the MacroRecorder):

$.modifiers[#Array].countX = 2500

[dswahn]

That's helpful, @ads_delesdr. Would it be possible to add this information to the documentation section about the Array modifier? It isn't obvious at all that this limit can be overridden via maxscript, but if the documentation explained this briefly it would likely help users looking for answers.

[ads_delesdr]

This wouldn't be something specific for the Array modifier, these sort of workarounds to UI limits are available everywhere in 3ds Max. Agreed that we could be more clear about this as a benefit of MAXScripting.