<?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: Collaboration: Revit Support in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Collaboration-Revit-Support/m-p/581028#M42787</link>
    <description>&lt;P&gt;Yes!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is interesting - we are about to become multi-platform (not by choice) and this would be crucial for our collaborations wihtin project teams.&lt;/P&gt;
&lt;P&gt;If we can't change our clients then we have to try the second best...&lt;/P&gt;</description>
    <pubDate>Tue, 19 Dec 2023 13:18:40 GMT</pubDate>
    <dc:creator>Erik Bjornhage</dc:creator>
    <dc:date>2023-12-19T13:18:40Z</dc:date>
    <item>
      <title>Collaboration: Revit Support</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Collaboration-Revit-Support/m-p/580900#M42786</link>
      <description>&lt;P&gt;More than just having to share model content with other consultants, our practice is multi-platform because of client mandates and so we are working between both Archicad and Revit every day. There is a limit to how much I can complain about how bad Revit's implementation on IFC importing is but I'd like to get some discussions going on how the IFC export from Archicad can be tweaked to better enable importing to Revit.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;RFA/RVT addon&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;No support for Storeys / Reference Levels in the exported geometry. The resultant Revit model may be geometrically correct but it cannot be used to view the building cut into floors.&lt;/LI&gt;
&lt;LI&gt;No support for grids.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;IFC Model Exchange with Revit Add-on&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;The add-on currently uses the "Open IFC" workflow which I understand Autodesk has stopped development on many years ago. They now focus on the Link IFC workflow which opens/translates IFC data much faster but uses an entirely different engine. On some of our projects this difference can equate to a hour versus a day to open a 30 storey IFC model. This means if we want a fast translation to Revit we have to forego the benefits of the Add-on and do the steps manually.&lt;/LI&gt;
&lt;LI&gt;On of the issues we are curerently wrestling with is the visability of 2D information for doors and windows.&amp;nbsp;&lt;A href="https://github.com/Autodesk/revit-ifc/issues/358" target="_blank" rel="nofollow noopener noreferrer"&gt;https://github.com/Autodesk/revit-ifc/issues/358&lt;/A&gt;. ifcOpenShell has a patch to attempt to fix the issue (when it works) but it would be great to have the fix built into the Achicad IFC export in the first place. According to the programmers at ifcOpenShell:
&lt;PRE&gt;ArchiCAD has the ability to store 2D data with objects like doors for door swings. ArchiCAD's implementation is not 100% correct (using&lt;BR /&gt;footprint instead of annotation contexts), but otherwise not too shabby.&lt;BR /&gt;&lt;BR /&gt;Revit, however, is incapable of understanding this 2D representation. Revit users linking in IFCs produced by ArchiCAD may experience the&lt;BR /&gt;following symptoms:&lt;BR /&gt;&lt;BR /&gt;A. Invisible doors, and difficulty selecting doors&lt;BR /&gt;B. Invisible door swings, or only visible at particular view ranges&lt;BR /&gt;C. Weird arc shapes around doors&lt;BR /&gt;D. Extra lines around doors and walls&lt;BR /&gt;E. Cannot easily change visibility graphics of 2D vs 3D elements&lt;BR /&gt;F. Cannot view 2D data in a 3D view&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Grid elements trasferred to Revit via IFC have a behaviour of being generated first so their 2D extent is correct but their height is limited to 0-1m so they have to be manually stretched to match the height of models and reference levels before they can be seen in plan views.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm sure there will be more items to dicsuss, but I thought I'd get a topic going so that we have somewhere to discuss them.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jan 2025 12:44:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Collaboration-Revit-Support/m-p/580900#M42786</guid>
      <dc:creator>Matthew Johnson</dc:creator>
      <dc:date>2025-01-03T12:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Collaboration: Revit Support</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Collaboration-Revit-Support/m-p/581028#M42787</link>
      <description>&lt;P&gt;Yes!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is interesting - we are about to become multi-platform (not by choice) and this would be crucial for our collaborations wihtin project teams.&lt;/P&gt;
&lt;P&gt;If we can't change our clients then we have to try the second best...&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2023 13:18:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Collaboration-Revit-Support/m-p/581028#M42787</guid>
      <dc:creator>Erik Bjornhage</dc:creator>
      <dc:date>2023-12-19T13:18:40Z</dc:date>
    </item>
  </channel>
</rss>

