Service Pack 12 Changes

Curb Height Calculation Rounding

Inch to Feet Conversion

Until this update, curb-height elevation values have been rounded to different precisions based on your activity. Generated profiles round the conversion result to two decimal places. This has always been the standard behavior. However, curb heights calculated in any other context did not round the converted values at all. Details

Rounding Comparison

The problem was most prevalent with 4" values, since it's used more than any other height. The table below illustrates the curb heights applied in any 'non-Profile Generator' context. Note that as of this service pack all curb height calculations now use elevations at the top-of-curb based on curb-height values rounded to two decimal places of precision before adding the result to the flowline elevation.

Curb Height Rounding.png
Corridor Assembly Adjustment

Corridor 'Alignment Configuration' Changes Re-Enabled

All alignments will now react to any changes in its individual corridor's configuration.



In previous builds there was a randomly-occurring issue preventing some alignments from rebuilding their corridor to reflect a designer's assembly changes. After rebuilding the corridor, the output was unchanged for some alignments. The source code had not been modified for years, but this issue was verifiable.

Root Cause

A large portion of ASE Civil was developed using Visual Lisp/ActiveX. There is a problem with two of the ActiveX keywords:

These keywords no longer function as they did when they were first implemented in ASE Civil. The solution involved substitution of those faulty keywords with a different keyword that works in a similar way. Although this change resolved this issue, the same fix will need to be applied throughout ASE Civil.


Workaround Previously Recommended [ISSUE RESOLVED: For Reference only]

It appeared that problematic alignments would in-fact, respond to changes in the site configuration of the corridor models. Consequently, the only way to make adjustments to a single alignment's corridor output was to do the following:

  1. Open the corridor site preference dialog

  2. Adjust the site preferences so corridors are not automatically rebuilt after the dialog closes

  3. Modify the site configuration to match desired alignment's configuration

  4. Open the corridor refresh dialog

  5. Select only the desired alignment for refreshing

  6. Ensure that all auto-refreshing of corridors is disabled

Nominal Offsets in Profile Generation

Offset Labels Option

This option has been broken until this update.  Each control in the offsets preferences dialog now functions as-designed.

Extended Capabilities

Historically, when the option to label transitions only was selected, only cul-de-sacs and knuckles were recognized as transitions. As of this service pack, offset locations within a corridor identified as being within a transition now include interior transitions (e.g., widenings, bus-bays, parking bays, traffic control devices, etc.) and intersection interior return points.

Transition Regions Example 

The image shows a 'plan & profile' view of the vertical design & generated profile drawings for an alignment in a 'real-world' project. Note the regions & point-locations that are now identified by ASE as 'Transitions' (highlighted in cyan). When offset values are displayed for PVI labels within transitions only, additional labels will appear. (Click to enlarge)

(Click to enlarge ~ Image Size: ‪1,828 x 1,155‬ pixels)​

Nominal Offset Trans Regions 2021-11-26 220920.png



Nominal Offsets 

A nominal offset is determined for each offset component of an alignment. A nominal offset is defined as the measured offset value which has the most occurrences on a given component. When ASE displays offset values in PVI labels for transitions regions only, the only offsets visible in the labels will be those which do not match the pre-calculated nominal value.​