Model export to STL repeatedly fails

[Anonymous]

Attempting to export a model to STL and it repeatedly fails.  Error message just says max attempts tried.  However, other models successfully export to STL before and after this one, repeatedly.  Support offers useless options like restart computer, restart fusion, etc, all of which did not help.  This appears to be a software related issue.  Is there a model size/complexity limit that they are not telling me?  

[wmhazzard]

I make a lot of models for 3d printing and I have never exported to STL. I always right click on the body and select save as STL and save it to my computer. It takes all of 10 seconds total to do and there are more options when saving as STL. Forget exporting and get less stress.  

[Anonymous]

While your solution works in theory, I now get an STL model the size of a pen cap , which is just as useless as the export feature (which fails only on this model) currently is... 

I just don't understand how a company can market a software package which is as flawed as Microsoft's garbage is.  Something as simple as correctly scaling imported, exported, or converted models is a no brainer, but then again, if I import a SVG to get a baseline, I have to upscale 3.78 times.  This is 2020, I shouldn't have to deal with stupid coding oversights like this.

[wmhazzard]

My theory works in practice for me every time with no problems.

It is not a coding oversight, STL's are unitless, a one inch cube is just the numbers 1 by 1 by 1 in an STl, no unit of measure. When you import an STL, Fusion assumes the file is in cm, most slicers assume mm. That means if you are saving as an STL, you have to save the file in mm. 

[Anonymous]

Yes, while that may be true, EVERY other model I have exported to STL using cloud services has not had a scaling issue, however, this ONE model (that fails cloud services), that I have to internally "save as", has a significant scaling issue utilizing a similar "point and click" command.  So, there IS a coding issue after all.....   

[TheCADWhisperer]

Can you File>Export your *.f3d file to your local drive and then Attach it here to a Reply?

This will be an easy one to solve.

[Phil.E]

Agreed. There is probably a coding issue that is exposed by your one model. When a bug is experienced in one model out of many, it could be geometry or some kind of corruption, or just a case that is not expected for the translation engine. So to say "coding" means only that the code doesn't handle this case (or cases like it) for some reason.

If you share the model it will help us figure out what error state or geometry combination that case this represents and then try to support it.