Architecture Suite question - How do I import AutoCAD Arch '09 model into Revit '09?

[happystan5678]

We bought Revit Arch. '09 as a part of Autodesk's "Arch. Suite '09", which sounded pretty promising, since it included AutoCAD Arch. '09, which you'd think would interface with Revit.

Unfortunately, when I try to import AutoCAD Arch '09, into Revit '09, it gives me a message that says,

"Some elements were lost during import. Active X and some proprietary components cannot be imported.Try exploding the file in AutoCAD or setting Poxygraphics to 1."

Then it tells me "Import detected no valid elements in the file's Model space. Do you want to import from the Paper Space?"

I tell it "Yes" then it brings in nothing.

If I set the proxygraphics to 1, then I still get nothing.

If I explode the file in CAD then it flattens the whole model and turns it into a 2D drawing.

I've tried the IFC export, which sort of works, but none of the components belong to any Revit Families, so they're not editable.

Any idea how I use information I've generated in AutoCAD Arch in Revit Arch?

You'd think they'd be compatible if they came in the same AutoDesk Suite, right?

Am I expecting too much? Or did I buy a bill of goods?

[Scott D Davis]

AutoCAD Architecture (ACA) and Revit handle 3D completely differently. You can bring in your ACA 3D model, but it will be "dumb" linework and 3D faces. A wall from ACA doesn't know its a wall in Revit.

If you set Proxygraphics to 1 in ACA, and then export, this will "convert" the ACA objects into AutoCAD objects...ie lines, arcs circles and 3D faces if there is 3D. Not sure why you are seeing nothing without actually looking at the file.

Best to use the command in ACA "Save to AutoCAD" which will cnvert everything to 2D linework. Use this 2D linework as an underlay in Revit to build your model.

Revit hasn't always been an Autodesk product. In fact it competed direclty with ACA (ADT back then) for about 4 years. They are in the same Suite to help those moving from ACA to Revit to make the transition. Use Revit and ACA at the same time without losing the ACA license. They aren't meant to be 100% "interchangable" with each other on the 3D level. In fact, it would be very tough to make this happen froma programming standpoint. The Revit objects are just much more intelligent.

[happystan5678]

Actually, when I set the proxygraphics to "1" and import the 3D ACA file into Revit, it comes in as a component, which I can't alter.

Then if I select it and do a "partial explode" it flattens out the entire 3D model.

So in other words, ACA is pretty much worthless for importing ACA files into Revit and I should just abandon the hope of ever using ACA information in Revit?

[jeffh]

The 3d information can be passed from AutoCAD Architecture to Revit as "intelegent" objects by exporting to IFC.

This will transfer walls, windows, doors etc... but it will be at a pretty basic level. I would not depend on this workflow except in specific situations. Modeling in Revit or AutoCAD Architecture and keeping the model native to it's own application will be far earier to manage and will produce better results over all as opposed to switching the model back and fourth VIA IFC imports and exports.

[Steve_Stafford]

If I may say what the others said slightly differently. The bundle of the three isn't a work flow bundle. It is a sales/marketing bundle as well as licensing resolution bundle. The primary issue as I understand it is that firms that are currently using ACA/ADT and want to use Revit had no way to retain their ACA/ADT licensing while working on their transition. There was Revit and Revit bundled with AutoCAD but nothing other than full price for both, Revit and ACA.

With the bundle firms that have bought Revit will now have authentic licenses for ACA as well as AutoCAD so they can legally continue to manage their legacy files and continue with their transition to Revit for new work.

The bundle does not really help (isn't as nice as deal for) firms that have not purchased Revit yet except that the upgrade price to acquire it is still less than a full seat of either product.

Ultimately if you purchased the bundle because you believed or were led to believe that there was some increased interoperability between them...it is incorrect, sorry!

[Scott D Davis]

Actually, when I set the proxygraphics to "1" and import the 3D ACA file into Revit, it comes in as a component, which I can't alter.

Right...this is because the ACA objects don't become Revit objects. They display, and can be cut, but don't expect to select an ACA window and swap it out for a Revit Window.

What Steve Stafford said in his post is spot on. It's not an interoperability bundle.