Importing DWG file...
-
Yeah, go for DoubleCAD. It has a free version which may be fully functioning for what you need. Even if you are not experienced in CAD apps, it's worth a little look at how things work if you use a lot of import (and therefore you need to "collaborate" with other people using CAD).
DoubleCAD can even import skp files natively (whenever you need some backward process).
-
Hey guys,
Thanks for the time responding to my question...
Sounds like a great idea, but is Windows only... but i've seen the light and i'm now on Mac...
But more importantly, why exactly would I need this? Is this about simplifying the file prior to import, as suggested above?
In which case I can easily ask those sending me DWG or DXF drawings to do so prior to sending them.
Thing is, I need to really understand what the issue is in SU... So a small 'checklist' would be greatly appreciated...Ronan
-
@ronanr said:
But more importantly, why exactly would I need this? Is this about simplifying the file prior to import, as suggested above?
It's a matter of cleaning up the DWG file before importing. In most working DWG there's lots of extra "junk" data that isn't needed for the import. And then there's also the matter of SU not liking real word co-ordinates.
@ronanr said:
In which case I can easily ask those sending me DWG or DXF drawings to do so prior to sending them.
It's still good to have the ability to check the file yourself. Even though I've told people how I'd like the file presented to me, most people get it wrong anyway.
-
Yeah, like Thom says,it's always good to be able to control what you're doing as well as to be fully aware what the problems inside CAD can be.
@thomthom said:
And then there's also the matter of SU not liking real word co-ordinates.
You can control that during the import phase; in the Options,uncheck"Preserve drawing origin". This is important because dwg files are generally "geolocated" in the co-ordinate system and this way may end up miles (or hundreds of miles) away from your SU origin thus creating all the OpenGL issues like clipping and distorting...
-
@gaieus said:
You can control that during the import phase; in the Options,uncheck"Preserve drawing origin". This is important because dwg files are generally "geolocated" in the co-ordinate system and this way may end up miles (or hundreds of miles) away from your SU origin thus creating all the OpenGL issues like clipping and distorting...
I don't trust this option, as some times there could be some random lines located by the origin. Or, like the DWG I just got dumped on me right now; some lines located 2000km !!! under 0! arggfh
-
Well, in any case, never trust a dwg file entirely at all!
If there are stray lines in outer space, those definitely need to be purged anyway. -
@gaieus said:
Well, in any case, never trust a dwg file entirely at all!
I never do. Like in this case. I now have to import it bit by bit as I manage to untangle the data I need.
Which is why, when you import DWG files, you do need a tool to edit them. -
OK both, thanks very much for your insight... i'll see what I can get the the other party to do when sending plans. Thankfully I only need minimal information from the DWG, so with some luck it'll work.
Best wishes from sunny London.
Ronan
-
@ronanr said:
Best wishes from sunny London.
What what what?! I certainly know where you've misplaced the rain at the moment... ...hail, in June...
-
At least we only have "simple" rain here. So much about global warming.
-
@gaieus said:
At least we only have "simple" rain here. So much about global warming.
No, Gaieus
Here in the north it goes: Higher temperatures in the Arctic> more evaporation, more winds> more rainAs to importing DWG files, a valid file should import OK, but SU ignores many object types, especially those created by AEC applications like AutoCad Architecture. Those should be "Exported to AutoCad" prior to sending you the file. Cleaning the file of unnecessary geometry makes it import faster, but should otherwise not be necessary. There seems to be some limit to file size, though, I have read somewhere that at somewhere bigger than 10 Mb the importer begins to choke.
Note too that the new AutoCad 2010 version that came out this spring has a new file format that is not yet readable by SU. So if the person who is sending you files uses that, they should save the file in the 2007 format or older.
An intermittent problem with the same file might indicate some other problem, like a problem with a removable disk/memory stick or a network glitch, if the file resides on a server.
Anssi
Advertisement