When we create a field on the add-on interface panel, the value of which changes something in the node tree, each time the user changes the field value the node tree recompiles. If the user changes the value in that field by holding and moving the mouse, too frequent node tree recompilation will cause Blender to hangs.
This problem can be solved using decorators for deferred updating of the node tree.
This add-on for Blender 2.8 creates a grouping workflow using Blender 2.7 group style. Add-on doesn’t “brokes” the scene, so you can properly work with groups made with this add-on having no add-on installation.
By Michael Soluyanov.
ctrl+g – group selected objects
f9 – manage the group name and origin
tab – enter/exit group edit mode in separate space
With the Blender popularity growing, the number of add-ons created for it by third-party developers is growing too. A lot of high-quality professional add-ons are written for Blender now. Over time, the number of add-ons is becoming more and more. And on this wave aggregators appeared – programs and services independently searching for add-ons and allowing Blender users to install add-ons quickly, many at once, and bypassing add-on distribution channels selected by their authors. What caused a negative reaction of add-on developers.
Two new modes were introduced to work separately, one for materials (easier to use) and the second – for node groups (for advanced shader making). In the “Material” mode, the entire material is stored and loaded. In the “NodeGroups” mode, everything works without changes, a separate node group is saved and loaded for the convinient creating complex shaders.
In the “NodeGroup” mode uploaded node group adds to the current open node group instead of the node tree root as before.
Experimental mode can be enabled/disabled in the add-on preferences.
Nutti, the author of the “fake-bpy-modules” project, has made the installation of the Blender Python API autocomplete modules through the pip platform. Pip installation is faster and easier, but sometimes we just need to copy the autocomplete modules to our project but now they are not included in the Nutti’s GitHub.
When developing add-ons it is often necessary to give an ability to set a number of parameters that affect the whole add-on work to the user. For example, the user can specify a directory for saving/loading files, set some default variables or switch between add-on modes. Of course, the interface for setting such parameters can be placed in the add-on panel, but it is better to place it in a separate add-on preferences panel, which is located in the “Preferences” window under the add-on installation panel.
The main advantage of the add-on preferences is that they don’t reset when Blender restarts. The user does not need to configure the add-on preferences each time, it’s enough to set the necessary parameters once, personalizing the add-on for convenient work.
Let’s create an add-on and define a parameter, placing it in the add-on preferences panel.
In the latest version 2.8 of Blender developers have made many changes in API, so all the scripts and add-ons written for earlier Blender versions (2.7 and below) have stopped working. To run your add-ons in the new Blender 2.8, you need to port them – correct their code to work properly with the new Blender API.
To enable your add-on in Blender 2.80 you have to make the following changes in code:
The add-on branch for Blender 2.7 is fixed on the number 1.5. The master release for Blender 2.8 has the version number 1.6 and higher in future development.
For both add-on versions the same library is used, so all BIS materials are available for all add-on versions, however, please note, materials made for Blender 2.8 may not look correct in Blender 2.7 and backward.
Now the download consists of two archives to install the add-on: