A post in the discussion group today got me thinking about something I do and take for granted. He was complaining, rightfully so, about how slow corridors are in the object viewer. Read on to find out a way to improve your performance.
The performance of the Object Viewer seems to be inversely proportional to the amount of data you’re trying to view. Corridors have a ton of information in them typically.
- You have corridor sections every X feet or metres; the more you have, the slower it will be.
- Each corridor section has a ton of information as well. Just think of a LaneOutsideSuper.
That’s 27 objects…and that’s just a single subassembly. A typical urban road may have over 120 pieces that make up EVERY corridor section.
We may need all of that when we create our assembly, but we don’t need to display all that info inside our corridor. Really, we just need the Top.
A savings of 114 objects per corridor section. a 93% reduction in objects. Even the most jaded techie can appreciate that.
How do we do this? Easy…the dreaded Code Set Styles.
Just to make sure you’re not missing anything. When you are creating those “No Markers” type of styles make sure you turn off the Links, Markers, or Shapes in both the 2D view and the 3D view. If you forget the 3D view then, well, you’ve done a lot of work for nothing.
There is even more you can do to help yourself. Turn off all those pesky corridor feature lines that you really don’t need…like all those that lie underground. You’ll find a Feature Lines tab in corridor properties.
Good luck and thanks for watching.