Does this extension run Blender 3.3 ?

[ACMOIDRE]

Should i need to work 2.90 ? are there any quick work around ? to run blender 3.3

[ACMOIDRE]

OR should i need to install the BETA/development build of blender ?

[M-Scott-Lassiter]

I am actively using the extension now with Blender 3.3.1.

[ACMOIDRE]

Can you Please help me to setup. i'm trying from days no result.

[ACMOIDRE]

when i try to run blender instance this error pop up how can fix it. or any thing I missed ?

[KaijuKoder]

How to migrate blender_vscode to a new Blender version:

Yes, it does run under 3.3 and 3.4. I'm running it now, and have been doing this since 3.0.

However whenever you upgrade Blender to a new major version (e.g. 3.3 to 3.4, but not 3.3.0 to 3.3.1) you need to do a few things to keep Jacques's blender_vscode working on Windows. Part of the problem is Blender doesn't handle symbolic links properly when it copies the addons directory to the new version, and Python has issues with some of the necessary modules.

The symbolic links are really useful. They let us have one copy of our code, instead of a different copy in each version which inevitably results it lost code changes, a real problem with Blender's built in scripting editor.

For example to upgrade from 3.3 to 3.4:

1. Install then start the latest version of blender, choose to keep the 3.3 settings on the splash screen, then quit.

2. Go to "C:\Users\YOURNAME\AppData\Roaming\Blender Foundation\Blender\3.4\scripts\addons

3. OBVIOUSLY DO A BACKUP OF YOUR ADDONS BEFORE YOU DO THIS JUST IN CASE: Replace the addon directories of your own addons (the ones you created using blender_vscode) with symbolic links to the original code directory. Easier to show with an example. Suppose you keep your own addons MYADDON1 MYADDON2 so on in a directory z:\mysrc. From the Administrator-Mode Command Prompt you can do this: del C:\Users\YOURNAME\AppData\Roaming\Blender Foundation\Blender\3.4\scripts\addons\MYADDDON1 mklink /d C:\Users\YOURNAME\AppData\Roaming\Blender Foundation\Blender\3.4\scripts\addons\MYADDDON1 z:\mysrc\MYADDON1 del C:\Users\YOURNAME\AppData\Roaming\Blender Foundation\Blender\3.4\scripts\addons\MYADDDON2 mklink /d C:\Users\YOURNAME\AppData\Roaming\Blender Foundation\Blender\3.4\scripts\addons\MYADDDON2 z:\mysrc\MYADDON2 and so on

4. Install the missing Modules: "c:\Program Files\Blender Foundation\Blender 3.4\3.4\python\bin\python.EXE" -m pip install debugpy click flask

5. There have been some issues with debugpy and Blender's version of Python. If you start Blender from VSCode and it can't start, complaining about debugpy, try this: cd c:\Program Files\Blender Foundation\Blender 3.4\3.4\python\lib\site-packages xcopy "c:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\site-packages\debugpy" debugpy /s /e Copying modules between versions is dubious so this will break eventually. For now though it works.

These work for me, but I really wish the above could be done automatically and we could get the Blender Foundation to take over this Jacque's code.

[clankill3r]

These work for me, but I really wish the above could be done automatically and we could get the Blender Foundation to take over this Jacque's code.

He work's for blender :) But yeah, I get what you mean.