<?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: Skin priorities override? in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262217#M137381</link>
    <description>That's excellent, I hadn't realised the material IDs didn't need to be unique.  Completely solved my problem!</description>
    <pubDate>Sun, 18 Nov 2018 05:31:58 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-11-18T05:31:58Z</dc:date>
    <item>
      <title>Skin priorities override?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262215#M137379</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I'm creating a library of walls and having trouble getting intersections to form correctly in triple membrane systems (stud/air gap/plasterboard fire barrier/air gap/stud) see attachment.&lt;BR /&gt;
&lt;BR /&gt;
I cannot find a way to get the central fire barrier (made of plasterboard) from both walls to connect.  I've made the air barrier material a higher priority than the studs so it passes through correctly, but I can't make the plasterboard higher than the air barrier because it is used as a finish material on other walls.  The only way I can see to do it is to make 2 versions of the plasterboard materials, one for the core and another for finishes...but then they are listed separately on material takeoffs which I don't want.&lt;BR /&gt;
&lt;BR /&gt;
Is there another way to achieve this???&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 10:39:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262215#M137379</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-24T10:39:32Z</dc:date>
    </item>
    <item>
      <title>Re: Skin priorities override?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262216#M137380</link>
      <description>You can give building materials an ID, you could use this for material take off to group together similar building materials with different priority.</description>
      <pubDate>Fri, 16 Nov 2018 08:19:16 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262216#M137380</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2018-11-16T08:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Skin priorities override?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262217#M137381</link>
      <description>That's excellent, I hadn't realised the material IDs didn't need to be unique.  Completely solved my problem!</description>
      <pubDate>Sun, 18 Nov 2018 05:31:58 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262217#M137381</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-11-18T05:31:58Z</dc:date>
    </item>
    <item>
      <title>Re: Skin priorities override?</title>
      <link>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262218#M137382</link>
      <description>No worries, it is rare if we have a single 'group' for any material. We ussually have a structural and non-structural application of building materials and group these all together in their own categories (concrete, bricks, plywood, gypsum board, etc etc) by ID. And some categories like concrete have even more subdivision to help with correct building material intersections (prefab v.s. on site etc).</description>
      <pubDate>Mon, 19 Nov 2018 09:17:35 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Skin-priorities-override/m-p/262218#M137382</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2018-11-19T09:17:35Z</dc:date>
    </item>
  </channel>
</rss>

