CMO Update - Update v1.06.1328.18

[LiamR]

Good news for you Command fans, we have an update out today. Your Steam version of the game will automatically update, or you can download the update directly here.

v1.06.1328.18 is mainly focused on bugfixes and tweaks, no new major features have been added. There has however been a significant change to the radar model.

Until now, radars with an air-search capability and those with space-search (ie. ASAT & ABM) capability were separated in their target detection capacity by altitude and target type; ie. air-search radars could detect aerodynamic targets within the atmosphere, whereas space-search radars could detect BMs and RVs outside the atmosphere. While broadly accurate, this abstraction left a lot of unrealistic cases: For example a fighter radar could detect an RV in its terminal phase, or endoatmospheric guided weapons such as hypersonic missiles where not detected by BMD radars.

In real life, radars use velocity filters (in addition to altitude ceilings) to specialize in their search task and minimize false contacts etc. Command now correctly replicates this behaviour, with some assumptions for the minimum and maximum velocity values:

Air-only search radars may detect any target from 0 knots (hover) up to Mach 5.

Space-only search radars (ie. BMD/ASAT) can detect any target from Mach 2 up to "unlimited" velocity.

Combined air & space-search capable radars use the full velocity spectrum.

This addition allows more realistic representation of the capabilities and limitations of each type of radar, against the full gamut of endo- and exo-atmospheric targets.

You can read the whole changelog here.

Enjoy the update, and good hunting everyone.

[Nikel]

No more betas?

But there are bugs still not fixed

[Dimitris]

No more betas?

But there are bugs still not fixed

There are always some bugs to fix. We are already busy on the next update release, which will address numerous reported issues.

[Nikel]

Yes, I know there will be bugs always, but I think more beta rounds were needed.

So if you have 1328.14 + 1328.18 beta applied you do not need this patch?

[Dimitris]

Yes, I know there will be bugs always, but I think more beta rounds were needed.

Keep in mind that most users do not apply the public beta / soft-release updates. For them, it's better to get an official build right now which solves a lot of important issues (even though many others are still unresolved) than keep waiting for the unicorn "flawless" release.

So if you have 1328.14 + 1328.18 beta applied you do not need this patch?

Yes, although this is a more convenient manner.

[BDukes]

No more betas?

But there are bugs still not fixed

There are always some bugs to fix. We are already busy on the next update release, which will address numerous reported issues.

If you can really handle the critical one's that would be great. The missile guidance things Kobu mentioned and missions with aircraft circling waypoints seem to be the biggest turnoffs.

Mike

[Nikel]

Keep in mind that most users do not apply the public beta / soft-release updates. For them, it's better to get an official build right now which solves a lot of important issues (even though many others are still unresolved) than keep waiting for the unicorn "flawless" release.

OK, thanks

Waiting for the ugly unicorn next beta release

[thewood1]

I'm a little concerned that a couple important issues still aren't resolved before an official Steam patch is released. I was using .14 on Steam assuming those would be addressed before an official patch went out that included those. I was using Steam .14 until the next patched fixed some of those issues. My choices now are another Matrix CMO install at .14, just live with the issues in .18, or give up for now.

[thewood1]

I was reading the release notes for 1328.18 release and saw something that jarred my memory.

I saw the comment that 1328.14 release + 1328.18 beta = 1328.18 release as above. But in 1328.16 beta I saw this from the notes:

"Air-only search radars may detect any target from 5 knots up to Mach 5"

But in the 1328.18 release (not beta) notes, I saw this:

"Air-only search radars may detect any target from 0 knots (hover) up to Mach 5"

I didn't see anything mentioned in 1328.17 beta or 1328.18 beta notes that mentioned the change from 5 knots to 0 knots. Was it just missed in the notes of 1328.17 beta or 1328.18 beta? Or is that change only in 1328.18 release?

[caelunshun]

