Displaying features in Cross Section Issues (Dynamic vs. Static)

Question

Hello, 
 I am using InRoads SS4 version 08.11.09.878 and came across a potential bug. The project is utilizing native styles to handle the display of features. I am cutting sections through multiple corridors, and the crossing features (crosses, points, etc) are showing up as expected in the dynamic view. However, when I cut static cross sections, some of the features are missing especially those of the adjacent corridor. If I cut the sections along the native alignment of the adjacent corridor the missing features are present. Is this working as intended? Is this a function of the relative skew of the adjacent corridor? Is there a workaround? I need these features to be present for annotation purposes. Thanks in advance for the insight.

Chris Key · Accepted Answer

After testing this data, I could not find a reason the features would not display in the static sections. I have logged a defect so development can look into the issue further. 
 
Defect 682236

Derek Schmidt · Answer

Chris Key 
 Is there any news on this defect? 
 I don't know whether this would work for anything else that has been discussed in this thread, but I found that in my circumstance today, I was able to solve this problem by changing the terrain's class from construction to primary. 
 My terrain was showing up in dynamic cross sections just fine, but didn't show up in the static cross sections until I attached a surface template on it. After investigating further, I discovered that I could have skipped the surface template if I'd changed the class.

mlemieux · Answer

We had a situation where this was happening on one of our projects. In our situation our team modeled the eastbound road in one dgn and the westbound road into another dgn. They were then referenced both corridors into a new dgn for cutting sections. Initially we could ONLY get the crossing features to appear for one corridor while in the section dgn file despite the fact that if i cut sections directly in the corridor dgn files the crossing features displayed as expected. After closer examination I discovered that each of the corridor dgn files had a different resolution setting (both for advanced resolution and the solid working area). When the corridor dgn files were corrected so that the design file setting resolutions consistently matched the client seed file the crossing features then displayed properly in the section dgn.

Displaying features in Cross Section Issues (Dynamic vs. Static)

Top Replies