Why Your Corridors Are Slow And How To Prevent It

You’re Too Slow!

Have you noticed your computer taking ages to load your corridors? Have you taken a nap and woke up to find your computer still reprocessing? Are you considering quitting and working for Publix where shopping is a pleasure? I have a few reasons for you.

1. Your corridor has a lot of template drops looking for a terrain
2. Your corridor has several hidden conditions built inside its template and has to resolve them for every template drop
3. The corridor objects (i.e., parametric constraints, point controls, etc.) have to resolve their conditions in a sequential order for every template drop
4. Your unlocked corridors reprocess everytime you open its DGN!
5. OpenRoads Designer is probably plotting against you

Keep It Simple!

I’ve personally experienced over a 90% improvement to corridor processing times. Here are some of the things I did:

1. Lock/Deactivate your corridors – only unlock them if you need to edit them again
   • This will prevent all your DGNs reprocessing everything every time you open and make corridor edits. Unlock to reprocess after you’ve made the edits.
2. Separate the end condition components into their own DGN and corridors
   • Your pavement, gutter, and sidewalk corridors can load in the blink of an eye if there isn’t any terrain they have to target. Splitting them into modular components is always a gain and not a loss. This is the 3D Linear Method I’ve been writing about here.
3. Don’t over complicate your template’s and their hidden conditions
   • Stop trying to make a master template. The stink to try and fix. Also, they take longer to process since they have to resolve these conditions. Modular modeling is quicker, has better design intent, and is a lower learning curve for most people.