Why you need to pay for an add-on
It’s simple. When paying for the add-on, you are not paying for the add-on you are buying. This add-on is already written. The developer has already spent his time and strength on it. About this particular add-on – there is completely no difference will it be paid or not. So, why to pay? You pay for the future. You pay for the add-ons that the developer writes now and will write in the future. If the addon is bought, the developer has the opportunity to continue development. If not, he will do something else, and you will not receive new add-ons, as well as enhancement and porting to future platforms existed. When paying for an add-on, you provide, first of all – for yourself, the opportunity to receive new add-ons and technical support for the old ones. Pay for add-ons and donate for free – this will benefit yourself!
Assigning custom properties to vertexes
Working with mesh geometry, it may be necessary to assign each vertex some custom properties or data that must be written to the blend-file when saved, and which must be accessed later.
However, an attempt to assign the necessary data to the vertexes through the creation of custom properties fails. Instead of the custom vertex property, only a tuple with reference to the type of the property is created.
How to split and join Blender interface windows thruough the python API
A set of operators is provided in Blender for manipulating with the location of its interface windows.
To split the current window (using the current context) into two in a specified ratio, we need to execute the following operator:
1 |
bpy.ops.screen.area_split(direction='VERTICAL', factor=0.5) |
With:
- direction – set the splitting direction (‘HORIZONTAL’ or ‘VERTICAL’)
- factor – percentage ratio of splitting windows
How to split and join Blender interface windows thruough the python APIRead More »
How to save mesh data to text
Sometimes it is necessary to save data for creating a mesh (its vertices and polygon indices arrays) to text, for example, for further use in a script or addon.
We can export the mesh to one of the open formats, for example, to *.obj, but if we need only its vertexes and polygons data, we can use the following simple script:
Custom property
The Blender API provides a set of simple property types described in bpy.props (IntProperty, BoolProperty, etc.). But the basic types are not always enough, sometimes we need more complex ones. The Blender API allows to group simple properties to make complex properties.
Let’s consider such complex property creation and make the 3×3 matrix property as an example.
How to get current Blender version number through the Python API
To get current Blender version number through the Python API we need to execute the following command:
1 2 3 |
bpy.app.version # (2, 81, 16) |
or
1 2 3 |
bpy.app.version_string # '2.81 (sub 16)' |
How to get current Blender version number through the Python APIRead More »
Blender add-on: Wire (for 2.8x) v.1.1.0
Blender add-on Wire (для 2.8x) updated to version 1.1.0.
- Fixed bug with the enabled “Filmic” color correction and color wireframe.