LUV2YODEL Posted November 6, 2001 Share Posted November 6, 2001 We are working with an architects office that does all their work in Architectural desktop 2000 on Windows machines, our in house design staff is working in Vectorworks on Mac machines Problem is that we are unable to open their files. We have tried saving things as DXF files with limited success. These experiments enabled us to only be able to see what appeared to be one layer of the drawings. Can you help us? You will be saving us weeks of work if you can. Thanks in advance. Quote Link to comment
Matthew Giampapa Posted November 7, 2001 Share Posted November 7, 2001 Unfortunately, I do not know enough of the specifics of how Architectural Desktop 2000 works to be very specific here. Generally there are a few limitations on importing a DXF or DWG from AutoCAD and I assume they also apply here. 1) We do not support paper space perfectly so we recommend that the drawing be copied into model space before it is saved. 2) Xrefs are also not supported, if the other layers were X-refed in, they will not be read by VectorWorks. (You will know if this has happened by a text block called X-ref in the document) 3) ACIS based solids are not supported, these have to converted to 3D polygons before VectorWorks can read them 4) It is generally a good idea to explode and drawing before sending it to VectorWorks. If you continue to have problems getting the file to convert properly. Email the file to tech@nemetschek.net and we can tell you exactly what needs to be done to have it successfully import into VectorWorks. Matthew GiampapaTechnical Support quote: Originally posted by LUV2YODEL: We are working with an architects office that does all their work in Architectural desktop 2000 on Windows machines, our in house design staff is working in Vectorworks on Mac machines Problem is that we are unable to open their files. We have tried saving things as DXF files with limited success. These experiments enabled us to only be able to see what appeared to be one layer of the drawings.Can you help us? You will be saving us weeks of work if you can.Thanks in advance. [ 11-07-2001: Message edited by: Matthew Giampapa ] Quote Link to comment
Guest Posted November 7, 2001 Share Posted November 7, 2001 There's a couple possible problems. 1) They are not saving proxy images. Older versions of AutoCAD had an options button in the Save As dialog which brings up an option to save proxy images. Make sure that button is checked. AutoCAD2002 has the options under a Tools menu in the Save As dialog. Arch Desktop should have a similar option somewhere. An alternative is to select any objects that are not included in basic AutoCAD and explode them. 2) They are saving proxy images, but Arch Desktop doesn't make a proxy image for every object. You can identify these by opening the file in a basic version of AutoCAD that doesn't have any of the "object enablers". Anything that basic, umodified AutoCAD can't see, VW won't be able to see. These should be exportable by exploding them. 3) They may include ACIS solids. VW currently can't import ACIS solids. The DXF chapter in the manual explains how to get around this by exporting to .3DS format and then importing again. Exploding these probably won't help. Sometimes problems can also be cleared up by exporting to version 12 DXF or DWG. Quote Link to comment
defjef Posted November 25, 2001 Share Posted November 25, 2001 A problem when trying to use an ACAD file... if that you need to do more than simply imprt the file to a blank document. The ACAD user... which may be in another office, needs to create a compatible file which will open in VW. The effect of this is that a series of daughter files, perhaps with exploded elements etc., snapshots in the life of the file are created. A daugher file may serve the purpose. However, beware that as the ACAD files progresses / is developed / is revised, you will have to create a new daughter file to reflect these changes in YOUR work. I do not know of any way to reference files created on other platforms and / or other networks. And of course if you are exporting BACK to ACAD... you have all sorts of layer class conversions / coordination to deal with. All this cross file / cross platfor, / cross network effort is time consuming and not real productivity. Such is life.... go figure. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.