Steve Johnson’s more Autocad based blog nauseam has an interesting question today: Trusting Autodesk? Contemplating a new product. Go over and take a spin through the thought process of dealing with new offerings from Autodesk.
How many of you remember Field Survey and its joyous interactions? How many of you think these questions still apply to C3D? Fire off here or at Steve’s site.
We are happy to announce the return of our EE Cast Civil 3D webinars. We are going to kick things off on October 7 at 12pm CDT with a presentation on the improved Quantity Takeoff tools in Civil 3D 2010. We’ll then present a new topic the first Wednesday of every month. In addition to learning about Civil 3D from some of the best in the business, EE will also be giving away free stuff at each EE Cast. We have a prize closet full of Civil-related stuff, ranging from old books (2006 Essentials anyone?) to fully functioning seats of Civil 2010 and Civil 3D 2010 . Be to join us each month for chance to win. Make the jump for the schedule and registation links.
In our first article in this series, we explained that LISP is a List Processing language. This means that all coding you write in this language has to be contained in a list. The list is created by enclosing your phrase in parentheses (). For example, to add two plus one in lisp you would write (+ 2 1).
In this exercise, we are going to start building our function as described in the first article.
Apparently Matt’s on a hot streak, two in a row for our Canadian contributor! JW
I’m willing to bet if you’ve had a little more than zero experience with corridors you know what Bowties are. maybe not in name, but in practise. Bowties are what happens when your corridor has a bend in it that is too tight for the width of the section. Here’s an image. The circle shows overlapping links.
This is a perfectly understandable phenomena; each corridor section is its own standalone entity without thought to preceding or successive sections. Same thing happened in Land Desktop, it’s just that there was no Corridor in LDT so it wasn’t blatantly obvious. Additionally, this overlap condition is not problematic unless you’re creating a surface. This is Civil 3D after all and it’s all about making surfaces; far more than Land Desktop, at least in my experience. Make the jump to find an alternate solution.
So you have a corridor surface which needs a boundary. You’re used to using Civil 3D 2009 and you know about the Automatic boundary, say, from the daylight lines.
You also know that the Automatic boundary doesn’t always happen depending on certain conditions. So you installed Civil 3D 2010 because you heard about this new fantastic boundary method known as “Corridor extents as outer boundary”. You opened your corridor properties only to discover that the option isn’t where it’s supposed to be. Follow the jump to find it.
Talk Back