This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
rhino:dwgemptyinrhino [2023/04/04] 127.0.0.1 external edit |
rhino:dwgemptyinrhino [2023/08/10] 127.0.0.1 external edit |
||
---|---|---|---|
Line 21: | Line 21: | ||
===DWG/DXF File Version=== | ===DWG/DXF File Version=== | ||
- | * 2018 (includes AutoCAD versions 2019, 2020, 2021, 2022, 2023 & 2024. | + | * 2018 (includes AutoCAD versions 2019, 2020, 2021, 2022, 2023 & 2024) |
* 2013 (includes AutoCAD versions 2014, 2015, 2016, 2017) | * 2013 (includes AutoCAD versions 2014, 2015, 2016, 2017) | ||
* 2010 (includes AutoCAD versions 2011 and 2012) | * 2010 (includes AutoCAD versions 2011 and 2012) | ||
Line 35: | Line 35: | ||
====Proxy objects==== | ====Proxy objects==== | ||
- | Proxy objects are placeholders for custom objects created by ObjectARX® applications, | + | Proxy objects are placeholders for custom objects created by ObjectARX® applications, |
By default, proxy object messages are displayed when opening a dwg in plain AutoCAD if the application that created the custom objects is not currently running. For example, if a drawing created in Autodesk Mechanical Desktop is opened in plain AutoCAD®, objects that were created as Autodesk Mechanical Desktop objects are displayed as proxy objects. | By default, proxy object messages are displayed when opening a dwg in plain AutoCAD if the application that created the custom objects is not currently running. For example, if a drawing created in Autodesk Mechanical Desktop is opened in plain AutoCAD®, objects that were created as Autodesk Mechanical Desktop objects are displayed as proxy objects. | ||
Line 53: | Line 53: | ||
- Import this file in Rhino. | - Import this file in Rhino. | ||
- | Proxy object will always have to be exploded. | + | Proxy object will always have to be exploded |