1. Go to the Releases page and download build_dashboard.exe from the latest release.
2. Copy it into your game's DB folder — the one that contains DB3K_517.db3. On a typical Steam install that's:
...\steamapps\common\Command Modern Operations\DB\
Double-click build_dashboard.exe. It finds the newest database automatically, builds the dashboard (about ten seconds), and opens it in your browser. Done.
That's the whole process — no Python, no command line, nothing to type.
First run: a blue "Windows protected your PC" box may appear. That's SmartScreen being cautious about a new file from an unknown indie author — it is expected here and does not mean anything is wrong. Click More info → Run anyway. If you'd like to confirm the download first, each release includes a build_dashboard.exe.sha256 checksum you can verify.
The generated DB3K_517_dashboard.html is saved right next to the game's database — it's a permanent file, not just a browser view. Keep it in the DB folder (so it can find the unit photos) and double-click that .html, or bookmark it, to reopen any time — you don't need to rebuild. Only re-run the tool when your game database updates.
Want an older database? Double-clicking always builds the newest. To build a specific one instead, drag its .db3 file onto build_dashboard.exe (or, from a terminal, build_dashboard.exe DB3K_515.db3). The dashboard is written next to whichever database you pick.
"Windows protected your PC" on the .exe → expected for an unsigned indie tool; click More info → Run anyway.
https://github.com/twistedpretzel/cmo-db-dashboard
I'd like to provide the full prebuilt html for ease of use, but providing this includes game data from the DB files which violates the EULA, so there is some user effort required to get it up and running.
A single-file, offline HTML dashboard for browsing and analysing the Command: Modern Operations unit database.
You point the included script at the database from your own CMO install and it generates a self-contained .html file you can open in any modern browser.
Every number is extracted from the database. Where a value is a modelled estimate rather than a stored field — notably the RCS-scaled radar detection ranges — the page says so and shows the method, so you can sanity-check it. Treat radar/IR ranges and threat rings as clean-air planning envelopes: they don't account for terrain masking, jamming, or the game engine's full dynamic detection model. Browse all five platform types plus sensors and weapons, with fast search, sortable columns, and rich filters (guidance, features/codes, damage points, target class, sensor capability/band, "carries weapon family", operator, era, and more). One-click CSV export of any filtered list.
Detail pages with type-aware visualisations — radar frequency strips and detection envelopes, optics/IR zoom, sonar depth envelopes, ESM direction-finding, weapon engagement envelopes and warhead breakdowns, per-aspect signatures, propulsion speed-by-altitude curves, and the mounts/magazines/loadouts each platform carries.
Compare up to four platforms, sensors or weapons side by side with overlaid envelopes.
Systems tools: an Electronic Warfare explainer (OECM/DECM), a Detection matchup calculator (at what range does X detect Y, by radar/IR/EO, per aspect), and Threat rings (a platform's search / engagement-radar / SAM envelope, scaled to a chosen target's radar cross-section).
Analysis tools: a Trend explorer (plot any metric against any other), and Leaderboards (top-N by speed, range, stealth, quietness, etc., with a service-era timeline).
- DB Dash 4.jpg (405.37 KiB) Viewed 335 times
- DB Dash 3.jpg (355.77 KiB) Viewed 335 times
- DB Dash 2.jpg (250 KiB) Viewed 335 times
- DB Dash 1.jpg (337.52 KiB) Viewed 335 times
