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

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

Derek Schmidt — Thu, 20 Oct 2022 17:27:22 GMT

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.

What is the client seed file you're referring to? The one that you select as you create a new file? I would think that just means that each of the 3d files being sliced need to be coordinated, not that the seed has any bearing on anything. I guess you're probably working in ORD and I might be too SS10 (sadly) to understand what seed you're referring to.

Whatever the answer, very interesting observation, and I'm sure it'll help in the future. Thanks for sharing.

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

mlemieux — Mon, 17 Oct 2022 19:05:54 GMT

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.

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

Tu Nguyen — Wed, 28 Apr 2021 16:27:13 GMT

Thank you Dan! I will look into it. Everything of my model is going very smooth except this problem. it takes so much of mine time already.:(

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

Dan Cryan — Wed, 28 Apr 2021 16:15:57 GMT

This problem still happens to me about 50% of the time, no idea what causes it. The only workaround that I have found is to cut the static cross sections within the same file as the primary corridor model. This is not ideal as it can create very large files, and creates a need for archiving at various progress submittals to minimize file size. I still have issues with some referenced linear template elements or feature definition linework not displaying cells.

I've also found that creating "stacked" cross sections without a border auto-attach (similar to previous 'green-cell' cross sections) has been more successful with displaying the cells from features in separate reference files. This is also not ideal because you then need to go through the additional step of cutting sheets/attaching border files, but at least you are able to annotate more elements.

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

Tu Nguyen — Wed, 28 Apr 2021 16:02:50 GMT

Hi Jared, I run my static cross sections ("Create Cross Sections" tool)today and have same issues. The " cell" does not show up in XS, So I cannot annotate them. All feature in template set up correctly. It's been almost a year since you posted your issue. I wonder if you already solved this problem? If yes, can you please share how you fixed it? I am struggling on this and could not find the solution. Thank you!

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

Derek Schmidt — Wed, 30 Sep 2020 14:51:16 GMT

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.

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

Derek Schmidt — Thu, 27 Aug 2020 12:58:54 GMT

Ah, this may explain why I've had the same trouble. I used to be on Power Geopak SS4 and could create static cross sections and cells would show up. On Microstation/Geopak SS4, the cells wouldn't be rendered. (I haven't tried the same operation in Geopak SS10.)

Do you suppose it's a workspace setting, or maybe it's embedded in the software processors?

It may be worth noting that in my experience, circles or characters representing points do show up in the static cross sections, so I don't know if my observation is the same.

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

Dan Cryan — Fri, 07 Aug 2020 19:21:51 GMT

I am running Power Geopak (SS10) Version 08.11.09.918 and am having the same issue. I am able to see cells where we have linear elements set to feature definitions displayed correctly in the Dynamic "CrossSection View" but they do not display when I use "Create Cross Sections."

I did not have this problem when running Power Geopak SS4. The Element Templates/Feature Defintions appear to be set up correctly as they display in the dynamic viewer, but we need them to display on our Cross Section Sheets for production submittals.

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

Jared Sandberg — Wed, 20 May 2020 22:53:21 GMT

Hi - I'm running Power InRoads V8i (SS4) Version 08.11.09.904 and this issue is happening for me. To clarify, I am able to see elliptical pipes in the "CrossSection View", but if I use the "Create Cross Sections" tool (which is what I want to do), the elliptical pipes do not show up in the created sections.

Can anyone advise on how to fix this issue? It does not seem to have been fixed, 3 years later.

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

Chris Key — Mon, 03 Apr 2017 17:55:55 GMT

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

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

Derek Schmidt — Sun, 26 Mar 2017 20:11:07 GMT

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.

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

Errick Gray — Sat, 25 Mar 2017 17:46:28 GMT

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.

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

Derek Schmidt — Mon, 20 Mar 2017 14:35:38 GMT

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.