I am using ORD 10.10.21.004 with the FDOT Connect Workspace, latest version. I have a brand-new file where I have started doing some cross-slope correction. I have three Views open: Default model, Default3D, and Cross Section. Going from Default View to either Default3D or XS is seamless; there is no discernable lag, I just start working in that view. If I am in either the Default3D or the XS view, and try to switch back to Default, there is about a 10-15 second hang that occurs where ORD is not responding. After that time, I am able to work just fine, but this hang is slowing me down quite a bit.
I do not have Explorer or Properties open, as I know this was the cause of hanging / not responding issues I was having previously when switching views in this manner. This hanging issue is being caused by something else I have yet to determine. Several others on my team have reported this issue as well.
Has anyone encountered this issue?
Thanks
Yes, we have also run into this. Not sure if there's a real solution, but we did find that we were having issues in particular with the dynamic views. When this is happening in one file in particular, we've resorted to deleting the dynamic XS view (GEOMETRY DYNAMICSECTION DELETEDXSVIEWS) which seems to at least temporarily resolve the problem. You will need to regenerate the dynamic XS view and you may lose any manual edits to that view as well (i.e. manually drawn MicroStation lines).
Can I ask, do you have any points in your template(s) that are using Project to Surface as a constraint? I have a theory this is causing the issues, but have yet to prove it.
Eddie Giese, PEProduction Manager | Senior Roadway Engineer | AssociateLicensed in FL & PAACEC FDOTConnect Instructor on behalf of FDOT
Patel, Greene & Associates, LLC PowerGEOPAK V8i SS10 (08.11.09.918)OpenRoads Designer 2022 R3 (10.12.2.4)ProjectWise Explorer CE 10.0.3.453OpenRoads Conceptstation CONNECT Edition (10.0.16.84)LumenRT Pro CONNECT Edition (16.17.60.73)
We've stayed with 2021 R1 (10.10.21.003) for now since it keeps things more consistent between other client workspaces. It seems to work fine with FDOT's latest. I know .004 is what they've certified. Frankly not sure why FDOT released it on 004 and why Bentley is calling this release a minor release despite a fairly significant "speed boost". You may consider going back to 2021 R1 due to many other community issues with R2. A few issues found below... For us, these were secondary reasons to staying on R1.
https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/233189/ord-2021-r2-undo-command-causing-crashes
https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/226224/ord-ce-2021-r2---change-name-and-feature-definition-disabled/698332#698332
https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/232759/ord-2021-r2-vertical-point-control-not-working-on-linear-template/722419#722419
https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/227856/ord-10-10-massive-lag-with-named-boundary-command-in-existing-files/704625#704625
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
I think I might have determined what was causing my problem. We are working on a milling and resurfacing project with cross-slope correction for about 26 miles. Whoever set up the alignment file and baseline used the existing terrain as the active profile. I have had issues with this in the past as it produces a lot of data points for ORD to read every time it looks at that alignment.
So, I went in and drew some lines on top of the existing ground, essentially created a profile based upon the existing ground made up of curves and tangents. When I go back into the file I was having issues with and process my corridors, I am no longer having the issue I was having.
I need to see if the next file I work in is also fixed, but I think that may have done it.
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 4090 FE | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME
ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00
YouTube Page for ORD: https://tinyurl.com/BillingsCADD
I wasn't aware there was a .003 release. I recall being on some other release between the initial 10.10 release and the current, but I think it was a different number entirely.
Thanks for posting all those other bugs. I have certainly experienced some of those, especially the ridiculous slow undo.
It's been very frustrating being a glorified beta tester for almost three years now. Maybe someday they will get this thing right..
I did seem to find a fix that I posted in a reply to Eddie, so I think I am good for this particular issue.
Thanks again
Appreciate the follow up! This is really good information.