Endpoint trim/break problem with MCX

[Don Trust]

Hi all,

 

I've uploaded two files into the MCX files directory at the FTP site.

 

WITHMC.mcx

WITHACAD.mcx

 

Both are simple squares (centered) with a circle attached tangent to the middle of the bottom edge. One created entirely in Autocad 2000, one created entirely in MCX.

 

The one created in Acad was imported into MCX and then the circle and bottom line broken at the intersection of the two.

 

Look at the endpoints of those entities (withacad.mcx). MC reports the endpoints at X Zero, as they should be. The file created in MCX (withmc.mcx)and broken the same way shows the endpoints at X-.0001381.

 

What the heck??? I have been having this problem since ver 8.1. It is driving me nuts. You would think that if the geometry was created in MC, it would be the most accurate way to do it, but noooo, the files created with ACAD and brought into MC breaks at the correct points.

 

Has anyone else run into this??

[kinglouie V]

can't remember if I've had the exact problem but when I import from acad I always end up analizing chains and doing some repair on the geo. Not that it always warrants it, just so I don't have to worry about it one way or the other. Most times if the file is to scale I'll just extrude it anyway to work with.

[Don Trust]

I have found that if you explode any polylines created in Acad, they come in clean into MC.

 

I am having the opposite problem, though. The imported Acad file is better than the MC created one! (when entities are broken at intersection points)

 

Strange

[kinglouie V]

could be just me, I import acad with the solidworks dwg. editor and the inventor autodesk. It's not really like mcdirect just -save copy as, then open in mc. like I said it's just a trust issue with me and acad since thier technology is older (at least in my mind) so I fuss with it more to make myself comfortable with it.