Corridor Cul-de-sac troubleshooting


Corridors are quite fun to build, configure and eventually model various surfaces. Everyone has seen the smooth and clean examples.

Sometimes, the corridor object can get out of whack; subassemblies targeting the wrong alignments, daylighting specified to the wrong surface, etc. Maybe you’ve seen this simple error…

image

Of course intersection can pose their own problems, but what about all of those other corridor examples like bus stops or knuckles or even cul-de-sacs. Recently, I had a chance to help someone with just such an issue. And it looked like this. For some reason, the lane was not respecting the closest target making a hole in the surface.

SNAGHTMLa601a59

Let’s see what we can find out….

Read more of this post

Advertisements

Vault and XREFs


As many may know, Vault has a love hate relationship with external drawing references.  What’s that? You don’t know what I’m talking about? Let me begin by saying that when I first ran into this issue, I found a workaround and have been using that ever since.  It seems that a resolution to this issue is on the horizon, or not. We will see. 😉

But first, the problem… Read more of this post

HOW TO: Deal with “multiply owned objects”


OK, so this is more of a simple reminder to myself. Many places, discussion groups, other blogs, etc., have gone in depth about this issue. Suffice it to say that the solution is “unsupported”.  🙂

With that, here’s the issue. At various times, like after a save, you might see (actually, SAVE might be the only place, just not awake to remember…):

*Warning* Mulitply owned object, handle “##zz#z#z”

You may even see this several times at the command line, the only difference being different “handle” strings. Take note of each one.  Then, type this at the command line for each handle:

(ENTDEL(HANDENT “handle”))

This will remove the problem, which appears to center around a style error. The above resolves that error but may delete the style to do so.

If so, simply use the new commands in 2011 to import the style;

AECCImportStyles.

Enjoy your Monday!

%d bloggers like this: