1 Reply Latest reply on Apr 8, 2013 3:00 PM by Jerry Steiger

    Iport export conundrum

    Aaron Tuck

      Hi guys.

       

      I recently convinced my empolyer to shell out for a license of solidworks for use at work. It was under the condition that it interface with their current planning software Pytha, so I did some exports as STL files which pytha can import and they opened fine, so I thought that was that.

       

      Now I have solidworks up and runninng there have been some complaints about the "look" of the STL files. As some of you would know, STL files are composed of triangles, so complex curves come in as hundreds of surfaces and create a lot of visual noise.

       

      I did a bit of research and found that if I save as a ACIS (.sat) file, I can open in draftsight and then save as a 3D DWG/DXF file which this Pytha software can open, however saving as ACIS has it own problems. When I save as ACIS, there are often surfaces missing when I open in draftsight.

       

      A classic example of this is a 3D sweep I used to create the base of my chair. I did get some files to import fine as 3D DWG, but the format needs to be 2004-2006 for Pytha to open them. If I could get consistent clean 3D DWG files, my worries would be over, but I'm not sure if this is possible.

       

      If anyone can help that would be great, but I think maybe the only option is going to be STL until; solidworks adds 3D DXF/DWG as a format.

        • Re: Iport export conundrum
          Jerry Steiger

          Aaron,

           

          Just to make your Monday even more miserable, I have to tell you that I have had more trouble with ACIS exports than any other format.

           

          Since you are exporting to DraftSight, which is emulating AutoCAD, it probably makes sense to set your export options to the last version of ACIS before AutoDesk went off on their own. I have this vague memory that means Version 7.0, but I'm not sure that is right.

           

          Jerry S.