I wanted to follow up on the Subassembly Composer tip I tossed out on the SAC release day and More on the theme of the cumulative nature of AutoCAD Civil 3D knowledge. It is...
Faster than a Speeding Bullet
In my SAC post I pointed out that employing the NAMES used in the default Civil 3D codeset file might be a good idea and save you a LOT of work.
Use the default CODE NAMES and you don't have to update all your existing Code Set Styles to employ your own new SUPER subassemblies created in the new Subassembly Composer for AutoCAD Civil 3D 2011 and AutoCAD Civil 3D 2012.
Code Set Styles
Code Set Styles in C3D carry a lot of load. They manage the intimate connection between the Corridor Model and the Cross Section Assemblies. You can think of Code Set Styles are sort of a Layer State Manager for the Civil 3D Corridor engine.
Code Set Styles define how corridor are displayed in plan and section, how your Assemblies are annotated, and a whole lot More.
Silly typos can drive you nuts since the Code Set Style is depends on a host of exact reference name matches and textually detailed descriptions.
It's been a while since I did a Code Set Style "basics" training webinar, but the essentials remain the same...
Even our InstantOn Basic NCS 4.0 products that include "basic" Civil 3D templates do some really nice things with Code Set Styles - screened plan views, and automatically arranged Section View labels. Our Jump Kit NCS 4.0 in-depth Style collections do More - a lot more. For example...
How about "parameter-driven. self-scaling expressions" that automatically produce Section View label arrangements. Way cool and somewhat geeky stuff that saves USERS tons of time on essential output tasks that should and can be EASY in AutoCAD Civil 3D.
Want a preview...here's the link to recent a recorded free webinar I did that shows off some of that capability for Section Views and Roadway Sections in Civil 3D 2012.
National CAD Standards 4.0
Inside AutoCAD Civil 3D Today
Yes. It is possible to be NCS 4.0 compliant, be more productive in AutoCAD Civil 3D, and look better than anyone else around for a song.
So you see, my SAC release day tip was a bit obsure since I didn't let even let you know WHAT and WHERE that key Civil 3D resource file was. Silly me - everyone who cares knows that. Not!
Sometimes when your face is planted on the wheel of progress, it's way too easy to forget to mention the obvious.
The Self Improving SAC Tip
I'd also talk to him about building the subassemblies you need. I know for a fact he's built great ones in code and there aren't many around with that level of expertise. Save yourself time and money, get what you need, and get back to work.