Requirements
- Windows, MacOS or Linux
- Blender 3.6 LTS, 4.1 Stable
Experimental Builds
Experimental Blender builds such as 4.2-alpha are not supported, and fixing any issues related to them, will not be a priority, but reporting them is still encouraged.
Custom Builds
Custom Blender builds such as OctaneRender for Blender may not support all of Blender's native shader nodes.
DECALmachine only relies on native Blender nodes and is not at fault for any issues resulting from using custom builds.
Blender on MacOS
MacOS users should install Blender properly, by following the official instructions.
Avoid running it just from the Downloads folder!
Note that, for dragging of files and folders, you need to hold down the COMMAND key.
This will ensure AppTranslocation1 is avoided.
Blender on Arch Linux
Arch Linux users and users of other Arch based or similar rolling release distros are advised to use the official Blender builds.
The Blender package in the Community repository does not supply its own Python, and does not follow official recommendations.
As a consequence, the system's python version may not work with DECALmachine.
Latest DECALmachine
The latest version of DECALmachine is 2.11.2 - available on Gumroad and Blender Market.
See this page to learn what's new in the latest versions, or see the changelog for the full, detailed release history.
Installation
1. Fresh Installation
NO previous version of DECALmachine installed
2. Update Installation
previous version of DECALmachine installed already
Attention
The video below applies to updating from DECALmachine 2.11 (or later).
If you are updating from an earlier version of DECALmachine, that doesn't have the Integrated Updater yet, please see these legacy update instructions.
Post-Installation
PIL/Pillow
For more advanced usage of DECALmachine, a python module called PIL/Pillow is required.
PIL enables DECALmachine to manipulate images, and so is required for Decal and Trim Sheet Creation, as well as for Atlasing and Baking.
Installation has been automated and is covered below. Some additional information can be found the FAQs.
Keep in mind
If you use DECALmachine 2.11.2 in Blender 4.0+, you will need PIL to update the supplied example assets.
Move Assets Location
After a fresh Installation, when unfolding the addon preferences, you will always be greeted with this message, asking you to move your assets location elsewhere, and out of the DECALmachine addon folder.
I highly recommend you follow this advice, and when you do so, pay attention to the Move toggle.
If this is the first time you are going to use an outside assets location for DECALmachine, you should set the Move toggle to True. With it enabled, all assets from the current location will be moved to the new location, as you change the assets path.
If on the other hand you have used DECALmachine before and have a previous asset location for it setup already somewhere, or if you use a shared assets location as part of a team, you should disable this toggle before you change the assets location.
Update Legacy Assets
Depending on the Blender version you are using with DECALmachine, an update even of the supplied example assets may be required. This is currently the case when using DECALmachine 2.9+ in Blender 4, but not when using the same version of DECALmachine in Blender 3.6.
A Batch Updater message like this - or similar - may show in the DECALmachine addon preferences
This will also be the case for any assets you have created previously, and it may also be the case for any 3rd party decal libraries, that you may want to import and use.
The reason for this is, that every time Blender introduces changes to materials with an update, in particular to the Principled BSDF shader node, DECALmachine will try to make use of any new shader inputs, so they are properly supported for Material Matching. In addition to new shader inputs, Blender 4 also introduced foldable panels on shaders and node groups, and DECALmachine 2.9+ makes full use of these in its decal- or trimsheet node groups.
Decal Node Groups with panels in Blender 4
Changes like these will require an update of all previously saved decal assets and libraries, and also an update of all .blend files, that still use these legacy assets.
At least if you want to continue to work on them - they should still render and display fine even without being updated.
The two tools used for this are: UpdateDecalLibrary and UpdateBlendFiles.
In addition and for convenience there is a BatchUpdater, that iteratively calls the UpdateDecalLibrary tool for each legacy decal or trimsheet libraries in your chosen assets location.
This is what's shown above in the screenshot, exposing the Update and Fix Them All button.
Issues with Assets
Go to the next page covering the addon preferences, to learn more about dealing with failed asset registrations.
-
Learn more about AppTranslocation on MacOS. ↩