See pic. I'm using C3D 2013. I received Aerial Contour Mapping. I added contours, spot elev blocks and added a boundary.
Surface is fine and definitions are present.
Then, I perform an audit and surface definitions are gone and a snap shot appears in definitions that says 'created in recover command'...see pic.
Any idea why?
Could it be where I ran the contours through Drawing Cleanup to weed vertices first? I usually run contours (polylines) through Drawing Cleanup to simplify objects and weed vertices before I add to a surface to keep file size down. Today, I didn't do simplify objects because it caused a few contours in steep areas to cross other contours, so I only weeded out vertices.
Solved! Go to Solution.
Update: Drawing cleanup had nothing to do with this issue. I just ruled that out.
I added contours and spots to my EG surface and definitions are present until I perform an Audit and as stated in prior post and shown in pic, definitions go away and a snapshot is created. Makes no sense.
Can Autodesk answer this, please?
If you need a response from Autodesk then you should log a Support Request through your Subscription Center portal.
What does Audit report when you run it? Can you provide a copy of the drawing prior to the Audit?
audit...see pic. yes, i have a copy of the drawing before an audit with definition shown. i'll also try to go thru mu subscription center to get an answer. if you want a copy of the drawing, let me know. its about 22mb.
Update: Fixed issue.
The problem was how I added the boundary. Initially, I used the mapping limit polyline as my boundary with Non-Destructive toggled 'ON'. Then I went back to original, deleted boundary and re-aded with Non-Destructive toggled 'OFF' and definitions remained.
I guess where surface was built from contours and they stopped at the mapping limit polyline which was used as a boundary with Non-Destructive toggled 'ON', that caused the surface to get corrupt. Lesson learned about Non-Destructive boundaries.
Make sure to mark your post as the solution. And thanks for posting it! That should help others in the future.
"Make sure to mark your post as the solution"
No absolutely not. This should be sent in immediately as a Product Defect in order to let the Civil 3D team know.
Non-Destructive boundaries preserve the integerity of the surface. They should be the first choice for boundary.
This is another miss by the Beta Testing program.
"I guess where surface was built from contours and they stopped at the mapping limit polyline which was used as a boundary with Non-Destructive toggled 'ON', that caused the surface to get corrupt. Lesson learned about Non-Destructive boundaries."
OP: Please remove the Solution marking... Marking this as a Solution only serves to help inhibit the problem being appropriately addressed, and to lead other astray.
I never had contours outside of the mapping limit, so there was nothing to triangulate outside of the boundary. The contours I added to EG stopped at the mapping limit which came from the mappers, and that is what I used as my boundary line inside my surface definition.
Not so sure it's a product defect as much as a UE (user error) on my part. I could've left Non-Destructive toggled 'ON' IF, I would've offset the boundary in just enough to where the contours extended past. That would've worked also because then there would've been possible triangulation past boundaries....correct??
I strongly disagree, Fred, regarding the "mark as solution". This solved the problem the OP was having with the corrupted surface so he no longer got that corruption. If another user runs across the same problem and finds this thread to help them with the workaround, then it IS a solution to their immediate problem.
However, yes, it SHOULD work as he was doing and should be logged as a support request. Please remember that this forum is mainly for peer to peer support. It is NOT a place to be posting bugs and expecting a fix, that is what the Support Portal is for. Whether this thread is marked as solved or not, will not affect any actual support case opened with Autodesk.
sfore, that is what I thought may have been going on. If the boundary ends up being coincident with the polylines defining the contours then I can see how this may confuse/corrupt the surface. There are likely many TIN lines affected by this.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.