CMO Public Beta - Build 1263.1
Moderator: MOD_Command
CMO Public Beta - Build 1263.1
Download: https://drive.google.com/file/d/1qDPMuc ... sp=sharing
To apply: Unzip on the existing installation of CMO + "Tiny" update.
NOTE: This is a public beta. Standard disclaimers apply.
Build 1263.1 Release Notes (changes from B1261.1)
========================================================================
* NEW UI/SIM FEATURE: Attack methods on airstrike missions: https://i.imgur.com/d1wkI0t.png
Using this, you can direct the air assets on a strike to attack using a number of different patterns. Example: https://i.imgur.com/fL66OpQ.png
* NEW SIM FEATURE: Field-of-view (FOV) restriction for rotating multifunction radars when in tracking / weapon guidance mode. The "archetypal" example for this is the Flap Lid / Tombstone radar family in the S-300/S-400 series of SAM systems. Instead of being able to provide weapon guidance throughout its 360-deg coverage arc concurrently (thus essentially laughing off multi-axis attacks until it runs out of missiles), it is now realistically restricted to a much narrower sector while guiding weapons. Likewise, if it is capable of volume search at the same time, the search is similarly limited to the same sector. The limited sector is also visually depicted on-map, as in this example: https://imgur.com/8yFstnH
Some notes:
- The angular width of the engagement sector is currently guesstimated from the radar type, as we currently lack DB values. The assumption is: 15 deg for mechanical scan, 60 deg for PESAs, and 90 deg for AESAs.
- This change significantly reduces the resilience of such systems against coordinated multi-axis attacks (as well as reducing the effective ROF against multiple threat vectors).
- This change impacts all multifunction radars that have the ability to guide weapons against multiple targets (e.g. Flap Lid, Tombstone, Top Dome, MPQ-53/65 etc.)
- While engaging on a sector, the "crew AI" tries as much as possible to keep the maximum number of targets within the engagement sector. This is why the sector wedge may appear to move as the targets move around.
- ARH weapons fired by such systems (e.g. 9M96, 40N6, PAC-3 MSE etc.) are exempt from this restriction as they do not need continuous illumination from the launch facility. This is part of the reason for their emerging popularity.
- In-between engagements, the radar may switch briefly back to volume search in order to update its threat picture (and possibly take ARH shots if available), before again focusing on a different engagement sector. Once all engagements are over, the radar returns to normal volume-search mode.
* ADDED: #14793: Added ground unit cargo data to DB viewer
* FIXED: #14797: [B1260.1] Missiles crash into ground
* FIXED: #14797: [B1260.1] Missiles reverses course
* FIXED: #14791: Altitude Buttons Missing from Right Side Panel
* FIXED: #14796: Unable to load infantry, Cargo transfer window doesn't update after transferring cargo.
* FIXED: #14790: [B1258.2] Weird behavior for ballistic missiles
* FIXED: #14794: Cargo mission issues with facility group as host or destination
* FIXED: [B1258.2] Strike Mission Escorts Not Respecting "Enforce Flight Size" Option
* FIXED: [B1261] Error message when selecting UAV in the DB Viewer
* FIXED: The various "[timespan]IsChanging" checks during time progression were not evaluating correctly under 5-sec slice mode
* FIXED: Max Flight number was preventing Escort flights to be created
To apply: Unzip on the existing installation of CMO + "Tiny" update.
NOTE: This is a public beta. Standard disclaimers apply.
Build 1263.1 Release Notes (changes from B1261.1)
========================================================================
* NEW UI/SIM FEATURE: Attack methods on airstrike missions: https://i.imgur.com/d1wkI0t.png
Using this, you can direct the air assets on a strike to attack using a number of different patterns. Example: https://i.imgur.com/fL66OpQ.png
* NEW SIM FEATURE: Field-of-view (FOV) restriction for rotating multifunction radars when in tracking / weapon guidance mode. The "archetypal" example for this is the Flap Lid / Tombstone radar family in the S-300/S-400 series of SAM systems. Instead of being able to provide weapon guidance throughout its 360-deg coverage arc concurrently (thus essentially laughing off multi-axis attacks until it runs out of missiles), it is now realistically restricted to a much narrower sector while guiding weapons. Likewise, if it is capable of volume search at the same time, the search is similarly limited to the same sector. The limited sector is also visually depicted on-map, as in this example: https://imgur.com/8yFstnH
Some notes:
- The angular width of the engagement sector is currently guesstimated from the radar type, as we currently lack DB values. The assumption is: 15 deg for mechanical scan, 60 deg for PESAs, and 90 deg for AESAs.
- This change significantly reduces the resilience of such systems against coordinated multi-axis attacks (as well as reducing the effective ROF against multiple threat vectors).
- This change impacts all multifunction radars that have the ability to guide weapons against multiple targets (e.g. Flap Lid, Tombstone, Top Dome, MPQ-53/65 etc.)
- While engaging on a sector, the "crew AI" tries as much as possible to keep the maximum number of targets within the engagement sector. This is why the sector wedge may appear to move as the targets move around.
- ARH weapons fired by such systems (e.g. 9M96, 40N6, PAC-3 MSE etc.) are exempt from this restriction as they do not need continuous illumination from the launch facility. This is part of the reason for their emerging popularity.
- In-between engagements, the radar may switch briefly back to volume search in order to update its threat picture (and possibly take ARH shots if available), before again focusing on a different engagement sector. Once all engagements are over, the radar returns to normal volume-search mode.
* ADDED: #14793: Added ground unit cargo data to DB viewer
* FIXED: #14797: [B1260.1] Missiles crash into ground
* FIXED: #14797: [B1260.1] Missiles reverses course
* FIXED: #14791: Altitude Buttons Missing from Right Side Panel
* FIXED: #14796: Unable to load infantry, Cargo transfer window doesn't update after transferring cargo.
* FIXED: #14790: [B1258.2] Weird behavior for ballistic missiles
* FIXED: #14794: Cargo mission issues with facility group as host or destination
* FIXED: [B1258.2] Strike Mission Escorts Not Respecting "Enforce Flight Size" Option
* FIXED: [B1261] Error message when selecting UAV in the DB Viewer
* FIXED: The various "[timespan]IsChanging" checks during time progression were not evaluating correctly under 5-sec slice mode
* FIXED: Max Flight number was preventing Escort flights to be created
Re: CMO Public Beta - Build 1263.1
Excellent! Thank you!
Re: CMO Public Beta - Build 1263.1
Thanx, I really appreciate the Field-of-view (FOV) restriction for rotating multifunction radars when in tracking / weapon guidance mode feature.
Thought it was not possible, but you made it posssible thumbs up!
Thought it was not possible, but you made it posssible thumbs up!
Re: CMO Public Beta - Build 1263.1
Thank you!
-
- Posts: 904
- Joined: Sun Apr 22, 2001 8:00 am
Re: CMO Public Beta - Build 1263.1
Excellent! Thank you as always.
Question: Will the AI make use of the new airstrike method options?
Question: Will the AI make use of the new airstrike method options?
Re: CMO Public Beta - Build 1263.1
FYI...I keep getting this message when I try to download the file. Am I doing something wrong or do I just need to try later when Google is in a better mood?

