<?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: Unclear Intersection point Column/beam in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267455#M139579</link>
    <description>You could duplicate the Building Material (BM) and its Cut Fill as well. The Column's BM should use the first Cut Fill, the Beam's BM should use the duplicate. Also, set the Intersection Priority Number of the Column's BM to a higher value than the Beam's BM. This way the Column will cut the Beam because of the higher Intersection Priority Number, and since they have different Cut Fills (although their patterns appear identical) the fills will not be merged in Section.</description>
    <pubDate>Mon, 13 Mar 2017 15:30:12 GMT</pubDate>
    <dc:creator>Laszlo Nagy</dc:creator>
    <dc:date>2017-03-13T15:30:12Z</dc:date>
    <item>
      <title>Unclear Intersection point Column/beam</title>
      <link>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267454#M139578</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hello,&lt;BR /&gt;
&lt;BR /&gt;
When a wooden beam and a column of the same material intersect. the intersection point shows a merged column and beam. It does not show which one of them is the continious one. &lt;BR /&gt;
&lt;BR /&gt;
For our production team, it is quite important to know which one they have to cut. &lt;BR /&gt;
&lt;BR /&gt;
is there a way for Archicad to show a continious outline on these beams and columns without merging the objects?&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image instersection point.png" style="width: 870px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/16240i2481D1A5920A55D4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image instersection point.png" alt="Image instersection point.png" /&gt;&lt;/span&gt;</description>
      <pubDate>Fri, 26 May 2023 10:27:19 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267454#M139578</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-26T10:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: Unclear Intersection point Column/beam</title>
      <link>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267455#M139579</link>
      <description>You could duplicate the Building Material (BM) and its Cut Fill as well. The Column's BM should use the first Cut Fill, the Beam's BM should use the duplicate. Also, set the Intersection Priority Number of the Column's BM to a higher value than the Beam's BM. This way the Column will cut the Beam because of the higher Intersection Priority Number, and since they have different Cut Fills (although their patterns appear identical) the fills will not be merged in Section.</description>
      <pubDate>Mon, 13 Mar 2017 15:30:12 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267455#M139579</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2017-03-13T15:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unclear Intersection point Column/beam</title>
      <link>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267456#M139580</link>
      <description>Thanks, worked perfectly fine!</description>
      <pubDate>Tue, 14 Mar 2017 08:39:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Unclear-Intersection-point-Column-beam/m-p/267456#M139580</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-14T08:39:08Z</dc:date>
    </item>
  </channel>
</rss>

