With regular MicroStation lines, when using the "move parallel" tool (Offset), there is an option to choose "Round" which creates rounded corners for the offset line. There should be a similar option when using the ORD Tool "Offsets and Tapers." C...

If we add the Volume Exception stations (Cross Section Named Boundaries) for which we don not want to generate the End Area Volumes, The generated report still reports the Stations with the 0 Volume and its area. Kindly add an option to remove the...

In the Feature Definition Toolbar, there is a button to "Use Active Feature Definition" This should be enabled by default. When a users selects a feature definition from the list, they expect that is what will be used for civil elements.

The default object marker associated with Plan Annotation should be able to be customized using a template or feature property. The object marker is currently hard to use because the default circle has five grips to manipulate, which often causes ...

When we create a new file we often start with a 2D seed with only one 2D model in it. We often would like to have a linked 3D model associated with that 2D model. It would be great to have a simple button that force creates the linked 3D model.

The RIM Elevation is a stagnant number once you enter an elevation it does not update in relation to any surface changes. RIM Elevation would be better suited for use if it can be defined with an offset. Another field would be needed: RIM Depressi...

For large projects, we need the ability to have multiple engineers working on the hydraulic model. We can achieve this by splitting the pipe network into multiple files and creating catchments in separate files. Doing so causes us to lose the abil...

Currently Civil Cells are sorted by date created rather than by name when loaded from a dgnlib. This makes it very difficult to sort these. Oddly, when they are within a file (where the civil cell is "living") they sort by name.

Similar to the new Station/Offset Expressions, it would be great to query a terrain in an item type on an element and return the elevation. It would be used primarily for point cells, but I could also see it being useful for linework.

Let's say there are 4 spans and the user defines a bridge with 5 supports and the deck and beam groups run from support 1 to support 5. Then the engineer learns that we don't want this long of a bridge, only 3 spans. Please add the ability to chan...