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

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.

Parents
  • The usual case is that the dynamic view presents whatever is shown in the 3d model, but this isn't always true. The static cross sections draw from the 3d model, not dynamic cross sections. In order to help anticipate what your static cross sections will look like, you may want to confirm that both are rendering the same linework. (Note that even while both are rendering the same linework doesn't always mean presenting the linework in the same way.)

    To make sure your dynamic cross sections are rendering what your 3d model is showing, I think you can do this by creating a brand new one, though you may have to deliberately delete your other cross section model.
  • Hello Derek,

    This is not the case since the features shown in the dynamic view will render in the static view. The problem is that some of the features will render in the static sections only if I change the alignment being used to cut the sections.
Reply Children
  • If the behavior you're describing occurs, then it is most definitely a bug.

    Consider checking to make sure that if it is indeed plotted, you can expect the linework to show up. By this I mean look at the View Attributes to make sure the attributes are the same between the two cross section models, and that Level Display is the same between them.

    Another practical troubleshooting question that just came to mind: How long is the range over which you expect the 3d elements to show up in either of the two sets of cross sections? It is conceivable (though unlikely, I expect) that the linework doesn't show up in the one set of cross sections because that linework is somehow interrupted right at the cross sections.

    I'll be surprised if Bentley's people will see this and not ask for your file, so you might want to save the time and upload your relevant files in a package. Instructions are provided with the advanced reply editor. Meanwhile, I would not be surprised if they do not look at it within the week before it decays from their system (as they've done to some of my uploads), so you might want to save your work in a ZIP file so that even if you have a workaround established by then, you can re-upload it when they're ready.