ASE Civil 17 SP13a
Civil 3D 2020
A client reported an output problem with one of the offset components of an alignment.
The problem occurred within a transition region, presumably a cul-de-sac.
2 separate PVI labels reported the same station value.
After trying just about everything we could think of, The CAD manager tried removing the Civil 3D data shortcuts from the profile drawing. He then regenerated this profile shown above and it fixed the issue.
FWIW the CAD Mgr informed me they use Civil 3D alignments exclusively.
About Paving Model Files
If you were to open one of the paving model files, you'll note that station data is recorded with the Design Marker locations and elevations. This enables ASE to generate a profile without access to alignment data of any kind. During profile generation, the station & elevation grids are created based on the content of the paving model file.
I've always recommended adding an alignment data shortcut to the dedicated profile generation drawing for each road, when using Civil 3D alignments. I need to take a closer look at the logic currently in-place that would allow this kind of output to occur. I'll follow-up on this later.