Nested families do not join cleanly in project environment

[Sahay_R]

I have a whole bunch of nested solid families in an empty host. The families join beautifully in the family editor, but you can see the join lines in the project environment. All nested families are NOT shared. One solution would be to hide the geometry in plan views and see symbolic lines - YUCK! Is there a better solution at all?

[ToanDN]

the 3d elements set to not show. what you see in your screenshot are the symbolic lines, no?

[barthbradley]

No.

[ToanDN]

---

@barthbradley wrote:

No.

---

Can you post that family?

[barthbradley]

It is the family she posted in #17.  Header doesn't show above Project Plan View Cut Plane.  

And, all the linework being shown in Cut View isn't coming from the geometry; it's symbolic linework in the family.  

[ToanDN]

That is exactly what I said.  Below is what I see when I edit a nested family.

If she turns the 3d elements to show for Plan/RCP then the header will show if it is joined with the pillars.

[barthbradley]

This is what I see:

And...this is what I see (after deleting detail lines in family) in Project Plan View (Cut Plane 4'-0"). I don't see no header.  

[ToanDN]

No you don't.

[barthbradley]

What do you mean?

[ToanDN]

I mean you are correct.

[FAIR59]

As joining works on the material level, you need to link all the walls to the same material- parameter.

[Sahay_R]

@barthbradley - that is precisely what I see! At last we are on the same page! Bravo! (BTW the header visibility - or non-visibility - is not a part of the problem.....)

BTW there are no detail lines in the part families that can be seen to rear their ugly heads. FYI.

@FAIR59 - I tried assigning a material parameter to the geometry in each of the families, then associated them to a material parameter in the host family - no change. Unless I am missing something?

[FAIR59 · Accepted solution]

@Sahay_R, sorry, I was also looking at the symbolic lines. I had hoped to avoid it, but then the only solution I see, is to make the nested families shared.

[Sahay_R]

@FAIR59 - YOU RULE!!!!

[Viveka_CD]

@Sahay_R, @FAIR59, @ToanDN, @barthbradley, @Avaris.

Excellent brainstorming so far! Kudos to your participation and keeping the forums alive 

Regards,

[ToanDN]

What I collect from this is that families can only join geometries cleanly (no lines) within their immediate or the very first level of nesting.  Making the nested families shared essentially set the project equal to the 1st level of nesting environment, thus they work.

[barthbradley]

@Sahay_R: May I ask you a question? Is this an As-Built Construct? Just trying to wrap my brain around the overall construction/assembly, and why all the odd dimensions (fractional increments at 1/32"?) and misaligned planes between the components.  

Anyways, my OCD kicked in big-time and the result was this Generic Model construct (attached).  Maybe you can use it.  Geometrys' are all aligned and lock to Ref. Planes and readied for labeled dimensions. 

All surfaces in the final Assembly line up precisely. The main issue I found, was that your "Entry-Side2.rfa" (my "Jamb.rfa") refused to join to your "Entry-all around.rfa" (my "Surround.rfa") -- no matter what approach I took.  Very, very strange. I reconciled by modeling the jambs (a.k.a. "entry sides") directly in the "Surround" family (your "Entry-all around" family).    

FWIW...

[Viveka_CD]

@barthbradley, @Sahay_R, @ToanDN

Here's another nested family issue that you the famous trio EE's may want to chime in.and offer your expert advice..

Regards,

[Sahay_R]

@barthbradley - yes, it is an as-built guided by PDFs and photos - hence the non-sculptural approach.  Also - I created the family because there are multiple entries.

Thank you for the RFA - however my original RFA has grown and matured since then and is now very docile and polite. Just the way it should be.....

[vuk.vukanic]

I did not test it on complex families, but this works:

Nest 2 child shared families (C1, C2) into parent family (P1), then nest P1 family into yet another parent family (F1).

Conditions:

1. Joining needs to be done in P1 family

2. P1 family must not be shared

F1 family in project shows correct joining.

Not sure if this is something I would suggest, but just thought I'd share on a slim chance anyone might find it of use...