CMO v1.04 Update - Build 1147.40 (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series



Message

Dimitris -> CMO v1.04 Update - Build 1147.40 (1/28/2022 4:05:18 PM)

Download: https://drive.google.com/file/d/1AzNByMoCLFC6f5NHej6xkyb1stkBv6QO/view?usp=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-story-of-the-giraffe-missions-and-how-iraf-mirage-f-1-fighter-bombers-were-able-to-shoot-down-four-iriaf-f-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 -> RE: CMO v1.04 Update - Build 1147.40 (1/28/2022 4:23:34 PM)

Cool ! Thank you ! [&o]



Swant -> RE: CMO v1.04 Update - Build 1147.40 (1/28/2022 4:44:32 PM)

Thank you!



Parel803 -> RE: CMO v1.04 Update - Build 1147.40 (1/28/2022 6:40:52 PM)

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



alphali -> RE: CMO v1.04 Update - Build 1147.40 (1/28/2022 7:16:42 PM)

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/28/2022 10:17:56 PM)

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/28/2022 11:15:01 PM)

Thanks for the update!



boogabooga -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 3:11:20 AM)


quote:

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 3:58:49 AM)

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



boogabooga -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 4:14:55 AM)

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 4:17:05 AM)

Thank God for the chaff fix. [&o]



alphali -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 7:27:56 AM)

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



Dimitris -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 7:38:39 AM)

quote:

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.

quote:


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 -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 8:51:26 AM)

quote:

* 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 -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 1:59:59 PM)

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 5:18:29 PM)

quote:

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/29/2022 8:23:13 PM)

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/30/2022 1:02:29 AM)


quote:

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 -> RE: CMO v1.04 Update - Build 1147.40 (1/30/2022 6:37:36 PM)

Thank-you to all the devs for this update

Scott



SteveMcClaire -> RE: CMO v1.04 Update - Build 1147.40 (1/31/2022 4:15:46 PM)

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.



PaulWRoberts -> RE: CMO v1.04 Update - Build 1147.40 (1/31/2022 8:21:31 PM)

In practice, what "generation" of ground/ship-based radars are affected by the 30-degree limit? When do phased-array radars become common, and for whom?

Thanks!



c3k -> RE: CMO v1.04 Update - Build 1147.40 (1/31/2022 10:49:55 PM)

Outstanding!

A great game keeps getting more refined and better and better.

Thanks.



boogabooga -> RE: CMO v1.04 Update - Build 1147.40 (2/1/2022 3:31:55 AM)

quote:

ORIGINAL: Dimitris

quote:

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.


Sure, but what if you are already tracking someone that goes 30 deg below you, wouldn't you steer the radar to maintain the track? Or on the other end, there are probably some non-steerable radars for which the 30 deg. scan limit is too generous.

However, when one works out the trig- from 36 000 ft, an enemy flying NOE has to get within 12nm or so to get underneath a +-30 deg search cone-basically point blank range for anything with a powerful radar in the first place- so really the issue is not so severe. It's a nice touch, anyway.

BTW, with the new model, I've noticed that AESA-equipped aircraft lose their targets when they crank, affecting BVR accuracy somewhat; one might consider reducing the crank angle by a few degrees.




nkocevar -> Issues when deleting units? (2/1/2022 3:38:57 AM)

Is anyone else having an issue where the Delete key doesn't delete a unit while in the scenario editor with this update?



boogabooga -> RE: Issues when deleting units? (2/1/2022 4:04:40 AM)

Yes on the delete key.

Could you please explain this further:
FIXED: #13816: GUI QoL 11.4 Throttle and Altitude settings

Is there supposed to be a new hotkey for this?



BDukes -> RE: CMO v1.04 Update - Build 1147.40 (2/1/2022 4:36:52 PM)

quote:

Sure, but what if you are already tracking someone that goes 30 deg below you, wouldn't you steer the radar to maintain the track? Or on the other end, there are probably some non-steerable radars for which the 30 deg. scan limit is too generous.


This is a good point. I think I'll be setting up high and low caps regardless.

Mike



Dimitris -> RE: CMO v1.04 Update - Build 1147.40 (2/1/2022 8:13:45 PM)

quote:

ORIGINAL: boogabooga
BTW, with the new model, I've noticed that AESA-equipped aircraft lose their targets when they crank, affecting BVR accuracy somewhat; one might consider reducing the crank angle by a few degrees.


Thanks, it was also pointed by someone else and we have a tweak in place for the next update; aircraft with a PA will now crank less aggressively for this reason.



Dimitris -> RE: Issues when deleting units? (2/1/2022 8:14:25 PM)

quote:

ORIGINAL: nkocevar
Is anyone else having an issue where the Delete key doesn't delete a unit while in the scenario editor with this update?


Yes, it has been replicated and fixed for the next update.



slimatwar -> RE: Issues when deleting units? (2/1/2022 9:18:05 PM)

The DELETE key also doesn't delete selected waypoint also.



AKar -> RE: CMO v1.04 Update - Build 1147.40 (2/2/2022 9:56:37 AM)


quote:

ORIGINAL: Dimitris

Download: https://drive.google.com/file/d/1AzNByMoCLFC6f5NHej6xkyb1stkBv6QO/view?usp=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. [...] There is an exception, however: Phased-array radars can scan upwards close to the vertical limit.



A noteworthy detail is that many phased arrays are installed at a downward angle to reduce the frontal radar cross section of the antenna. This results in the center axis of the possible scan 'cone' being pointed downwards. At the edge of the electrical scanning limits, the beamforming is subject to similar limitations on the effective aperture both in horizontal and vertical axes, further reducing the effectiveness of the extreme limits.



Page: [1] 2   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
4.375