CMO Public Beta - Build 1266.1

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: 15321
Joined: Sun Jul 31, 2005 10:29 am
Contact:

CMO Public Beta - Build 1266.1

Post by Dimitris »

Download: https://drive.google.com/file/d/1s0GP07 ... sp=sharing

To apply: Unzip on the existing installation of CMO + "Tiny" update.

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

Build 1266.1 Release Notes (changes from B1265.1)
========================================================================

* ADDED: [Lua] New method for LOS checks: Tool_LOS(table).
Valid Parameters:
- MODE (byte, default is 0): If set to 0, the method returns the radar/ESM horizon (in nm) of a given unit at a defined altitude. If set to 1, it returns the result of a LOS check between two specified units as a boolean (true/false).
- HORIZON (byte, default is 0): Specifies the horizon type used (0 = radar/ESM, 1 = visual). NOTE: Depending on the horizon type, the observer unit's corresponding mast height (radar/ESM or visual) is also taken into account.
- USERANGELIMITS (boolean, True by default): If set to True, the max/min range limits of the unit's sensors are used. This can substantially speed up performance as no checks are made outside the max sensor range of the unit(s) involved.
- OBSERVER (numeric, string or table, default is 0): If numeric, it represents the observer unit's altitude (in meters). If string, it is the observer unit's GUID.
- TARGET (numeric, string or table, default is 0): If numeric, it represents the target unit's altitude (in meters). If string, it is the target unit's GUID.
For the altitude input, you can also use tables to precisely specify the altitude format. Examples:
Tool_LOS( {observer = {alt='100 ft'}, target = {alt='10972 ft'} } )
Tool_LOS( {observer = {alt='100 m'}, target = {alt='10972 m'} } )

* ADDED: Scenario, Global and Camera Minimap upgrades. Example: https://i.imgur.com/MlD1wSh.png
* ADDED: Added (capability for) images and descriptions for sensors to DB-viewer
* ADDED: Implemented Ship Flag #2101 - can launch amphibs at sea
* ADDED: Show fuel tanks in a/c unit fuel panel
* ADDED: [Operation Planner] Added sort mission by name option
* ADDED: [Operation Planner] Added an option to change mission's phase in bulk
* ADDED: [Operation Planner] Added buttons to check/uncheck all missions
* ADDED: [Operation Planner] UI: Mission description now automatically populates with the current count of assigned and mobilised units if the description is empty.
* ADDED: AC exhaustion max level now scales with Proficiency Level (better crews last longer and manage their planes more efficiently)
* TWEAK: Mission editor displays a dynamic tooltip for multi-mission unit
* TWEAK: [Event Editor] Let RemainsInArea trigger handle multiple units

* FIXED: #14816: Iron Dome doesn't activate its radar versus incoming threats
* FIXED: #14815: Exception changing side from Lua from event
* FIXED: [B1253.1] Aircraft not getting up to Altitude
* FIXED: Torpedo won’t launch with “XX % maximum range” WRA setting (Build 1265.1)
* FIXED: [Lua] SetUnitEmission had wrong key
* TWEAK: [Lua] Added properties/methods to Sensor wrapper: .type , .role , .ranges , .altitudes , .RangeAgainstTarget
* FIXED: Mobile decoys prevent other guided weapons from firing at same target
* FIXED: #14814: 1265.1 Sporadic 'index out of bounds' error loading scen
* FIXED: [Lua] ScenEdit_UnloadCargo & ScenEdit_TransferCargo units as cargo
* FIXED: [Lua] Inconsistent use of "GROUND UNIT" type naming in ScenEdit_AddUnit()
* FIXED: [Lua] ScenEdit_UpdateUnitCargo() fails adding/removing units as cargo
* FIXED: Erratic rotations of units
* FIXED: [B1265.1] Exhaustion RTB/Bingo pathfinding issues
* FIXED: #14811 - Contacts lost for all units
* FIXED: [B1265.1] "RTB - Exhaustion" state right after take off on MiG-31BM
* FIXED: [B1255] Waypoint issue
* FIXED: [B1147.45] "Load group" window issue
* FIXED: [B1261] Issue with mission planner
* FIXED: [Event Editor] Exception in RemainInArea trigger
* FIXED: [Event Editor] Trigger 'RemainInArea' not firing on time in "double flame" mode
* FIXED: #14809 - Issues with HGV launched from ballistic missile
* RE-FIXED: Slug trail "use" option being ignored.
* FIXED: Tacview window was not updating unit positions
* FIXED: [B1263] Duplicate Aircraft in Mission Editor

* Includes the new "Europe, ME & Pacific USAF bases" installations pack by Kushan
morphin
Posts: 747
Joined: Fri Apr 26, 2002 6:51 pm
Location: Switzerland

Re: CMO Public Beta - Build 1266.1

Post by morphin »

Great :D
Thank you very much
User avatar
michaelm75au
Posts: 12457
Joined: Sat May 05, 2001 8:00 am
Location: Melbourne, Australia

Re: CMO Public Beta - Build 1266.1

Post by michaelm75au »

Michael
BDukes
Posts: 2678
Joined: Wed Dec 27, 2017 12:59 pm

Re: CMO Public Beta - Build 1266.1

Post by BDukes »

Sorry guys. Found an issue. Mission editor land strike with F-22. The strike planner throws a warning and blocks stuff from going forward. Shouldn't get a speed warning if you're not tinkering with the speed at all.

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


Mike
Don't call it a comeback...
Gainful
Posts: 41
Joined: Thu May 13, 2021 1:57 am

Re: CMO Public Beta - Build 1266.1

Post by Gainful »

Sorry to say this, but I can't help but be disappointed that you guys fixed the altitude bug but completely ignored the speed bug that I even mentioned in the thread relating to this bug.

Edit: Okay, on further testing it looks like the speed works for every other setting except loiter.
c3k
Posts: 445
Joined: Mon Apr 24, 2017 11:06 pm

Re: CMO Public Beta - Build 1266.1

Post by c3k »

Great to see the rapid pace of new builds!
Transient
Posts: 110
Joined: Sat Jul 23, 2022 12:02 pm

Re: CMO Public Beta - Build 1266.1

Post by Transient »

Hi all, I have a query regarding the ATO and the “Task” column.

Under the task tab for each flight there is a whole list of mission sub types. When I tried to use it the calculated flight plan routing turns red. But I don’t see how there is any change to the flight plan routing or speed and altitude.

Is it a latent/future feature or something?
Post Reply

Return to “Command: Modern Operations series”