- Remove clashes with legacy version when linking extension (#210).
- Starting Blender with C and Python debugger.
- Pin Werkzeug library to avoid crash when opening add-ons in user-preferences (#191).
- Make
.blend
files use the Blender icon (#187)
- Linux and MacOS: fixed
blender.executables
not showing when callingBlender: Start
(introduced in #179)
- Add setting to specify to which repository install addons from VS code. Default value is
vscode_development
(#180) - Automatically add Blender executables to quick pick window. Search PATH and typical installation folders (#179)
- If Blender executable does not exist indicate it in quick pick window (#179)
- Support bl_order in auto_load.py (#118)
- Allow user to develop addon even it is placed in directories like (#172)
\4.2\scripts\addons
-> default dir for addons\4.2\extensions\blender_org
-> directory indicated bybpy.context.preferences.extensions.repos
(list of directories)
- Remove duplicate links to development (VSCode) directory (#172)
- Remove broken links in addon and extension dir (#172)
- Updated dependencies. Now oldest supported VS Code version is
1.28.0
- version from September 2018. (#147) - Addon_update operator: Check more precisely which module to delete (#175)
- Formatted all python code with
black -l 120
(#167) - Fix most of the user reported permission denied errors by changing python packages directory (#177):
- Instead of installing to system python interpreter (
.\blender-4.2.0-windows-x64\4.2\python\Lib\site-packages
) - Install to local blender modules
%appdata%\Blender Foundation\Blender\4.2\scripts\modules
(path indicated bybpy.utils.user_resource("SCRIPTS", path="modules")
). - Existing installations will work fine, it is not a breaking change
- Instead of installing to system python interpreter (
- setting
blender.allowModifyExternalPython
is now deprecated (#177)
- Path to addon indicated by
blender.addonFolders
now works correctly for non-system drive (usuallyC:
) on Windows (#147) - Pinned requests to version 2.29 to maintain compatibility with blender 2.80 (#177)
- Find correct python path for blender 2.92 and before (#174). This partly fixes compatibility with blender 2.80.
- "Blender: Run Script" will no longer open read-only file when hitting debug point (#142)
- Initial support for extensions for Blender 4.2.
- New
blender.addon.justMyCode
option. Previously, this was enabled by default and made it more difficult to debug addons that used external libraries. Restart Blender debug session after changing this option.
- Prioritize addon path mappings to make it more likely that the right path is mapped.
- Fixed "Run Script" support for Blender 4.0.
- New
blender.environmentVariables
option. Can be used to define environment variables passed to blender onBlender Start
. - New
blender.additionalArguments
option. Can be used to define additional arguments used when starting blender onBlender Start
.
- Changed scope of
blender.executables
toresource
. The value is firstly looked up in workspace settings before user settings.
- Behavior of scripts that changed context like the active object.
- New
blender.addonFolders
option. Allows to specify absolute or root workspace relative directories where to search for addons. If not specified all workspace folders are searched.
- Update
get-pip.py
. - Use
ensurepip
if available.
- Fix after api breakage.
- Use
debugpy
instead of deprecatedptvsd
.
- Update
auto_load.py
again.
- Update
auto_load.py
to its latest version to support Blender 2.93.
- New
blender.addon.moduleName
setting. It controls the name if the generated symlink into the addon directory. By default, the original addon folder name is used.
- Fix detection for possibly bad addon folder names.
- Addon templates did not contain
version
field inbl_info
.
- New
Blender: Open Scripts Folder
command. - New
CTX
variable that is passed into scripts to make overwriting the context easier. It can be used when calling operators (e.g.bpy.ops.object.join(CTX)
). This will hopefully be replaced as soon as I find a more automatic reliable solution.
- Scripts were debugged in new readonly documents on some platforms.
- Addon package was put in
sys.path
in subprocesses for installation. - Warn user when new addon folder name is not a valid Python module name.
- Path to Blender executable can contain spaces.
- Support for multiple addon templates.
- Addon template with automatic class registration.
- Initial
Blender: New Operator
command.
- Handle path to
.app
file on MacOS correctly (#5). - Better error handling when there is no internet connection.