A.B.

JonM, the new version you uploaded fixes the issue. Thank you very much!

Attached is a Revit file with four air terminals from four families and the corresponding IFC file (IFC4 design transfer view, but from previous experiments it looks like the result is the same with other setups). Two of the air terminal families (M_Return Diffuser_exportAsFlowTerminal and returnAirTerminal_selfMade_exportAsFlowTerminal) have IFCExportAs set to IfcFlowTerminal, and they do export to IfcFlowTerminal (but type IfcDistributionElementType, although IFCExportType was IfcFlowTerminalType)....

Hello, I would like to export air terminals in IFC4 as IfcAirTerminal. I set a shared parameter IFCExportAs accordingly, but it does not work: I still get IfcBuildingElementProxy instead of the desired entities. I am all the more puzzled by this behaviour since: It does work with other families, which I do manage to export for instance as IfcFlowTerminal, IfcSensor etc. If I try to export as IfcFlowTerminal from a self-made family, I do get an IfcFlowTerminal. * If I try to export as IfcFlowTerminal...

The plugin solves the issue and I do not see any problem. Thank you so much, JonM!

JonM, thank you so much for your answer and for the plugin! Would it be easy for you to build it also for Revit 2017? I would be even more endebted to you.

Hello, I would like to export a group of HVAC components (e.g. air terminals) as IfcSystem (IfcDistributionSystem would be best but is apparently not possible) without all the duct segments and fittings. When I only have the air terminals grouped into a duct system, this does not export as IfcSystem. As soon as I create the detailed duct layout, I do get an IfcSystem in the resulting IFC. How would you explain this behaviour? Is there a way I can export the system and the IfcRelAssignsToGroup relationship...

I am having the same issue today. Maybe something to do with daylight saving time again?