- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am suddenly unable to run any of my existing scripts which previously functioned just fine in fusion due to this error. Most forum posts that show this issue are simply because they are not running the script from fusion, or in the vscode instance created by fusion with the debugger. This is not the case for me.
I experienced this issue once before when I found my VS Code editor was automatically updating the python interpreter. I fixed it before by following the steps in this forum post; changing the interpreter and adding adsk.core to path and restarting fusion/vscode.
I now suddenly am getting what I believe is the same problem again, but changing the interpreter and adding the adsk.core path to environment variables has not fixed anything.
I even went so far as to uninstall VS Code, and python, and remove all of the folders with any associated data. I then let fusion install python and vs code and set up the environment from scratch... and I get the same error. I am so confused how starting completely from scratch will not yield a functional setup. I do some coding outside of fusion that requires different python versions and packages so I was hoping to have some kind of profile in vs code with the proper settings that won't be changed when I update my other environments, but I am not sure that is possible with fusion.
Any insight would be very much appreciated. I am at my wits end with trying to figure this one out. I will attach pictures of the errors I am seeing below.
Solved! Go to Solution.