One of the benefits of being a long time Civil 3D user is knowing about some of the built-in Map 3D Features that enable users to attach an existing drawing to an empty file as a database.
As I previously mentioned, I went through what I consider due diligence whenever troubleshooting an issue related to mysterious drawing behavior checking the number of scale lists ( SCALELISTEDIT), ensuring that there aren’t excessive registered applications ( REGAPPS), purging any unused styles ( -PURGE), and auditing the file for corruption ( AUDIT), however none of these methods resolved the bloat problem nor did they identify the source of the cause. Examining a sample drawing that a client sent me, I noticed what appeared to be a small drawing with very little line work weighing in at 7.38MB. Identifying certain characteristics of a problem usually helps single out its cause, much like I imagine a doctor’s diagnosis would be based on a patient’s symptoms. All this to say that I found myself asking what could be possibly done to not only identify this problem but resolve it once and for all? Even blocking out the drawing into a clean template made no difference. Purging did nothing to reduce the file size. At a cursory glance, there seemed to be nothing wrong with these drawings. One such recent issue involved multiple clients all of whom exhibited the same mysterious crisis: having a user base working with DWG files that kept getting increasingly larger. While I generally find my own motivations in life aligned with Isaac Asimov’s quote which declares that “ the true delight is in the finding out rather than in the knowing“, there have been times troubleshooting certain issues where I found myself wishing I just knew what was wrong.
0 kommentar(er)
