If you have experienced the issue of point symbols disappearing when you use the “Export to AutoCAD 20XX” commands you are not alone. This was a tricky issue that would veer its ugly head every now-and-then and stumped my company for years. There is a good post Compatibility 101 – part 2 that was recently published and the message of setting PROXYGRAPHICS to 1 (ON) was well received to avoid having to perform an Export to AutoCAD. However, as outlined in that post, there are still some times when Export to AutoCAD is needed.
Below is a pic of the issue. After the jump check-out a tip that might help you overcome this issue.
If you are in the process of upgrading to Windows 7 (64-bit) and are still using Civil 3D 2009 you might notice files take longer to save. In this example we are saving a 65mb file (very large file). To save the file to the C: drive with Civil 3D 2009 on Windows XP it takes 45 seconds. Whereas, with Civil 3D 2009 loaded on Windows 7 the same file takes 1.5 minutes to save. So essentially, the file takes twice as long to save. I have no idea why it takes longer to save, it just does. Also note, C3D 2009 is not officially supported on Win7.
However, there is a light at the end of the tunnel. Civil 3D 2011 (64-bit), with ISAVEPERCENT set to 50% – after the 1st two saves – only takes 15 seconds to save the file. So essentially it takes 1/3 of the time it took C3D 2009 to save on XP; an increase in proficiency.
After the jump see some more save-time results. Including over the LAN and WAN (w\ Riverbeds).
We invite you to a special webinar session in which A.J. Whitaker, PE, PLS and Director of Site Development for Ware Malcomb, shares business development tactics and best practices for getting the most out of SITEOPS, patented online collaborative CAD software.
A.J. will share real-world examples of how SITEOPS has helped him win projects, find new solutions for sites, and “wow” clients through the power of online optimization and collaboration. “The clients love it and we’re winning new business as a result.”
When: Wednesday, June 23 – 2PM-3PM EST
Guest Speaker: A.J. Whitaker, PE and PLS, Director of Site Development
Who should attend: Engineers, Architects, CEO/VPs of AEC firms
Register today to reserve your seat: http://www.siteops.com/news/civil.shtml
No we are not talking about the European way to describe elevations (I just couldn’t resist) and we are not talking about the Bentley way to describe layers. We are talking about the idea that with Civil3D, getting the settings to work is based upon a hierarchical level. Let’s illustrate this and see if we can better understand Civil3D settings and their relations with each other.
Have you ever went to Draw Pipe Network Parts in Profile View only to have the Profile View become a “Sky Scraper” or in the case of setting the Profile View elevations to user specified, not have any of the pipe network parts show at all? (That’s because they’re lost in the Sea, Right? Well not really, they just have an elevation that is 0.00 or less.) Sea Level, get it? OK, maybe that was a stretch.
Has it been so early in the design process that your co-worker wants to get started on the Storm Sewers design before you’ve even touched the PG surface and they want to get started preliminarily on the pipe calcs. and you’re afraid to define any Pipe Networks until you get the PG finalized or at least close to done?
I’m going to make an educated guess that some of you have. This topic might be somewhere out in Blog Land or Discussion Depths, but I occasionally see this happen to a few users. Hopefully this post will help those few and/or it may just create an additional item to your list of best practices. Make the jump for a tip that may just stop any of those from ever happening.