v0.54

  1. The Curtain Walls hierarchy on the EC3 now has one more level to group together Curtain Wall Panels and Mullions.

  2. During the initial export, all quantities for EC3 building elements & their sub-elements (materials) are coming from Revit. After that, during each subsequent synchronization:

    1. Sub-elements (materials) are governed by EC3, if manually altered. Even if a sub-element’s quantity gets changed in Revit, during the next sync the existing EC3 quantity/formula will be left intact.

    2. The building elements and up are always governed by Revit. If a parent elements quantity gets changed in Revit, the EC3 quantity will be overwritten on the next sync.

  3. If a material collection requires mass but the EC3 is unable to provide reliable density to calculate it, an erred equation will be used instead of quantity, e.g., "123.4*kg_per_{{volume_unit}}", so the user could set the density themselves. Also the corresponding comment note will be added.

  4. We had a bug when words ‘concrete’, ‘brick’, ‘steel’, etc. in the parent element’s name affected the mapping of the sub-elements too much. This is fixed now.

  5. A lot of bugfixes and improvements.

Testing recommendations

  1. Please check if the projects which produced errors before are now exported fine.

  2. Also please check the performance and the WebView behavior.

  3. Please pay attention to various sync-related scenarios, e.g.:

    1. A project is exported to the EC3.

    2. Sub-element (material) quantities are changed on the EC3 and saved.

    3. Parent element quantities are changed in Revit, new material layers are added to family types, etc.

    4. The project is synced with the EC3. In this case, the parent element quantities should be updated by Revit, the sub-element quantities should retain their EC3 values, new layers should be added from Revit.

  4. Also please check Curtain Walls export/sync.

  5. Please check whether the words ‘steel’, ‘brick’, ‘concrete’, ‘wood’, etc. in a parent element’s name affect the sub-elements’ mapping in a wrong way.

Last updated