Load Family - The parameter ... doesn't exist in the Family. It will be ignored.

Load Family - The parameter ... doesn't exist in the Family. It will be ignored.

Nik4_99
Enthusiast Enthusiast
1,791 Views
6 Replies
Message 1 of 7

Load Family - The parameter ... doesn't exist in the Family. It will be ignored.

Nik4_99
Enthusiast
Enthusiast

Hi.


I am trying to add a HEB 240 beam from the German Content Pack (RVT2021_DEU_Libraries) into the project.

I get 16 warnings: "The parameter ... doesn't exist in the Family. It will be ignored."

The beam is added with the name "HEB 240", but the actual measures are from HEB 260. "Edit type" shows all parameter values from HEB 260.

If I take a look at the TXT file, all the parameters are there, for all HEB beam family.


This topic:

Revit 2017 - Canada CISC Structures Beams family - Parameters don't exist

might be related.


My user interface is English. We have to use HEB beams (and other diverse elements from German CP) in our project.


Regards,

N


Win 10 Enterprise:
Revit 2021; Autocad 2021; Autocad P3D 2021

0 Likes
1,792 Views
6 Replies
Replies (6)
Message 2 of 7

RPTHOMAS108
Mentor
Mentor

It is telling you that the column in the type catalogue doesn't have a compatible parameter in the Family. So you should check the family has the parameter of same name and type for each of the columns in the type catalogue.

 

Since structural section properties were introduced the columns in the type catalogue to represent those have SECTION_PROPERTY in the header, prior they would have been just 'length'. If you look at some of the families they have not been updated for the structural sections i.e. the RSJ in UK still has the old system, but we never use RSJ's so seemingly nobody cares or has noticed.

 

This may be the source of the issue, if it doesn't find a match it will just give that warning and use the value defined in the family (rfa file).

 

For that reason, it is probably good practice to ensure the library rfa files have just one easy to recognise as wrong size defined rather than an actual size. You do a headroom check on a 610 UB which is sized like a 254 UB, who is going to pay for the cost of that. For clash check better to oversize the erroneous default but for structural checks better to undersize it (so that in both instances the error is highlighted as a failure). I expect most independent structural analysis and design programs would base design on the serial size of the member (for the off the shelf cases that type catalogues cover anyway). 

 

Probably wise to validate the sizes with the model checker or some other system prior to export regardless. Who knows what someone may have done between when it was loaded in and when it was exported. Some people do the craziest things to solve a high-pressure issue in short term (not thinking of future consequences) way I've noticed.

0 Likes
Message 3 of 7

Nik4_99
Enthusiast
Enthusiast

Hi, thank you for the reply.

 


@RPTHOMAS108 wrote:

It is telling you that the column in the type catalogue doesn't have a compatible parameter in the Family. So you should check the family has the parameter of same name and type for each of the columns in the type catalogue.


This is the Autodesk's content package - I didn't edit no content - am I the only one having this issue?

Is anyone who is working with a Content Pack other than the original installation language supposed to edit every family's txt file to modify the attributes?

This is frustrating and time-consuming.

When I open the family in Revit, it has English naming, while the .txt file has German naming.

Same content package.

I assume that Revit automatically translates the parameter names from RFA, while the TXT naming remains untranslated.

I can't see the logic. Especially when I encounter other RVA families that have parameter names that are NOT translated.

That being said, I have translated

