I run audit on a vairly regular basis. This is a new one for me.
Command: AUDIT
Fix any errors detected? [Yes/No] <N>: Y
Auditing Header
Auditing Tables
Auditing Entities Pass 1
Pass 1 25800 objects audited
Auditing Entities Pass 2
Pass 2 25800 objects audited
Auditing Blocks
343 Blocks audited
Total errors found 0 fixed 0
Erased 0 objects
No solution
No solution
No solution
No solution
Command:
This drawing has no glitches or hiccups that I notice. And the Audit finds no errors. But it says "No solution" 4 times. No solution to what? Running a recover produced similar results.
Civil 3D 2011, 32 bit
Win 7 Pro, 32 bit; Intel Core i5 @ 2.80GHz; 4GB RAM
Any ideas?
Thanks!
Mark Green
Working on Civil 3D in Canada
Hi,
Please confirm if this is drawing specific, I can't seem to replicate the issue with tutorial drawings. Could you please attach the drawing as well so that we can verify and research into the issue?
Thanks,
Mark Green
Working on Civil 3D in Canada
Mark Green
Working on Civil 3D in Canada
Well, I finally got back to it. Here's the drawing (2011 format).
Mark Green
Working on Civil 3D in Canada
Did you ever get a solution to this problem?
I'm having the same issue and trouble with my Intersections.
I never received any response other than what you see from @Matt_Haokip above.
I should perhaps add; I'm not using intersections to their full potential, only to lock two profiles to each other.
What trouble are you having with your intersections?
Mark Green
Working on Civil 3D in Canada
I had used a subassembly that had subbase, base, pave2, and pave1 courses, LaneSuperelevationAOR - Right. At intersections (my intersections are separate corridors) the corridor surface would alternate between points at the top of pave1 (the finish surface) and the top of pave2 , 1.25" below the finish surface. This caused zigzags in the contours across the intersections. I thought I'd force it not to do this by replacing the pavement subassembly, with a LinkWidthAndSlope subassembly so that there was only one surface that it could not miss. This caused more problems where I had to split curb returns at the intersection point and manually set their targets to the respective alignment so they would extend to the centerlines (there are no actual curbs except in one location, most are just plain edge of pavement). I get surface lines extending for thousands of feet beyond the intersection which I have to delete.
I see upon examining the model from other than the normal axis of the plan that the troublesome region has dropped to elevation 0.0 or there abouts.
What causes this?
I created a Profile View and a Layout for the curb return alignment and then the Corridor straightened up. I'm still a noob. IDK why it works okay without doing this sometimes and other times not.
I was able to get the curb return to come up with the rest of the intersection by creating a profile view and a layout for the curb return offset alignment but it still didn't match the adjacent part's elevations
When I deleted the Profile view I had created it adjusted to match the adjacent parts.
I still don't know why it chamfered the corner at the primary road offset and the secondary road centerline.