Re: CMO Public Beta - Build 1263.1
Might want to try again. I just tried it and it worked right off.
Re: CMO Public Beta - Build 1263.1
No, but now I know what's going on. The new message I'm getting from Google is "download quota exceeded." Too many people have downloaded the file. The nerve of some people!

Re: CMO Public Beta - Build 1263.1
Just tried it four times in the last hour to see if its time-based. Worked all four times. Might want to clear your cache or it might be a regional issue.
-
- Posts: 971
- Joined: Wed Jul 18, 2018 12:05 am
Re: CMO Public Beta - Build 1263.1
I had what Mgellis had, but when I got to the "There was a problem with the preview" screen, I clicked on the little download icon at the top right instead of the big blue download icon in the center. That seems to have downloaded it.
The boogabooga doctrine for CMO: Any intentional human intervention needs to be able to completely and reliably over-ride anything that the AI is doing at any time.
Re: CMO Public Beta - Build 1263.1
Attack Methods is something that I hadn't thought of in a while and is very much appreciated. Alongside other more recent updates, there has been a multitude of functionality added. Very, very much appreciated.
Re: CMO Public Beta - Build 1263.1
I like where you guys have been headed lately!
Keep 'em coming.
Keep 'em coming.
Re: CMO Public Beta - Build 1263.1
Curious what criteria is used to determine when a beta is released to steam as well as here? The last beta release to steam was 1243.5.
edit: Just curious, not criticizing. I'm loving the updates, fixes and changes! Thank you!
edit: Just curious, not criticizing. I'm loving the updates, fixes and changes! Thank you!
Clear skies and tailwinds,
Chuck
Chuck
Re: CMO Public Beta - Build 1263.1
Steam gets more stable releases, for a number of reasons. Once the issues currently reported are under control we should be able to refresh the Steam branch.
Re: CMO Public Beta - Build 1263.1
Thought it may be something along those lines. I've seen some beta patch chaos in other games on steam where players have given negative reviews over betas with clearly written warnings.
Well, fingers crossed this one is stable enough.

