<?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: Columns Vs. Walls in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21182#M10092</link>
    <description>Oreopoulos agree with you 100%. It gets very complicated in the end. &lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Archicad has just to respect those &lt;/BLOCKQUOTE&gt;
Maybe something to keep in mind for the Version 10.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Karl sometime you need software to do it the easy way for you and not build it as you would in reality. &lt;/BLOCKQUOTE&gt;
Yeap, think you dont model your buildning brick by brick.</description>
    <pubDate>Mon, 06 Feb 2006 11:56:47 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2006-02-06T11:56:47Z</dc:date>
    <item>
      <title>Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21174#M10084</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Helo again.&lt;BR /&gt;
Is this possible. I found options on walls vs beams and columns vs. beams.&lt;BR /&gt;
On the picture you can see the corner concreate columns but when rendered they are not shown clearly. Any way to get the right effect, so that the columns are visible, bouth, in shaded and rendered display?&lt;BR /&gt;
&lt;BR /&gt;
Walls Vs. beams. If I have eg. reinforced concreate beam above the door/window opening can I place it without triming the whole wall structure(picture).&lt;BR /&gt;
Many thanxs!&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 25 May 2023 16:19:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21174#M10084</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-25T16:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21175#M10085</link>
      <description>Colums problem&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/15640iB65906F1D462AF1C/image-size/large?v=v2&amp;amp;px=999" border="0" alt="columns.jpg" title="columns.jpg" /&gt;</description>
      <pubDate>Thu, 02 Feb 2006 19:08:44 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21175#M10085</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-02T19:08:44Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21176#M10086</link>
      <description>Beam problem</description>
      <pubDate>Thu, 02 Feb 2006 19:10:45 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21176#M10086</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-02T19:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21177#M10087</link>
      <description>You have your columns, walls and beams all sharing the same physical space.  Can that happen in reality?  No.  Model as in reality, and the drawings and images will be correct.&lt;BR /&gt;
&lt;BR /&gt;
Karl</description>
      <pubDate>Thu, 02 Feb 2006 20:19:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21177#M10087</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2006-02-02T20:19:31Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21178#M10088</link>
      <description>Has crosed my mind. &lt;BR /&gt;
Thouht there was a workaround.</description>
      <pubDate>Thu, 02 Feb 2006 21:16:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21178#M10088</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-02T21:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21179#M10089</link>
      <description>Try to change the layer "Intersection Group Number" in the Layer Settings dialog&lt;BR /&gt;
Check this also &lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?t=9383" target="_blank"&gt;archicad-talk.graphisoft.com/viewtopic.php?t=9383&lt;/A&gt;</description>
      <pubDate>Fri, 03 Feb 2006 21:42:27 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21179#M10089</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-03T21:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21180#M10090</link>
      <description>What you want should be possible in principle, but can be difficult in practice. Beams will automatically penetrate walls, but they have the unfortunate property of subtracting an infinite tube (thus the voids beyond the ends of the beams. &lt;BR /&gt;
&lt;BR /&gt;
There is a similar problem with columns. They will automatically be voided where they intersect with walls. This creates problems when the columns are taller than the walls (a common condition).&lt;BR /&gt;
&lt;BR /&gt;
These problems arise mostly from historical (legacy) issues in the development of ArchiCAD which should be ironed out in due course. In the meantime what you want to do can be accomplished with SEOs, or simply modeled without overlapping as Karl said.</description>
      <pubDate>Sat, 04 Feb 2006 17:49:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21180#M10090</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-04T17:49:02Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21181#M10091</link>
      <description>Karl sometime you need software to do it the easy way for you and not build it as you would in reality.&lt;BR /&gt;
&lt;BR /&gt;
When you have a priority intersection number for each entity, it should "logicaly" do the job. Well sometimes it does, sometimes it does not.&lt;BR /&gt;
&lt;BR /&gt;
This goes for calcualtion issues too. &lt;BR /&gt;
You dont expect a user to do seo bookeeping (which is impossible in the current version) in something so fundamental. In a big building that would mean an enormous amount of time. Not to think what editing may cause to the whole project.&lt;BR /&gt;
&lt;BR /&gt;
I also have the same problem in Sections.&lt;BR /&gt;
I have a wall, and a slab that cuts the wall.&lt;BR /&gt;
I expect the wall to be cut, and to see only the slab hatch. But i see both!.&lt;BR /&gt;
Ofcourse i could cut the wall at the intersection point and make it 2 walls, but this generates unnecessary bookeeping. Every change done at the wall or slab, would result editing in the other 2 newly created parts. Not very smart.&lt;BR /&gt;
&lt;BR /&gt;
So the solution is there (priority intersection numbers).&lt;BR /&gt;
Archicad has just to respect those &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_smile.gif" style="display : inline;" /&gt;&lt;BR /&gt;
And not just beams and collumns and walls. Add slabs too.</description>
      <pubDate>Mon, 06 Feb 2006 08:52:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21181#M10091</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-06T08:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21182#M10092</link>
      <description>Oreopoulos agree with you 100%. It gets very complicated in the end. &lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Archicad has just to respect those &lt;/BLOCKQUOTE&gt;
Maybe something to keep in mind for the Version 10.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Karl sometime you need software to do it the easy way for you and not build it as you would in reality. &lt;/BLOCKQUOTE&gt;
Yeap, think you dont model your buildning brick by brick.</description>
      <pubDate>Mon, 06 Feb 2006 11:56:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21182#M10092</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-06T11:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: Columns Vs. Walls</title>
      <link>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21183#M10093</link>
      <description>&lt;BLOCKQUOTE&gt;dada wrote:&lt;BR /&gt;
Maybe something to keep in mind for the Version 10.
&lt;/BLOCKQUOTE&gt;

Maybe add 2-3 versions.</description>
      <pubDate>Mon, 06 Feb 2006 18:10:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Columns-Vs-Walls/m-p/21183#M10093</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2006-02-06T18:10:51Z</dc:date>
    </item>
  </channel>
</rss>

