It seems that only R2018 can import the export types from a mapping table. R2016 and R2017 simply ignores those values in the txt files. Is it just me, or is it a general issue? On the other hand the txt files seems weird, it show export layers colors, cut layers as fields, like the dwg layer mapping table.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What you descibe is correct. And I'am glad that the behavior is changed in R18.
Still, try not to use these (strange) tables for explicite mapping. Use the IfcExportAs and IfcExportType Parameter for mapping. This table is useful on a Category level as a backup mapping. But it primarly works as a do or don't export filter for subcategories.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that only R2018 can import the export types from a mapping table. R2016 and R2017 simply ignores those values in the txt files. Is it just me, or is it a general issue? On the other hand the txt files seems weird, it show export layers colors, cut layers as fields, like the dwg layer mapping table.
Can you explain more what you are trying to do?
In R > Export > Options > IFC options window when I load the IFC Export Classes txt file R2018 loads the IFC Type values, but R2017 &2016 don't. Also if I set them manually they got cleared on reopening Revit.
Screenshots:
https://1drv.ms/i/s!AlwJ7sqwratrmPFjwUmw-wJsWu76ZQ
https://1drv.ms/i/s!AlwJ7sqwratrmPFid3OYhG-l5pWyfg
What you descibe is correct. And I'am glad that the behavior is changed in R18.
Still, try not to use these (strange) tables for explicite mapping. Use the IfcExportAs and IfcExportType Parameter for mapping. This table is useful on a Category level as a backup mapping. But it primarly works as a do or don't export filter for subcategories.