Add better management tool/window for terrains sources elements
There is no effective panel for editing the terrain sources elements. The only available tools are the add/remove feature or the "Edit Terrain" tool with it's ""delete feature". All the above are extremely dependable on visual and clickable data. ...
this comes from CS0394270 the Microstation Named Boundary tool is still present in ORD. In the search ribbon if you type in Named Boundary and take the first option it opens the Microstation Named Boundary dialog and not the ORD one (so its missin...
Enhancing Named Boundaries: Updating Named Boundaries and Applying Geometry Rules
To enhance productivity and efficiency in live projects, we need dynamic Named Boundaries linked to Geometry. This includes the ability to update the shape or location of a named boundary after creating a sheet model, with the changes reflected in...
For the OpenCivil products, it would be nice to have the civil preferences folders that are located under C:\Users\<username>\AppData\Local\Bentley\OpenRoadsDesigner\<version>\prefs (both the civil and civil_commands folders) use the b...
Corridor Objects Dialog box to stay put after creating parametric constrains/point controls and etc.
The corridor objects dialog box is currently disappearing whenever you try to add parametric constraints/point controls/curve widening/end condition exception/external reference and etc. This would be much better if we could have at least make the...
Seperating the "add point control/parametric constraint" and "delete point control/parametric constraint" buttons within the corridor objects tool.
Many times a day I accidently delete a point control or parametric constraint when I'm trying to add. The buttons are extremely close, is there a way to move the delete button further away?
Ability to define the slope of any points within the dynamic section using the measure tools
Having the ability to quickly check both existing and design crossfall/superelevation would increase efficiency within the program as there would be no requirement to run a template and report to evaluate existing cross slopes
Currently, Drainage and Utilities feature definitions get captured via the CIVIL_CONTENTMANAGEMENTDGNLIBLIST variable within the workspace. Many configurations often use wildcards and file names that lump together features of D&U with road, ra...
Ability to export and import all corridor objects such as point controls to enable rebuilding of corridors
I know parametric constraints can be exported but if a corridor becomes corrupt then being able to rebuild it from scratch easily would be useful. Similar to an input file in MX