I’ve been trying to use Blender since what feels like the dawn of time, but its notoriously opinionated user interface clearly hasn’t stuck, and every time I go back to it I find myself having to re-learn the basics.

Regardless, I go back to it every year or so.


Category Date Link Notes
Models 2020 CC0 Public Domain models an amazing collection of free to use models
Tools 2018 Armory3D A 3D game engine based on Blender
2020 Sofware OpenGL For Windows. Essential if you want to run Blender via RDP
SpaceshipGenerator a procedural spaceshipt generator
BlenderGIS OpenStreetMap plugin for importing textures and 3D terrain meshes
CAD Transform add-on a genius free add-on with multiple snapping options

Notes on network rendering

The canonical way to do network rendering out-of-the box in 2.76–2.79 was to:

  1. Remove objects and lighting from the default scene
  2. Enable the netrender addon in User Preferences...
  3. Select it from the top-level menu
  4. Set mode to Master and set the master parameters in the side panel
  5. Save the file as master.blend
  6. Set mode to Slave and set the slave parameters in the side panel
  7. Save the file as slave.blend

After copying the .blend files to the relevant machines, they should be invoked as such:

# master
blender --background master.blend --addons netrender -a -nojoystick -noaudio

# slaves
blender --background slave.blend --addons netrender -a -nojoystick -noaudio

This is, of course, ridiculous since it bakes the IP address and port of the master into the .blend file, but might be fixable by manipulating the file itself.


  • The 2.76b version that ships with Ubuntu Xenial (16.04 LTS) armhf doesn’t include the netrender add-on for some reason. 2.79 is slated to ship with Bionic (18.04 LTS) armhf, and appears to include the add-on.

This page is referenced in: