CMO Public Beta - Build 1263.1
Posted: 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
* 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