Profile Generation

ASE Civil 17 SP13a Civil 3D 2020 Duplicate Stations 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. Workaround After trying just

Client "... I exported one alignment ... When I generated a profile with our company template it truncates the stationing, elevations and slopes that end with zero … When I use a basic Civil3d Template it doesn’t do that … I’m sure it’s one of ACAD’s SETVARs, but which one?..." ASE "... I download

​ Issue "... When I create a new drawing for generating the profiles for my road design, after I select the project data folder and try to generate the profile (a really simple design, just to test the software) ASE just crashes.." Cause Profile Generator Preferences Bug The initial Profile Genera

'Bout Time... This shortcoming has bothered me for a long time: Scenario When choosing the option to suppress station labels in selected PVI's, if your PVI's contain descriptions, they're left floating with a huge empty area where the stations used to be. Unless you've found a workaround for this,

Problem "...Offset values in PVI labels should be visible when the option is enabled, but they are not. Nothing shows up at all..." Solution When using Civil 3D alignments, the definition must be accessible inside the profile production reference drawing. This enables offset calculation capabi

In SP13, there will be a new command in ASE Civil's Profiles ribbon tab: The "Align Select" option provides a way to change the alignment used for profile generation without creating a new drawing. Freedom to Explore So essentially, you could use this new option to browse all the available pr

Issue "... I am having issues with my profiles where they are dropping the P= or TC= when you edit the pvi labels? Have you run into this? How can I fix this?.." Why PVI Prefixes May Be Lost After Editing The situation described is an anomaly that is unavoidable in the current version. However,