CMO v1.09 Public Beta - Build 1776

[Dimitris]

NOTE: This is a public beta. Standard disclaimers apply. If you are uncertain, wait for the official release.

DOWNLOAD: https://drive.google.com/file/d/161OCOC ... sp=sharing
Installation: Unzip to your CMO installation folder, accepting any overwrite prompts as necessary. !!!Backup your existing files, especially Command.exe!!!
NOTE: If you have already installed B1774, the only changed file in this pack is Command.exe .

Command v1.09 Beta - Build 1776 Release Notes (changes from B1774)
----------------------------------------------------------------------------------------------

Fixed: #17020: Underground Shock not taking in consideration the size of affected area of a huge facility when calculating damage
FIXED: Mission escort constantly targeting and dropping a mission target that it has no suitable weapons for
FIXED: Aircraft on strike mission continuously targeting and then dropping extremely ambiguous target
FIXED: Ground-unit icons not size-scaling properly
FIXED: [Build 1774] Fire Control Auto Evasion by unaffected units
Fixed: #17078: [B1774] Submarine battery status does not change bold text based on what propulsion system is being used

[BrianinMinnie]

Outstanding work Gang!!!

[KLAB]

Thanks. Hadn't even had chance to use 1774 yet. K

[BDukes]

Nice!

M

[Blast33]

Nice timing, just for the weekend...I won't leave my room coming days
Thank you guys for all the effort!

[rvseydlitz]

There have only been beta releases since 1.08 months ago...any idea when a non beta 1.09 will be out? Thank you~

[Dimitris]

When it's ready.

Thank you for your patience!

[Nikel]

There have only been beta releases since 1.08 months ago...any idea when a non beta 1.09 will be out? Thank you~

I see no reason to wait for an official release.

Just jump to the last beta

[rvseydlitz]

Steam...every time I have installed a beta ...requires hours (at my net speed) of reinstalling the game each time I restart it making betas virtually unplayable beyond once each

[thewood1]

There is something wrong with your settings. I have been using Matrix betas on Steam for years. Not sure what it could be, but I'd start there.

A quick search on Steam...https://steamcommunity.com/discussions/ ... 818898671/

"External hard drives are not recommended for use with Steam or Steam's games. Aside from many potential performance issues, external hard drives may connect or disconnect from the computer at inopportune times as part of their normal operations. If you encounter this issue with an external drive, install Steam and your games to an internal drive instead.

To ensure that you do not encounter this issue, always allow Steam to close properly when shutting down your computer. Allowing Windows to force Steam to close when it is writing to a hard drive may cause Steam library and installation information to become corrupted.

Additionally, third party applications can prevent Steam from writing essential information. Ensure that none of your installed applications are interfering with Steam:

https://help.steampowered.com/en/faqs/v ... -FF28-5748"

Personally, I think the above is a longshot, but you never know.

[thewood1]

The more I think about this, I think the issue might be an anti-virus issue. I would reach out to Matrix tech support. The only issues I have ever had with Steam and CMO has been anti-virus blocking Command.exe from running. One symptom of an anti-virus is that Steam will revalidate the files.

The other potential issue is the Matrix Launcher. That app does weird things with updates sometimes. I never use it.

[rvseydlitz]

Thank you. I will try these out!

[leemiller24]

It may be a good time to revisit the effectiveness of Chinese, Russian and Iranian radar and SAM capability in a modern electronic battlefield— I’m not trying to start any controversy, it just appears there needs to be some adjustments in effectiveness.

[Dimitris]

It may be a good time to revisit the effectiveness of Chinese, Russian and Iranian radar and SAM capability in a modern electronic battlefield— I’m not trying to start any controversy, it just appears there needs to be some adjustments in effectiveness.

We've been here before, oh so many times: https://command.matrixgames.com/?p=5349

[thewood1]

It may be a good time to revisit the effectiveness of Chinese, Russian and Iranian radar and SAM capability in a modern electronic battlefield— I’m not trying to start any controversy, it just appears there needs to be some adjustments in effectiveness.

Or you could just read a few posts on the forum...https://forums.matrixgames.com/viewtopic.php?t=414779

[Mgellis]

In fairness, there is a LOT of stuff in the forum. I sometimes miss things even after I use the search function.

It may be a good time to revisit the effectiveness of Chinese, Russian and Iranian radar and SAM capability in a modern electronic battlefield— I’m not trying to start any controversy, it just appears there needs to be some adjustments in effectiveness.

Or you could just read a few posts on the forum...https://forums.matrixgames.com/viewtopic.php?t=414779

[Mgellis]

It may be a good time to revisit the effectiveness of Chinese, Russian and Iranian radar and SAM capability in a modern electronic battlefield— I’m not trying to start any controversy, it just appears there needs to be some adjustments in effectiveness.

I think some of these issues could be addressed with the Proficiency rating. The devs could obviously provide more information here, but I wonder if the quality of the equipment is what it SHOULD be, based on the technology itself. The performance we're seeing in the real world might simply be that the equipment itself has not been well-maintained and/or the people using it are poorly trained (or just haven't been paid in the last few months).

Maybe there should be a "poor maintenance record" setting for units, groups, and sides that would simulate things like degraded performance, even longer OODA loops, etc.

[tylerblakebrandon]

It may be a good time to revisit the effectiveness of Chinese, Russian and Iranian radar and SAM capability in a modern electronic battlefield— I’m not trying to start any controversy, it just appears there needs to be some adjustments in effectiveness.

I think some of these issues could be addressed with the Proficiency rating. The devs could obviously provide more information here, but I wonder if the quality of the equipment is what it SHOULD be, based on the technology itself. The performance we're seeing in the real world might simply be that the equipment itself has not been well-maintained and/or the people using it are poorly trained (or just haven't been paid in the last few months).

Maybe there should be a "poor maintenance record" setting for units, groups, and sides that would simulate things like degraded performance, even longer OODA loops, etc.

I use proficiency to adjust unit capabilities although this could possibly be finessed more. I will leave that to the devs.

But people see events and want units altered to fit a result but factors beyond the units physical aspects have major impacts. Maintenance, crew training, morale, etc take an SA-3 from HARM fodder in Iraq to a F-117 slayer in Serbia. Substandard upkeep and training mean Moskva is dead compared to a well maintained and well drilled ship.

[lumiere]

For non-player side, terrible mission settings on purpose is also useful to recreate bad performances:
-WCS is HOLD/EMCON is passive until one of friendly unit is destroyed (use Lua for activation event).
-patrol mission area is out-of-place/unit do not investigate contacts outside of narrow patrol area.
-WRA range for AAM/SAM are maximum range, allowing easy evasion.
-in contrast, too short WRA range could not respond to threats until it's too late.

Reducing unit's SAM rounds (whether actually supplied or not, you couldn't use them) is quite useful too.

In all, they require deep understanding on game system of Command (it's been ten year since I bought CMANO!), which is not out-of-box game.

[Boppel2001]

I have installed beta version 1.09 1776.
I download the zip file from Google.
Unfortunately, with version 1.09. 1774 and also with 1776, no scenario is loaded anymore.
I have tested it on two computers running Windows 11 Pro (Core i9 9th Gen and Core i9 last Gen). When a scenario is to be loaded, CMO freezes.

Bild2.png (1.08 MiB) Viewed 190 times