Matrix Games Forums

I am showing Version 1.00.11158 which almost a month ago. Is this correct? Or did I miss an update along the way?

Thanks guys.

Kevin

If you want to update CMO to the 1121.3 (beta) version:

On Steam:
- right click on Command Modern Operations > Properties
- BETAS tab > Choose "Beta Open Beta"

Perhaps you are looking at the version number that appears at the top right corner of the steam launcher.
that number does not change. instead look for the version number at the bottom of the load/menu screen.

Dave

Thanks guys. Maybe I need a another coffee, but Dave where is the "load/menu screen"? I am not familiar with that one. But anyway, is Steam still on 1.00.11158? Based on the picture above that appears to be the case. I guess the real question is what version should we be designing and testing scenarios for the Community on? The Steam version, if it is 1.00.11158, is ancient history given the numerous fixes the past several weeks. Ideally, we would design off of official builds not betas. But CMO is so new, maybe that is not the best way to design at the moment. Maybe I am wrong, but it appears a player's experience with a scenario will depend highly on which version of CMO that have installed. At least in the early days. A year from now, not so much of an issue.

Kevin

Hi Kevin,
The load/menu screen I'm referring to is what you see after you click on the play button in my screenshot ( rotating globe graphic and play options) If you are on steam then your version will likely have already updated at least once since release day.

Dave

Ooooo thanks! Didn't know abt this... [;)]

ORIGINAL: kevinkins

Thanks guys. Maybe I need a another coffee, but Dave where is the "load/menu screen"? I am not familiar with that one. But anyway, is Steam still on 1.00.11158? Based on the picture above that appears to be the case. I guess the real question is what version should we be designing and testing scenarios for the Community on? The Steam version, if it is 1.00.11158, is ancient history given the numerous fixes the past several weeks. Ideally, we would design off of official builds not betas. But CMO is so new, maybe that is not the best way to design at the moment. Maybe I am wrong, but it appears a player's experience with a scenario will depend highly on which version of CMO that have installed. At least in the early days. A year from now, not so much of an issue.

Kevin

The good news is that it doesn't really matter what game version you design a scenario on, at least not at the scale of changes we have seen since CMO release day. If the scenario is totally dependent on a particular mechanic that is changed it could upset balance, but the scenario itself will run fine--and when I say a mechanic that is changed, I mean something like the introduction of the CoW features or a large and pivotal new feature, not bug fixes and tweaks.

As an example, I develop scenarios on a bunch of different versions of CMO/CMANO from PE to betas to retail to Steam to CMANO for GameBoy(TM). So far the only issues have been due to me making mistakes, not mixing versions of the programs.

The only real constraint is that scenarios created in CMO cannot be loaded into CMANO.

DB updates have far more impact, but that again is mitigated by the system of manually upgrading scenarios to the latest DB, which allows you to roll back if there's issues.

Confirm that steam version is update to 1.00.11158 version, right?

Officially, the Steam, and Matrix, version is 1.00.11158 (aka build 1115.8). The last few *beta* builds (the 1121.x series) have not been released through the Steam/Matrix auto-updaters yet. The Steam launcher (see above) will still report the old version as it (apparently) reads that from the Steam server, but the main loader screen (the one that actually allows you to start or continue a scenario/campaign) will say "Build 1121.x" at the bottom of that screen as it reads the local version.

Ok, I see that now at the bottom of the initial menu screen. Looks like Steam is at 1.00.11158.1 Thanks again.

I would like to see Steam updated to incorporate: "FIXED: #13480: "Unit is Damaged" Trigger goes off multiple times for the same unit"
This fix is from public beta Build 1121.2. I am still finding the tigger going off too much with my Steam. So it looks like the fixed has not made it over to the Steam version. I know players can update to the public betas. But for whatever reason they do not, the automated scoring system for a whole bunch of scenarios could be affected if some players are only relying on Steam auto updates. Again, this is not an big issue down the line months from now. But in the early days, a fix like #13480 is an important one when you designing with units like ships or infrastructure which are difficult to outright destroy.

Kevin