paoloemilioserra
commented
4 years ago @Lazarica-t The problem is not in the node but in the way your Corridor is built. If you need two different assemblies in two consecutive regions you should consider two separate baselines, one per assembly. The applied subassemblies in the first station of the region that follows are the same as in the region that precedes. This is a Civil 3D behavior that is used to compute the Corridor Feature lines and it cannot be changed.
Lazarica-t
Hi,
There seams to be am issue with the AppliedSubassemblyShape's that I get from the nodes BaselineRegion.Shapes and Corridor.Shapes when dealing with certain types of Corridors. The problem I'm facing is when I have a corridor made up multiple Regions with different Assemblies, see example below:
Red = 1st Sub-Region with it's respective Assembly
Blue = 2nd Sub-Region with it's respective Assembly
As you can see the two Sub-Regions form a continuous Region with station 104.78 being common.
I've noticed some time ago that I get some gaps in the Mass's obtained using Mass.ByShapes nodes, but did not quite understand why this was happening
So the conclusion that I arrived at is that is has something to do with the Subassembly Shape not being properly detected at the intersection of the 2 Sub-Regions.
For some reason the Assembly at station 104.78 where the two Sub-Region's intersect is taken from the previous Sub-Region 1 when in reality it should be from the second one.
I'm assuming the *.Shapes nodes are trying to avoid 2 Assembly instances existing at the same location.. is this correct? Or is there another explanation.. Is there any solution when faced with Corridors that have multiple Regions with different Assemblies?
Thank you!