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.
Well some more water has passed under the bridge. 2020 is due out today, maybe this vital functionality will be one of the many enhancements in this latest release?
We are updating this thread to Gathering Support. We are continuing to evaluate where this request falls into our roadmap and will provide an update when we have made a decision.
This would be super useful for the families I've created. I have a nested family of panels and channels to create a wall out of our company's components, and having to go through the workaround of using an empty family rather than an array that can have a single component is difficult to set up and maintain.
We do a lot of car-handling facilities: car parking, car stacking, car storage. This needs arrays, sometimes 2-way, for which total car capacity can be calculated & scheduled. Frequently, due to oddly-shaped spaces / circulation, there are random singles. Would be great to have tidy, efficient families to handle this.
Today I had to take my sweet time with a family going through this issue. Seems to be something simple to work around inside Revit's code. Please, make this a reality.
Yes this is overdue, only way of achieving it at moment is to hoodwink Revit with a single and a multiple instance in a family with visibility control linked to a conditional if statement or Not logic operator. So that when an amount is less than 2, the multiple instance disappears and shows a single instance instead.
Same in Revit 2023 so my prayers will continue! Who at Autodesk do we need to buy a beer for to make this happen? 😛
Come on please. 5 years to implements such an elegant solution. This is really needed in Revit. In generel a lot more QoL improvements or less restricted ´play area´ to model families is necessary. Programming is a part of many people everyday life. Make it possible in Revit too.
I agree. 0 or 1 elements allowed would greatly simplify array implementation. For someone practiced in the process, it wastes a lot of time. Learning the workaround process takes even longer.
Yes @Anonymous , it would be so much neater just to have arrays that could start with only one instance and not two! My current solution is to use a shared family in the repeating family and also have a single instance of the shared family in the project as well. It's an annoying workaround but it does work, I would much prefer the above.
It would be great to be allowed to have array of '1'.
This annoyance becomes especially clear when trying to make a family, where a nested family is repeated X times, and driven with a parameter. X=2 onwards works fine. Until the user wants to place the nested Family once.. and crashed the whole family. Why can't we do just X=1???!!!!!!! This is very counter-intuitive.
Imagine creating a simple.. ..windows with x dividers..
..or a ikea Kallax shelf with x rows..
etc. etc.
The workaround for this isue is huge, clumsy, takes tons of time and testing, and make a family way bigger and complex than it needs to be.
--- PLEASE JUST FIX THIS BY ALLOWING THE ELEGANT 'ARRAY=1' INTUITIVE SOLUTION---
Congrats! We think this is a great idea, so we've decided to add it to our roadmap. Thanks for the suggestion!
To follow the progress of features in development, please see the Revit Public Roadmap and join the Revit Preview Release to participate in feature testing. (Note that Accepted Ideas may not be immediately available.)
Has anyone combined this madness with void elements in arrays? The crazy workarounds break down when there are voids. The voids in nested array elements cut whether visible or not and one gets an error condition when one void occupies the same space as another (as in the case of placing two identical instances and trying to control their visibility workaround) - the void can't cut the host because it's already cut. Nuts!
