This post is loosely-related to the last post re: Corridor model output failure. That was shown to be a result of invalid Base Map Control data source objects. Usually, duplicate/overlaid objects are the root-cause of the ugly corridor models output seen at times. However, this issue appears to be
top of page
To see this working, head to your live site.
Design Markers, Constraints, Flow Labels, Civil 3D Profile Sync, [ASE] Pads, Corridors, Basins, Surface Mgt
After taking a look at that error message closely, then running this on a test drawing, I realized that the error indicates of a missing reference to the “base surface”. Issue ASE Civil displays an error dialog when attempting to open the Surface Mgt. toolbar. Cause This is caused by a bug in A
Problem "...ASE crashes during the initialization process. More specifically, this is happening while the pads are being updated..." I get the following message at the command prompt after just one alignment's pads attempt to update: Command: Command: _INITIALIZE_ASE ------------------------------
Client Issue "...I have a sheet dwg where the alignment comes in slightly off of where it should. It’s not on the centerline. It must be a artifact of an earlier alignment or something. When I initially saw it, I went back, deleted and recreated the alignment. When that didn’t work, I deleted the
Problem "...When the design drawing cannot be initialized due to an error in one of the systems that are audited during initialization, the user cannot continue working with the program. This is because ASE is almost completely unusable if initialization cannot be completed without crashing..." So
I recently fielded a support request that cited slight elevation differences between the tops of 4" curbs on the ASE corridor model versus the elevations labeled in the profile output generated by ASE in the same locations. Unfortunately, It's True Referencing images and feedback from the client an
Problem Why does ASE crash whenever I try to use the 'Batch Mode' to define my pads? Cause This will happen whenever your Base Map Control data is lacking the key layers required to calculate the 'Curb Reference Points' for each lot. This is one subsystem operation that cannot be shortcut with 'qui
Issue: "...while modifying an existing 2017 ASE corridor, the corridor linework disappears for the current alignment. The only solution we have found is to delete a marker, export the corridor, then add the marker back in, export the corridor, and the corridor linework is back. Any suggestions?…"
bottom of page