Void issue

[Randy_CaS]

Loading this family into a project via catalog file results in the void size not matching the type, as seen in the image. The void size appears to always load at the size that is saved as the default type in the parent. Opening the family and reloading into the project without saving it, will fix the issue. Parameter "A" drives the size of the void and a family type parameter drives the size of the fan.

I think I could just add parameter A to the catalog file, but I am trying to understand what's going on here.

Thanks in advance

[dalmore]

Cannot reproduce. RAC 2012

[mark b]

Seems to work fine here as well, RAC 2012

[mdradvies]

Doesn't work in RAC2011 NOR in 2012 for me.
It seems Revit will only fill in parameters which are indeed specified in the type catalogue. All others remain standard. Fastest way to solve this is simply put the parameter in the catalogue file.

[Alfredo Medina]

The "A" parameter and the different types of the family seem to be working well here (tested with RAC2012).

[mdradvies]

Are people testing in 2012 actually following the OP?
Open new project > draw wall.
Place component > Load family > select one from the TC (NOT first one).
I tried this several times and it doesn't work, also not in 2012...

[dalmore]

Right. I could reproduce. Looking at the TXT file the bahviour seems quite natural. Parameter A is nowhere defined. Solution could be to attach the void to the fan outline instead of to the reference line. Or set Values for parameter A. At the same moment the 6 warnings could be resolved.

[Alfredo Medina]

Are people testing in 2012 actually following the OP?
Open new project > draw wall.
Place component > Load family > select one from the TC (NOT first one).
I tried this several times and it doesn't work, also not in 2012...

Well, the family does not show up immediately on the screen, but it is in the Generic models folder of the family browser; from there, you can create instances to place on the face of the wall. Then, switching to different types seems to work fine. The only issue is about some text parameters, such as Description, URL, etc, that are still to be linked from the base family to the host, which creates some warnings.

[mdradvies]

Well, the family does not show up immediately on the screen, but it is in the Generic models folder of the family browser; from there, you can create instances to place on the face of the wall. Then, switching to different types seems to work fine. The only issue is about some text parameters, such as Description, URL, etc, that are still to be linked from the base family to the host, which creates some warnings.

??? It does with me. I am placing it from a 3D view btw. Maybe that's the difference?

[mdradvies]

Right. I could reproduce. Looking at the TXT file the bahviour seems quite natural. Parameter A is nowhere defined. Solution could be to attach the void to the fan outline instead of to the reference line. Or set Values for parameter A. At the same moment the 6 warnings could be resolved.

Dalmore, I was thinking this too... But this kind of means that when using a Type Catalogue ALL your parameters need to be:

1. Included in the TC.
2. Driven by parameters in the TC (by formula).
3. Manually set up after placement...

This is somewhat unexpected and troublesome... I don't really use TC's a lot (except for structural members) so I never noticed this before. But this does imply some major constraints to the use of TC's.