One of the greatest strengths of Autodesk products is the extensive Application Programming Interface (API), which gives users the ability to customize and extend the functionality of the software. In the past, some favorite techniques included using Visual Lisp or VBA to create any needed customizations. However, technology has been changing, and with Civil 3D, we need a somewhat different approach…
Archive for Civil3D2009
You guys know I love a good soapbox rant, but I love a good debate almost as much. This morning the one-year release cycle came to the front of the Discussion groups as a user was looking for a way to deal with 2010 dwg files in an older version. Sinc’s an advocate for change, but personally, I think he’s too narrow in his vision of the product’s worldwide and industry wide scope. I’ve put in the major points here as quotes, but I hope you’ll join the debate in the comments section. Make the jump to read the thread.
Starting with Civil 3D 2009, text can be associated to the design model directly through the XREF. It raises the question, "What happens if you Unload or Detach the xrefs?". Basically the answer is "…it depends on what you do…" .
After the jump learn the different behaviors.
For those of us still using Civil 3D 2009 or less:
There are lots of times when grading an intersection of two roads with steep slopes that you need to adjust a lane cross slope to make the intersection drain properly. Lets review how to grade an intersection using Featurelines (FL) – the fastest way if you don’t need to run pavement quantities off the Corridor model, until you upgrade to Civil 3D 2010, 2011, etc… – and also lets look at a fast way to adjust road cross slopes using Superelevation points.
The first step is to extend the Corridor Model up to the curb radii. Unless the roads are coming together at exactly 90-degree angles you will need to add a region to the corridor model and create an assembly that is only the right – or left – lane (see image below).
Do your Subassembly names disappear whenever you use the subassembly commands “Copy to”, “Move to”, or “Mirror”?
After the jump learn how to resolve this issue.