CMO v1.04 Update - Build 1147.40

[Dimitris]

Download: https://drive.google.com/file/d/1AzNByM ... sp=sharing

To apply: Unzip to the CMO installation directory, overwriting as necessary (backup the existing Command.exe, just in case)

NOTE: This is a public beta. Standard disclaimers apply.


Build 1147.40 Release Notes (changes from Build 1147.39)
-------------------------------------------------------------------------------------------------

* NEW FEATURE: Radar vertical scan angle limitations. Radars can only look up/down to a maximum of 30 degrees. This restriction severely curtails their ability to search for targets high above or well under them, and has indeed been used and exploited operationally (Example: https://theaviationgeekclub.com/the-sto ... 14-tomcats ). There is an exception, however: Phased-array radars can scan upwards close to the vertical limit.

* The DB integrity check mechanism has been improved (kudos to Knighthawk75 for pointing out the cause of the problem)
* FIXED: #13811: GUI QoL 7.3 Order of Battle + Order of Battle Contacts
* FIXED: #13801: GUI QoL 4.2 Side Selection and Briefing window
* FIXED: #13800: GUI QoL 4.1 Side Selection and Briefing window
* FIXED: #13816: GUI QoL 11.4 Throttle and Altitude settings
* ADDED: Lua wrapper for Scenario object allows setting scenario Title
* ADDED: #14339: Hotkey for "Define Area" (Ctrl + K)
* FIXED: Out-Of-Comms Group vector icon
* FIXED: [B1147.38] Airgroup RTB'ing through No Nav Zone
* FIXED: ORBAT - Contact default list is collapsed, and no tab 3 in this branch
* FIXED: Can't kill that platoon and a lag problem
* FIXED: [Lua] "Contact" Wrapper .fromside null-reference exception
* FIXED: ASBM/RV "Hyunmoo 2C" salvo causes loop "Error at 100971"
* FIXED: [B1147.38] Mission Editor UI Freezes when LCAC Assigned to Cargo Mission
* FIXED: Chaff ineffective?
* FIXED: Space bar re-opening doctrine screen
* FIXED: List of missions should be in alphabet order, for aircraft on airfields
* FIXED: #13784: Bugfixing for default Expand/Collapse state of ORBAT
* FIXED: Airops form show "Label1" in the quick turnaround info when empty
* FIXED: [B1147.38] Units unloading the square of their cargo
* FIXED: QOL [Feature Request] cmanouser1's list of QOL requests (1.4 1.5 3.1 7.2 7.5)

[nukkxx5058]

Cool ! Thank you ! [&o]

[Swant]

Thank you!

[Parel803]

Thank you, as always great work by you all.
regards GJ

[alphali]

Where can we find the exact detail of the QOL improvement? what are the changes to the "side selection" and "Throttle and Altitude settings"? And what are these "cmanouser1's list of QOL requests"? Couldn't find the related posts, if anyone has links to share. Thx

[BDukes]

My impressions:

Order of battle window work is definitely a step up. Some color coding and UI controls make a better user experience.
Order of battle contacts is very nice. Takes a second to load.
Side Briefing is full screen at scenario launch. Edit HTML button position might be new (maybe).
Throttle and Altitude settings dialog seems much more responsive to changes instead of the weird misclick shiznit that would go on.

Looks really great.

Anybody tried the Mirage vs. Tomcat thing yet? Might have to start thinking about high and low altitude CAP[8D]

[KnightHawk75]

Thanks for the update!

[boogabooga]

ORIGINAL: alphali

Where can we find the exact detail of the QOL improvement? what are the changes to the "side selection" and "Throttle and Altitude settings"? And what are these "cmanouser1's list of QOL requests"? Couldn't find the related posts, if anyone has links to share. Thx

https://www.matrixgames.com/forums/tm.asp?m=4788701

[fulcrum28]

thank you. I noticed that the aircraft range blue circle is not showing.

[boogabooga]

While I like the idea of radar vertical scan angle limitations, I'm not sure about the one size fits all 30 deg limit. Do you have information supporting a global 30 deg limit? I was under the impression that radars could be tilted quite a bit, as is modeled in the horizontal.

Also, is it 30 deg up and 30 deg down, or 30 deg TOTAL (+15 , -15)? Will 'tracking' have a different limit than 'search', as it is for horizontal?

[Shkval25]

Thank God for the chaff fix. [&o]

[alphali]

Wow it's from 2020, didn't think it would be that old, thanks

[Dimitris]

ORIGINAL: boogabooga
While I like the idea of radar vertical scan angle limitations, I'm not sure about the one size fits all 30 deg limit. Do you have information supporting a global 30 deg limit? I was under the impression that radars could be tilted quite a bit, as is modeled in the horizontal.

Currently it's the same for everyone. It may be expanded to individualized in the future if there is strong need for it (this would, however, probably require DB schema mods).

According to our sources, airborne radars (and other sensors e.g. IRSTs) are typically auto-stabilized in order to maintain a consistent picture during turns, climbs/dives etc. (except on extreme attitude change). While manual tilting is possible (e.g. in extreme snap-up/down engagements) it is not common because it can severely curtail general SA. We are of course open to sourced feedback on this, as usual.

Also, is it 30 deg up and 30 deg down, or 30 deg TOTAL (+15 , -15)? Will 'tracking' have a different limit than 'search', as it is for horizontal?

IIRC it's the former.

[nukkxx5058]

* FIXED: Can't kill that platoon and a lag problem

Wow !! Just had a try in the editor and ground combat is now greatissimo ! Damn lethal. Brillant, I'm so glad you fixed it guys ! [&o][&o][&o]

[ClaudeJ]

Great stuff!
Thanks to the team for keeping at it. GUI/QOL improvements are welcome, whenever they come.

Now, does this beta include what came with v1.04.114734.01 - Update Sam posted ?

[Eggstor]

ORIGINAL: ClaudeJ
Now, does this beta include what came with v1.04.114734.01 - Update Sam posted ?

I would presume so given the .39 beta added back the missing Kashmir Fire scenarios and had some fixed/tweaked scenarios (Operation Brass Drum, Shifting Sands #13, The Silent Service #2, Red Tide #3 & #10).

[Fido81]

Thanks for the update!

I have a couple quick questions about this exciting new feature:
1. Do the scan angle limitations affect space-, ground-, and sea-based radars in addition to aircraft radars?
2. Is the scan angle limitation modeled in the LOS tool?

[ronmexico111]

ORIGINAL: Fido81

Thanks for the update!

I have a couple quick questions about this exciting new feature:
1. Do the scan angle limitations affect space-, ground-, and sea-based radars in addition to aircraft radars?

My question would be if this affects all aircraft radars as well, including aboard AWACS, or if it only applies to certain types of aircraft.

[Phobosdeimos71]

Thank-you to all the devs for this update

Scott

[SteveMcClaire]

Hi Fido81 -- yes, the scan angle limits effect all radars. In fact this is an issue for satellites that I'll fix for the next update. As for the LOS tool, this uses only the theoretical radar horizon range and does not take scan angle limits (or other specific radar technical limits) into account.