Command Modern Operations v1.01 update - Build 1147.10

Take command of air and naval assets from post-WW2 to the near future in tactical and operational scale, complete with historical and hypothetical scenarios and an integrated scenario editor.

Moderator: MOD_Command

Post Reply
Dimitris
Posts: 15567
Joined: Sun Jul 31, 2005 10:29 am
Contact:

Command Modern Operations v1.01 update - Build 1147.10

Post by Dimitris »

Download: Superseded by B1147.11

To apply: Unzip to the CMO installation directory, overwriting as necessary.

NOTE: This is a public beta. Standard disclaimers apply.


Build 1147.10 release notes (changes from B1147.9)
-----------------------------------------------------------------

* Added support for CWDB in the Quick-Battle Generator. You can now specify which DB to employ in a QBG template, by using a 'hidden'-type HTML element. Examples: <input type="hidden" name="DB" value="DB3000"> or <input type="hidden" name="DB" value="CWDB"> . This element must be present in the Form.html file in the template folder. If it is not present, the QBG defaults to using the DB3000 database.
* Added: [Lua] VP_GetScenario method (Exposes some scenario data such as duration, start time, complexity & difficulty, DB file used etc)
* Map tweak: Fixed SSM facilities (e.g. ICBM silos) use the "fixed facility" icon rather than the "mobile missile artillery" one
* FIXED: UI Cross-threading violation in Migration form when migrating single scenario
* FIXED: Diesel sub not going to flank & deep to evade incoming torpedo
* FIXED: #14000: Floating point precision issue with nuclear warhead yields on DB viewer
* FIXED: #13768: Aircraft switch to pure-pursuit within sensor or weapon range
* FIXED: #12657: Aircraft flying too high on localization run
* FIXED: #13861: Ground Units not pathing as a Group
* FIXED: #14120: Strike Mission target list not evaluated correctly
* FIXED: Code typo causing incorrect target priority
* FIXED: #13768: Aircraft switch to pure-pursuit within sensor or weapon range
* FIXED: #13846: Dipping sonar doctrine not working
BrianinMinnie
Posts: 166
Joined: Thu May 07, 2015 3:12 pm

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by BrianinMinnie »

Thanks All!
Scorpion86
Posts: 264
Joined: Sun Feb 26, 2017 1:19 pm

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by Scorpion86 »

You just keep spoiling us and spoiling us with updates, don't you?

...go on.

(and thank you!)
KnightHawk75
Posts: 1850
Joined: Thu Nov 15, 2018 7:24 pm

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by KnightHawk75 »

Thank you!!
kentcol
Posts: 153
Joined: Sat Jul 01, 2006 3:37 pm

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by kentcol »

Steam still has the version 1147.4. How do I update to the current version?
KnightHawk75
Posts: 1850
Joined: Thu Nov 15, 2018 7:24 pm

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by KnightHawk75 »

ORIGINAL: kentcol

Steam still has the version 1147.4. How do I update to the current version?
If you want to use the beta you copy the contents of the zip over the existing installation, replacing existing files.
To apply: Unzip to the CMO installation directory, overwriting as necessary.

NOTE: This is a public beta. Standard disclaimers apply.
magi
Posts: 1533
Joined: Sat Feb 01, 2014 1:06 am

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by magi »

thank you..... you are my favorite.....
boogabooga
Posts: 1012
Joined: Wed Jul 18, 2018 12:05 am

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by boogabooga »

ORIGINAL: Dimitris
* Added support for CWDB in the Quick-Battle Generator. You can now specify which DB to employ in a QBG template, by using a 'hidden'-type HTML element. Examples: <input type="hidden" name="DB" value="DB3000"> or <input type="hidden" name="DB" value="CWDB"> . This element must be present in the Form.html file in the template folder. If it is not present, the QBG defaults to using the DB3000 database.

It seems that the CWDB version being referred to here is 466. Is there a way to specify a newer version, or just go with 466?
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.
User avatar
KLAB
Posts: 507
Joined: Tue Feb 27, 2007 5:24 pm

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by KLAB »

Nice. All sorts of stuff now running smoothly, thanks.
Dimitris
Posts: 15567
Joined: Sun Jul 31, 2005 10:29 am
Contact:

RE: Command Modern Operations v1.01 update - Build 1147.10

Post by Dimitris »

ORIGINAL: boogabooga
ORIGINAL: Dimitris
* Added support for CWDB in the Quick-Battle Generator. You can now specify which DB to employ in a QBG template, by using a 'hidden'-type HTML element. Examples: <input type="hidden" name="DB" value="DB3000"> or <input type="hidden" name="DB" value="CWDB"> . This element must be present in the Form.html file in the template folder. If it is not present, the QBG defaults to using the DB3000 database.

It seems that the CWDB version being referred to here is 466. Is there a way to specify a newer version, or just go with 466?

Can you please open a new thread about this on the Tech Support forum? Thanks!
Post Reply

Return to “Command: Modern Operations series”