<?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: SEO's, Intersect Priorities and Layer priorities in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279922#M145033</link>
    <description>&lt;BLOCKQUOTE&gt;Gerald wrote:&lt;BR /&gt;I do think that SEO's should trump every other priority as it seems to me that when you have gone to the time and trouble to use them it is because you can't quite do what you want with priority settings&lt;/BLOCKQUOTE&gt;

Agreed!</description>
    <pubDate>Tue, 30 Jun 2015 13:08:33 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-06-30T13:08:33Z</dc:date>
    <item>
      <title>SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279919#M145030</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Question:&lt;BR /&gt;
&lt;BR /&gt;
I'm trying to cut away a piece of wall with a piece of trim. The trim I have is of a lower intersect priority than the wall, so it doesn't actually work with the SEO. It does work if the intersect priority is higher. It also works if I change the layer priorities so they are not the same. But if I change the layer priorities, then my building material intersects do not work.&lt;BR /&gt;
&lt;BR /&gt;
Is there something else that can make this happen?&lt;BR /&gt;
&lt;BR /&gt;
Maybe this is more of a wish... shouldn't SEO's work regardless of intersection priority or layer priority?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 06:49:19 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279919#M145030</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-24T06:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279920#M145031</link>
      <description>Seems strange, normally SEO are independent of IPs.</description>
      <pubDate>Mon, 29 Jun 2015 19:17:15 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279920#M145031</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-06-29T19:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279921#M145032</link>
      <description>&lt;BLOCKQUOTE&gt;Steven wrote:&lt;BR /&gt;Question:&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Maybe this is more of a wish... shouldn't SEO's work regardless of intersection priority or layer priority?&lt;/BLOCKQUOTE&gt;

I have wrestled with this as well and finally given up. I do think that SEO's should trump every other priority as it seems to me that when you have gone to the time and trouble to use them it is because you can't quite do what you want with priority settings. This was not the case before the advent of priorities.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,</description>
      <pubDate>Mon, 29 Jun 2015 19:19:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279921#M145032</guid>
      <dc:creator>Gerald Hoffman</dc:creator>
      <dc:date>2015-06-29T19:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279922#M145033</link>
      <description>&lt;BLOCKQUOTE&gt;Gerald wrote:&lt;BR /&gt;I do think that SEO's should trump every other priority as it seems to me that when you have gone to the time and trouble to use them it is because you can't quite do what you want with priority settings&lt;/BLOCKQUOTE&gt;

Agreed!</description>
      <pubDate>Tue, 30 Jun 2015 13:08:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279922#M145033</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-06-30T13:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279923#M145034</link>
      <description>&lt;BLOCKQUOTE&gt;Steven wrote:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;Gerald wrote:&lt;BR /&gt;I do think that SEO's should trump every other priority as it seems to me that when you have gone to the time and trouble to use them it is because you can't quite do what you want with priority settings&lt;/BLOCKQUOTE&gt;

Agreed!&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
&lt;BR /&gt;
Definitely agree.  Has anybody tried in AC19 yet?</description>
      <pubDate>Tue, 30 Jun 2015 15:01:26 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279923#M145034</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-06-30T15:01:26Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279924#M145035</link>
      <description>Hello Gents,&lt;BR /&gt;
&lt;BR /&gt;
Since it seems pretty clear this would be a useful option I thought I'd create a post in the Construction Wishes area. Please vote there and I will also create a corresponding wish item on our internal database.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=243801" target="_blank"&gt;&lt;/A&gt;&lt;S&gt;&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=243801" target="_blank"&gt;&lt;/A&gt;&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=243801" target="_blank"&gt;&lt;E&gt;&lt;/E&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Best regards,&lt;/S&gt;</description>
      <pubDate>Wed, 01 Jul 2015 01:35:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279924#M145035</guid>
      <dc:creator>NCornia</dc:creator>
      <dc:date>2015-07-01T01:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279925#M145036</link>
      <description>The way the program works is it creates those Priority Based Connections for certain element types automatically. That trumps all, including SEO (PBC in itself being an automatic SEO). For example, it will create such a connection between a Wall and a Slab, and the stronger will always cut the weaker, so then performing an SEO with the weaker as Operator cutting the stronger as Target will not make a difference, because the weaker is already cut so it has no geometry intersecting the stronger at the moment the SEO command is issued. The SEO is performed, it just has no visible result as there are now intersecting geometries. This is important to understand.&lt;BR /&gt;
&lt;BR /&gt;
This is how it works internally, as fair as I know: &lt;BR /&gt;
When there is an automatic Priority Based Connection between a Wall and a Slab, and the BM of the Wall has a higher Intersection Priority, a "Subtraction" SEO is performed, with the Wall as Operator and the Slab as Target. Therefore if you now do a "Subtraction" SEO, with the Slab as Operator and the Wall as Target, no change in either geometry occurs because they don't actually have intersecting geometries since the Slab's intersecting part with the Wall was already cut by the Wall because of PBC. This is why the SEO doesn't work in this case. The Priority Based Connection already performed the SEO on their intersecting parts.&lt;BR /&gt;
&lt;BR /&gt;
You cannot cut from A by B the intersecting portion which has already been cut from B by A.&lt;BR /&gt;
&lt;BR /&gt;
However, in cases where a Priority Based Connection is not performed automatically, the intersecting geometries are there and therefore SEO works as expected. For example, if that Trim was modeled using a Morph, you could perform the SEO to cut the Wall (since no internal SEO is performed automatically between the two based on Intersection Priorities and the intersecting geometries are there):&lt;BR /&gt;
&lt;BR /&gt;
This is the table that shows which connections are performed automatically on which element type combinations:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://helpcenter.graphisoft.com/guides/archicad-17-guides/archicad-17-int-reference-guide/virtual-building/construction-elements/element-intersections/basic-intersection-principles/" target="_blank"&gt;&lt;LINK_TEXT text="http://helpcenter.graphisoft.com/guides ... rinciples/"&gt;http://helpcenter.graphisoft.com/guides/archicad-17-guides/archicad-17-int-reference-guide/virtual-building/construction-elements/element-intersections/basic-intersection-principles/&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Edit: based on a tweet by James Badcock:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://twitter.com/JRPBadcock/status/616181976853282816" target="_blank"&gt;&lt;LINK_TEXT text="https://twitter.com/JRPBadcock/status/6 ... 6853282816"&gt;https://twitter.com/JRPBadcock/status/616181976853282816&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
another good point: PBC is skin-based, while SEO is element based. Just something to keep in mind.</description>
      <pubDate>Wed, 01 Jul 2015 09:29:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279925#M145036</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2015-07-01T09:29:44Z</dc:date>
    </item>
    <item>
      <title>Re: SEO's, Intersect Priorities and Layer priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279926#M145037</link>
      <description>This probably explains some of the glitches I have had,  especially with beams inside walls. Seems that when you carry out too many operations with seo and pbc on a building element it finaly gives in and glitches. Im talking about obvious bugs where the wall geometry goes completly out of whack.</description>
      <pubDate>Wed, 01 Jul 2015 11:55:59 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-s-Intersect-Priorities-and-Layer-priorities/m-p/279926#M145037</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-07-01T11:55:59Z</dc:date>
    </item>
  </channel>
</rss>

