AWS deadline-cloud: Add Blender 5.2 support and rename add-ons section
Summary
Adds Blender 5.2 to the version/conda support tables, renames the 'Blender add-ons' heading to 'Use custom Blender add-ons', and adds guidance on distributing custom add-ons via Deadline Cloud plugin sync from the queue's job attachments bucket in addition to conda packages.
Security assessment
Content is product-version support and add-on distribution workflow guidance; the added text documents plugin sync from the job attachments bucket but introduces no new security controls, permission guidance, or vulnerability information.
Evidence
+## Use custom Blender add-ons
Diff
diff --git a/deadline-cloud/latest/userguide/blender.md b/deadline-cloud/latest/userguide/blender.md index 84fbe558b..3e5298f31 100644 --- a//deadline-cloud/latest/userguide/blender.md +++ b//deadline-cloud/latest/userguide/blender.md @@ -7 +7 @@ -Support overviewBlender version compatibilityDeadline Cloud Conda ChannelGetting startedInstallationUsing the Blender submitterAdvanced configurationsBlender add-onsBlender render enginesOpen source resources +Support overviewBlender version compatibilityDeadline Cloud Conda ChannelGetting startedInstallationUsing the Blender submitterAdvanced configurationsUse custom Blender add-onsBlender render enginesOpen source resources @@ -38,0 +39 @@ Major Version | Submitter Support | Conda Support | Render Engines +5.2 | Windows, macOS, Linux | Linux | Cycles, Eevee, Workbench @@ -50,0 +52 @@ Linux | blender | 5.1 | Includes all built-in render engines +Linux | blender | 5.2 | Includes all built-in render engines @@ -246 +248 @@ If you require an unsupported version of Blender, you have the following options -## Blender add-ons +## Use custom Blender add-ons @@ -248 +250,3 @@ If you require an unsupported version of Blender, you have the following options -You can make Blender add-ons available on service-managed fleet workers by building a conda package from a conda recipe and adding it to a custom conda channel. When the conda environment activates on a worker, the add-on is installed through Blender's API; when it deactivates, the add-on is removed. For more information about custom conda channels, see [Creating custom conda channels](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/configure-jobs-s3-channel.html). +You can make custom Blender add-ons available with Deadline Cloud plugin sync or a conda package. Plugin sync copies an add-on from your queue's job attachments bucket when the worker session starts. For setup options, see [Use custom plugins with Deadline Cloud](./custom-plugins.html). + +For add-ons that require installation steps or dependency resolution, build a conda package from a conda recipe and add it to a custom conda channel. When the conda environment activates on a worker, the package installs the add-on through Blender's API. When the environment deactivates, it removes the add-on. For more information, see [Create a conda channel using S3](https://docs.aws.amazon.com/deadline-cloud/latest/developerguide/configure-jobs-s3-channel.html) in the _Deadline Cloud Developer Guide_.