BIS (Blender Interplanety Storage) update to v.1.4.1.
- Added “prev” and “next” page button for “pro” accounts.
- “Page” structure changes on the BIS server-side.
Tag: Add-ons
Blender add-on: BIS v. 1.4.0.
BIS (Blender Interplanety Storage) update to v.1.4.0.
- Added “update” functionality for node groups and texts.
BIS – 300
There are more than 300 public materials in the BIS – Blender Interplanety Storage library now.
Blender add-on: BIS v. 1.3.6.
Blender add-on BIS (Blender Interplanety Storage) update to v.1.3.6.
- Fixed some issues with saving Script nodes.
Blender add-on: BIS v. 1.3.5.
Blender add-on BIS (Blender Interplanety Storage) update to v.1.3.5.
- Fixed some issues with nodes from future Blender versions.
BIS – tiling the procedural texture with random rotation along a z-axis
Example of tiling the procedural texture with random z-axis rotation with procedural nodes.
All used nodes are available in the Blender material library BIS.
Blender add-on: BIS v. 1.3.4.
Blender add-on BIS (Blender Interplanety Storage) update to v.1.3.4.
- Checked all compositing nodes, provided proper work with compositing node trees.
BIS: Scene for creating material previews
The Blender scene for creating material previews in the BIS style.
Continue reading “BIS: Scene for creating material previews”
BIS: the Open storage
Materials which owners granted access to them for all other BIS users are placed in the “Open storage” section.
How to share material for all BIS users
Attention! The shared material becomes available to all BIS users. Sharing your materials you agree to their distribution under a Creative Commons license.
- Sign in your account on the BIS website.
- Switch to the “Node Groups (Object)” section.
- For the material you want to share, click the “Share” button.
BIS: saving materials to the storage
The “Personal storage” section of the BIS is used for saving users own materials. Stored in the personal storage materials are accessible only to there owner and no one else.
Saving materials to the BIS:
- Sign in the Blender add-on.
- Make the node tree group.
BIS: How to start
Welcome to “BIS” (Blender Interplanety Storage) – a service for downloading, storing, management and sharing materials for the Blender 3D suite.
Introducing to BIS:
- Create a personal account:
Open the BIS website https://bis.interplanety.org/ in your favorite browser:
Press the “Sign up” button.
Fill in the “Login” and “Password” fields. Please specify an active email address. On the checkbox that confirms your acceptance of the User Agreement.
Blender add-on «BIS» v. 1.3.0.
Blender add-on BIS (Blender Interplanety Storage) update to v.1.3.0.
- Added the “Open storage” section.
Any material stored in the BIS storage is enabled to share by the owner for other BIS users. Shared materials can be used by all BIS users.
Learning loops
In general, the “loop” is usually a sequential selection of several points, edges or polygons of a mesh.
However, there is an element in the mesh structure, which is also called a “loop”. It is a combination of one vertex with one edge of the mesh. Let’s try to learn what these “loops” are for.
Blender add-on «BIS» v. 1.2.0.
Blender add-on BIS (Blender Interplanety Storage) update to v.1.2.0.
- The node group storage divided into three separate node group storages by types: Shader, Compositing, World.
There were some issues with the add-on functionality during the reorganization of the server “BIS” storage engine. Now the add-on is fully functional.
Blender add-on «BIS» v. 1.1.1.
Blender add-on BIS (Blender Interplanety Storage) update to v.1.1.1.
- Added labels to preview images
- Fixed some bugs with “Frame” and “Reroute” nodes
Blender add-on «TimeMe» v. 1.1.2.
Blender add-on “ColorMatching” v. 1.1.
Blender add-on “ColorMatching” v.1.1 update.
- Added:
- Three additional color fans for search: RAL Classic, RAL Design, RAL Effect.
How to pass command line arguments to a Blender python script or add-on
When starting Blender from the console it processes all parameters passed through the command line. However, some scripts and add-ons for proper work may require specifying their unique command line arguments. If you specify such additional parameters in the command line, Blender will also try to process them, which is likely to result in an error. Blender provides a special way to exclude such arguments from own processing.
Continue reading “How to pass command line arguments to a Blender python script or add-on”
Add-on Mesh-Int v.1.1.
Creating radio buttons in the Blender add-ons interface
State switches so-called “radio buttons” are used in the case to limit the choice by one value from several available ones. There are a lot of such buttons in the Blender interface, for example, switching between RGB and BW rendering modes or setting the texture mapping mode. Such buttons can be created in the Blender add-ons interface too.
Let’s create our own radio button switcher.
Continue reading “Creating radio buttons in the Blender add-ons interface”
Add-on TimeMe v.1.1.1
Add-on TimeMe v.1.1.0
How to programmatically check if the operator is registered in Blender API
Single add-on or script can contain several different operators, and not all of them may be registered in the API by the register() function. To verify that the required operator is registered in the Blender API, run the following command:
|
1 |
hasattr(bpy.types, bpy.ops._operator_bl_idname_.idname()) |
Where:
_operator_bl_idname_ – the text value of the bl_idname operator property.
For example for an operator:
|
1 2 3 4 5 6 |
class TestOperator(bpy.types.Operator): bl_idname = 'test.operator' bl_label = 'Test operator' def execute(self, context): pass |
the command will look like this:
|
1 |
hasattr(bpy.types, bpy.ops.test.operator.idname()) |
How to programmatically check if the Blender add-on is registered
To start working every Blender add-on must be registered by setting up the checkbox before add-on name in the User Preferences window – Add-ons page.
To programmatically find out if the required add-on is registered, run the following command:
|
1 |
'add-on_name' in the file bpy.context.user_preferences.addons |
Where:
add-on_name – the name of the add-on file (without the .py extension) or the name of the add-on package, if it was installed from the package.
