Serk_237, Are they SolidWorks Drawing files (.SLDDRW) or Part files (.SLDPRT)? As Gorn suggests, V9.1SP2 will read SolidWorks parts from any version of SW. It will not read .SLDDRW files at all. When you bring the IGES file into Mastercam (and can't pick endpts, midpts, etc.), what entities are they? Ue Screen/Statistics if you're not sure. Pete Rimkus ("ProductDevelopmentGuy")

Boolean operations only work on "closed" (some folks call them 'watertight') solids. "Closed" solids enclose a 3D volume. When you stitch surfaces to make a solid, you may or may not get a "closed" solid. If you get an "open" solid, then boolean operations are not allowed. Example.. Make a six-sided block with Create/Surfaces/Next/Primitive/Block. Go to Solids/Next/FromSurfaces, uncheck the 'all surfaces' checkbox, and select only 5 of the blocks sides. The resultant surface is "open". It does not enclose a 3D volume. Now delete that solid, go back to Solids/Next/FromSurfaces, re-check the 'all surfaces' box, and the resultant solid, made with all 6 sides of the block, will be "closed". Clear? Pete Rimkus ("ProductDevelopmentGuy")

Avs_fan, Understood. We're still hoping we can correct it. Pete Rimkus ("ProductDevelopmentGuy")

Use SAT. Explanation: When we attempt to read the DWG file, we're really looking to get to the SAT data imbedded in there. Some methods of storing solids in MDT, most notably as "block references" yield unpredictable results, including crashes. I don't know enough about MDT to know how they get that, but virtually ALL of the problem MDT solid files we've gotten (including those from Avs_Fan) contain this type of entity. Since what we're trying to do is get to the SAT data, by exporting directly to that format from MDT, you're actually DESCREASING your "error-risk". Please note also that DWG files from MDT contain entities that are often non-recognizable to regular old AutoCAD. This is because, even though AutoDesk develops MDT, it's really treated as if it were some random 3rd-party addon. Pete Rimkus ("ProductDevelopmentGuy")

In m_menu.h, there is a SetUnits() function. There are also separate SetUnitsEnglish() and SetUnitMetric() functions.

Tiny, How are you trying to bring the file into Mastercam V6? Are you using File/Convert/IGES/Read. That should work. Don't use File/Get PDG

Mike, That's what I meant too. ("Where did this file come from & what did I do with it last"). We have our ways..... Pete P.S. MMetzinger: you can e-mail the file(s) to [email protected]

MMetzinger, If you don't mind sending the 2 files, I bet I can probably get you some history information. ProductDevelopmentGuy

Skulpter, I'm going to ask you to back up a bit and ask why you feel you need to use surface toolpaths? Why not just 2D contours at different depths using the lines you have? ProductDevelopmentGuy

I see you're in V8. What are the date/time of the M_INIT.OBJ and M_PTRS.OBJ you're using? I think we found a problem in the V8 cycle with this function. ProductDevelopmentGuy

I, for one, have never heard of the .XPX extension. I know for certain it's not a Parasolid format. The .X_T format can support assemblies (i.e. multiple solid bodies) as one as single parts. ProductDevelopmentGuy

Glenn is right - "Squash" became a standard Mastercam function in V9 (Draft too!) PDG

James, You think I'm going to touch this one?!?!?! I may be dumb but I'm not stupid. And I'm not wearin' my flame-proof boxers today. We'll have to talk about this in-house. I'll keep you posted. PDG

Several of us here at CNC worked at one or more of the Gerber companies - they're right down the highway from us. Most of us worked on Gerber Systems Technology's SABRE 5000 - a UNIX-based CAD/CAM product that was sold to a very small customer base. That software is now owned by a company in Germany. The Plotters (and sign making, and apparel design/cutting, and publishing) come from different divisions. And we're loaded with ex-Cadkey people too (they used to be just down the highway too) so we've got lots of man years in this industry!

Or better yet, in V9, go to File/Converters/Next/SaveAsMc8. This will not pass operations (toolpaths) to the MC8 file, but all the geometry will be preserved. PDG

You can use Screen/Next/ToClipboard. It'll copy just the graphics portion of the Mastercam window to the clipboard. Also, it'll let you select two screen points (essentially a 'window') and only copy that portion of the graphics window to the clipboard PDG

If you've got a 3.5 Mb Mastercam file, make sure your 'Database Allocation' under Screen/Config/Allocations is at least 4Mb (or 4000 Kb). That should be the only thing you need to worry about (I'm going to assume your computer has a goodly amount RAM - at least 128Mb). If you want you can Zip up the file and E-Mail it to me ([email protected]) so that I can see if there's anything inherently wrong with the file