SP3 => weird feature line behavior?

[carguychris]

I just installed Service Pack 3, and the feature lines in one of my projects have stopped changing one another dynamically- i.e. where two feature lines have a common PI, changing the PI elevation of one line does NOT change the other line's PI elevation anymore.

This problem has got me baffled. I tried to audit the file, but it did nothing. Does anyone have a fix?

HELP!

Chris Walton

[Anonymous]

I had problems using the elevation editor. Not sure if something got corrupted or what but now everything crashes when I try to edit a feature line.

Fred Mitchell
APAI

[kevincurrey]

I can reproduce this. This was a problem when 2007 first came out. I posted about it just before SP1 came out, and they fixed it for SP1A or SP2. I can't believe they broke it again.

http://discussion.autodesk.com/thread.jspa?messageID=5194312

Glenn Albert, are you listening?

[Anonymous]

Yup, that's what it was! I moved the PI away just a bit and now I'm good! Thanks.

Fred Mitchell
APAI

[Anonymous]

Are you saying that the situation is you have two feature lines, and they
each have a PI at the same location? Editing one does not update the
elevation of the other? Are they in the same site? Can you send me a drawing
with instructions on reproducing it.

The problem referenced by Kevin is still fixed. That was the scenario where
you had a T intersection and the horizontal line did not have a PI point at
the intersection with the vertical. In the Editor (or the Edit Elevatins
command) the horz line would appear as a single segment with just two rows
in the editor, the start point and the end point. It wasn't picking up the
intersection point at the mid point so the grade value was wrong. With the
fix you now see that intersection point in the editor.

Glen

glen dot albert at autodesk dot com



wrote in message news:5387921@discussion.autodesk.com...
I just installed Service Pack 3, and the feature lines in one of my projects
have stopped changing one another dynamically- i.e. where two feature lines
have a common PI, changing the PI elevation of one line does NOT change the
other line's PI elevation anymore.

This problem has got me baffled. I tried to audit the file, but it did
nothing. Does anyone have a fix?

HELP!

Chris Walton

[Anonymous]

It's a 21,000 mb drawing. I had to feature lines that met but were not joined. When I would try to use elevation editor to change some of my slopes, I would lock up. I pulled the PI back just a bit and everything is working fine now.

Fred Mitchell
APAI

[Anonymous]

If you get a chance, can you send me a screen capture of what it looked
like.
Thanks,
Glen

wrote in message news:5389269@discussion.autodesk.com...
It's a 21,000 mb drawing. I had to feature lines that met but were not
joined. When I would try to use elevation editor to change some of my
slopes, I would lock up. I pulled the PI back just a bit and everything is
working fine now.

Fred Mitchell
APAI

[Anonymous]

Crud! Even Autodesk can't stop the spam

[kevincurrey]

Glenn,

If I follow the exact same procedure that I outlined before, I get the exact same problem as before the SP2.

The attached drawing has two feature lines that cross each other. Both started out with zero elev. at the endpoints. I changed it to 10' at the endpoint of one of the lines. This put a PI in the second line that doesn't show up in the elevation editor. So the second line shows two PIs with 0 elevation and 0% slope in between, even though graphically it has a PI in the middle with an elev. ~5.

[carguychris]

OK, I actually seem to have figured out the source of the problem... but it brings up another problem.

The feature lines were on different sites. However, they did not start out that way! I drew ALL the feature lines on the same site, and I have been editing the file since last week with no problems.

However, when I installed SP3, Civil 3D seems to have spontaneously created another site with the same name as one I was working on, only with a "|1" suffix added to the name. For reasons that cannot be explained by medical science, about 1/3 of my feature lines "migrated" to the new site, seemingly at random. 8-0

I've been able to get the feature lines to edit dynamically by making sure that both lines are on the correct site before starting. Unfortunately, when I change one of the "migrated" feature lines to the correct site, it removes it from my proposed ground surface and I have to add it all over again. >8-(

Also, when I select feature lines and use the "Move to Site" command, the command fails and shuts itself down if I select feature lines on more than one site. This does not cause Civil 3D to lock up, the command just doesn't work. Since there's no way to visually tell which feature lines are "migrated", I can't grab large numbers of feature lines and change them globally; I have to check which lines are "migrated" one at a time. Major PITA. >8-(

I guess my problem has changed. Why did Civil 3D spontaneously create a second site?

[Anonymous]

Fred:

Do you really have a 21,000 MB file?



Bill

