<?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: Slab and Wall Intersection Issue in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227577#M122445</link>
    <description>Have you tried using a roof set to zero depth for your operator?&lt;BR /&gt;
&lt;BR /&gt;
Cheers,</description>
    <pubDate>Fri, 09 Sep 2016 00:06:50 GMT</pubDate>
    <dc:creator>Gerald Hoffman</dc:creator>
    <dc:date>2016-09-09T00:06:50Z</dc:date>
    <item>
      <title>Slab and Wall Intersection Issue</title>
      <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227576#M122444</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi All&lt;BR /&gt;
&lt;BR /&gt;
I’ve come upon a modelling issue where I have a tapering floor slab which i’ve modelled with a SEO using a morph to cut the slab. &lt;BR /&gt;
&lt;BR /&gt;
A part of the wall that the slab sits on is now missing, The BM of the slab and the wall has the same PI of 450. but the wall is still reading the extents of the slab and not the cut section.&lt;BR /&gt;
&lt;BR /&gt;
The only way i can find to remedy this is to convert the slab to a morph (with slab class). &lt;BR /&gt;
&lt;BR /&gt;
Is this the only way to solve this issue?&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://s16.postimg.org/s3g9mlqv9/Screen_Shot_2016_09_08_at_14_14_26.png" target="_blank"&gt;&lt;LINK_TEXT text="https://s16.postimg.org/s3g9mlqv9/Scree ... _14_26.png"&gt;https://s16.postimg.org/s3g9mlqv9/Screen_Shot_2016_09_08_at_14_14_26.png&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://s16.postimg.org/rf7f3ns5h/Screen_Shot_2016_09_08_at_14_16_49.png" target="_blank"&gt;&lt;LINK_TEXT text="https://s16.postimg.org/rf7f3ns5h/Scree ... _16_49.png"&gt;https://s16.postimg.org/rf7f3ns5h/Screen_Shot_2016_09_08_at_14_16_49.png&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 09 May 2023 14:20:27 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227576#M122444</guid>
      <dc:creator>Bobby_ja_tt</dc:creator>
      <dc:date>2023-05-09T14:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: Slab and Wall Intersection Issue</title>
      <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227577#M122445</link>
      <description>Have you tried using a roof set to zero depth for your operator?&lt;BR /&gt;
&lt;BR /&gt;
Cheers,</description>
      <pubDate>Fri, 09 Sep 2016 00:06:50 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227577#M122445</guid>
      <dc:creator>Gerald Hoffman</dc:creator>
      <dc:date>2016-09-09T00:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: Slab and Wall Intersection Issue</title>
      <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227578#M122446</link>
      <description>Hi.&lt;BR /&gt;
Check this wish and the two links to the corresponding threads for explanation.&lt;BR /&gt;
&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?t=49481&amp;amp;sid=132bdc1ba8827d21f75f615afc57f374" target="_blank"&gt;&lt;LINK_TEXT text="http://archicad-talk.graphisoft.com/vie ... 5afc57f374"&gt;http://archicad-talk.graphisoft.com/viewtopic.php?t=49481&amp;amp;sid=132bdc1ba8827d21f75f615afc57f374&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
It's cases like this where "but then" applies when looking for workarounds:&lt;BR /&gt;
1. You could adjust the slab perimeter so it doesn't go above the wall (would depend on the project's design intent) but then you could have wrong slab volumes and the wall might not be shown correctly in a perpendicular section.&lt;BR /&gt;
2. You could use a profiled beam for the tapered part of the slab, but then you'd have to keep track of two distinct elements and clean up the junction in floor plan (a case where I think fills should clean up when two elements have the same BM, like in elevations) and when exporting to IFC, for example, you'd have two elements for a single slab.&lt;BR /&gt;
3. You could solve this if you have the walls that fall under the tapered part of the slab in a different layer with distinct intersection group and then use SEO (between wall and already SEOed slab) to cut out the remaining part of the wall.&lt;BR /&gt;
&lt;BR /&gt;
Best thing would be if PBC would work &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;after&lt;E&gt;&lt;/E&gt; a SEO has been done to a certain element because SEO are element based.... &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;but then&lt;E&gt;&lt;/E&gt; other things might happen.&lt;BR /&gt;
&lt;BR /&gt;
Best regards.</description>
      <pubDate>Fri, 09 Sep 2016 20:05:37 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227578#M122446</guid>
      <dc:creator>sinceV6</dc:creator>
      <dc:date>2016-09-09T20:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: Slab and Wall Intersection Issue</title>
      <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227579#M122447</link>
      <description>I would handle this situation by creating a Morph for the missing part in the Wall and performing an "Addition" SEO with the Wall as Target, the Morph as Operator. This way the missing gap in the Wall will be filled. Also, since the geometry of the Morph body would be added to the Wall geometry, it will be seamless so you will not see any unneeded edges appearing in 3D.&lt;BR /&gt;
In the attached image I selected the Morph I added and you can see that a SEO Addition was performed between it and the Wall.&lt;BR /&gt;
The SEO operators are normally placed on a hidden wireframe layer (so even when the layer is shown the SEO cutting bodies are shown in wireframe).&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/17516i3A3F0EFD5C0B03B6/image-size/large?v=v2&amp;amp;px=999" border="0" alt="SEO-AdditionToFillGeometryCutBySlab.png" title="SEO-AdditionToFillGeometryCutBySlab.png" /&gt;</description>
      <pubDate>Sun, 11 Sep 2016 11:46:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227579#M122447</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2016-09-11T11:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: Slab and Wall Intersection Issue</title>
      <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227580#M122448</link>
      <description>Depending on the geometry of the entire thing, I'd use a complex profile beam. The beam will interact with slabs, walls etc the same way the slab would and having the cross section as an easy to edit fill rather than having to deal with manipulating morphs is, in my opinion, more productive over the course of the project and any changes to come.&lt;BR /&gt;
&lt;BR /&gt;
If it's a tapered shape that appears in many places. but is not consistent throughout the project, it might be faster to manipulate a morph.</description>
      <pubDate>Mon, 12 Sep 2016 09:58:26 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227580#M122448</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2016-09-12T09:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: Slab and Wall Intersection Issue</title>
      <link>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227581#M122449</link>
      <description>&lt;BLOCKQUOTE&gt;sinceV6 wrote:&lt;BR /&gt;...a case where I think fills should clean up when two elements have the same BM, like in elevations) and when exporting to IFC, for example, you'd have two elements for a single slab.&lt;/BLOCKQUOTE&gt;

Oh yes, is there a wish about this? Especially for the floor plan clean-up, you could assign the two elements for an IFC group - that's something.</description>
      <pubDate>Thu, 25 Jan 2018 14:00:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Slab-and-Wall-Intersection-Issue/m-p/227581#M122449</guid>
      <dc:creator>furtonb</dc:creator>
      <dc:date>2018-01-25T14:00:43Z</dc:date>
    </item>
  </channel>
</rss>

