Issue
Solution
Delete Fusion 360's non-design cache (click here for more info) and restart Fusion 360 and Bommer.
If this does not resolve the issue, you may need to clean out additional local Fusion 360 files, located in:
- On Windows: %LocalAppData%\Autodesk\Autodesk Fusion 360\xxx (where xxx is the letters and numbers of your Autodesk account's unique user id)
- On macOS: ~/Library/Application Support/Autodesk/Autodesk Fusion 360/xxx (where xxx is the letters and numbers of your Autodesk account's unique user id)
In our experience, the W.login folder contains your local design cache and the queue of uploads waiting to be sync'd to the cloud. While we don't recommend deleting this folder outright (to avoid losing any local work) you can stop Fusion 360, move this folder to another location (or rename) it, restart Fusion 360, and then confirm this issue is gone. Then, check to see if any local work is missing and, if not, safely delete the old W.login folder.
Explanation
Fusion 360 caches your design and non-design data; sometimes that cache can become corrupted or can lead to underlying issues that show up when Bommer attempts to access your BOM data. This generally indicates an issue with Fusion 360, with Bommer as the trigger of the crash. Because of this, we can help troubleshoot and gather data or find workarounds but we may need to escalate to Autodesk to fix the real issue.
If you are still having trouble, please contact our support or Autodesk support so we can investigate further. Please remember to submit Autodesk Fusion 360 crash reports and make note of the crash report IDs it gives you.
Comments
0 comments
Please sign in to leave a comment.