<?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: Controlling beam intersections in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231640#M124104</link>
    <description>?</description>
    <pubDate>Tue, 26 Sep 2017 00:34:57 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-09-26T00:34:57Z</dc:date>
    <item>
      <title>Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231637#M124101</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi, I'm trying to arrange two complex profile beam elements without having the materials overlap each other. I would like them to touch without connecting. &lt;BR /&gt;
&lt;BR /&gt;
I have created a gutter+fascia profile (steel+timber) and a fascia (timber) profile without gutter. As I mentioned the profiles were assigned as beams and wherever the two elements meet the gutter can be seen overlapping the individual fascia element.&lt;BR /&gt;
&lt;BR /&gt;
I have changed the junction order of the individual fascia to have a higher priority, although there has been no change to the connection. It seems the only way I can prevent them from overlapping is to avoid them touching. Which is fine for 1:100 elevations as the small gap can't be seen. However I'm sure there is something simple I'm missing. Is this a case of changing material/intersection priorities? Thanks for any feedback.&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="beam intersection 3.jpg" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/9199i76F9903955EE1293/image-size/large?v=v2&amp;amp;px=999" role="button" title="beam intersection 3.jpg" alt="beam intersection 3.jpg" /&gt;&lt;/span&gt;</description>
      <pubDate>Fri, 26 May 2023 10:26:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231637#M124101</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-26T10:26:53Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231638#M124102</link>
      <description>&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/9090i5046305BE9A1E8AC/image-size/large?v=v2&amp;amp;px=999" border="0" alt="beam intersection 1.png" title="beam intersection 1.png" /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 04:25:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231638#M124102</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-22T04:25:08Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231639#M124103</link>
      <description>&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/15442i223E5DA72D1A3DB9/image-size/large?v=v2&amp;amp;px=999" border="0" alt="beam intersection 2.png" title="beam intersection 2.png" /&gt;</description>
      <pubDate>Fri, 22 Sep 2017 04:32:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231639#M124103</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-22T04:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231640#M124104</link>
      <description>?</description>
      <pubDate>Tue, 26 Sep 2017 00:34:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231640#M124104</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-26T00:34:57Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231641#M124105</link>
      <description>??</description>
      <pubDate>Tue, 26 Sep 2017 00:34:58 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231641#M124105</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-26T00:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231642#M124106</link>
      <description>My guess is that the steel has a greater intersection priority.&lt;BR /&gt;
Make another BMAT with a lower one than the timber for the gutter. It should work then.</description>
      <pubDate>Tue, 26 Sep 2017 10:03:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231642#M124106</guid>
      <dc:creator>runxel</dc:creator>
      <dc:date>2017-09-26T10:03:49Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling beam intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231643#M124107</link>
      <description>The timber fascia needs to have a building material that is stronger than the gutter and fascia building materials.&lt;BR /&gt;
Or you could try moving the reference line position of the fascia to the gutter side.&lt;BR /&gt;
Or manually trim the gutter fascia so it doesn't overlap (select in plan and CTRL click on the inside edge of the fascia).&lt;BR /&gt;
Or place them in different layers and ensure they have different intersection priority numbers.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 03 Oct 2017 08:06:18 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Controlling-beam-intersections/m-p/231643#M124107</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2017-10-03T08:06:18Z</dc:date>
    </item>
  </channel>
</rss>

