OpenRoads: Problem with Missing Dynamic Cross-sections

Published on January 5, 2018

Written By: Robert Garrett

Occasionally, an OpenRoads file will fail to show the dynamic cross-sections properly.  I really don’t know what precisely causes this but it is a royal frustration, to say the least. When you open the dynamic cross-section view you see something like this:

That is, you see an empty view where there should be some cross-sections.

The fix is pretty simple. Right-click and hold in the cross-section view until the following context toolbox opens:

Then click on Delete Dynamic Cross Section Views.  I know, it sounds pretty scary. And yes, there are actually some things being deleted, namely the cross-section view and model definitions.  This should not be confused with the models created as part of the cross-section plans production processes using the Create Cross-Sections tool.

After clicking on this command, the software will work a bit. The view being used for cross sections will be closed and the other views will do some strange things but don’t be alarmed. Nothing bad is happening, except…

Your other views will be reset to a different state. The logic which drives this reset escapes me, but there is apparently some sort of saved settings which are used to reset the views. Your results will vary, but in the most recent project where I did this, the Default-3D model in view 5 was reset to Default, levels display was changed and both views had the ACS triad turned on and Level Overrides turned on. These reset display settings match a state of the file when I received it from my client but I had changed the settings and saved settings long since.  So, it appears that the views are being reset to a state which existed at the time that the Dynamic Cross-Section views became corrupt.

See more Tips or dive deeper with Instructor-Led or Self-Paced Training.

Tags: , , , , , , ,
Like this article? Share it!

Leave a Comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Privacy Policy