<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How To Get DWG Solids From Inventor?</title>
	<atom:link href="http://www.deelip.com/Index.php?feed=rss2&#038;p=745" rel="self" type="application/rss+xml" />
	<link>http://www.deelip.com/?p=745</link>
	<description>My Views on the CAD (Computer Aided Design) Software Industry</description>
	<lastBuildDate>Wed, 08 Sep 2010 08:34:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: ob1966</title>
		<link>http://www.deelip.com/?p=745&#038;cpage=1#comment-1823</link>
		<dc:creator>ob1966</dc:creator>
		<pubDate>Tue, 12 Jan 2010 05:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.deelip.com/?p=745#comment-1823</guid>
		<description>Using Inventor .ipt and .iam works just fine (i.e. associatively linked) if you use ACAD-Mechanical with Inventor link. I think that&#039;s what ADSK wants you to use for IV/ACAD interoperability. I&#039;ll let you all speculate as to the reasons why.</description>
		<content:encoded><![CDATA[<p>Using Inventor .ipt and .iam works just fine (i.e. associatively linked) if you use ACAD-Mechanical with Inventor link. I think that&#39;s what ADSK wants you to use for IV/ACAD interoperability. I&#39;ll let you all speculate as to the reasons why.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deelip Menezes</title>
		<link>http://www.deelip.com/?p=745&#038;cpage=1#comment-1494</link>
		<dc:creator>Deelip Menezes</dc:creator>
		<pubDate>Thu, 12 Nov 2009 14:13:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.deelip.com/?p=745#comment-1494</guid>
		<description>Joris,

I have been in this data exchange business long enough to know that most of the noise of interoperability by CAD vendors is only marketing and also serves to hide their real intentions. Proprietary file formats have been, are being and will continue to be used to put users in positions that they ought not be. I believe that this problem can be solved only by legislation and nothing else.</description>
		<content:encoded><![CDATA[<p>Joris,</p>
<p>I have been in this data exchange business long enough to know that most of the noise of interoperability by CAD vendors is only marketing and also serves to hide their real intentions. Proprietary file formats have been, are being and will continue to be used to put users in positions that they ought not be. I believe that this problem can be solved only by legislation and nothing else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deelip Menezes</title>
		<link>http://www.deelip.com/?p=745&#038;cpage=1#comment-1493</link>
		<dc:creator>Deelip Menezes</dc:creator>
		<pubDate>Thu, 12 Nov 2009 14:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.deelip.com/?p=745#comment-1493</guid>
		<description>Norm,

Earlier releases of AutoCAD could import IGES as well. They subsequently moved it to MDT. SYCODE does offer IGES and STEP import plug-ins for AutoCAD. As of now solids in IGES and STEP files are imported into AutoCAD as wireframe only. But we are working on importing them as true 3D solids. We hope to release updates soon.</description>
		<content:encoded><![CDATA[<p>Norm,</p>
<p>Earlier releases of AutoCAD could import IGES as well. They subsequently moved it to MDT. SYCODE does offer IGES and STEP import plug-ins for AutoCAD. As of now solids in IGES and STEP files are imported into AutoCAD as wireframe only. But we are working on importing them as true 3D solids. We hope to release updates soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joris Steurs</title>
		<link>http://www.deelip.com/?p=745&#038;cpage=1#comment-1491</link>
		<dc:creator>Joris Steurs</dc:creator>
		<pubDate>Thu, 12 Nov 2009 13:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.deelip.com/?p=745#comment-1491</guid>
		<description>Feel the same about this, it is possible trough AEC and then only since inv 2010 but the most important is that you can&#039;t bring over the data from the model as well, parameter Iprop, custum prop etc. 
Al this should be convert or even better linked to the attributes and fill up the parts list in ACAD / mech. When autodesk is making big noise about data managenment etc..... start with the beginning I would say</description>
		<content:encoded><![CDATA[<p>Feel the same about this, it is possible trough AEC and then only since inv 2010 but the most important is that you can&#8217;t bring over the data from the model as well, parameter Iprop, custum prop etc.<br />
Al this should be convert or even better linked to the attributes and fill up the parts list in ACAD / mech. When autodesk is making big noise about data managenment etc&#8230;.. start with the beginning I would say</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norm C.</title>
		<link>http://www.deelip.com/?p=745&#038;cpage=1#comment-1490</link>
		<dc:creator>Norm C.</dc:creator>
		<pubDate>Thu, 12 Nov 2009 09:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.deelip.com/?p=745#comment-1490</guid>
		<description>One thing I find odd is you can&#039;t import a STEP file in AutoCAD. It&#039;s only either ACIS or IGES (which is surfaces only, as AutoCAD doesn&#039;t offer automatic conversion to solid like most MCAD packages do).

But you used to be able to open STEP files in Mechanical Desktop, which has finally been discontinued, i.e. no longer provided with Inventor as of v2010...

I guess this is all part of the plan to push people to Inventor. ;-)

(yes, the mention of MDT is a wink to Mr. R. Paul Waddington ;-)</description>
		<content:encoded><![CDATA[<p>One thing I find odd is you can&#8217;t import a STEP file in AutoCAD. It&#8217;s only either ACIS or IGES (which is surfaces only, as AutoCAD doesn&#8217;t offer automatic conversion to solid like most MCAD packages do).</p>
<p>But you used to be able to open STEP files in Mechanical Desktop, which has finally been discontinued, i.e. no longer provided with Inventor as of v2010&#8230;</p>
<p>I guess this is all part of the plan to push people to Inventor. <img src='http://www.deelip.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>(yes, the mention of MDT is a wink to Mr. R. Paul Waddington <img src='http://www.deelip.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R. Paul Waddington</title>
		<link>http://www.deelip.com/?p=745&#038;cpage=1#comment-1489</link>
		<dc:creator>R. Paul Waddington</dc:creator>
		<pubDate>Thu, 12 Nov 2009 00:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.deelip.com/?p=745#comment-1489</guid>
		<description>Beginning at the introduction of Inventor Autodesk has deliberately made it difficult for users to share AutoCAD and Inventor solids.

It has absolutely nothing to do with what can be done, it&#039;s that Autodesk DO NOT want it to happen.  It ALL to do with marketing and nothing to do with what is best for customers.  We regularly NEED to share solid files in both directions and do so several ways - at un-necessary cost.

Autodesk will persist in its stupidity for as long as customers are too lazy to make the noises necessary!</description>
		<content:encoded><![CDATA[<p>Beginning at the introduction of Inventor Autodesk has deliberately made it difficult for users to share AutoCAD and Inventor solids.</p>
<p>It has absolutely nothing to do with what can be done, it&#8217;s that Autodesk DO NOT want it to happen.  It ALL to do with marketing and nothing to do with what is best for customers.  We regularly NEED to share solid files in both directions and do so several ways &#8211; at un-necessary cost.</p>
<p>Autodesk will persist in its stupidity for as long as customers are too lazy to make the noises necessary!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
