First off, Welcome to the forum Harnta! :thumbsup:

Yes - with some caveat.

You will not be able to employ the (Revit) column, nor beam, family templates to first make these sub-children, as they are "specials" that enable certain behaviours once loaded into a project - you would however be able to build the components using the more generic, er generic model category family templates - which you could then switch to the column and/or beam categories, then load within a "parent" family - which itself could potentially be one of the "cleverer" category-specific family templates (say column, to exploit level-to-level control).

BUT

before doing that, you would also need to plan out your scheduling strategy - so that you can consider your parameter controls and associations. At the very least you will probably want your "children" families to be shared, to scheduled directly, rather than "through" the parent, but whether their sizes are controlled by the "parent" family (or not) will define how you approach instance/type parameter assignments.

Has that made any sense?

Alternatively, and with out much context, this may be a good use of Assemblies inside of Revit- it would allow you to gather all of the elements and not have to do as much forward assumptions of what will be needed. - A process to consider


Sent from my iPhone using Tapatalk

Thanks for your answer!


Now it works, but I need to create a own shared parameter that will represent the lenght and cut length in schedule. I supose it is not possible to get the "real" length from beams and columns when you create them in a generic family template first, or am I doing anyting wrong?

Not sure I understand where you're coming from, but inclined to answer the question as posed "yes of course it is!" but perhaps post up your .rfa so we might take a look?

I post the column and beam I have created with genric model template, the problem I have is that I can´t get any length or cut length when loading them into Project and making Schedule. What have I done wrong?

In de family are none shared parameters. You should them as absolute minimum. Have you thought about the material? Gool luck. I tried it also with steel. I did not get the changing of profiles right. With wood that is much more easy. (Only 3)

They are shared, at least when I nested them. I have nested them in to a family, and can get the information I could not get earlier. The problem now is how I get the length and cut length from the ”children” family created in generic family template. The length dosen’t even appear if I am not putting it in parent family.

Until the wood comes in a different profile.

To clarify (for Harnta): material (parameter) tieing is entirely possible, parent-to-child.

That is correct shared but you did not use shared parameters. Look it up.


Verstuurd vanaf mijn Moto G (4) met Tapatalk