<?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 Complex Profile vs. SEO in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Complex-Profile-vs-SEO/m-p/175416#M95078</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Is there a consensus on using complex profiles over seo'ing slabs/walls ect...?&lt;BR /&gt;
I am wondering for stairs which would be more efficient in terms of model size and complexity.  Thoughts?  Thanks for the input!&lt;BR /&gt;
-Chris&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 24 May 2023 10:55:30 GMT</pubDate>
    <dc:creator>Chris Grantham</dc:creator>
    <dc:date>2023-05-24T10:55:30Z</dc:date>
    <item>
      <title>Complex Profile vs. SEO</title>
      <link>https://community.graphisoft.com/t5/Modeling/Complex-Profile-vs-SEO/m-p/175416#M95078</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Is there a consensus on using complex profiles over seo'ing slabs/walls ect...?&lt;BR /&gt;
I am wondering for stairs which would be more efficient in terms of model size and complexity.  Thoughts?  Thanks for the input!&lt;BR /&gt;
-Chris&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 10:55:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Complex-Profile-vs-SEO/m-p/175416#M95078</guid>
      <dc:creator>Chris Grantham</dc:creator>
      <dc:date>2023-05-24T10:55:30Z</dc:date>
    </item>
  </channel>
</rss>

