Offline CMO Database Viewer — v1.3.0 — Scenario ORBAT, satellites & ASAT, attributes glossary, DBID search

[Parel803]

For the record, yes I was really trying to help. If my text was rude in any way I do apologize as it was in no was my intention to offend anyone.
Love the tool and be sure to use it in future endeavours.
regards GJ

[thewood1]

For the record, yes I was really trying to help. If my text was rude in any way I do apologize as it was in no was my intention to offend anyone.
Love the tool and be sure to use it in future endeavours.
regards GJ

It absolutely was not you. It was the "I can read" comment that seemed rather snippy to someone going well out of his way to help.

[Blast33]

Oh this is nice!

Tnx so helpful

[Twistedpretzel]

If you're like me you've come across numerous features in-game that either you have no idea what it does or maybe you're confident with your understanding, but uncertain with how it is implemented within CMO.

Update — v1.1.0: Feature & Guidance Glossary

New in this version: a built-in reference that explains what every sensor capability, feature code, and weapon-guidance method actually means and does in game.

• 251 terms described — guidance methods, sensor capabilities & modes, sensor types, weapon codes, target classes, and weapon types.
• Hover any feature chip on a sensor or weapon page for a plain-language explanation; click it to open the full write-up on the new Feature Glossary page.
• Searchable — filter by keyword (LPI, illumination, wake, TERCOM…), see how many items use each term, and jump to that list.
• Guidance methods spell out what each needs and does — e.g. SARH needs the shooter to keep illuminating the target and can't do anything else while guiding; laser-guided needs a designator with line of sight; active-radar is fire-and-forget.
• Write-ups are paraphrased from the in-game manual where it covers a term (page-cited) and tagged OBSERVED / INFERRED / SPECULATIVE so you can judge how firm each is.
• Works for both DB3K and Cold War (CWDB) databases.

Get it: grab the latest build_dashboard.exe from the Releases page, drop it in your game's DB folder, and double-click. Note: the glossary is part of the generated dashboard, so you need to re-generate (run the new .exe once) — a dashboard you made with an older version won't update on its own.

Releases: https://github.com/twistedpretzel/cmo-d ... d/releases

[thewood1]

Thats a great tool. Thanks for the effort on it.

[BrianinMinnie]

Man you guys are on it, thanks for this!

[JFS737]

Incredible. I've often wished for context and info like this. Thank you very much again! What a great asset you've produced.

[Knightpawn]

Amazing. Thank you

[serjames]

It is a brilliant tool....

[Twistedpretzel]

Question for the group, I've noticed the radar tracking and resolution specs show "Height Resolution" with a fixed number, such as "320 meters" for the AN/SPY-6(V)4. Shouldn't the height resolution also be an angular error tolerance, as implemented for bearing error? (Coincidentally called "Angular resolution"). The way it reads to me, all radars have a fixed number elevation error from max detection to min detection. If it were an angular error, as implemented for bearing, then it would scale based on distance which makes sense to me for radars. Does anyone know more about how height resolution is implemented?

[Twistedpretzel]

v1.2.0 — "What's new" changelog

The dashboard can now show you exactly what changed between two database
versions. Keep your previous DB3K (or CWDB) in the DB folder and the tool
builds a What's new page automatically:

• Units, weapons and sensors added, deprecated or removed
• The exact stats that changed on existing entries — ranges, Pk, service dates, cost, and more
• Component changes: mounts, sensors and loadouts per platform; sensor capabilities; weapon guidance, targets and warheads
• Filter by name, hide minor data tweaks, and click through to any entry

How to use it (no Python):

1. Grab build_dashboard.exe from the Releases page and drop it in your game's DB folder.
2. Double-click it — the dashboard opens with a What's new page comparing the newest database against the one before it.

It also works if you drag a specific .db3 onto the exe: it builds
that database and compares it against the next-older one in the folder.

Everything is offline: the comparison is between the two files on your
disk, nothing is fetched from anywhere. If you'd rather build just the one
dashboard with no changelog, run it from a command prompt with
--no-changelog.


