Newest update crashes when exporting a body as .stl

Newest update crashes when exporting a body as .stl

tonberryhunter
Advocate Advocate
792 Views
7 Replies
Message 1 of 8

Newest update crashes when exporting a body as .stl

tonberryhunter
Advocate
Advocate

Experiencing a new bug since the latest update I haven't seen before in my 3 or so years of Fusion 360.  When exporting a body as .stl for print Fusion crashes with no error message.  Ive exported this same body before the update without issue.

 

Any thoughts?

0 Likes
793 Views
7 Replies
Replies (7)
Message 2 of 8

MoshiurRashid
Advisor
Advisor

Hello,

 

Thank you so much for posting. I found 2 solutions.

1. Export the STL files from a web browser instead of the Fusion 360 desktop client.
2. If that fails, perform a clean uninstall/reinstall:  How to do an automatic clean uninstall for Autodesk Fusion 360

 

Additional: If you want to make it quick, I think you should use the "3D Print" command in the Tools> Make.

I created a screencast video on that. Fusion to Slicer (stl export) | Fusion 360 | Autodesk Knowledge Network

Moshiur Rashid
Autodesk Certified Instructor
ACP | CSWE
https://www.autodesk.com/expert-elite/overview

LINKEDIN | FACEBOOK

0 Likes
Message 3 of 8

tonberryhunter
Advocate
Advocate

Here is another version of the bug now with a simple cube.  The bug seems to be related to Windows Explorer integration with Fusion 360.

 

0 Likes
Message 4 of 8

lance.carocci
Autodesk
Autodesk

@tonberryhunter thanks for the report and video! We are chasing this on a few fronts, but it has been difficult to reproduce.

 

Is there anything notable about the directory or directories last-accessed by Explorer? Any other file types in the folder? Do you have any Explorer extensions, or perhaps a specific app set to handle/open STL files? Would you be able to include a screenshot of the contents of a crash-inducing directory?

 

If possible, please attach a DxDiag report for any affected devices to help us profile this issue.

  1. Press the Windows Key+R for Run
  2. Type DxDiag and press Enter
  3. In the DxDiag window, click Save All Information
  4. Upload the file here
    • Please note - this report contains usernames, which are often based on personally identifying information (i.e. your name). If you prefer, you can edit this out of the text file, or directly message me a hosted link.

I'd also be interested in any unique traits about the directory or folders, e.g. synced/backed up by a cloud storage application e.g. OneDrive, or configured with OS-level features like encryption, file compression, or a different "owner" in the eyes of the Windows system. The contents of the folders may be a clue, too - even if the folders are seemingly random, they might have similar content types, such as something that might generate a [corrupted] thumbnail.

 

We might as well consider the hardware, too - examples include whether the drive is connected in any special way such as USB/Thunderbolt/network, or the make/model/format/configuration of the physical drive itself.

 

The next time the crash happens, check if there is a related entry in the Windows Event Viewer, located in the Start Menu under Windows Administrative Tools, or simply search for Event Viewer. In the left column under Windows Logs are a few category pivots - the two we're most interested in are Application and System - depending on the nature of the error, a timestamped event might be logged related to Fusion 360, or the underlying Windows disk and Explorer process. If you see anything of note, please let us know.


Lance Carocci
Fusion QA for UI Framework/Cloud Workflows, and fervent cat enthusiast
0 Likes
Message 5 of 8

tonberryhunter
Advocate
Advocate

Its not a graphics or disk related bug.  My hardware is completely capable and in working order.  The gpu isnt crashing the program is and no error is generated that I can see aside from Windows based errors on occasion when the crash occurs.  It seems to be a memory related bug.  The program crashes before any icons load in the pop up explorer Window but its also slightly erratic in its behavior timing wise.  There is no file recovery window when the program is restarted either.  Typical crashes prompt a file recovery pop up upon restart.    

0 Likes
Message 6 of 8

Phil.E
Autodesk
Autodesk

Update: A likely cause has been identified. Please help confirm.

 

See message 15 here.





Phil Eichmiller
Software Engineer
Quality Assurance
Autodesk, Inc.


0 Likes
Message 7 of 8

webberen2502
Observer
Observer

OH MY this is annoying...

 i have the same!

0 Likes
Message 8 of 8

Phil.E
Autodesk
Autodesk

A cause has been identified. 

 

See message 15 here.





Phil Eichmiller
Software Engineer
Quality Assurance
Autodesk, Inc.


0 Likes