Offline DB Viewer v1.1.0 Feature Glossary

[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?