STEP File Corruption when imported in to SolidWorks

[kevinwatts]

I read half way through a post, that there is a fix in this weekends upgrade (June 20) related to STEP files?

http://forums.autodesk.com/t5/design-and-documentation/notice-june-update-materials-changes-retiring...

“STEP FILE EXPORT PROBLEM thread that the Shanghai team (Jerry and others) are working to solve the Hidden Body problem in STEP file export (from the Parametric Mode). ”

PROBLEM

I just ran in to an error with the exported STEP file that showed up when importing it in to Solid Works at another company. The same components exported as STL files are fine. However some unusual/inconsistent effects showed up in some of the STEP files.

However, when I upload the exported file from my local cpu and then Insert them in to a new/empty default project, they look fine.

Has anyone run in to this or has an idea?

[kevinwatts]

I have also noticed that the applied Apearance material is not retained with STEP files exported from Fusion and then imported back.

It is my understanding that the Fusion translator supports  AP214 when exporting STEP files. Or is that only importing?

[kevinwatts]

Make that both Materials and Appearances are not exported to the STEP file. When importing the STEP file back in to Fusion both applied Materials and Appearances are dropped.

[Phil.E]

Materials and appearance (color only) is preserved for STEP import only, in current Fusion 360.

[kevinwatts]

BODY COMPONENT CORRUPTED ON EXPORT

I have run some new exports using both STEP and IGES and am waiting for feedback.

There seems to be at least two problems: 1) hidden bodies are exported and 2) some surface faces are missing, corrupted or even added. This is not evident in Fusion or when importing the STEP files back into Fusion. However, they do show up when importing into SolidWorks.

I think that the hidden body being exported, as you mentioned, has been resolved with the June update. The file size indicates that. I need to confirm.

Surface faces missing, corrupted or even added is another issue that is the most important! I have asked for screen shots to show what I saw on Friday when importing to Solidworks. I found a post by Claas Kuhnen, with screen shots of what he found regarding this problem.

STEP export bugged
http://forums.autodesk.com/t5/design-and-documentation/step-export-bugged/m-p/5473787#M13253

My export was done from the Browser within Fusion. Notice the missing rear car body faces/panels. The recommended work around suggested is to use IGES files to retain the correct geometry.

AppearanceExport
https://screencast.autodesk.com/Main/Details/c3c25fb3-821d-4d6c-9de3-d335bfdddd40?t=2m22.30000000000...
This last post shows a workaround by applying Appearances to individual faces rather than bodies. This tells me that the data is being retained in the Fusion code but it is not being Mapped correctly in the Export Translator.

[NicolasXu]

Hi Kevin,

Thanks for reaching out.

Regarding the issue of surface faces missing, I just confirmed the case Claas mentioned has been resolved in the June update this Saturday. Would you check your case in the new update and see if it works? If you still see the problem, would you send the file to me (lixiong.xu[AT]autodesk.com) for further investigation?

Best Regards,

[kevinwatts]

Hi Nicolas, Nathan Chandler is working on this under CaseNo:10874370. Export Issues with STEP/IGES from Fusion 360. Native import/export with Fusion 360 does not indicate any issues. Testing with other Autodesk programs (AutoCAD) needs to be done. We are finding less import issues with Solidworks using the SAT files. The Solidworks version and import options which allow automatic import fixing and flags also seems to be an area that creates unnecessary import issues. Regards, Kevin

[kevinwatts]

Phil and Nathan Chandler with Autodesk Support Team have conducted testing with some of my Fusion 360 exported files. Native Autodesk cross product import/export compatibility is very important and seems to work fine. To my understanding this is what we found: STEP & SAT Files Import and Export native to Fusion 360 without problems Import in to AutoCAD from Fusion 360 without problems IMPORTING TO SOLIDWORKS (from files exported from Fusion 360) SAT files import with fewer or no issues/flags STEP files may import fine or may require some editing in Fusion before they can be imported Import problems with SolidWorks seem to be dependant on the version of SolidWorks, patches applied, import options selected, and the complexity of the component being imported. These affect the SolidWorks translator which often tries to automatically repair bodies and details that it senses are or could be a problem. Therefore at the present time I have found it is easier to import SAT files. STEP files may need to be adjusted or details removed and then added within SoldWorks after. I am a Fusion 360 supporter and I appreciate the effort of the support and development teams to improve this design program.

[kevinwatts · Accepted solution]

Phil and Nathan Chandler with Autodesk Support Team have conducted testing with some of my Fusion 360 exported files. Native Autodesk cross product import/export compatibility is very important and seems to work fine.

To my understanding this is what we found:

STEP & SAT Files

• Import and Export native to Fusion 360 without problems
• Import in to AutoCAD from Fusion 360 without problems

IMPORTING TO SOLIDWORKS (from files exported from Fusion 360)

• SAT files import with fewer or no issues/flags
  STEP files may import fine or may require some editing in Fusion before they can be imported
