<?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 IFC &amp;gt; HLM story range snag in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-gt-HLM-story-range-snag/m-p/606285#M43098</link>
    <description>&lt;P&gt;we run into this in almost every project we pull an IFC into with the hotlink module manager.&lt;BR /&gt;obviously the model exchange has some give and take and compromises and a little extra work go into it. If it is 1-4 stories outside our project range, I'll often just add dummy stories above/below to get the consultants work in range. But something like this (screen shot), I usually send it back and ask for a specific story range break down.&lt;BR /&gt;Anyone have any other tricks or workarounds to getting an ifc in without having to run it back and forth? is there some buried translator setting I'm unaware of, to flatten or compress source files story range to fit?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-06-03 at 3.28.17 PM.png" style="width: 640px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/61633i019E78BACA8B9B2A/image-dimensions/640x789?v=v2" width="640" height="789" role="button" title="Screenshot 2024-06-03 at 3.28.17 PM.png" alt="Screenshot 2024-06-03 at 3.28.17 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Thu, 06 Jun 2024 16:53:50 GMT</pubDate>
    <dc:creator>Patrick M</dc:creator>
    <dc:date>2024-06-06T16:53:50Z</dc:date>
    <item>
      <title>IFC &gt; HLM story range snag</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-gt-HLM-story-range-snag/m-p/606285#M43098</link>
      <description>&lt;P&gt;we run into this in almost every project we pull an IFC into with the hotlink module manager.&lt;BR /&gt;obviously the model exchange has some give and take and compromises and a little extra work go into it. If it is 1-4 stories outside our project range, I'll often just add dummy stories above/below to get the consultants work in range. But something like this (screen shot), I usually send it back and ask for a specific story range break down.&lt;BR /&gt;Anyone have any other tricks or workarounds to getting an ifc in without having to run it back and forth? is there some buried translator setting I'm unaware of, to flatten or compress source files story range to fit?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-06-03 at 3.28.17 PM.png" style="width: 640px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/61633i019E78BACA8B9B2A/image-dimensions/640x789?v=v2" width="640" height="789" role="button" title="Screenshot 2024-06-03 at 3.28.17 PM.png" alt="Screenshot 2024-06-03 at 3.28.17 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 16:53:50 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/IFC-gt-HLM-story-range-snag/m-p/606285#M43098</guid>
      <dc:creator>Patrick M</dc:creator>
      <dc:date>2024-06-06T16:53:50Z</dc:date>
    </item>
  </channel>
</rss>

