ORD Hangs When Changing Views

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

Parents
  • 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, PE
    Production Manager (licensed in FL & PA)

    Patel, Greene & Associates, LLC
    PowerGEOPAK V8i SS10 (08.11.09.918)
    OpenRoads Designer 2021 R2 (10.10.21.4)
    OpenRoads Designer 2020 R3 (10.9.0.91)
    ProjectWise Explorer CE 10.0.3.453
    LumenRT CE Update 14 (16.14.60.98)

  • 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 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.10.21.04 | FDOT Connect Version 10.10.03

    YouTube Page for ORD: https://www.youtube.com/channel/UC3S-94f7_yUJ-GMhMYPhInA

  • Appreciate the follow up! This is really good information. 

    Eddie Giese, PE
    Production Manager (licensed in FL & PA)

    Patel, Greene & Associates, LLC
    PowerGEOPAK V8i SS10 (08.11.09.918)
    OpenRoads Designer 2021 R2 (10.10.21.4)
    OpenRoads Designer 2020 R3 (10.9.0.91)
    ProjectWise Explorer CE 10.0.3.453
    LumenRT CE Update 14 (16.14.60.98)

Reply Children
No Data