Intersection priorities help the user control interactions between certain elements. Wall and beam elements have their own intersection priority; I'm calling that the element priority. Composite skins (and components of custom profiles) have their own intersection priorities. Those are skin priorities. Neither of these should be confused with the intersection group number property of layers, though that bears on intersections
Searched for "beam"
4 Results
Location: 06 Wood & Plastic A beam, or any other ceiling element, should be shown dashed in the architectural plan, because it's overhead. That same beam needs to be shown solid in the reflected ceiling plan, because then you're upside down looking straight at it. Using a conventional beam element, you would draw it with a dashed line in plan.
(1) A custom profile for modeling and (2) an object for annotation. Profile: In the profile editor • The shape is that of two fascia boards with a reveal of 1/4" below the soffit board. • The horizontal stretch extents are inside the fascia board reveals. This way, when you adjust the overall width the fascia thickness will be unchanged.
Pretty tricky This is so trivial/obvious that I hesitate to point it out. You can't rotate a conventional beam element about the long axis. (Why? Dunno.) But you can rotate profile beams. So you just need a rectangular profile. But if it's so obvious, why isn't there such a profile in the default templates, among the faux-proof-of-concept distorted steel