<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IFC export - Missing Meshes in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255734#M33438</link>
    <description>Apologies, I should point out that we check out saved IFC file in Solibri and the mesh doesn't show up there, nor does it appear in Revit when our engineers open the file.&lt;BR /&gt;
&lt;BR /&gt;
Cheers</description>
    <pubDate>Tue, 17 Sep 2019 22:03:51 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-09-17T22:03:51Z</dc:date>
    <item>
      <title>IFC export - Missing Meshes</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255733#M33437</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;We're finding that whenever we export a project to IFC, no matter what classifications, translators or mapping we use the site meshes never export. Has anyone else found this problem, and found a solution? We use the our of the box classifications &amp;amp; translators but always seem to have issues!&lt;BR /&gt;
&lt;BR /&gt;
Much of the time everything also exports as IfcBuildingElementProxyType too, with no obvious logical reason (walls are classified as walls, etc but still come out wrong!) It's obviously something we're doing this end, but although sometimes we get it to work there never seems to be one solution!&lt;BR /&gt;
&lt;BR /&gt;
Cheers&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 17 Sep 2019 21:55:45 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255733#M33437</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-09-17T21:55:45Z</dc:date>
    </item>
    <item>
      <title>Re: IFC export - Missing Meshes</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255734#M33438</link>
      <description>Apologies, I should point out that we check out saved IFC file in Solibri and the mesh doesn't show up there, nor does it appear in Revit when our engineers open the file.&lt;BR /&gt;
&lt;BR /&gt;
Cheers</description>
      <pubDate>Tue, 17 Sep 2019 22:03:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255734#M33438</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-09-17T22:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: IFC export - Missing Meshes</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255735#M33439</link>
      <description>As I can remember, a mesh is tagged as "ifcsite" (or so..) and in the "element/domain-export filter" ifcsite is not included in the group of exported ifc-typs to ifc... &lt;BR /&gt;
&lt;BR /&gt;
best regards from Vienna,&lt;BR /&gt;
Klaus</description>
      <pubDate>Wed, 18 Sep 2019 10:10:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-export-Missing-Meshes/m-p/255735#M33439</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-09-18T10:10:43Z</dc:date>
    </item>
  </channel>
</rss>

