<?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: Intersection Priorities in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Intersection-Priorities/m-p/93719#M48992</link>
    <description>&lt;BLOCKQUOTE&gt;Srinivas wrote:&lt;BR /&gt;I created a tapered column with the profiler tool,  my beams were passing through this column. So i want to make sure the intersection priority is made to the column so that my volumes were exact. &lt;/BLOCKQUOTE&gt;

Objects don't automatically clean up to anything, so the intersection priority is not a factor. For the beam to cut your object-column, you need solid element ops. Unfortunately, I don't think object volume is correctly calculated with the object has been cut by SEO.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Srinivas wrote:&lt;BR /&gt;or is it possible to create an intersection priority when i create the same tapered column with the mesh tool? &lt;/BLOCKQUOTE&gt;

Meshes, too, don't respond to intersection priorities, and they are not automatically cut by beams. You would need to do an SEO subtraction there too, but with a mesh, the volume is calculated correctly, considering the subtraction.&lt;BR /&gt;
&lt;BR /&gt;
Best* would be a scripted object that could adapt to various situations without needing SEOs, so the volume could be calculated. For the non-GDL person I would go with the mesh.&lt;BR /&gt;
&lt;BR /&gt;
Probably not what you were hoping for.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_sad.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
*Well, 'best' would be a column tool that tapered, and subtractions that calculated right, etc...</description>
    <pubDate>Fri, 09 Dec 2005 11:41:11 GMT</pubDate>
    <dc:creator>James Murray</dc:creator>
    <dc:date>2005-12-09T11:41:11Z</dc:date>
    <item>
      <title>Intersection Priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/Intersection-Priorities/m-p/93718#M48991</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi Everybody,&lt;BR /&gt;
&lt;BR /&gt;
I created a tapered column with the profiler tool,  my beams were passing through this column. So i want to make sure the intersection priority is made to the column so that my volumes were exact. &lt;BR /&gt;
&lt;BR /&gt;
Is there any way to set the intersection priorities to the custom objects we created or is it possible to create an intersection priority when i create the same tapered column with the mesh tool?&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance.&lt;BR /&gt;
&lt;BR /&gt;
Best Regards,&lt;BR /&gt;
Srinivas.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 25 May 2023 15:15:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Intersection-Priorities/m-p/93718#M48991</guid>
      <dc:creator>Srinivas</dc:creator>
      <dc:date>2023-05-25T15:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: Intersection Priorities</title>
      <link>https://community.graphisoft.com/t5/Modeling/Intersection-Priorities/m-p/93719#M48992</link>
      <description>&lt;BLOCKQUOTE&gt;Srinivas wrote:&lt;BR /&gt;I created a tapered column with the profiler tool,  my beams were passing through this column. So i want to make sure the intersection priority is made to the column so that my volumes were exact. &lt;/BLOCKQUOTE&gt;

Objects don't automatically clean up to anything, so the intersection priority is not a factor. For the beam to cut your object-column, you need solid element ops. Unfortunately, I don't think object volume is correctly calculated with the object has been cut by SEO.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Srinivas wrote:&lt;BR /&gt;or is it possible to create an intersection priority when i create the same tapered column with the mesh tool? &lt;/BLOCKQUOTE&gt;

Meshes, too, don't respond to intersection priorities, and they are not automatically cut by beams. You would need to do an SEO subtraction there too, but with a mesh, the volume is calculated correctly, considering the subtraction.&lt;BR /&gt;
&lt;BR /&gt;
Best* would be a scripted object that could adapt to various situations without needing SEOs, so the volume could be calculated. For the non-GDL person I would go with the mesh.&lt;BR /&gt;
&lt;BR /&gt;
Probably not what you were hoping for.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_sad.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
*Well, 'best' would be a column tool that tapered, and subtractions that calculated right, etc...</description>
      <pubDate>Fri, 09 Dec 2005 11:41:11 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Intersection-Priorities/m-p/93719#M48992</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2005-12-09T11:41:11Z</dc:date>
    </item>
  </channel>
</rss>

