Setup Blender Add-Ons
Update Add-Ons
To learn how to update the core Blender Studio Add-Ons see Update Blender Studio Add-Ons guide.
Modify Update Add-Ons Script
Users can modify the update_addons.py
script to include external add-ons not managed by the Blender Studio.
Example
# Append the follow lines to the end of the `update_addons.py` script.
download_file(
"https://gitlab.com/blender/CloudRig/-/archive/individual_addon/CloudRig-individual_addon.zip",
download_folder_path,
"CloudRig.zip",
)
Manually installing Add-Ons
To manually install Add-Ons without using any scripts, simply drop the .zip file and the shasum256 file of the addon into the projects shared/artifacts/addons
folder. If the zip doesn't already have a shasum file, you can generate it yourself with the shasum256
program. For example, on Linux you can generate it like this:
shasum256 my_test_addon.zip > my_test_addon.zip.sha256
Removing Add-Ons
To remove Add-Ons you are not using anymore, you remove both the Add-On zip file and shasum file from the projects shared/artifacts/addons
folder. Next time you run the run_blender.py
script, it will remove the addon locally.
Package Blender Studio Add-Ons from Source
Blender Add-ons can be packaged directly from the Blender Studio Pipeline repository. Personal Add-Ons can be installed normally.
- Enter Directory
cd ~/data/blender-studio-pipeline/scripts/pipeline-release # Linux/Mac
cd %HOMEPATH%\data\blender-studio-pipeline\scripts\pipeline-release # Windows
- Update Git
# Windows & Linux/Mac
git checkout main # Checkout main branch
git reset --hard # Remove any changes stored in your branch
git pull --rebase origin # Pull to update to latest commit
- Run Package Local Script
./package_local.py ~/data/your_project_name/shared/artifacts/addons # Linux/Mac
python package_local.py %HOMEPATH%\data\your_project_name\shared\artifacts\addons # Windows
Gentoo Users
Flamenco is installed and updated by the package manager of your Gentoo workstation. To learn more see Update Local Add-Ons in the Gentoo section.