Today I decided to give myself a little break from programming and declare a Blender day – try to dive back into the world of 3D. Every other attempt I’ve ever made at it ended in a frustrated failure after a few hours, but this time I intend to do it differently. Most of all, I’ve decided not to try to go against my programmer’s way of thought, and try to create a heavily script-centric way of work. I hope I’ll have some success.
Unfortunately it was kind of a struggle – Blender scripting documentation is much less impressive than I would’ve expected, and only made worse by the fact that like many things in Blender, it was changed so much in recent versions that many of the tutorials you can find online are close to worthless (hint for anyone looking for one – if you have a new enough version of Blender, ignore any tutorial that references a module called “Blender”. The new version uses module “bpy”). However, after enough searching (this was useful) and experimenting I’m starting to see how it works. No scripting results yet because I do want to learn a little about how things are done manually before I start scripting them, but I think there is room for optimism.
For now it’s just for fun – all my current projects are Isometric, side-view, text-based, or whatever strange idea I had at any time. But learning 3D is, I think, an important investment for the future. Also, a lot of fun (at least when things work).
Results for the first day – I hereby present what was supposed to kind of be the temple of Kukulkan, but went wrong in several magnificent ways:
Tomorrow I’ll be back at programming, but I’m definitely going to go back to 3D once in a while.
 Also, it doesn’t help that I’ve pretty much never seen Python code through a telescope, let alone write any. But it seems like a member of the C family, so it shouldn’t be too difficult.