For full debugging, you’ll have to tab over to the CLI where Blender was launched.

The default workspace includes a Console and an Info Panel that reflects the underlying Python executed by actions taken in the GUI. It’s also worth going into Edit > Preferences > Interface and enabling the Python Tooltips checkbox. Because this will vary with OS, check Blender’s documentation for yours: Launching from the Command Line.įor convenience, all of the screenshots I’m including show the Blender Scripting environment - but any text editor works. Finally, turns out this is a pretty good way to start learning the Blender Python API.įor full access to the debugging output generated in the Python script, launch Blender from the command line. I assume I’m not the only one, but even if that were the case, it would still be worth writing down these notes to help future-Jim.īlender is great for 3D Printing, but configuring the environment each time is tedious - and clicking back and forth between Blender and YouTube trying to remember all of the settings to change wasn’t cutting it. Besides, writing this kind of boilerplate-useful code is 1000% the type of thing I tend to do, then forget how I did.

Time to start changing both those conditions. Writing tutorials is good - and I haven’t been doing it repetitive clicky-draggy thing things are bad, and I’ve been doing it too much.

Blender and 3d printing