Fusion 360 is not launching Visual Studio Code to edit my script

Fusion 360 is not launching Visual Studio Code to edit my script

oafak
Enthusiast Enthusiast
1,186 Views
3 Replies
Message 1 of 4

Fusion 360 is not launching Visual Studio Code to edit my script

oafak
Enthusiast
Enthusiast

I have installed Python from python.org as well as Anaconda. Before installing Anaconda, I had no issues with editing Python scripts containing API calls from within Fusion 360: each attempt at editing automatically called the Visual Studio Code IDE. Running the program was always done in Fusion 360. After installing Anaconda: needed to bring in symbolics, numerics and other useful libraries, I found that Fusion 360 appears not to be able to automatically launch Visual Studio Code any longer. I am still able to edit the code by manually wading through the lengthy path to reach the IDE and edit the scripts, yet I want the quick automation provided by Fusion 360 back! Can anyone help?

0 Likes
1,187 Views
3 Replies
Replies (3)
Message 2 of 4

OceanHydroAU
Collaborator
Collaborator

Ugh - sounds like dependency hell!!  Are you planning to share your script?  If yes - it will not work on anyone else's computer except yours now because they won't have the "other useful libraries" you're using.  You either need to stick to the ones that are included, ask Autodesk to include any good ones you need, or include those libraries yourself in your own script/add-in folders.

0 Likes
Message 3 of 4

oafak
Enthusiast
Enthusiast

@OceanHydroAU,
Thanks for your note and assistance. The problem is solved. From a similar problem addressed here, I did the following:

1. Changed back to Python 3.7.6 instead of 3.8.3 that was installed in Anaconda.

2. Changed the Python extensions from 2020.7.947 to an older version 2019.9.34911 as advised in a response to a similar problem by BrianEkins. Fusion 360 API and Visual Studio Code worked again as expected.

0 Likes
Message 4 of 4

scottmoyse
Mentor
Mentor

For others landing on this thread searching for a solution to this problem. You now need to be using the latest version of the Python Extension in VS Code as per this blog post. https://modthemachine.typepad.com/my_weblog/2020/10/switch-to-latest-vs-code-python-extension.html 


Scott Moyse
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.


EESignature


RevOps Strategy Manager at Toolpath. New Zealand based.

Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project

0 Likes