I am using OpenRoads Designer CE 2021 Release 1 for an urban roadway project that utilizes a lot of custom Civil Cells for driveways. Today I deleted one of the driveway Civil Cells and replaced it by using new reference graphics. Everything seemed to work out okay until I tried adjusting the width of the driveway. I noticed that the cell seemed to be following a jagged vertical alignment along the roadway gutterline reference. I did a little troubleshooting and found that the profile along the gutterline, which is based on a 2% slope from my baseline geometry, was not smooth. I checked the profile along my roadway baseline and it was smooth so it didn’t make any sense why the gutterline profile, which is relative to the baseline profile, was not smooth. I investigated further by doing a partial offset of the baseline by 10’ and then setting the profile along this temporary geometry element using the “Profile by Slope from Element” command and using the baseline profile for a reference. Once again, I ended up with a jagged profile as shown in the attached image.
Out of curiosity I had one of the other engineers in the office, also using OpenRoads Designer CE 2021 Release 1, open the same file and try the exact same trouble shooting. He ended up with a nice smooth profile along the temporary geometry element. The only difference I can determine is we tried this on two different computers. I have not had this issue in the previous versions of OpenRoads using this same DGN file. Any ideas?
This is a known issue that has been addressed in a priority build of OpenRoads Designer. If you log a service request at connect.bentley.com noting the details of the problem the technical support team will be able to provide access to the priority build as it is not available on software downloads.
Thanks for the information. Any idea how long a service request might take? It seems like there should be a pretty quick response if it is a known issue and there is already a priority build available.
I hate to think I will have to wait for several days when I have a project deadline to meet.
If the service request has not been responded to promptly then I would suggest to contact your Bentley Account Manager or local Bentley office and ask to speak to someone in the OpenRoads technical support team. (I am based in Australia and for anyone in this region they can call 1800 500 227 24 hours a day and we will divert your call to the nearest open technical support team).
MaryB, priority builds for technical support issues are not posted to software downloads but the fixes they include are rolled into future product releases that are posted to software downloads. The next release is still several months away so users who need access to a version that includes the specific fix to this issue before the next release can obtain that from technical support.
After spending time on the phone and upgrading the priority of this issue I was informed by support that there is no priority build to fix the problem. I didn't receive information on a work-around either. I was informed that the issue will be fixed in the next release and "Sorry for the inconvenience". This is beyond maddening.
Do you have the option to "demote" your design to 2020R3? I believe 2021R1 allows you to have both versions on your computer.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
I have a lot of files that this could potentially affect and will have to consider if it's worth it. I appreciate the suggestion. I might just try to limp along and use one of the workstations in the office that doesn't seem to have this issue. Not ideal but I don't know if I really have any other options at this point.
I was contacted by Technical Support last night and was told that, after further research into the issue, they determined there is a priority build to fix the problem I have been having. I downloaded and installed the build and it seems to work. I appreciate the perseverance of the Technical Support staff and everyone else who helped me out.
Just asking, but does this priority build also fix the bug with the XS annotations?