• Import problems with SolidWorks seem to be dependant on the version of SolidWorks, patches applied, import options selected, and the complexity of the component being imported. These affect the SolidWorks translator which often tries to automatically repair bodies and details that it senses are or could be a problem. Therefore at the present time I have found it is easier to import SAT files. STEP files may need to be adjusted or details removed and then added within SoldWorks after.

I am a Fusion 360 supporter and I appreciate the effort of the support and development teams to improve this design program.

[Willa1980]

Hi,

I have very similar issues with all kind of file formats imported to solidworks. The problems with STP files do not only exist in Solidworks, but also in ProE and UG. This makes it currently impossible to start manufacturing my project. This is imho a major issue that autodesk needs to solve somehow...!

https://knowledge.autodesk.com/community/screencast/a98bdd46-0cce-4741-80ae-80478283c745

[Phil.E]

Hi,

Thanks for posting the video.

Couple things come to mind: Is your SWx installation up to date with patches and updates? Does it happen only with modeled threads? What about SAT export from Fusion, is it the same?

Thanks for helping us get to the bottom of this.

Regards,

[PhilProcarioJr]

@Phil.E @Willa1980

Modeled threads export to Solidworks has been broke for a long time I reported this to @jeff_strater and the team fixed it but the fix is being tested and has not been released yet.

I have been told it's coming soon though.

[Phil.E]

Thanks for clearing that up @PhilProcarioJr.

Regards,

[kevinwatts]

Hi Willa1980,

I can appreciate your frustration. My project is also proceeding ahead and exporting files seamlessly for manufacturing by companies that use Solidworks (or other software) is urgently needed!

The problem is not just with the threads. Although, I had to remove all threads from my model in order to eliminate that as a cause of import errors. Sometimes small problems with the physical body that are not easily identifiable have caused problems. Finding and fixing them is also a problem at times.

I have tried exporting various file formats with the same or worse results. I have had other parts “explode,” have error flags or just “fail” to import. I have been able to import to AutoCAD and the parts look fine until they have to be exported/imported in the other software. Importing components to Onshape and then exporting was the only way that I have been able to get my 3D printed prototype made. Even then they did not always import in to Solidworks correctly or without adjustments once imported.

We need some sort of an industry standard that is cross compatible. If Soldworks is trying to create this problem it is not appreciated.

Perhaps Phil or Nathan can suggest where we as Fusion users and supporters can promote this issue in the IdeaStation for attention by the development team.

[PhilProcarioJr]

@kevinwatts

I can assure you the Fusion team takes this very seriously and through my talks with jeff, the export to Solidworks problem should be under control. If you have any models that don't export correctly send them to @jeff_strater and they will get things sorted out.

[jeff_strater]

Thanks, @PhilProcarioJr for the mention.  Yes, we believe that the problem has been fixed.  I am trying to find out now whether this fix will be available in the update going out tomorrow, or whether we missed that train, and it will go out in the subsequent update.

@kevinwatts:  I agree that "We need some sort of an industry standard that is cross compatible".   The irony is that STEP is supposed to be exactly that standard.  However, even with a standard, there seem to be degrees of support.  In the specific problem that Phil reported, the problem was that single spiral face that is the shaft of the bolt, divided by the thread faces.  This, apparently, is  a difficult face to represent cleanly in all modeling kernels, because it is periodic surface (cylinder), but one that is trimmed in a fairly complex way.  While Fusion can understand this kind of surface, it appears that some other CAD systems cannot.  Whether this is a bug in the export (Fusion), or the import (Solidworks) is debatable (and you can imagine what our opinion on that is...).  But, we were able to work around this by splitting up that face on export.

Thanks for reporting this, and keeping us honest.

Jeff

[Willa1980]

Hi,

thanks for the feedback. I just updated solidworks to the latest version, and the error with the stp import still remains. It also exists with sat and iges, but the errors look a bit different. The thread model was just an example, the error occurs on my (complex) model of a product that urgently needs to be processed in china. The export problem is currently delaying the whole project.

Thanks for the tip with onshape, I can import the stp there and export it as parasolid (*.x_t). This is the only file format that imports correctly to solidworks, all other file formats fail with different kinds of import errors.

Please tell us when we can expect a solution to this - thanks!

[PhilProcarioJr]

@Willa1980

Whenever you are sending files to someone using Solidworks, and you yourself are not using Solidworks, always try to send Parasolid files. I know Fusion doesn't create those but that is the best non-native format for Solidworks.

[jeff_strater]

I followed up with the translator team.  Unfortunately, the workaround to this problem did not go out in the recent update (Oct 5).  When making changes like this, we have to be very careful that we don't break anything else, so the change has to percolate through the system a bit.  It is planned for the next update, in early November.  I apologize for the delay, we'd all like to get this in place, but hope that everyone understands our need to be as careful as possible.

Jeff

[kevinwatts]

Thank you for the update Jeff. This is very much appreciated!

Regards,

Kevin