Think for a moment – how many real scenes you created really with using that default cube?
Not much, right? But all the same, each time starting a clear scene, you press: x – delete. Again. And again. Let’s put on white magician gloves and once for all escape this nonsensical action:
For an effective portfolio demonstration, there is a good practice to show together with the color render the clay render to emphasize scene volume, lighting, models topology, as well as, in the case of photo-realistic rendering, showing scene “3D-essence”. The overlaying of these two renders in the same image could be an even more spectacular trick.
Add-on PartitionRender v.0.0.4 update.
Add-on PartitionRender v.0.0.3 update.
Add-on PartitionRender v. 0.0.2 update.
Blender add-on allowing to interrupt the rendering process and resume it from the interrupted place. For those who are not able to have the powered-on computer for render for a long time.
For example, the whole image render takes 12 hours. And there is no way to have the computer powered on all the time, but it is possible to power it on for 5 hours with breaks. If you interrupt the standard rendering process to turn off the computer – the next time render starts from the beginning, and all progress is lost. PartitionRender add-on allows dividing the image into several blocks – partitions, each of them is rendered separately. Choosing division by X and Y in 2 parts, the image is divided into 4 blocks. Each of them will be rendered about 3 hours that fit in the time to work. Each partition after rendering saves to file. The next time (after rebooting the computer) PartitionRender automatically continues with the partition on which the break occurred. After finishing all partition renders, partitions automatically compile to the whole image in compositing.
Add-on is free and open-source. If you want to support it – you can buy the add-on for a convenient price, or set the price to 0 to download it for free.
To clear compositing window (completely remove all nodes from it), run the following code:
|
1 2 3 4 |
import bpy nodesField = bpy.context.scene.node_tree for currentNode in nodesField.nodes: nodesField.nodes.remove(currentNode) |
In the development of add-ons, their modules should be abstracted as much as possible. For a very simple reason – functional, created for a current add-on, will likely need in the next add-on, and possibly not even in one. In the add-on release, the problem of accessing to such common functionality modules is easily solved – all the necessary modules are included in a single package and distributed together. However, during the add-ons development, such modules are much easier to store separately, in one instance, without associating them with any particular package, and import if necessary the desired modules to the desired add-on.
In accordance with the packages import rules, Python allows to refer modules in the following ways:
Blender add-ons development code reuse with symbolic linksRead More »
Get on Gumroad