Blender addon for remote debugging Blender with VS Code (and Visual Studio)
DO NOT download the addon from here! Use the Clone or Download button.
This is because blender has a problem with the periods in the name from the version number. It used to be you could rename the zip, but this no longer works, you'll get an error when you try to enable the addon. The only fix is to go where the addon was installed and rename the folder there.
Addon will now attempt to find debugpy by using pip show debugpy first.
DO NOT download the addon from here! Use the Clone or Download button.
This is because blender has a problem with the periods in the name from the version number. It used to be you could rename the zip, but this no longer works, you'll get an error when you try to enable the addon. The only fix is to go where the addon was installed and rename the folder there.
Command now takes waitForClient option. See readme for more details.
DO NOT download the addon from here! Use the Clone or Download button.
This is because blender has a problem with the periods in the name from the version number. It used to be you could rename the zip, but this no longer works, you'll get an error when you try to enable the addon. The only fix is to go where the addon was installed and rename the folder there.
DO NOT download it from here! Use the Clone or Download button.
This is because blender has a problem with the periods in the name from the version number. It used to be you could rename the zip, but this no longer works, you'll get an error when you try to enable the addon. The only fix is to go where the addon was installed and rename the folder there.
Mostly just releasing this to confirm 2.9 support.
1.0.0+ all work with both blender 2.8 and 2.9.
Now that blender 2.80 has been released, I have merged the update-to-2.8 branch with master.
If you want to use this addon with 2.79, just download version 0.3.0. Functionality is the same.
The VS Code Python extension (vscode-python) changed their default port from 3000 to 5678 which has caused some connection problems from using the default launch.json configuration it generates. So I have changed the default port accordingly and added the ability to pick it just in case.
If you're new to the addon, it should work out of the box with the default configuration vscode-python creates for Python: Attach / Attach (Remote Debug.
If you've been using the addon for a while, you can either change the port in your launch.json to 5678 or change the addon's port back to 3000.
If you download the add-on from any of the zips attached to a release, please make sure to rename it to blender-debugger-for-vscode-master.zip as the full stops/periods in the version number mess with Blender and will cause the add-on to silently fail installing.
If you download the add-on from any of the zips attached to a release, please make sure to rename it to blender-debugger-for-vscode-master.zip as the full stops/periods in the version number mess with Blender and will cause the add-on to silently fail installing.