Currently Corridor Vertical/Both Point Controls link the the specific Vertical Profile and when these get deleted, the Point Control is removed without warning. An option to set this point control to always use the Active Profile would allow this ...

Support use of cell definitions for sleeper placements. Long sleeper sets placed at turnout locations, have variable width so these will still be using existing box shaped sleepers but normal sleepers will be using the cell based definitions. This...

Currently the Create Closed Mesh Tool produces static meshes which do not update when base elements change. When any of the base elements change, the existing meshes need to be deleted and created from scratch. We would like to see the following i...

There are currently some things needed to be added to the Corridor Object dialog to help communicate design intent a bit better to users (especially with Parametric Constraints): The lack of information as to the rules linked to Parametric Constra...

I was told it's in the backlog, so I put it to vote. Add ability to model flexible vertical support (spring) in LEAP Bridge Steel - it's important for bridges that are supported with piers of a compliant nature. This type of support may quite sign...

Currently when developing a object that is at a skew, whether it be a road, bridge, culvert, or other detail modeling. If the start/end of the object is at a skew compared to the alignment that it is attached to, it is difficult to model. The user...

If you create a 3D slope line using the tool "Create 3D By Slope To Target" the result becomes an intelligent line dynamically linked to the horizontal/vertical geometry which is great, however, there are times when we would like to be able to qui...

Either add ability for multiple users to be in the same ITL and save the information. At the moment we run a separate ITL for segments of a project which leads to slight differences to similar items. It is cumbersome to use the template library or...

Currently, OpenRoads Designer does not support a native method for designing an end condition that targets both the terrain model and a specific elevation simultaneously without relying on external geometry such as contour lines or point controls....

Currently, you can click the delete components within templates and draw a line through any component(s) to delete it(them). It would be nice to have a similar function to delete points by encircling them so you do not have to delete them using th...