2016/2017 nested family bug?

[aditazz]

When I nest a particular family (child.rfa) into another family (parent.rfa), parent.rfa doesn't render correctly when inserted into a project.  Note that child.rfa has nested families that are scaled, and that seems to be an issue.  Please confirm.

[barthbradley]

Some of the components don't have a material assigned to them.  

....You meant "Render" as in a photo-realistic image; right? 

[aditazz]

Thanks for the quick response, but I should have been more clear: the nested families in child.rfa are not scaled correctly.  See screenshot: the partitions, among other things, should not have gaps.  I have another example where mirrored nested objects aren't mirrored.

[barthbradley]

I'm am not having issues mirroring child at my end. Perhaps you can provide a workflow to follow, and I'll work through your steps and see if something happens. 

[aditazz]

Clarification: there aren't nested mirrored family issues in the attached example.

Are you seeing the toilet partition gaps when loading the attached example in a project?  Note that if you double-click on it to edit it, you won't see the gaps in the family file.

[barthbradley]

I see gaps where there should be gaps (e.g. at anchor locations)

[aditazz]

Are you seeing the big gaps as shown in the screenshot?

[barthbradley]

NO. 

[aditazz]

Can you send me a screenshot of the project file into which you inserted parent.rfa and the project file itself?

Thanks!  Chuck

[ToanDN]

Below is what i see when I loaded it in a new project.  All screwy.

Stop making every level of nested families Shared.  Only share the root level and it should fix your problem.  See attached file.

[barthbradley]

Interesting. Loads fine here. Mirrors fine here. Both Child and Parent.  R2018. 

[aditazz]

I think I need to share families at the lower levels so that they show up as nested blocks when I export to AutoCAD (I know...AutoCAD).

[aditazz]

Per the post header, 2016/2017.  If it works in 2018, then I know it's not a problem with our programmatic model creation.  Thanks!

[barthbradley]

@aditazz wrote:

I think I need to share families at the lower levels so that they show up as nested blocks when I export to AutoCAD (I know...AutoCAD).

---

Change your load order: Load child first and then load parent. 

[barthbradley]

Work fine in R2017. 

Load child.rfa first, and then the parent.rfa. Parent looks fine. Mirrors fine. Export out from project. 

[aditazz]

No joy in loading child then parent.  Again, no worries since it seems to work in 2018...

Thanks! Chuck

[barthbradley]

Like I said, I have no issues with the family in R2017 or 2018 -- no matter how I load it into the project. Odd, since both you and Toan are.  Anyways, good luck. 

[ToanDN]

---

@aditazz wrote:

I think I need to share families at the lower levels so that they show up as nested blocks when I export to AutoCAD (I know...AutoCAD).

---

As said, you CAN share the lowest level (partition component, door panel, fixture, etc...).  But the intermediate levels can be unpredictable sometimes.

[barthbradley]

Parent in 2017