Getting Started

This page covers the basic setup path for the Battlezone Blender Toolkit.

Install

Blender 4.5 LTS is the primary target.
Blender 5.1 is supported for the main import/export workflows.
The optional native Ogre fast path is available on Windows Blender 4.5.x. Blender 5.1 falls back to XML conversion until a Python 3.13 native backend is available.

File > Import: import legacy .geo, .vdf, .sdf, and Redux .mesh workflows.
File > Export: export legacy geometry, legacy vehicle/structure data, or Redux mesh output.
Scene Properties > Battlezone: model metadata, validation, animation entries, collision helpers, export settings, ZFS explorer, and reference popups.
3D View > Battlezone: selected GEO tools, cockpit tools, organic Redux skin tools, animation tools, and map tools.

Import or build a legacy GEO hierarchy, validate it, then export .vdf or .sdf.
Import stock or stock-derived models with Auto-load .map textures, optionally using a texture folder or stock ZFS archive for missing stock textures.
Export legacy plus Redux files when you want Redux .mesh/.skeleton/.material generated from the legacy control hierarchy.
Use Redux Mesh Only when you already have a Redux-oriented mesh/skeleton workflow.
Use map tools for .HG2 terrain import/export, path points, and terrain texture painting.

If Blender is already running, installing a new zip may not reload all Python modules immediately. After updating:

Disable and re-enable the addon, or restart Blender.
Confirm the addon version in Blender preferences.
If testing a local development copy, make sure the AppData addon folder matches the repository copy you expect.