Fusion API and Scripts
Got a new add-in to share? Need something specialized to be scripted? Ask questions or share what you’ve discovered with the community.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Add-in which ran a couple days ago now crashes

Message 1 of 4
980 Views, 3 Replies

Add-in which ran a couple days ago now crashes

Hi all,

I wrote a script to automate creation of some geometry using Custom Events to speed things up. The code worked fine up until last week, but off late, it's been giving me ghost geometry, and some loops cause the whole thing to crash. The report I'm getting is:

Date/Time: 2022-01-28 12:15:15 +11:00
Application: Fusion360.exe
Error: Access violation - code c0000005 (first/second chance not available)
Crashed Module Name: NsGeometry10.dll
Exception Address: 0x00007ffacced7ced
Exception Code: c0000005
Exception Flags: 0


Does anyone know how to deal with this error? There has been news that Fusion has updated to a newer Python version which might cause errors with previous codes. Does this have anything to do with the error I'm getting? Any help would be appreciated! Do let me know if I should post any other information to help find the solution.


Labels (2)
Message 2 of 4
in reply to: manharXEA2X

Hi @manharXEA2X .


The version of Python used by the Fusion360API has not yet been upgraded. (Version 3.7.6)

I was told about it here. 

Perhaps the cause is in another part of the system.

Message 3 of 4
in reply to: manharXEA2X

Yeah, the Fusion 360 Python interpreter is still on v 3.7.6, but they implemented the Add-in interface update, so I thought they might have changed some functionality to work on the new Python version, causing some crashes on v 3.7.6. I'm saying this because Fusion created another Python folder in the "Local" directory yesterday (6783e...).

Message 4 of 4
in reply to: manharXEA2X

Okay, so I found the bug. It seemed to be the "adsk.doEvents()" command which was messing things up for me. Technically, it was supposed to pause the commands in my workflow to execute them in the Fusion 360 workspace, but that was not happening. Instead, it seemed to be re-running the loop in my Event Handler class method. I removed that line because  it wasn't really helping me out anyway, but I'd still like to know the reason for it doing that. Could anyone explain why?

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th

Autodesk Design & Make Report