<?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 NO-GO in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114808#M60645</link>
    <description>&lt;BLOCKQUOTE&gt;Tom wrote:&lt;BR /&gt; I usually get some crazy intersection that is not what I have in mind.  &lt;/BLOCKQUOTE&gt;

Perhaps you could post a sample of what happened when you used the roof intersection method and sketch or note what you had wanted instead?</description>
    <pubDate>Fri, 10 Apr 2009 17:54:14 GMT</pubDate>
    <dc:creator>Erika Epstein</dc:creator>
    <dc:date>2009-04-10T17:54:14Z</dc:date>
    <item>
      <title>SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114802#M60639</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Have intersected various roofs via SEO process.  Looks great in 3d.  However, SEO does not appear to update the cover fill on the roof materials.  &lt;BR /&gt;
Is this how it typically works.  Have been doing this for a some time now with Archicad and wondered if there is a work around.  Is a pain in the neck to have to figure out the roof intersections the old fashioned manual way.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 23 May 2023 13:04:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114802#M60639</guid>
      <dc:creator>Tom Krowka</dc:creator>
      <dc:date>2023-05-23T13:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114803#M60640</link>
      <description>You are not using the ROOF TOOL's built in intersection feature?  Select one roof and cmd-clk on an opposing EDGE.  It will join with the other roof... Repeat this choosing the opposite roofs and they will both join.</description>
      <pubDate>Thu, 09 Apr 2009 00:05:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114803#M60640</guid>
      <dc:creator>vfrontiers</dc:creator>
      <dc:date>2009-04-09T00:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114804#M60641</link>
      <description>SEOs do not change the 2D (plan) view, only the model.&lt;BR /&gt;
&lt;BR /&gt;
David</description>
      <pubDate>Thu, 09 Apr 2009 12:23:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114804#M60641</guid>
      <dc:creator>David Maudlin</dc:creator>
      <dc:date>2009-04-09T12:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114805#M60642</link>
      <description>The only workaround that I use , is to isolate the roofs ( the ones that modified by SEO) by layer combination , and create a 3D documentation , top view .&lt;BR /&gt;
&lt;BR /&gt;
and place it  where its needed in the layout book . at least 3DD is live !</description>
      <pubDate>Thu, 09 Apr 2009 12:32:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114805#M60642</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-04-09T12:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114806#M60643</link>
      <description>Have not had real good luck with roof intersection tool.  I usually get some crazy intersection that is not what I have in mind.   Am going to add the seo/fill issue to the wish list.   Seems pretty straight forward that one operation would cover all aspects of the elements involved.</description>
      <pubDate>Thu, 09 Apr 2009 14:27:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114806#M60643</guid>
      <dc:creator>Tom Krowka</dc:creator>
      <dc:date>2009-04-09T14:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114807#M60644</link>
      <description>Tom:&lt;BR /&gt;
&lt;BR /&gt;
I get very reliable results from Roof Intersections if I roughly draw the perimeters of the roofs where I think they belong before getting ArchiCAD to do the precise work. The issue with SEOs (besides the fact that they do not show in the plan view), is that you will probably end up using some roofs as both Operators and Targets, and the SEOs may become too complex for ArchiCAD to parse reliably.&lt;BR /&gt;
&lt;BR /&gt;
David</description>
      <pubDate>Fri, 10 Apr 2009 12:40:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114807#M60644</guid>
      <dc:creator>David Maudlin</dc:creator>
      <dc:date>2009-04-10T12:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: SEO NO-GO</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114808#M60645</link>
      <description>&lt;BLOCKQUOTE&gt;Tom wrote:&lt;BR /&gt; I usually get some crazy intersection that is not what I have in mind.  &lt;/BLOCKQUOTE&gt;

Perhaps you could post a sample of what happened when you used the roof intersection method and sketch or note what you had wanted instead?</description>
      <pubDate>Fri, 10 Apr 2009 17:54:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-NO-GO/m-p/114808#M60645</guid>
      <dc:creator>Erika Epstein</dc:creator>
      <dc:date>2009-04-10T17:54:14Z</dc:date>
    </item>
  </channel>
</rss>

