<?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: FeatureCAM API Bounding Box Math Error in FeatureCAM Forum</title>
    <link>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6923768#M7054</link>
    <description>&lt;P&gt;There are no trimmed surfaces.&amp;nbsp;Thanks for asking though.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Mar 2017 15:35:04 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-03-06T15:35:04Z</dc:date>
    <item>
      <title>FeatureCAM API Bounding Box Math Error</title>
      <link>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6919377#M7052</link>
      <description>&lt;P&gt;Having an issue with FeatureCAM's bounding boxes when using the API. We're using the API to import Inventor files with multiple solids (one stock, others to indicate information) and then generate CNC programs to manufacture&amp;nbsp;them.&amp;nbsp;We import them&amp;nbsp;either as a .ipt, or a .sat file. Once imported, we're seeing instances where the bounding box returned for some bodies is incorrect, up to 0.4 - 2.0 mm off over a a distance of around 20-25&amp;nbsp;mm.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else noticed a similar issue with either bounding boxes or other math functions? I'm&amp;nbsp;wondering what the cause is and how to resolve it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2017 17:18:56 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6919377#M7052</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-03T17:18:56Z</dc:date>
    </item>
    <item>
      <title>Re: FeatureCAM API Bounding Box Math Error</title>
      <link>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6920215#M7053</link>
      <description>&lt;P&gt;Just a shot in the dark, are there any trimmed surfaces that the software is seeing as untrimmed?&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2017 22:58:35 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6920215#M7053</guid>
      <dc:creator>jeff.brower</dc:creator>
      <dc:date>2017-03-03T22:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: FeatureCAM API Bounding Box Math Error</title>
      <link>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6923768#M7054</link>
      <description>&lt;P&gt;There are no trimmed surfaces.&amp;nbsp;Thanks for asking though.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2017 15:35:04 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/featurecam-forum/featurecam-api-bounding-box-math-error/m-p/6923768#M7054</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-06T15:35:04Z</dc:date>
    </item>
  </channel>
</rss>

