Civil Cell - Corridors not clipping

Question

Any ideas on why corridors do not clip correctly when using a civil cell? I'm using the 'Basic T' civil cell provided with SS3. The intersecting corridors are using the same template/end condition as the civil cell. I've gotten it to work just fine in the past but now it only partially works. See included image.

Ian Rosam · Accepted Answer

It looks like you have a corridor running through on the SW-NE geom and a civil cell overlaid at the end. You should really pull the start of the corridor back onto the end of the end of the control geom for the civil cell. Then add the civil cell as a clipping refernce to the corridor running NW-SE, 
 Clipping is triggered in a civil cell by defining the primary surface terrain as a clipping reference for the corridor, when placing this terrain and all linear templates are then added as corridor clipping refernces to the selected corridor. 
 The presentation and workshop from the BLC2013 should be available on the Learn Server. Information on how to access these is included in the sticky post 'SELECTseries 3 WORKSHOPS AVAILABLE!' 
 communities.bentley.com/.../84935.aspx 
 I hope this helps. 
 Regards 
 Ian

Mike Barkasi · Answer

After reviewing the files used in Rons design above.... I had previously replied to the follow up post by Ron "BasicT" 
 Ron 
 It appears what is hapening is the base geometry file being used has a resolution set to metric values while the file you are placing the cell in uses Feet to define the resolution. 
 when the cell places the Hz position is worked out but the cell does not construct at the correct elevation. I suspect this is a resut of mis matched units.. Because this does not place correctly terrain is not copying to the placed cell. 
 The civil cell clips the components but the middle portion does not clip .. this is because the terrain is required for this clip... 
 As a general practice ALL civil user should be sure there DGN file (Advanced) units coincide. working with mismatched units can at times cause undesirable results. in the instances of feet and survey feet the issue can easily go unnoticed at times, however in the case of meters to feet the issues are magnified. 
 Additionally working in a 3D file can add complexity (this can be managed but the user needs to be aware of the cooresponding 2D 3D entities that will reside in this one file) this can be avoided by working from a 2D seed and letting the open Roads Technology manage the 3D model (this would then be the equal to the components being displayed in 3D in pre SS3 versions) 
 One last comment - when referencing Terrain DGNs and Geometry DGNs live nesteing (IMHO) should NEVER be used. The use of live nesting with the new technology introduces complexity that most users will want to avoid. There does NOT appear to be any benifit from using live nesting with Terrain, geometry, and corridors. In some cases circular references can end up causing problems. 
 HTH