Requirements: Blender 4.2 LTS or newer. Scene generation and Cycles renders tested on 4.2 and 5.0.1. EEVEE has not been tested. Uses numpy, which is bundled with Blender. 8 GB RAM recommended.

Quick start (no scripting):

1. Unzip the download.
2. Open the .blend of the system you want (Wolf1061_MHDINT.blend, TauCeti_MHDINT.blend or GJ667C_MHDINT.blend).
3. Press F12 to render the current frame, or Ctrl+F12 to render the animation.

Change the camera: go to the Scripting tab (the script is already open inside the .blend), set ONLY_SWITCH_CAMERA = "c" and press Alt+P. This does not rebuild the scene: it switches the camera and shows the objects that belong to that view. Camera keys: general, inner, top and one key per planet letter (Wolf 1061: b, c, d; Tau Ceti: f, g, h; GJ 667 C: b, c, e, f, g).

Rebuild with your own settings:

1. In the Scripting tab, edit the settings at the top of wolf1061_v1.0.py (or tau_ceti_v1.0.py, gj667c_v1.0.py). The main ones: the duration and speed of the animation, TRUE_SCALE, lighting, RESOLUTION (all with comments in the file).
2. Set ONLY_SWITCH_CAMERA = None and press Alt+P. The scene is rebuilt from scratch.

Read the data: select an object named MHDINT_… and open Object Properties → Custom Properties. Values carry their source and say whether they are measured, computed or illustrative.

Performance: each system rebuilds in a few seconds. At the default 1920×1080 and 128 samples a Cycles frame takes several minutes on a CPU and much less on a GPU; lower the samples for quick drafts.