from Civil to Inventor

The Autodesk enthusiast exile

Civil 3D – 2010 Pipe Network Label BUG

We’ve moved. Join us and get these articles and more tips and reviews at Design and Motion

 

NOTE: I have revisited this issue and article 4 times over now.  I am rewriting this…again…, but the images are old because I don’t have time to cut new ones.  I hope the article is still understandable.

I needed a fast certificate of completion letter, and the drawing to go with it.  I’ll just throw down some pipes here in 2010; it’s simple, no need to go to 2009. A good job to start getting a feel for this part of the new version.

I thought I would put down some simple structures, labeled automatically, edit the network, and spend the bulk of time messing with the profile (at least I hoped).  My styles are all formatted, and all work smoothly.

Things did not go as planned.  The profile was a lost cause.  Perhaps we’ll discuss that later.

Pipe Network Labels

image

I laid down this arrangement from my (imported 2009 template) Network Parts List. Notice the disgusting mismatched labeling on the pipes and structures.  The blue, while not labeled correctly, is formatted to what I thought I’d get by default.  The Red is useless.  You have to manually change the description.

Continue reading

Advertisements

June 19, 2009 Posted by | 2010, AutoCAD Civil 3D, Labels, Pipes | , , , , , , , , | 3 Comments

Civil 3D – XML Pipe Import Parts Catalog problem

Pipe Networks and the beloved XML has once again bit someone in the fanny.  This time it is the ‘Can’t Swap Part’ on imported pipe networks.

Here’s the deal.  Among all the interesting stuff an XML file will bring in for you, it won’t bring in the Parts List name.  It contains the Material and size of the part as well as the name, just not the Parts List.  I suspect this is good, considering you may not have that named List, but this still leaves us with pipes that have to be swapped.

It seems as though the Network adopts the creation aspects of the commands settings.  The network is created, and then handed the parts to complete the pipe network.  When it does, it sets them by the information in the XML.  The size is correct, but the XML has no idea what to tell your application about what these should look like, other than diameter. 

The application responds with it’s defaults.  If you have no default Parts List set, then the parts list comes in NULL. Notice the example below.

image Continue reading

November 12, 2008 Posted by | Data References | , , , , , , , , | Leave a comment