<?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: Automatic display of elements on stories in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89274#M46614</link>
    <description>&lt;BLOCKQUOTE&gt;Joeri wrote:&lt;BR /&gt;... it's strange to have disappearing lines of walls / corners / ... when there are faulty connections a few stories above...&lt;/BLOCKQUOTE&gt;

You are right, that is a frustration with them, in fact it was while I was struggling to resolve some of the missing bits of walls from the intersections above that I found the missing polygon wall bug and the alt+click eyedropper bug.&lt;BR /&gt;
&lt;BR /&gt;
It seems to be a bit hit and miss at to whether the wall intersections display correctly for multi-storey elements.  I had some missing triangles from wall intersections on the ground floor even though the wall intersections on the first floor were correct, again this seems to occur only if the wall above has its absolute base height set to within the current story's range.&lt;BR /&gt;
&lt;BR /&gt;
I will add this to the original list if I can.&lt;BR /&gt;
&lt;BR /&gt;
It's a case of 5 steps forward two steps back, understanding what causes the problems at least helps avoid them.</description>
    <pubDate>Fri, 09 Feb 2007 13:55:57 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2007-02-09T13:55:57Z</dc:date>
    <item>
      <title>Automatic display of elements on stories/storeys</title>
      <link>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89272#M46612</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;I am still trying to get my head around using multi-story elements such as walls - that is using the default setting of &lt;FONT color="#336699"&gt;'Show on / Link to stories - Automatic'&lt;/FONT&gt;&lt;BR /&gt;
&lt;BR /&gt;
There seem to be a few weird or unexpected results or am I wrong?
&lt;UL&gt; &lt;LI&gt;The wall is assigned to the story of it's &lt;FONT color="#336699"&gt;bottom reference level / absolute base height &lt;/FONT&gt;&lt;BR /&gt;
(even if it is only 1mm below the current story)&lt;BR /&gt;
&lt;BR /&gt;
If you use the eyedropper/alt-click to load up the parameters of a wall the height of the wall is correctly set, but its &lt;FONT color="#336699"&gt;bottom reference level / absolute base height &lt;/FONT&gt;is as follows:&lt;BR /&gt;
&lt;FONT color="#336699"&gt;the element absolute base height + the height of the current story above the original element's story&lt;/FONT&gt;&lt;BR /&gt;
&lt;BR /&gt;
If you adjust a standard wall's &lt;FONT color="#336699"&gt;absolute base height&lt;/FONT&gt; it will be assigned to the story of it's new &lt;FONT color="#336699"&gt;absolute base height&lt;/FONT&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
If you adjust a polygonal wall's &lt;FONT color="#336699"&gt;absolute base height&lt;/FONT&gt; it will stay assigned to the original story it was assigned to&lt;BR /&gt;
&lt;BR /&gt;
If you then turn off the &lt;FONT color="#336699"&gt;Automatic&lt;/FONT&gt; story display it will then be no longer displayed on the story it relates to on plan, it will be assigned to its original story, but will not be displayed on it because it is above the story cut plane.  It will however still exist in the 3D view.&lt;BR /&gt;
&lt;BR /&gt;
If a wall above (but with it's &lt;FONT color="#336699"&gt;absolute base height&lt;/FONT&gt; within the current story range) intersects with a multi-story wall in a different orientation from a single-story wall on the current storey, the mutistory wall intersects with the wall above not the wall displayed on the current story.&lt;/LI&gt;

 &lt;/UL&gt;
Am I right?&lt;BR /&gt;
&lt;BR /&gt;
The eyedropper/alt-click is a bit of a problem. And the polygonal wall is a bug.&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 08 Feb 2007 17:53:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89272#M46612</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-02-08T17:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic display of elements on stories</title>
      <link>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89273#M46613</link>
      <description>&lt;BLOCKQUOTE&gt;If you use the eyedropper/alt-click to load up the parameters of a wall the height of the wall is correctly set, but its bottom reference level / absolute base height is as follows:  &lt;BR /&gt;
the element absolute base height + the height of the current story above the original element's story&lt;/BLOCKQUOTE&gt; &lt;BR /&gt;
 &lt;BR /&gt;
Exactly what I meant when posting a few days ago... The thing with the eyedropper is a real problem because it's against the basics of ArchiCAD : use the eyedropper to continue working with the same element / &lt;U&gt;&lt;/U&gt;&lt;S&gt;&lt;U&gt;&lt;U&gt;&lt;/U&gt;&lt;/U&gt;&lt;/S&gt;preferences&lt;E&gt;&lt;/E&gt; / etc... &lt;BR /&gt;
 &lt;BR /&gt;
The display issues you quote, I can understand because AC 10 gets more and more intelligent "between" stories, however, it's strange to have disappearing lines of walls / corners / ... when there are faulty connections a few stories above...&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/13134i08AD52F119B2CEE9/image-size/large?v=v2&amp;amp;px=999" border="0" alt="afbeelding_1_932.png" title="afbeelding_1_932.png" /&gt;</description>
      <pubDate>Thu, 08 Feb 2007 19:59:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89273#M46613</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-02-08T19:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic display of elements on stories</title>
      <link>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89274#M46614</link>
      <description>&lt;BLOCKQUOTE&gt;Joeri wrote:&lt;BR /&gt;... it's strange to have disappearing lines of walls / corners / ... when there are faulty connections a few stories above...&lt;/BLOCKQUOTE&gt;

You are right, that is a frustration with them, in fact it was while I was struggling to resolve some of the missing bits of walls from the intersections above that I found the missing polygon wall bug and the alt+click eyedropper bug.&lt;BR /&gt;
&lt;BR /&gt;
It seems to be a bit hit and miss at to whether the wall intersections display correctly for multi-storey elements.  I had some missing triangles from wall intersections on the ground floor even though the wall intersections on the first floor were correct, again this seems to occur only if the wall above has its absolute base height set to within the current story's range.&lt;BR /&gt;
&lt;BR /&gt;
I will add this to the original list if I can.&lt;BR /&gt;
&lt;BR /&gt;
It's a case of 5 steps forward two steps back, understanding what causes the problems at least helps avoid them.</description>
      <pubDate>Fri, 09 Feb 2007 13:55:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Automatic-display-of-elements-on-stories-storeys/m-p/89274#M46614</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-02-09T13:55:57Z</dc:date>
    </item>
  </channel>
</rss>

