Yet another CAM error

[jesper8W75R]

After having exported a file to EAGLE 9.6 format, and when I click on CAM processor, it refers to the EAGLE file name just exported, instead of what I have open in Fusion.
It gives this error message, and if clicking or anything, Fusion crashes.

The reason the files does not exist, is because I strip off the stupid version number as EAGLE wants both SCH and BRD files to be named the same.

It's interesting, that if you export to EAGLE 9.x, Fusion "processes" the filename and replaces spaces with underscores.
For no reason whatsoever. EAGLE 9 handles spaces in the filenames just fine.
Now, it would have been a LOT more useful if it had instead stripped off the version number.

Aaaand, here we have another bug.
The underscore thing, ONLY happens if you switch from some other file format to EAGLE 9.x format.
NOT if you open the dialog and it's already set to EAGLE 9.x.
This will happen if you, for instance, first save the schematic file, changing from the normally default Fusion Archive Format format to EAGLE 9.x. Underscores will the be added. When you then go to export the board file, it is already set to export to EAGLE 9.x and the underscores will NOT be added.

@jorge_garcia .....???
Do the developers ever test their work?  Or to they just compile and ship?
Quality control on Fusion Electronics is just complete missing the mark.

I have NEVER, EVER seen a professional program crash so often and been riddled with this many bugs in a released version.
I have been in several beta tester groups of programs even bigger and more complex than Fusion, both open and closed source and there never were these constant crashes and errors.
Not only do we have to pay for it, but also spent countless hours with workarounds and reporting bugs.

[jorge_garcia]

Hi @jesper8W75R ,

I wanted to ask, when you got the crash did it give you the option to submit the CER report? I think you always submit them when it shows up but just in case it's important to submit them when ever you can. Support staff can't do much with them but it really helps the developers out since they can track patterns in crashes and figure out root causes faster.

Best Regards,

[jonrbloom]

I have felt for some time that it is Autodesk policy to charge it's users for Pre-Alpha testing on Fusion 360. This has plagued Fusion from the start, when it was just a modelling App. I wasn't paying then, so tried not to complain too much, and it has improved considerably albeit over many years. Drawings were no better at first, although they still feel detached from the main Fusion UI experience. I was late to CAM so haven't been burned too much there.

Electronics has taken it to a whole new level. It isn't even close to Beta quality, let alone production quality. I want it to be good. I am trying really hard to make it work because I am paying for the products other features and do like the underlying philosophy of unification of Modelling/Drawings/CAM/Electronics. But Electronics is shamefully unstable. I get several crashes a day and I only use it in my spare time. Then there's the Library update failures to content with, and yesterday I had to unwind my work when my board went out of sync with the schematic and nothing I did would bring it back into line.

I don't think we should have to keep submitting bug reports. The app is so unstable that AD must know that it is not stable. That AD throws it over the wall anyway and asks us to pay to smoke test it for them, AND then give up more time to put together a proper description in each crash report, or file a Post here suggests that AD have no respect for their customers. I now just click send, in the full knowledge that it goes into the autodelete folder once it reached AD.

AD needs to stop adding new features and consolidate what is already in place. They're concentrating on marketing headlines, instead of existing customers.

Again, I want to like this. I love the modelling and CAM features. Fusion as a whole is a great package. I will go (am going) out of my way and try really hard to make Electronics work for me. But I really do feel this is beyond the pail.

[jesper8W75R]

@jorge_garcia 
For crashes/bugs like this, I always submit a bug report to support, including the number of the crash report.
If any is given. Many times, Fusion crashes without generating a report.

This is suport case ID 19045212,  Crash reports: 323149703 and 323149879
I find it interesting that I submitted these, with just a restart between, so about 2-3 minutes apart I guess.
Looking at the numbers above, globally, Fusion crashed 176 times in that timeframe.
Well, that is the REPORTED times, it probably crashed at least 2-3 times as much, but without generating the report or people not sending it.
Impressive!