indiancad Posted Friday at 11:42 AM Posted Friday at 11:42 AM Both systems may have the same drawing, but the result can still be different. Fonts, SHX files, plot styles, support paths, and installed add-ons can change how the drawing behaves. This is why sending only the DWG file is sometimes not enough. For team projects, I usually keep the required support files together with the drawing. It makes troubleshooting much easier when another user opens the same file. What additional files do you always send with a DWG? Quote
BIGAL Posted Saturday at 01:58 AM Posted Saturday at 01:58 AM If you use Etransmit it will add extra files to what is exported, in particular say custom fonts and xrefs. 1 Quote
Steven P Posted Saturday at 08:34 PM Posted Saturday at 08:34 PM If it is going to a client I'll try to keep it all basic - no add ins, standard fonts, etc, if I can, on the assumption that their doc control will copy just the dwg file and all the rest will be lost to them at worst and at best when it is sent out again whoever sends it won't e-transmit, just the dwg, so we have to go round and round to get the rest. Quote
indiancad Posted 55 minutes ago Author Posted 55 minutes ago That's a point. Making the drawing as simple, as possible can definitely stop issues from happening when the client gets the DWG file. Using fonts not adding extra things and handling external references the right way can make a big difference. I have also noticed that missing supporting files are often the reason a drawing works differently on another computer. 1 Quote
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.