Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Submitted byAnonymouson05-27-201603:38 AM
Status:
Implemented
Allow a single instance of a model array
When controlling arrays with parameters it is sometimes convenient to allow the value to drop to a single instance i.e. Shelves in a cupboard.
The workarround (adding If statements, visibility parameters and additional single instances on top of the controlling instance) is clumsy and longwinded.
This would save a lot of time! There are a lot of instances where this would help. Even in a family where you doubt it would be an issue I like to put it in, because if placed wrong once it will break.
To expound on my previous comment in any of my families that have anything arrayed (A line based pendant family to signify the backstroke line in a pool, casework that can have 1 or more drawers, casework that can have 1 or more shelves to name a few) I have to have extra families and parameters to deal with the fact that array's break if set to 1.
Ideal - 1 instance of nested family to be arrayed (a
Parameters needed
Array Count (user input or calculated on length as appropriate, controls array)
Actual - 2 instances of nested family, 1 arrayed, 1 not
Parameters required to keep the family from breaking if the value needed is 1
Array Count [user input or calculated on length as appropriate]
array_count_true=if(Array Count<2, 2, Array Count) [integer that controls array]
multi=Array count>1 [y/n controls visibility of arrayed family]
single=not(multi) [y/n controls visibility of single instance of family]
To really solve the issue there also needs to be something in place to keep arrays from breaking if a formula sets the count to anything under 2 (including 0 & negative numbers), like hiding visibility if the count is less than one.
The title explains it all. I don't know how many families I have made that have unnecessary and annoying visibility parameters set up because I can't use 1 as a value in an array. It really is such a tedious, obsoletable (this really should be a word) step that drives me insane.
I suggest that it be possible for arrays to have the number of objects set to 1. Simple really.
Thanks for your submission and votes on this idea! We are evaluating where this request falls into our roadmap and will provide an update when we have made a decision.
Not a fan of the workarounds for arrays. I'm talking about if (Number < 2, Array = 2, Number). For nested families, you can end up with the warning "There are identical instances in the same place. This will result in double counting in schedules". Sometimes I want the instance to disappear when the array is 0, rather than setting up elaborate visibility parameters.
Please don't tell me that an array of 1 does not make sense. In practice, it happens all the time. Change the name from Array to something else if you must.
Having the ability to make an array with 1 instance would be extremely useful in situations where the array instance quantity is set to a parameter. For example: a vanity family with either 1, 2, or 3 sinks as options should be able to be constructed using an array.
I'd love to see an option for 0 as well. We have a round table with chair (driven by an array). 0 Chairs should also be an option. It makes it much less likely that people will brake the family + more intuitive.
Ideally, array of 0 should be allowed, and in a later phase when this idea on parameter limitations is implemented, people that don't want 0 to be an option can limit there parameter to have a lower limit of 1.
Enabling array value of 1 would save time and reduce complexity in almost every array I build for door and window families that have many design options and sizes. It's intuitive that it should function this way. Enabling 0 to make the seed element disappear as well--that would be incredible!
@Anonymous this has been "Under Review" for over a year, I understand wheels turn slowly in a company the size of AutoDesk but is it destined to remain "Under Review" forever?
