Problems Importing native Solidwork files

[Anonymous]

Our company is slowly making a switch from Solidworks to Fusion.  However, I have noticed there are instances of data corruption (intermittent and unpredictable) when I upload a native Solidwork file (2019 SP3.0) into Fusion (this is confirmed not to be a graphic card or appearance issue).  When opening the file in Solidworks, the geometry and faces are without error.

I have attempted to export from Solidworks in the following formats.  Please see the below results:

1.)  parasolid formats (version 31 and earlier):  corrupted

3.)  Solidwork 2019 SP3.0:  corrupted

3.)  igs:  less corruption, however, surfaces are not knitted together

4.)  Step (AP214 and AP203):  no corruption

5.)  SAT:  failed (would not import)

Please see the attached images for reference.

For a temporary solution, I can instruct all of our users to strictly stay with step files, however, this is not a fail-safe, nor permanent solution.  Please advise if this issue has been seen elsewhere and if there are more robust steps to ensure that there is no corruption.

Thank you.

Best Regards,

Dave Blandino

[TheCADWhisperer]

---

@Anonymous wrote:

5.)  SAT:  failed (would not import)

If using ACIS (*.sat) set the export in SolidWorks to ACIS v7.

Can you Attach a native *.sldprt file here that exhibits this behavior when translated?

[Anonymous]

Thank you for your attention to this matter.

I've attached s SW file that will import corrupted into F360.  I had to alter the data due to strict NDA's with our customer.  The ACIS v7 exported file appears to import well.  I've attached that also.  Thank you for the suggestion.  Unfortunately we do not receive SAT files from any of our customers.  We will just have to add this extra step during our data evaluation if the other formats continue to have corruption.

Please let me know if you can provide feedback in regards to the SW corrupted geometry.

Thank you for your assistance.

Best Regards,

Dave Blandino

[TheCADWhisperer]

I would need to see the original feature tree of the SolidWorks file to make any definitive diagnosis, but using another tool I found issues with the geometry.  I suspect the SolidWorks user could refine their modeling techniques.

Even the ACIS *.sat, while it looked identical, returned errors.