,Breite##SECTION_PROPERTY##MILLIMETERS,Höhe##SECTION_PROPERTY##MILLIMETERS,Flanschdicke##SECTION_PROPERTY##MILLIMETERS,Stegdicke##SECTION_PROPERTY##MILLIMETERS,Stegabrundung##SECTION_PROPERTY##MILLIMETERS,Querschnittsfläche##SECTION_AREA##SQUARE_CENTIMETERS,Umfang##SURFACE_AREA##SQUARE_METERS_PER_METER,Nominalgewicht##WEIGHT_PER_UNIT_LENGTH##KILOGRAMS_FORCE_PER_METER,Trägheitsmoment starke Achse##MOMENT_OF_INERTIA##CENTIMETERS_TO_THE_FOURTH_POWER,Trägheitsmoment schwache Achse##MOMENT_OF_INERTIA##CENTIMETERS_TO_THE_FOURTH_POWER,Elastizitätsmodul starke Achse##SECTION_MODULUS##CUBIC_CENTIMETERS,Elastizitätsmodul schwache Achse##SECTION_MODULUS##CUBIC_CENTIMETERS,Plastizitätsmodul starke Achse##SECTION_MODULUS##CUBIC_CENTIMETERS,Plastizitätsmodul schwache Achse##SECTION_MODULUS##CUBIC_CENTIMETERS,Schnittnamenschlüssel##other##,Typenkommentare##other##

to

,Width##SECTION_PROPERTY##MILLIMETERS,Height##SECTION_PROPERTY##MILLIMETERS,Flange Thickness##SECTION_PROPERTY##MILLIMETERS,Web Thickness##SECTION_PROPERTY##MILLIMETERS,Web Fillet##SECTION_PROPERTY##MILLIMETERS,Section Area##SECTION_AREA##SQUARE_CENTIMETERS,Perimeter##SURFACE_AREA##SQUARE_METERS_PER_METER SECTION_MODULUS##Nominal Weight##WEIGHT_PER_UNIT_LENGTH##KILOGRAMS_FORCE_PER_METER,Moment of Inertia strong axis##MOMENT_OF_INERTIA##CENTIMETERS_TO_THE_FOURTH_POWER,Moment of Inertia weak axis##MOMENT_OF_INERTIA##CENTIMETERS_TO_THE_FOURTH_POWER,Elastic Modulus strong axis##SECTION_MODULUS##CUBIC_CENTIMETERS,Elastic Modulus weak axis##SECTION_MODULUS##CUBIC_CENTIMETERS,Plastic Modulus strong axis##SECTION_MODULUS##CUBIC_CENTIMETERS,Plastic Modulus weak axis##SECTION_MODULUS##CUBIC_CENTIMETERS,Key Section Name##Other##,Type Comments ##Other##

I had to paste both lines along with values for default (HEB260) column in the same text editor, and then to color one by one parameter along with values, at the same time looking at the family opened in Revit to be sure that generic translates were accurate (as they weren't).

 

I have managed to alter the generic translation to represent the Revit's naming, except the (not so important) "Schnittnamenschlüssel". As I couldn't find the name in the Revit, I have named it "Key Section Name", and got the "The parameter Key Section Name doesn't exist in the Family. It will be ignored." warning.


Bottom line: Am I supposed to do the same for every family from "German Content Pack" as long as I work in English installed Revit?

There has to be a logical solution. I just refuse to believe that such a huge company like Autodesk has such a work philosophy.

What will happen if we get the project in Italy? I am afraid to mention Japan, China, Korea...?

 

 

0 Likes
Message 4 of 7

Nik4_99
Enthusiast
Enthusiast

Duplicate

0 Likes
Message 5 of 7

Nik4_99
Enthusiast
Enthusiast

Hi all,

 

I am basically doing the same for other steel structure families, and this

"The parameter Key Section Name doesn't exist in the Family. It will be ignored." warning is kind of annoying.

 

Does anyone know what is the English parameter for "Schnittnamenschlüssel"?

It definitely is not "Key Section Name".

 

Thanks, cheers,

N

 

 

 

 

0 Likes
Message 6 of 7

Emanuel.Nestor
Autodesk Support
Autodesk Support

Hi @Nik4_99,

I think you are looking for "Section Name Key". It is a built-in parameter that was used for mapping profile name during SMLX export.

You could leave it blanc, so the Family + Type names are used for export.

(If you use it, please add the correct section name to be used for export to SMLX file).

 

Hope it helps 🙂
Emy



Emy Nestor
Message 7 of 7

Nik4_99
Enthusiast
Enthusiast
Hi Emanuel,
Thank you for your reply (I don't know how I missed the e-mail notification) - I will check it definitely.
Cheers
0 Likes