Monday, May 03, 2010

Family Editor - Use a Default Type

It has always been a good idea to create a default type for a family, even if there is only one. When Revit loads a family into the project it gets a Type name that just matches the family name if you don't go to the trouble of making a default type.

When you reload the family later you might find that it doesn't update properly or that if you get around to creating more types you'll have this rogue original one to replace.

Simple solution, create a new type right away and you can call it default for now. Rename it later if you decide you don't like it or need it anymore.

With the 2011 release we can test parameters in-canvas. In the past any attempt to drag a reference plane or element that was constrained by a parameter/dimension would generate an error message. They provided this in an effort to make the Family Editor more relaxed about this. When you select a reference plane that has a dimension and parameter associated with it and drag it to change the size of a family Revit will just let you do it.

The change(s) you make is/are applied to the current type.

It becomes more important to consider a default family type in light of this. You probably don't really want to mess up specific type dimension values. If you are careful to make the default type current and then adjust the family you'll avoid creating a problem. Then again you can just reset all the values that get adjusted. Either way just be aware that you can manipulate them in-canvas and you can mess up existing family type parameters.

If you'd like to watch a video that discusses this new direct manipulation of families then check out Autodesk's You Tube Channel, THIS ONE narrated by Chico Membreno. I've embedded it here too.

1 comment:

Dave Baldacchino said...

Great heads up. Maybe a type called "Flexing" if you don't know what you want to name it; this would be a disposable type. Also probably it's even more important now to consider using Type Catalogs perhaps instead of putting too many types within the family. This would avoid unwanted mess-ups. I think that after we get used to the new functionality, we'll find it easier to work in the Family Editor. I know that new users tend to have issues with the concept of flexing with pre-2011 behavior.