Fusion 360 v2.0.12157 crashes when opening files saved in v2.0.11894

[bseibenick]

This morning, one of my computers upgraded Fusion 360 to the latest 2.0.12157 version.  Since that has happened I cannot open some files I have saved yesterday using version 2.0.11894 as Fusion 360 immediately crashes/closes with no crash report window popping up.  I have tried opening previous versions of the files which would have been saved by a version earlier than 2.0.11894.  I am, however, able to open files in 2.0.12157 that were last saved in a version prior to 2.0.11894.  I have tried completely uninstalling Fusion 360 from this computer, using the Fusion 360 cleaner, rebooting, and then re-installing Fusion 360 and that does not allow me to open these files, either.  I tried on another computer that was still running 2.0.11894 and I could still open the files.  I upgraded Fusion 360 on that computer and can no longer open the files as well.  As another test, I downloaded a .f3d from A360 website and imported it into Fusion 360 on a 2.0.12157 computer and Fusion 360 crashes immediately when I try to open that file as well.  Currently I can only open these files from one computer left that is running 2.0.11894.

[RajkumarIlanchelian]

@bseibenick Sent you a PM zoom call link 

[bseibenick]

The meeting number is invalid.

[RajkumarIlanchelian]

@ewing41 We have fixed the issue for @bseibenick by modifying one of his machine's xml file. We have a good idea of what could be happening. 

Until we can find a full fix, can you go to this location and send us your NGlobalOptions.xml -C:\Users\user\AppData\Roaming\Autodesk\Neutron Platform\Options\Your ID\

[bseibenick]

I have to thank Raj for keeping on this and getting the right people involved...thanks so much for getting me back up and running.

Brian

[ewing41]

Here is the file as requested.

[lowbrowroyalty]

I'd love to hear about the solution. Seems I am having the same issue. I cannot open any files with CAM operations. Playing with it a little, it seems to be associated with 2d contour. 

[RajkumarIlanchelian]

@ewing41 Thank you for sharing the xml. We are working to correct this and send you details on how to replace this. 

@lowbrowroyalty Can you please attach your xml file too - 

can you go to this location and send us your NGlobalOptions.xml -C:\Users\user\AppData\Roaming\Autodesk\Neutron Platform\Options\Your ID\

I completely understand these are not the true fixes but we ware working to see how not to get into this state to begin with. 

[ewing41]

Brian was able to help me out using the process that you guys came up with last night.   The Ramp tool path was giving me problems, so that is the line I deleted from the xml and all seems to work now.   I have checked a few of the problem files, and had to reset a few parameter is some of them.  Otherwise, I'm back up and running!   Thanks to everyone who helped us out and again to Brian I really appreciate the help!

[RajkumarIlanchelian]

@ewing41 Glad to know and thanks, Brian.

[lowbrowroyalty]

Hello,

Thank you for looking into it.

I greatly appreciate it.

Best Regards

[tom_bell_autodesk]

@lowbrowroyalty Here's the modified xml. Note that replacing this file will resolve the issue, but your default parameters for 2D Contour will go back to System Default. Just something to be aware of! As Rajkumar mentioned we are looking into handling this better to begin with.

[lowbrowroyalty]

 I just gave it a quick test, seems to have solved the problem. Greatly appreciate your help, time, and solution.

Out of curiosity, what is the problem? Rather, should I be concerned with changing any particular 2d contour defaults moving forward?

Thank you for the great help!

[tom_bell_autodesk]

@lowbrowroyalty The issue seems to be with handling circular dependancies created in the parameter expressions. For example the system default for tool_feedPerTooth references tool_feedCutting, so the problem can happen when modifying the user default for tool_feedCutting to reference back to tool_feedPerTooth. Hope that helps!