https://github.com/twistedpretzel/cmo-d ... ses/latest


As always this is a fan-made tool that ships no game data — you build the
dashboard from the database in your own copy of the game. Repo + full
feature glossary on GitHub.

Dash v1.2.0.jpg (461.69 KiB) Viewed 124 times

[thewood1]

Boy...the more I play with this the more amazing it seems. Thanks.

One feature request: In the sensor graphical display of a unit, allow clicking on a ring or sensor to isolate or at least highlight that sensor's ring. Maybe a check list of the sensors and checking a box shows that sensor's ring and any other sensors checked off. Allows a cleaner look at individual sensors.

One other suggestion is in areas where a lot of units are shown, like in "Used by" areas, use a scrollable list. Just seems cleaner to me. Also can use less real estate.

[Twistedpretzel]

v1.3.0 — Scenario ORBAT, satellites & ASAT, attributes glossary, DBID search

Scenario ORBAT (new). Ingest a snapshot of any scenario and browse its full order of battle inside the dashboard. Open Editor ▸ Lua Script Console, paste the one-click export script shown on the new Load scenario page, run it, and paste the output back in. (Parel803)

• Grouped Side → Task group → Platform type, sides collapsed on open (no spoilers).
• Aggregated by type ("12× F/A-18E"), expandable to loadouts and tail numbers.
• A rolled-up Airborne picture, a per-side Force summary, and live status / loadout / fuel / readiness.
• Aggregated ordnance — each group totals its magazines by weapon type (e.g. "142× UGM-109E Tomahawk Blk IV TACTOM") and expands to the count each hull carries.
• Loadouts link to the exact fit; everything deep-links to the catalog.

Satellites & anti-satellite engagement (new). Satellites are now a full platform type with orbital elements. Each satellite card shows which ASAT weapons in the database can reach that orbit (by altitude ceiling and range) and a ground-footprint diagram of where each could engage from.

Attributes glossary (expanded). The Feature glossary now also covers platform attributes (armor, ergonomics with OODA modifiers, autonomy with signal-loss behaviour, cockpit visibility), the comms model, and all 130 platform feature codes — 557 entries total. Attributes, codes and comms on a unit card link to their glossary entry; weapon cards show their datalink.

Search by DBID. Type a database ID (e.g. 7733) in the search box or any list to jump straight to that entity. (Parel803)

Also: per-sensor ring isolation on the coverage diagram; fixed aircraft at multi-facility airbases showing under "Independent" instead of the airfield. (thewood1)

As always: Download build_dashboard.exe from the GitHub Releases page, drop it in your DB folder, double-click. Thanks to everyone who sent feedback — DBID search, the weapon-modifier/attribute reference, and sensor-ring isolation all came from this thread.

Scen ORBAT.jpg (313.21 KiB) Viewed 86 times

Scen ORBAT 2.jpg (484.2 KiB) Viewed 86 times

[Nikel]

Thanks Twistedpretzel.

A log files reader, please

[Twistedpretzel]

Thanks Twistedpretzel.

A log files reader, please

What are you looking for? Something to parse down the logs in an easier way? Visualizations and charts of weapon performance in scenario?

[Nikel]

Not sure, the data in a more readable and clearer way.

Charts and graphics looks nice

[thewood1]

"Also: per-sensor ring isolation on the coverage diagram; fixed aircraft at multi-facility airbases showing under "Independent" instead of the airfield. (thewood1)"

He likes me...he really likes me!

[Twistedpretzel]

Not sure, the data in a more readable and clearer way.

Charts and graphics looks nice

Something like this? There isn't much in the logs to parse for aggregation or visualization in my opinion. They're good for analysis of specific instances. I was thinking maybe a "CEP map" to plot misses against a specific target, it would be a little misleading since all we have to work with is distance of the miss and not direction. (Thinking unguided bombing.) I'm open to suggestions. If you have any logs with lots of engagements I'll happily take them to play around.

Log Mockup.jpg (351.32 KiB) Viewed 34 times

Log Mockup 2.jpg (346.45 KiB) Viewed 34 times