wrote in message news:5389269@discussion.autodesk.com...
It's a 21,000 mb drawing. I had to feature lines that met but were not
joined. When I would try to use elevation editor to change some of my
slopes, I would lock up. I pulled the PI back just a bit and everything is
working fine now.

Fred Mitchell
APAI

[Anonymous]

I apologize, it's a 21,000 KB drawing.

Fred Mitchell

[Anonymous]

This is a different problem. In this case there isn't a PI on either feature
line, but because of the interaction between feature lines one will break
the other. I can't really make it an editable point in the editor because
it's no a permanent point. If you grip either feature line it gets
recomputed. There are a couple of solutions.

One is, when you create the second feature line, or grip edit it so that it
crosses another feature line, I could break it at the crossing and insert a
PI. The drawback to this is you couldn't grip edit the line in it's entirety
anymore because it's now 2 segments.

The other solution is to show the point in the editor as a non-editable
point, with a different icon, to indicate the break. Then we would need a
command similar to "draw order" that could be used to specify which feature
line breaks the other.

Which do you think is the better option?
Glen


wrote in message news:5389399@discussion.autodesk.com...
Glenn,

If I follow the exact same procedure that I outlined before, I get the exact
same problem as before the SP2.

The attached drawing has two feature lines that cross each other. Both
started out with zero elev. at the endpoints. I changed it to 10' at the
endpoint of one of the lines. This put a PI in the second line that doesn't
show up in the elevation editor. So the second line shows two PIs with 0
elevation and 0% slope in between, even though graphically it has a PI in th
e middle with an elev. ~5.

[Anonymous]

We actually have a pretty good spam filter now, but I'm still a little
paranoid about it. I used to get over a hundred a day, but it's down to
about a half dozen and I have an outlook add-on that catches those.

Glen

"Robert" wrote in message
news:5389327@discussion.autodesk.com...
Crud! Even Autodesk can't stop the spam

[kevincurrey]

Glen,

In 2006 any time 2 feature lines would cross each other, it would create a PVI in the elevation editor for both feature lines. If one feature line was erased, the remaining feature line would revert to only allowing elevations to be edited at the endpoints.

While the two line intersect, I could not grip edit either feature line at the intersection, only at the endpoints, but there was a third point in the elevation editor for both feature lines. This did create a little bit of a "drawback" in that if I wanted the feature line to have a constant slope of say 2%, I would have to enter it twice. But often I would want to change grade at that point, so it really wasn't a drawback at all.

This behavior allowed me to be pretty creative with what I could do with feature lines, and is what I would like to see again. I'm sure you still have access to 2006, so please take a look at what was different with that version.

Thanks,
Kevin

[Anonymous]

The site with the "|1" suffix gets created when you insert a drawing into
another with the same Site name. The inserted site gets the suffix so it
doesn't conflict with the one in the current drawing.

I'll have one of the QA guys check out the Move to Site problem, it sounds
like a defect. It should work the way you're attempting.

Glen

wrote in message news:5389396@discussion.autodesk.com...
OK, I actually seem to have figured out the source of the problem... but it
brings up another problem.

The feature lines were on different sites. However, they did not start out
that way! I drew ALL the feature lines on the same site, and I have been
editing the file since last week with no problems.

However, when I installed SP3, Civil 3D seems to have spontaneously created
another site with the same name as one I was working on, only with a "|1"
suffix added to the name. For reasons that cannot be explained by medical
science, about 1/3 of my feature lines "migrated" to the new site, seemingly
at random. 8-0

I've been able to get the feature lines to edit dynamically by making sure
that both lines are on the correct site before starting. Unfortunately, when
I change one of the "migrated" feature lines to the correct site, it removes
it from my proposed ground surface and I have to add it all over again. >8-(

Also, when I select feature lines and use the "Move to Site" command, the
command fails and shuts itself down if I select feature lines on more than
one site. This does not cause Civil 3D to lock up, the command just doesn't
work. Since there's no way to visually tell which feature lines are
"migrated", I can't grab large numbers of feature lines and change them
globally; I have to check which lines are "migrated" one at a time. Major
PITA. >8-(

I guess my problem has changed. Why did Civil 3D spontaneously create a
second site?

[kevincurrey]

In other words it basically behaved the same way t-intersections do now.

[mark]

Feature line editor issue:

Simple subdivision with one parcel.

I constructed a rectangular feature line with elevations at the corners to represent the top of a mound which I want to grade down from the top to the surface at 3:1. I create a grading object and mound surface. Every thing looks good. But...if I edit the feature line elevations, the feature line turns into a parcel and erases my property line parcel. Thoughts? Thanks.