Proxygraphics Problem when importing this Civil dwg into Revit

[Joelle_K]

I have the same issue when importing this Civil CAD into Revit. I have tried purging out all entities that may cause this, including using WMFOUT and WMFIN to purge linetypes with text. nothing is working.

when I type "QSELECT" there is not an option or proxy entities. according to CAD, I not longer have proxy entities in the file, However Revit can't import the file b/c it does...?

[RobDraw]

Proxy graphics are used to replace certain kinds of elements because the object enabler is not present. The reason you don't have any proxies is because your version of AutoCAD can display those elements in their original format because you have the object enabler. Those elements don't translate well to Revit. You need to dummy them down. This can be done by exporting your drawing to vanilla AutoCAD.

I would never import a .dwg unless it was absolutely necessary. Link it instead. You can avoid some of these translation type errors that come up when importing.

[Viveka_CD]

Hi @Joelle_K

• A proxy object is a substitute for a custom object created with an ObjectARX that is not available in e.g. plain AutoCAD/RealDWG.
• By setting the variable PROXYGRAPHICS to 1 and save the DWG file, you should be able to view the objects in AutoCAD.
• The same thing should apply when the DWG file is imported/linked into Revit.
• If that doesn't work, you can try to use the EXPORTTOAUTOCAD command in AutoCAD, which will create a file with all proxy AEC objects exploded into basic objects.

Please select the Accept as Solution button if my post solves your issue or answers your question. Kudos welcome!

Regards,

[Viveka_CD]

Hi @Joelle_K

I just wanted to follow up here, any progress on this issue?

Please mark any posts that help with "Accept as Solution" and thanks! Kudos welcome.

Regards,

[Joelle_K]

Hello Viveka,

I have confirmed the proxygraphics was / is set to 1. I have tried the export to autocad and that did not work. I also tried to insert the file as Xref in a dum drawing and then bind it to try and get rid of any object causing the error. it is still an issue.

I don't know what the other commenter was saying, with the CAD having an object enabler so that it can't be rid of? in the previous version of this same civil CAD fie I was able to utilize the qselect to purge out proxygraphics and I used WMFOUT and IN to break the custom linestyle with text. it inserted into Revit fine. however, with this most recent update those methods did not work out.

I was still able to coordinate what I needed to by exporting to CAD my plumbing site plan. I would like to show this updated civil plan on my site, however its not detrimental to the progress of the job.

any advice is appreciated. thanks for your time.

[Viveka_CD]

Hi @Joelle_K

I'll be happy to test your file if you can upload the model and journal files to a private folder. Let me know if you'd prefer that.

Regards,

[Viveka_CD]

Hi @Joelle_K

I received your file. Thanks for sharing! I will test and let you know for an update 

I would also need a copy of your journal file.

Regards,

[Viveka_CD]

Hi @Joelle_K

Which version of Revit are you using?

Can you confirm if you have the latest updates installed for your Revit version from the Autodesk Desktop app?

Let me know if you have questions about the updates.

Regards,

[Joelle_K]

yes, confirmed. This job is in Revit 2017

[Viveka_CD]

Hi @Joelle_K

I was able to import the dwg successfully in Revit 2018.2 without any proxy graphics error, whereas I get the proxy graphics error in Revit 2017.

Which version of AutoCAD did you use to create the CAD dwg?

Meanwhile, can you check if you have the latest updates for Revit 2017 (Revit 2017.2.3) installed from your Desktop App?

To make sure that the issue you are seeing is not something already fixed in one of the product updates, I would suggest checking the Desktop App to see if there are any Revit updates available. For information on using the Desktop App see the following article: About the Autodesk Desktop App

Note: If you are not able to download updates through the Desktop App, the following article has information on downloading updates through the Autodesk Accounts page: Install Updates, Add-ons, and Enhancements

Regards,

[ToanDN]

---

@Joelle_K wrote:

I have the same issue when importing this Civil CAD into Revit. I have tried purging out all entities that may cause this, including using WMFOUT and WMFIN to purge linetypes with text. nothing is working.

when I type "QSELECT" there is not an option or proxy entities. according to CAD, I not longer have proxy entities in the file, However Revit can't import the file b/c it does...?

---

Revit cannot read Civil DWG directly.  Even if you open it in plain AutoCAD, you will see proxy boxes everywhere.  You need to Export to AutoCAD from within Civil 3D to a plain (aka vanilla) DWG format.  Then link that exported file in Revit.

It is the same for all vertical variants of AutoCAD such as Architecture or MEP.

[Joelle_K]

Now that makes sense. I do not have Civil 3D.

If I communicate with the civil engineer to save down their Civil 3D file to a vanilla DWG format, will that solve it? Thanks for your time.

[Viveka_CD · Accepted solution]

Hi @Joelle_K

Sharing an update from the development team -

Your issue is in progress as to why this error occurs in Revit 2017 and not Revit 2018.

Although in some files with similar issue exploding the dwg seemed to resolve this issue, it did not resolve the error with your file. The behavior is being analyzed and I will share further feedback when as and when available.

Meanwhile, In order to work properly with Autodesk AutoCAD Civil 3D, you need to download and install the appropriate object enabler for your version of AutoCAD. As a follow up from @ToanDN's recommendation here's an article on How to convert Civil3D drawings to standard AutoCAD format within AutoCAD

Thanks,

[Viveka_CD]

Hi @Joelle_K

Sharing an update from the dedicated resource team:

There are some missing shape files (SHX) that appear to come from Civil3D.

The file contains thousands of proxy graphics and instantly fails in 2016 and 2017, but is fine in 2018. 

Further testing in Revit 2017 is in progress.

Regards,

[Joelle_K]

I clicked your link and I was following a string of hyperlinks leading me to the main software's page, not to the download. MPA is a mechanical / plumbing consulting firm. we all use AutoCAD MEP. When I selected the relevant software to download the object enabler, it sent me to the main page for Autodesk AutoCAD MEP. Not the download.

Please provide the download to me or a correct and direct link.

As I understood from you previous post, the fact we do not have a certain download did not cause this error. I don't know why installing the object enabler would prevent this error from reoccurring.  

Thanks for your time,

[ToanDN]

@Joelle_K
You need to export the MEP drawings to vanilla DWGs in AutoCAD MEP.

[Joelle_K]

yes. as discussed earlier in this post I have been through all that with this file. it did not work. Autodesk support was looking further into the issue.

[ToanDN]

Make sure you export to a DWG version equal or older than your Revit version.

[KIMRAMFI]

Any news here? When the fix for Revit 2017 is coming @Viveka_CD 

[ToanDN]

---

@KIMRAMFI wrote:

Any news here? When the fix for Revit 2017 is coming @Viveka_CD 

---

What fix?  There is never a fix for any versions. 

Just Export to AutoCAD from Civil3D and link the result DWG in Revit, or generate a point file CSV from Civil3D and use it to create the topo in Revit.