We’ve encountered an issue with OpenRoads’ cross-section engine in which solids that are hollow, whether by grouped hole or by subtract solid operation, do not cut in cross-sections created by the OpenRoads engine. The same problem occurs whether the hollow solids originate from an InRoads Template or from an AECOSim SmartSolid (it is extremely consistent, like a hard rule, with the AECOSim SmartSolids; with the InRoads Template objects, it was random, even within the same cross-section cut). It sounds similar (but not identical) to defect D14630, but this is applicable only to solids that are hollow; non-hollow solids do display as expected. The example in particular dealt with here is box girders as SmartSolids that need to be referenced into an OpenRoads corridor. Defect D14630 was logged with Geopak 08.11.09.722 and we're using Power Rail Track 08.11.09.845 (other 08.11.09.8XX versions have seen the same problem, too).
The weird thing is that the problem does not exist in the “Open CrossSection View” command, only in the “Create Cross Sections” command. So we can measure off the OpenRoads model in cross-section view, but not plot the same cross-section contents due to the two commands' different behaviours. Anybody have any experience similar to this?
Thank you