Hi there, I'm using OpenRoads Designer. For some reason, when I have the properties menu docked it'll be working just fine. However, if I leave the properties palette docked and open a different .DGN, the properties menu will then display "no content to display" when I select an element to display the properties of. I've tried to close the pallet and re-open the properties menu, as well as docking the menu to all a bunch of locations on the screen, and lastly un-docking the menu altogether. It seems that no matter what, the same message displays no matter what type of element I select (include referenced objects).
Does anyone have a fix for this? I just have to close ORD and re-launch the software, but I'd rather not have to do that every time I want to switch between files.
Thanks in advance!
Kelby
The only fix right now is to restart the software. Every time this happens, please send a Service Request via connect.bentley.com.
Consultant, Civil Engineering Success Services
Is there a defect number that we could reference when sending such service requests so that the techs know what issue we are logging?
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Interesting. I don't see it logged in the OpenRoads ticket system so I assumed it's a platform issue.
Still reporting this issue recently in 2021 R1. Has there been a solution or defect posted?
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
Still having this issue in 10.11.00.115 EVERY time I change files. Its making doing quantities infuriating.
Zachary Billings, P.E.
Senior Roadway Engineer (Licensed in FL and MI)
CONSOR Engineers, LLC
System Info:
Windows 11 | Intel Core i7-13700k | Nvidia RTX 3080 FTW3 Ultra | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME
Power GEOPAK V8i Select Series 10 Version 08.11.09.918 | FDOT SS10 Version 01.04.01
ORD Version 10.11.00.115 | FDOT Connect Version 10.11.00.02
YouTube Page for ORD: https://www.youtube.com/channel/UC3S-94f7_yUJ-GMhMYPhInA
I have not noticed this happening (yet) in 10.12 (2022 R3)... I will keep y'all posted if it occurs.
Mark
Unfortunately, I am stuck on this version until the FDOT workspace is updated. I have noticed this seems to occur a lot more on older files that have been upgraded through the newer versions. I think some of these files I am working on have been around since 10.07. This project has been around forever...