I've been working with the SprutCAM demo, and am really struggling with some aspects. If I import a DXF or Alibre part file, it seems to treat them as monolithic entities, and I can find no way to select specific features for operations, as I can with IGES files. What's the trick? I would, ideally, like to work directly from the Alibre models, but that seems, at present, to greatly limit the flexibility in defining toolpaths - it works fine if I let SprutCAM do what it wants to do, but I have limited ability to make it do what I want it to....
The same is true of STL imports.
Did you use the sew command??? Could you post the model and Sprutcam file so we can what your doing.
I don't have Alibre so maybe I shouldn't comment. I use SolidWorks and when I click on the little icon in SolidWorks for SprutCam it exports the model as a iges file and opens SprutCam for me with the model in the work area of SprutCam in model mode. I then select the whole model and "Sew Faces" while still in SprutCam Model Mode as well as locate zero as needed and rotate part as needed. I thought Alibre dose it the same way as SolidWorks... exporting out of Alibre and into SprutCam that is.
All I use is iges files, I guess because I solid model everything I need to machine.
Can you attach a file that gives you problems in SprutCam, all mesh, etc.?
The Alibre file, and the resulting SprutCAM file are attached. This was exported from Alibre using Tools->Add-ons->SprutCAM, though I get the same result loading directly into SprutCAM using File->Import.
I would not try to import a Alibre .prt file into SC. I would export or save as out of Alibre as a iges file and import the iges file into SC.
I also have problems when I try to import a SolidWorks .sldprt file into SC.
I have always just worked with iges files
That's great, IF you have Alibre Pro, but I have Alibre Personal, which does not do IGES export.... Is that really the only option? Seems odd that it will read an Alibre Part file, and properly display it, but can't extract the necessary geometry information? Same goes for STL import. The information is there, and it CAN interpret and display it. Why restrict the functionality?