<?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: Custom Composite Wall Intersections in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205403#M111208</link>
    <description>One of the advantages of using Composites is that fills rotate with the wall, whereas with standard walls they don't.</description>
    <pubDate>Tue, 16 Mar 2010 19:42:33 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2010-03-16T19:42:33Z</dc:date>
    <item>
      <title>Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205393#M111198</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Any input here would be welcomed!&lt;BR /&gt;
&lt;BR /&gt;
I've created multiple custom composite wall types and cannot for the life of me get them to intersect correctly (see screenshot).   I've tried making all the composite skins the same priority, the walls themselves are the same priority, I have the 'enable skin priorities' box checked, but still no luck... what am I missing?!&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;IMG src="http://community.graphisoft.com/t5/image/serverpage/image-id/67303iE8F8BB5CA8DCCAF0/image-size/large?v=v2&amp;amp;px=999" border="0" alt="Screen shot 2010-03-15 at 2.42.30 PM.png" title="Screen shot 2010-03-15 at 2.42.30 PM.png" /&gt;</description>
      <pubDate>Mon, 15 Mar 2010 18:53:16 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205393#M111198</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T18:53:16Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205394#M111199</link>
      <description>It looks like the lower wall is intersecting with a wall on a hidden layer.</description>
      <pubDate>Mon, 15 Mar 2010 19:03:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205394#M111199</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T19:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205395#M111200</link>
      <description>Matthew -&lt;BR /&gt;
&lt;BR /&gt;
Good thought, but unfortunately, I don't think this is the case.  There aren't any other walls in this area, and the layer the visible walls are on has a distinct priority that is not shared w/ any other layers...</description>
      <pubDate>Mon, 15 Mar 2010 19:16:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205395#M111200</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T19:16:44Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205396#M111201</link>
      <description>Check out Cecilia's post in &lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?t=18300&amp;amp;postdays=0&amp;amp;postorder=asc&amp;amp;&amp;amp;start=0" target="_blank"&gt;THIS THREAD&lt;/A&gt; for an explanation and diagram of skin priorities. This should help.</description>
      <pubDate>Mon, 15 Mar 2010 19:30:19 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205396#M111201</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T19:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205397#M111202</link>
      <description>Thanks s2art -&lt;BR /&gt;
&lt;BR /&gt;
Cecilia's diagram was helpful and is basically how I understood skin priorities to work.  I've attached a screenshot that shows how I have the priorities set up w/n my composites.  The '8s' are finishes and the '4s' are cores, but it doesn't seem to want to intersect correctly.  Could it because I Have different skin patterns to accommodate the 45 degree angle?  I feel like I'm missing something pretty simple here!</description>
      <pubDate>Mon, 15 Mar 2010 19:51:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205397#M111202</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T19:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205398#M111203</link>
      <description>You have the priorities reversed. The core should have the higher priority number.</description>
      <pubDate>Mon, 15 Mar 2010 21:24:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205398#M111203</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T21:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205399#M111204</link>
      <description>Hi Matthew -&lt;BR /&gt;
&lt;BR /&gt;
Just reversed the priorities so the core has a higher number priority, but the result is the same.  Any other thoughts?  Thanks.</description>
      <pubDate>Mon, 15 Mar 2010 21:41:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205399#M111204</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-15T21:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205400#M111205</link>
      <description>Can you post a s/shot showing your reference line clearly.</description>
      <pubDate>Tue, 16 Mar 2010 03:07:56 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205400#M111205</guid>
      <dc:creator>Rod Jurich</dc:creator>
      <dc:date>2010-03-16T03:07:56Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205401#M111206</link>
      <description>Check the presence of some column in the intersection.&lt;BR /&gt;
I noted that columns make interference with the composite structures if they are in a layer with the same number of intersection of the walls ... I think it is a bug</description>
      <pubDate>Tue, 16 Mar 2010 08:06:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205401#M111206</guid>
      <dc:creator>alemanda</dc:creator>
      <dc:date>2010-03-16T08:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205402#M111207</link>
      <description>&lt;BLOCKQUOTE&gt;BenY_Boston wrote:&lt;BR /&gt;Could it because I Have different skin patterns to accommodate the 45 degree angle?&lt;/BLOCKQUOTE&gt;

Absolutely in order to get a correct "contextual" fill orientation linked to the wall's direction you must &lt;BR /&gt;
&lt;BR /&gt;
1. use the same fill pattern (to get correct skin connections)&lt;BR /&gt;
2. set the skin fill to be linked to element origin (to get correct orientation)&lt;BR /&gt;
&lt;BR /&gt;
see attached</description>
      <pubDate>Tue, 16 Mar 2010 08:27:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205402#M111207</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-16T08:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205403#M111208</link>
      <description>One of the advantages of using Composites is that fills rotate with the wall, whereas with standard walls they don't.</description>
      <pubDate>Tue, 16 Mar 2010 19:42:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205403#M111208</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-16T19:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Composite Wall Intersections</title>
      <link>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205404#M111209</link>
      <description>Til -&lt;BR /&gt;
&lt;BR /&gt;
That was it!  Thank you.  I used the same fill for both skins and linked it to the element origin rather than project origin and I'm in business.  Thanks again!&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/10883i89B22D3316FFCF58/image-size/large?v=v2&amp;amp;px=999" border="0" alt="Screen shot 2010-03-17 at 12.01.15 PM.png" title="Screen shot 2010-03-17 at 12.01.15 PM.png" /&gt;</description>
      <pubDate>Wed, 17 Mar 2010 16:02:50 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Custom-Composite-Wall-Intersections/m-p/205404#M111209</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-03-17T16:02:50Z</dc:date>
    </item>
  </channel>
</rss>

