<?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 Corner wall junction with different heights causes accessory and schedule issues. in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Corner-wall-junction-with-different-heights-causes-accessory-and/m-p/663049#M14609</link>
    <description>&lt;P&gt;I'm running some scheduling checks on a project of mine and noticed the surface area calculations were coming out incorrectly and I'm trying to work out why. During this process I noticed an anomaly with a wall accessory that seems to happen quite often when walls are different heights and after a manual check, I can see that the surface area calculations are excluding the wall end of the adjacent lower wall for some reason.&amp;nbsp;Both walls are the same composite, have the same external surface and have the same junction order setting - the only difference is the height as one end is raked up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone advise if there is a setting somewhere that I am missing that can clean up this junction so that it just wraps around nicely?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Windows 6020 AUS&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="wall junction.png" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/87049i33FBB15D7AF7AB5B/image-size/large?v=v2&amp;amp;px=999" role="button" title="wall junction.png" alt="wall junction.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 26 May 2025 00:16:08 GMT</pubDate>
    <dc:creator>Liamthanks</dc:creator>
    <dc:date>2025-05-26T00:16:08Z</dc:date>
    <item>
      <title>Corner wall junction with different heights causes accessory and schedule issues.</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Corner-wall-junction-with-different-heights-causes-accessory-and/m-p/663049#M14609</link>
      <description>&lt;P&gt;I'm running some scheduling checks on a project of mine and noticed the surface area calculations were coming out incorrectly and I'm trying to work out why. During this process I noticed an anomaly with a wall accessory that seems to happen quite often when walls are different heights and after a manual check, I can see that the surface area calculations are excluding the wall end of the adjacent lower wall for some reason.&amp;nbsp;Both walls are the same composite, have the same external surface and have the same junction order setting - the only difference is the height as one end is raked up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone advise if there is a setting somewhere that I am missing that can clean up this junction so that it just wraps around nicely?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Windows 6020 AUS&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="wall junction.png" style="width: 999px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/87049i33FBB15D7AF7AB5B/image-size/large?v=v2&amp;amp;px=999" role="button" title="wall junction.png" alt="wall junction.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 00:16:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Corner-wall-junction-with-different-heights-causes-accessory-and/m-p/663049#M14609</guid>
      <dc:creator>Liamthanks</dc:creator>
      <dc:date>2025-05-26T00:16:08Z</dc:date>
    </item>
  </channel>
</rss>

