Then you have found the best fit for you, which is what its all about.
For the benefit of anyone else that thinks Revit cannot do muntins because
the process is too long:
I would make one muntin family that is parametric that can be any number of
muntin combinations. This family would then be nested into my door and
window families (much like nested xrefs as an analogy) where it could be
controlled from within any project. So in maybe half a day, I could create
something that is completely parametric and easy to control, without having
to create special door and window families for each and every style I have.
Just like learning any software, in the beginning it can seem like a
daunting task until you learn the correct process. Yes, creating a special
familiy for every window and door would take some time, but the point is you
don't have to do that.
"Tom DeMita" wrote in message
news:6031245@discussion.autodesk.com...
I don't think that you get it. That one function made my decision not to use
Revit. Revit takes too much time to make mutins. That makes the entire
package, "Revit", slower than ACA.
Making all of those families of doors & windows alone would take longer than
the time I could complete a permitable set of drawings with ACA. If you live
in a "muntinless" society, go ahead and use Revit.
"Scott Davis - Autodesk" wrote in message
news:6031011@discussion.autodesk.com...
Exactly my point. You shouldn't make that decision on one function. Its
about the entire package.
"Tom DeMita" wrote in message
news:6030625@discussion.autodesk.com...
That one feature is why Revit sits on the shelf for me. It would take me
hours what I can do in a couple of minutes in ACA. I don't like Revit grid
command as well.
"Scott Davis - Autodesk" wrote in message
news:6030215@discussion.autodesk.com...
Lets not get into another "This product can do this one particular function
faster than the other" battle. Feature-by-feature comparisons of any
software are worthless. It's about the entire package and what one can do
with it.