Continuing the marathon of Blender add-ons this time I’ve prepared an automatic armature generation script using only very roughly hand-assigned vertex groups as hints. You can judge the results of my endeavor by watching the tutorial video below and test the new functionality right away by downloading the script directly to Blender’s scripts/addons directory and enabling it in the Addons config tab. Enjoy!
There’s yet another fine addition to my blender-addons repository on GitHub. The object_place_on_surface.py operator allows to easily place selected object on designated surface (object with the name… surprise, surprise… “surface”) by simply placing the 3D cursor at target location and pressing the P key on the keyboard. Objects are placed with their Z direction aligned to the surface normal. Choices for amount of alignment and whether to use flat or smooth normals are also present. In many instances this is a more convenient alternative to particle systems with density weighting and/or placing object copies by hand. Extremely useful for myself, hope it serves you as well. Enjoy!
Credit: Images in this post use the following hand model authored by DennisH2010 from Blendswap made available under CC-BY-NC license.
You will find a new script in my Blender Addons repository. It’s called lightning_arcs.py and builds on top of the Blender Laplacian Lightning plugin to create configurable arcs of lightning between particles of an object. Three empty objects have to be present in the scene – ELorigin, ELground and ARCheight. The first two are for the Laplacian script, the third one’s Z position determines height of lightning arcs. Furthermore, the Laplacian addon has to be set to generate Single Mesh. Once you add a Particle System to the object of your choice find the “Lightning Arcs” entry using Blender’s Search function (press Space key in scene). Click. Enjoy!
In Blender, having greebles consisting of multiple loose parts can pose a problem when trying to warp them into shape of an arbitrary surface using modifiers such as Curve, Lattice or ShrinkWrap. The result pictured in the back of the scene above shows how loose parts tend to detach from the surface and the final output completely misses the artist’s intent. One solution that I came up with in my projects is to separate the loose parts into individual objects and then merge them together using Boolean Union operator. The addon union_loose_parts.py which you will find in the following repository: https://github.com/sadaszewski/blender-addons does just that and throws triangulation on top of it all. What you’ll usually need to do is apply simple (or Catmull-Clark) surface subdivision and you’ll be in good shape to do the warping. The mesh in front of the scene above illustrates output of such a workflow. Enjoy!
This subject seems to be a recurring question:
As much as I appreciate existing solutions, they do not perform precisely what is requested and therefore can be described rather as workarounds.
What I would like to present in this post is a utility capable of 1) creation of directory tree snapshots in a size-efficient manner, 2) fast comparison of two snapshots revealing files present in only one of them.
This kind of functionality is useful both for tracking of what is going on in your filesystem, as well as (especially if you use command line a lot and/or sometimes tend to lose focus) ensuring that you didn’t accidentally delete any important files. So basically a dream tool for paranoid people like myself who like to exert control over everything 😉
The usage is really straightforward (mind the trailing slashes) and pretty self-explanatory:
python2.7 dirsnap.py --snap /selected/directory/ --out snap1.out.gz ... a few days later ... python2.7 dirsnap.py --snap /selected/directory/ --out snap2.out.gz python2.7 dirsnap.py --compare snap1.out.gz snap2.out.gz
which should normally print to standard output comparison results looking similar to the following:
L /selected/directory/file_only_in_snap1 R /selected/directory/file_only_in_snap2
Where L and R respectively mark file paths found only in the first specified snapshot file and the second specified snapshot file.
There are as well some options allowing not to display Unix-style hidden files and/or limiting depth of search.
If you’re looking to add file date/size comparison, the code is extremely straightforward and consists of only 150 lines. So easy but finally something that does exactly what was needed 😉