2004-02-16 12:21 PM
2004-03-08 06:22 PM
kari wrote:Well, just happened the other day, to a colleague. Now the job is in question, as the probation is in progress and it is a single ArchiCAD in an AutoCAD office. Not nice.
I just heard that in Budapest it is a well known problem that “some AutoCAD versions” produce DWG which AC cannot open.
2004-03-09 12:45 PM
2004-03-09 03:20 PM
2004-05-11 01:13 PM
2004-05-11 07:10 PM
Macbook Pro M1 Max 64GB ram, OS X 10.XX latest
another Moderator
2004-05-11 11:47 PM
ejrolon wrote:Thanks for that, I will have a word with them and let you know if that worked. I did notice when I opened the DXF that I got an error saying that an entity was ignored as it wasn't recognised. I wonder if that could be due to some problem like you are saying.
Get the engineers to run the audit and recover command in their dwgs with AutoCAD.
Sometimes when using the boundary command or inserting a wblock in a dwg you get invalid polygons/hatches that wreak havok on AC imports and sometimes on AutoCAD too.
2004-05-13 06:06 PM
2004-05-21 09:56 PM
Macbook Pro M1 Max 64GB ram, OS X 10.XX latest
another Moderator
2005-02-10 05:25 PM
2005-02-10 05:55 PM
belly917 wrote:Your signature says "8.1" ... I can't recall if 8.1 could read 2004 format. But if you are actually using 9.0, then 2004 is of course OK, but to read 2000, you want to install the plug-in in the Goodies\DXF-DWG 2K In-Out folder.
I have also been experienceing the same problem with dwg files. Although the files that are causing the issues for us, aren't from AutoCAD LT.. Our different consultants use AutoCAD 14, 2000 or 2004.