v2.0.1 - Wizzo

Download Wizzo-2.0.1-win64.zip below, unzip it anywhere, and run Wizzo.exe. No Python, no install, no console -- the board opens in its own window.

Housekeeping, not features. If 2.0.0 works for you there is nothing here you need, with one exception: the 2.0.0 download was not built from the source the 2.0.0 tag points at.

Why this exists

The v2.0.0 zip was built one commit before a text change landed, so the same version number described two different trees and the packaged board still carried text the source no longer had. That is a small thing that makes a version number useless for telling anyone what they are running. This build comes from the tree its tag points at, and CI verified the packaged executable serves before attaching it.

Also in here

Python 3.10 is now actually tested. The README has said "3.10 or newer" for a while, but CI only ever ran 3.13, which made it an assumption stated as a fact. The test job now runs both ends and both pass.

33 tests, 27 of which need no game installed. The rest probe a real install and skip cleanly when there is not one, which is why a bare checkout still runs a useful subset.

No em-dashes anywhere, enforced by a test that names the offending file and line. They cause real problems in the places this text ends up.

Issue templates and a contributing guide. Most breakage in a project like this is a game patch moving a file the board reads, and that is the one thing I cannot check from my own machine. The templates ask for the sim version, the log and the mission, because without those a report cannot be acted on. The pylon template separates the three cases that look alike from the cockpit: a code with no name, a name with no employment detail, and a name that is simply wrong.

The workflow is off the deprecated Node 20 actions, which GitHub had already been forcing onto a newer runtime and warning about on every run.

Stale internal names. The update check introduced itself to GitHub as bms-kneeboard, and the stylesheet still described itself as a Falcon BMS board when it has covered three sims for some time.

Unchanged

Nothing about what the board reads, shows, or how it places a chart changed in this release. Settings and caches stay in %LOCALAPPDATA%\Wizzo.

v2.0.0 - Wizzo

Download Wizzo-2.0.0-win64.zip below, unzip it anywhere, and run Wizzo.exe. No Python, no install, no console -- the board opens in its own window.

The project was called Mini Kneeboard, and before that BMS Kneeboard. Neither was right any more: it reads Falcon BMS, DCS World and IL-2 Great Battles, and the DCS side is now the deepest of the three. Wizzo is how pilots say WSO -- the one in the back working the charts, the nav and the stores while you fly. That is the job.

What's new since 1.13.1

Pylon codes DCS never explained. A Hornet flying SEAD showed four stations reading {B06DD79A-F21E-4EB9-BD9D-AB3844618C93}. That is an AGM-88C HARM, and the loadout page was useless for the half of the aircraft that mattered.

DCS annotates that code in a comment on the same line, in four files it ships -- AGM-88 on LAU-118 in the Hornet's drag table, LAU-118 + AGM-88 in the Viper's, HARM LAU118 in the Intruder's, AGM-88C in the mission generator's data. Measured across the payload presets DCS ships, DCS's own comments name 86% of the opaque codes the curated library does not cover, and 91% of their placements.

The curated library still wins where it has an entry, because it carries employment detail a comment cannot. Names from the game's files are tagged NAME ONLY. A code with two contradictory comments is left unresolved rather than settled by a coin toss.

An MIT licence, so the project can actually be forked and used.

A test suite -- 32 tests over the terrain projection solver, the .sup5 tile-index record layout, the install-folder verifier and version comparison. 21 need no game installed; the rest skip cleanly.

CI builds the download. GitHub Actions runs the tests, starts the app, builds the zip and checks the packaged executable actually serves before attaching it. The file below was built in the open, not on one machine.

Also

• Screenshots in the README at last
• Python 3.10+ stated, and a note that the board listens on every interface by default (that is what lets a tablet open it) with instructions to bind it to localhost
• .gitattributes, so line endings stop churning across platforms
• pyproject.toml, so pytest works from anywhere in the tree

Upgrading from Mini Kneeboard

Settings and caches move from %LOCALAPPDATA%\Kneeboard to %LOCALAPPDATA%\Wizzo. Nothing is migrated: the caches rebuild themselves on first use, and the only setting worth re-entering is your laser code. The old folder can be deleted.