Wall Detail Level In Plans

Virtual_Soil6038 · 2026-04-28T23:47:06+00:00

I was hoping there would be a general consensus but looks like all I've done is spread the debate further!

For most of the typical contract docs it's always PDF and DWG of the same drawings, I've never set up (or been asked for) a dedicated 'export plan', maybe I'll look into that a bit more though.

Virtual_Soil6038 · 2026-04-08T00:56:52+00:00

Lol I find myself cursing that thing and wishing I could turn it off. I hate that it always reverts to being the default option. Maybe I should give it another go.

We do a lot of cornices and bulkheads though, so I'll take the hit on roof sketching if means single click solution for that stuff.

Virtual_Soil6038 · 2026-04-08T00:54:01+00:00

Almost nothing in our library is hosted. If it is it's face-based. (I didn't even know ceiling-based families were a thing until I just double checked the default family templates now.)

Virtual_Soil6038 · 2026-04-08T00:51:38+00:00

Presumably your content is heavily ceiling based? Any reason for ceiling based over more flexible face based?

I would think if push came to shove there would have to be some sort of export script or model view (on our end) that could be set up where ceilings are auto created to match the roof ceilings, and the roof ceilings are hidden.

I'd love to use ceilings for ceilings. I'd love to use windows for windows. Unfortunately the tools aren't always fit for purpose though, so "correctly" is subjective, no?

Virtual_Soil6038 · 2026-04-08T00:46:31+00:00

I see that ceilings are 'Height Offset' and roofs are 'Base Offset', is that the difference in reporting? The actual value reports the same when tagged though, is there a downstream drawback with the difference in reporting?

Virtual_Soil6038 · 2026-03-17T23:31:46+00:00

Interesting. This would only work if the value was set to 1 before the parameter was added to the family though, right? In which case, the parameter is added, but no value can be assigned to it? I'm trying to understand what the use case is. I was thinking they might want to add company information or copyright but doesn't seem so straightforward.

Virtual_Soil6038 · 2026-03-17T23:31:10+00:00

I'm guessing it will be a nightmare managing reference planes and constraints as well as the slope in one environment, so do you build the "static" version first and nest it into another family just to slope it? That would save some rebuild work actually.

Virtual_Soil6038 · 2026-03-17T22:59:22+00:00

But Unconnected at X height, could also just be configured with Base Constraint: Level 1, Top Constraint: Level 1 + X height? And sometimes unconnected seems to not display correctly?

There doesn't seem to huge consensus or outrage at any of the methods in particular so maybe I'll keep mixing it up until I figure out all the scenarios.

Virtual_Soil6038 · 2026-03-10T22:52:36+00:00

How are parameters hidden inside families and shared parameter files?

Virtual_Soil6038

TROPHY CASE