Clear skies and tailwinds,
Chuck
Chuck
-
- Posts: 971
- Joined: Wed Jul 18, 2018 12:05 am
Re: CMO Public Beta - Build 1263.1
Right now, changes are being introduced faster than I can beta test.
The boogabooga doctrine for CMO: Any intentional human intervention needs to be able to completely and reliably over-ride anything that the AI is doing at any time.
- AdmiralSteve
- Posts: 288
- Joined: Mon Mar 28, 2011 2:32 pm
- Location: Red Bluff, CA
Re: CMO Public Beta - Build 1263.1
Is anyone willing and able to explain the differences between the different patterns for us and possibly examples when to use each one? These are entirely French to me.Dimitris wrote: ↑Fri Jul 08, 2022 1:04 pm Download: https://drive.google.com/file/d/1qDPMuc ... sp=sharing
To apply: Unzip on the existing installation of CMO + "Tiny" update.
NOTE: This is a public beta. Standard disclaimers apply.
Build 1263.1 Release Notes (changes from B1261.1)
========================================================================
* NEW UI/SIM FEATURE: Attack methods on airstrike missions: https://i.imgur.com/d1wkI0t.png
Using this, you can direct the air assets on a strike to attack using a number of different patterns. Example: https://i.imgur.com/fL66OpQ.png

“There are no extraordinary men...just extraordinary circumstances that ordinary men are forced to deal with.”
Admiral William Frederick Halsey Jr. 1882-1959
Admiral William Frederick Halsey Jr. 1882-1959
-
- Posts: 971
- Joined: Wed Jul 18, 2018 12:05 am
Re: CMO Public Beta - Build 1263.1
AdmiralSteve wrote: ↑Sun Jul 10, 2022 12:16 pmIs anyone willing and able to explain the differences between the different patterns for us and possibly examples when to use each one? These are entirely French to me.Dimitris wrote: ↑Fri Jul 08, 2022 1:04 pm Download: https://drive.google.com/file/d/1qDPMuc ... sp=sharing
To apply: Unzip on the existing installation of CMO + "Tiny" update.
NOTE: This is a public beta. Standard disclaimers apply.
Build 1263.1 Release Notes (changes from B1261.1)
========================================================================
* NEW UI/SIM FEATURE: Attack methods on airstrike missions: https://i.imgur.com/d1wkI0t.png
Using this, you can direct the air assets on a strike to attack using a number of different patterns. Example: https://i.imgur.com/fL66OpQ.png
![]()
I think virtually all of the new features are going to need some more explanation/tutorials.
The boogabooga doctrine for CMO: Any intentional human intervention needs to be able to completely and reliably over-ride anything that the AI is doing at any time.
Re: CMO Public Beta - Build 1263.1
boogabooga wrote: ↑Sun Jul 10, 2022 12:37 pmAdmiralSteve wrote: ↑Sun Jul 10, 2022 12:16 pmIs anyone willing and able to explain the differences between the different patterns for us and possibly examples when to use each one? These are entirely French to me.Dimitris wrote: ↑Fri Jul 08, 2022 1:04 pm Download: https://drive.google.com/file/d/1qDPMuc ... sp=sharing
To apply: Unzip on the existing installation of CMO + "Tiny" update.
NOTE: This is a public beta. Standard disclaimers apply.
Build 1263.1 Release Notes (changes from B1261.1)
========================================================================
* NEW UI/SIM FEATURE: Attack methods on airstrike missions: https://i.imgur.com/d1wkI0t.png
Using this, you can direct the air assets on a strike to attack using a number of different patterns. Example: https://i.imgur.com/fL66OpQ.png
![]()
I think virtually all of the new features are going to need some more explanation/tutorials.
This is why I specifically asked in another thread if the manual would be updated with these new features and in-depth explanations upon the stable release and thankfully the answer was yes.