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.
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.
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.
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.:(
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.
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!