I didn't see anything mentioned in 1328.17 beta or 1328.18 beta notes that mentioned the change from 5 knots to 0 knots. Was it just missed in the notes of 1328.17 beta or 1328.18 beta? Or is that change only in 1328.18 release?

It was changed in 1328.17:

* TWEAK: Air-search radars can also detect hovering air targets

[thewood1]

Thanks.

[Nikel]

By the size of this patch, were the community pack scenarios included again?

[Dimitris]

I'm a little concerned that a couple important issues still aren't resolved before an official Steam patch is released. I was using .14 on Steam assuming those would be addressed before an official patch went out that included those. I was using Steam .14 until the next patched fixed some of those issues. My choices now are another Matrix CMO install at .14, just live with the issues in .18, or give up for now.

Can we get a detailed rundown of the unresolved issues you consider fundamental/critical? We can try to prioritize them for instrumentation and inclusion into automated testing so that they are caught more reliably.

We are not deaf to the increasing feedback on QC issues, but we need the community's help in triaging the pile. Not every potential issue is of equal priority or relevance.

[thewood1]

Below is the progression of fixes and then bugs in mission behavior that kept me applying beta patches.

14 had flight size issues in missions and sonar detection problems as well as a few other things.
.15/.16 was Air intercept units flying off in all kinds of directions and targeting issues related to mission WRA
,17 was some ships doing the same thing and going off on their own on missions
.18 was strike missions not following flight plans and a lot of other weird actions on missions. https://www.matrixgames.com/forums/view ... 1#p5160581

The link above is the mission issue I reported on the forum. Its been months since I trusted mission behavior to not force me to babysit units to make sure they have the right number of mission units, go after the right target, use the right speed/altitude, follow the flight plan, use the assigned WRA, etc. To me, these are the basic design functions within missions. And missions are core.

I think the pre-.18 issues are fixed. But its this ongoing set of issues, one after another, that is frustrating. One gets fixed only to have a another mission-breaking issue pop up.

[zclark]

To second what has already been posted:

Aircraft on air patrol missions fail to engage targets identified as hostile.
WRA settings not being followed.
Aircraft not RTB'ing when expending all munitions.

[Dimitris]

To second what has already been posted:

Aircraft on air patrol missions fail to engage targets identified as hostile.
WRA settings not being followed.
Aircraft not RTB'ing when expending all munitions.

Can we please get links to specific threads for each of these? thewood1 has provided a link for his still-open issue. We need specific, common-shared examples so that we are sure that we are looking at the same thing as you. Thanks!

[thewood1]

I would also make sure you have the right versions aligned with the issue. Some of those might have been fixed in .15/.16/.17/.18.

[mikerohan]

Refuelling issues: https://www.matrixgames.com/forums/view ... 0&t=403218

Not RTB on Winchester: https://www.matrixgames.com/forums/view ... 0&t=403217

This one is different: https://www.matrixgames.com/forums/view ... 0&t=402524
Here it would be great to know the devs expectations to CEC guidance when the firing platform wants to remain "silent".
I reckon it's not the same a bug than a change of behavior. In order to cry "bug" we need a better understanding of the results we are seeing (intended? unintended? right? wrong?)

Thanks for the extra effort!

[kahta]

I'm a little concerned that a couple important issues still aren't resolved before an official Steam patch is released. I was using .14 on Steam assuming those would be addressed before an official patch went out that included those. I was using Steam .14 until the next patched fixed some of those issues. My choices now are another Matrix CMO install at .14, just live with the issues in .18, or give up for now.

Can we get a detailed rundown of the unresolved issues you consider fundamental/critical? We can try to prioritize them for instrumentation and inclusion into automated testing so that they are caught more reliably.

We are not deaf to the increasing feedback on QC issues, but we need the community's help in triaging the pile. Not every potential issue is of equal priority or relevance.

I would say that the two biggest issues are:

Aircraft circling waypoints and running out of fuel.

https://www.matrixgames.com/forums/view ... 0&t=403435

[thewood1]

Any news on a near-term update to fix some of the mission issues that have been around a while?