The great leaps of v1.11: Winchester, Shotgun, Bingo, Joker and Chicken

March 4, 2016 · Posted in Command · Comment

The v1.10 update for CMANO was released on Feb 26 to widespread acclaim. The dev team is already hard at work preparing the next upcoming major release, version v1.11. After the panoply of new features in past updates, what new tricks do the CMANO devs have up their sleeves? Let’s find out.

Winchester, Shotgun, Bingo, Joker and Chicken

Winchester and Bingo are well-known brevity calls for “no ordnance remaining” and “low fuel state” respectively. However, in many situations it would make sense for aircraft to begin separation well before they are completely out of weapons or flying on fumes. Command v1.11 adds player-customizable “Shotgun” weapon state and “Joker” fuel state, and even includes the “Chicken” fuel state for emergencies. A quick intro to these terms can be found in the Multiservice tactical brevity code article on Wikipedia and in the Command Mega-FAQ.

Click on image for full view

All aircraft loadouts now have their own pre-defined Winchester or Shotgun weapon states. The default states depend on loadout role and weapon types, which vary from all-Sidewinder F-16 air superiority loadouts to MiG-31 long-range one-pass intercept loadouts.

In some cases the player may not want to use the pre-defined Winchester or Shotgun settings stored in the database. For instance, a loadout may allow an aircraft to bore in on and engage hostiles with guns. However that may not be desirable in many situations. Therefore, the player can decide to override the default settings through the Doctrine window. Weapon states are inherited like all other Doctrine settings, and can therefore be configured per unit, per group, per mission and/or per side.

Click on image for full view

There are approximately twenty different Winchester and Shotgun settings to choose from. The first two are normal Winchester weapon states while the remainder are Shotgun setups that allow aircraft to disengage when it is most advantageous to do so. It should be noted that Shotgun states are split into two main categories: those where aircraft will start separation when certain types or quantities of ordnance has been expended, and those that will make aircraft disengage after the engagement is over. The latter is usually preferred, as the aircraft will continue fighting until the enemy has been defeated or the weapon state has been reached, whatever comes first. This means aircraft may go home with weapons left onboard, and will not hang around after an engagement is over, low on fuel and ordnance, and risk getting ambushed by flights of ‘fresh’ bogies. Past experience shows that the latter settings significantly reduces losses to own forces and has also made the AI a tougher opponent.

The user-selectable Winchester and Shotgun doctrine settings are:

Use loadout setting – Uses default weapon state settings from the database, tailored to each loadout’s role and ordnance.
Winchester: Mission-specific weapons have been expended. Disengage immediately – The traditional pain vanilla Winchester weapon state.
Winchester: Mission-specific weapons have been expended. Allow targets of opportunity with air-to-air guns – Same as above, but engage nearby bogies with guns after we’re out of missiles. Applies to air-to-air missile loadouts only. For guns-only air-to-air loadouts and all air-to-ground loadouts the behaviour is the same as above.
Shotgun: All BVR or Stand-Off weapons have been expended. Disengage immediately – Disengage after firing all Beyond Visual Range (BVR, air-to-air) or Stand-Off (SO, air-to-ground) weapons. This is a risky option as your fighter aircraft may only have one medium-range air-to-air missile (AAM) left and then decide to engage ‘fresh’ flights of bandits. Use with caution!
Shotgun: All BVR or Stand-Off weapons have been expended. Allow easy targets of opportunity with WVR or Strike weapons. No air-to-air guns – Same as above, but if easy targets or threats are nearby then shoot at them with remaining Within Visual Range (WVR, air-to-air) or SR (Short-Range, air-to-ground) weapons before disengaging. A target has to be within 120% of the WVR/SR weapons’ range to be engaged. Otherwise, the aircraft will turn, go to afterburner, and try to leave the area at max speed.
Shotgun: All BVR or Stand-Off weapons have been expended. Allow easy targets of opportunity with WVR or Strike weapons, and air-to-air guns – Same as above, but also engage bogies with guns if given an easy chance. Typically, a target has to be within 5nm and closing to be of any interest. Applies to air-to-air (A/A) loadouts only. For air-to-ground (A/G) loadouts the behaviour is the same as above.
Shotgun: One engagement with BVR or Stand-Off weapons. Disengage immediately – Attempt one engagement with BVR or SO weapons. Continue fighting for as long as there are targets within easy reach and then disengage. This is a safe option as it ensures aircraft do not ‘hang around’ after they have expended their most potent weapons, and thus avoid becoming easy targets if engaged by ‘fresh’ enemy units.
Shotgun: One engagement with BVR or Stand-Off weapons. Allow easy targets of opportunity with WVR or Strike weapons. No air-to-air guns – Same as above, but if easy targets or threats are nearby, shoot at them with remaining WVR or Short-Range weapons before disengaging. A target is considered ‘easy’ when within 120% of the remaining WVR or Strike weapon’s maximum range (minimum 5nm). In other words, the fighter won’t spend much energy chasing down a bogey after the Shotgun weapon state has been reached, and will leave the target area as quickly as possible.
Shotgun: One engagement with BVR or Stand-Off weapons. Allow easy targets of opportunity with WVR or Strike weapon, and air-to-air guns – Same as above, but also engage bogies with guns. Applies to air-to-air (A/A) loadouts only. For air-to-ground (A/G) loadouts the behaviour is the same as above.
Shotgun: One engagement with both BVR and WVR or Stand-Off and Strike weapons. No air-to-air guns – Make one engagement with BVR and WVR, or SO and Strike Weapons. Do not disengage when out of BVR or SO weapons, but continue the engagement with WVR weapons.
Shotgun: One engagement with both BVR and WVR or Stand-Off and Strike weapons. Allow easy targets of opportunity with air-to-air guns – Follows the above logics.
Shotgun: One engagement with WVR or Strike weapons. Disengage immediately – Make one engagement with WVR or SR weapons. Continue fighting for as long as there are targets within easy reach and then disengage.
Shotgun: One engagement with WVR or Strike weapons. Allow targets of opportunity with air-to-air guns – Same as above but also engage bogies with guns. Applies to air-to-air (A/A) loadouts only. For air-to-ground (A/G) loadouts, the behaviour is the same as above.
Shotgun: One engagement with guns – Make one engagement with guns. Continue fighting for as long as there are targets nearby and then disengage.
Shotgun: 25% of relevant weapons have been expended. Disengage immediately – Disengage after 1/4 of mission-specific weapons have been expended.
Shotgun: 25% of relevant weapons have been expended. Allow targets of opportunity, including air-to-air guns – Same as above, but if easy targets or threats are nearby then shoot at those too. Also engage bogies with guns (applies to air-to-air (A/A) loadouts only).
Shotgun: 50% of relevant weapons have been expended. Disengage immediately – Disengage after half of mission-specific weapons have been expended.
Shotgun: 50% of relevant weapons have been expended. Allow targets of opportunity, including air-to-air guns – Same as above, but if easy targets or threats are nearby then shoot at those too. Also engage bogies with guns (applies to air-to-air (A/A) loadouts only).
Shotgun: 75% of relevant weapons have been expended. Disengage immediately – Disengage after 3/4 of mission-specific weapons have been expended.
Shotgun: 75% of relevant weapons have been expended. Allow targets of opportunity, including air-to-air guns – Same as above, but if easy targets or threats are nearby then shoot at those too. Also engage bogies with guns (applies to air-to-air (A/A) loadouts only).

The Joker fuel state can be set as a percentage of mission fuel, which is max fuel minus reserves. If an aircraft carries 10 000kg of fuel, reserves is typically 10%, which means mission fuel is 9000kg. If the player wants an aircraft to land with 40% mission fuel remaining (3600kg + 1000kg reserve), simply select ‘Joker: 40% above Bingo’.

In addition to setting the weapon and fuel state conditions, the player may also choose what shall happen when said state is reached. Shall a flight of fighters Return To Base (RTB) when the first aircraft reaches the fuel/weapon state? Last aircraft? Or shall the aircraft disengage and leave their wingmen behind as they run out of weapons and fuel? Or should they not RTB at all? The player now has full control – and responsibility.

Tags: no tags

Out To Sea Again: Command v1.10 has been released

February 26, 2016 · Posted in Command · Comment

The cat is now officially out of the bag; Command v1.10 has been released. The full release notes are available here. Arguably the biggest pull in the new version is a longtime request of Steam-side customers, proper integration of Steam Workshop. But v1.10 has plenty of goodness for simulation freaks and casual players alike. Let’s do a quick recap:

In addition, during the public Release Candidate phase, we snuck in a lot of gunnery-related improvements and numerous fixes, DB additions and other tweaks based as always on the feedback of our users.We had a lot of fun putting this update together and we are certain you will enjoy it as much as we did.

Our attention is now turning on the next major update, version 1.11 (some of our internal beta folks are currently filing their divorce papers :)) plus a few other parallel endeavors that will be disclosed… at some point in the future.

Stay tuned!

Tags: no tags

Preparing To Launch: Command v1.10 Release Candidate 1 now available

January 22, 2016 · Posted in Command · Comment

We have been talking about this for a while, and now it’s here. Release Candidate 1 of the v1.10 update for CMANO is now available for a test drive. Steam users have received an extra dose of TLC on this round and can fetch the update by a one-click switch to the “public beta” branch as described on the release notes.

v1.10 brings a lot of small improvements and a few biggies. Let’s recap the top items:

And in addition to these, there is the usual mile-long list of smaller fixes, tweaks and improvements, in addition to a parade of new database entries on platforms, components, sensors and weapon systems.

Give it a spin and tell us how you like it, and how to make it even better!

Tags: no tags

The road to v1.10: Special Actions, Lua additions and ScenEdit improvements

January 13, 2016 · Posted in Command · Comment

This is the last in our series of posts covering the new functionality offered by the forthcoming CMANO v1.10 update. This time we turn our attention to scenario authoring and Lua scripting.

Special Actions

Special Actions are similar to TOAW’s much beloved “Theater Options”, in the sense that they allow the player to execute a number of pre-defined actions that may bring favorable results (or not – often the best way to model such actions is as high-risk gambles that can spectacularly backfire). Contrary to TOAW, Special Actions can range from the strictly tactical (“Host this SOF squad into the building”) through operational (“request nuclear release”) all the way to grand strategic (“The Assad regime requests assistance from the Russian Federation and makes Latakia airbase and Tartus harbor available to their forces”).

Special Actions are created and edited through ScenEdit (Editor -> Event Engine -> Special Actions) and are made available to the player in normal play mode via Game -> Special Actions (disabled actions are hidden). Such an action may be one-off or repeatable (through Lua it can also be made active for only a finite number of calls, ie. “you may request this 3 times”). From a technical standpoint, Special Actions act as containers for Lua scripts so they can be very powerful. Once an action is executed a message (generated by the script) is shown to the player as to what happened as a result of the action, so scen authors are encouraged to be elaborate in their explanations.

Lua improvements

Lua scripting on Conditions: The immense power and flexibility of Lua scripting is now available not only on event actions but also on conditions. Authors can combine this with the existing event triggers to create very elaborate conditional triggers.

Lua counterparts for existing conditions: The existing “Side Posture” and “Scenario has started” event conditions now have Lua counterparts: ScenEdit_GetSidePosture(SideANameOrID, SideBNameOrID) and ScenEdit_GetScenHasStarted() respectively.

New Lua function: ScenEdit_SetSpecialAction. Usage example: ScenEdit_SetSpecialAction({ActionNameOrID=”MyAction”, IsActive=”True”, IsRepeatable=”False”, NewName=”MySpecialAction”, Description=”This is a very special action”}). This is very handy if the scen author wants to activate/deactivate special actions depending on other events happening.

New Lua method: ScenEdit_GetSideIsHuman(‘SideNameOrID’) . Returns ‘Yes’ if the referenced side is currently under human control, ‘No’ otherwise.

New Lua method: ScenEdit_SetLoadout. Usage example: ScenEdit_SetLoadout({UnitNameOrID=”Viper #1″, LoadoutID=631, TimeToReady_Minutes=45, IgnoreMagazines=”False”})

Length limit of Lua scripts: The limit has been raised to tens of millions of characters.

You can now order a unit to RTB via Lua: Using the existing ScenEdit_SetUnit method, use the “RTB” key (e.g. RTB=’Yes’)

You can now host a unit to a suitable parent unit/group via Lua (e.g. aircraft to airbase, small boat to larger ship etc.). The new method is: ScenEdit_HostUnitToParent(table). Usage example: ScenEdit_HostUnitToParent({HostedUnitNameOrID=’Eagle 1′, SelectedHostNameOrID=’Bitburg AFB’}) . The unit to be hosted is ‘snatched’ either from mid-air or from its current host.

You can now edit a unit’s fuel level through Lua. Usage examples:
a=ScenEdit_GetUnit{side=’a’,name=’test’}
print(a.fuel)
{ [3001] = { current = 240000, max = 240000 }, [4001] = { current = 3750, max = 3750 } }
fuel = a.fuel
fuel[3001].current=1000
a.fuel = fuel

ScenEdit and Event Engine improvements

* An extra criterion, “minimum classification level”, has been added to the “Unit Detected” trigger. This allows the scenario author to tailor the desired level of target classification reached (everything from simply “detected” all the way to “precise ID”) before the trigger is actually fired. For backwards compatibility, the default level is “Detected – Known Domain”.

* You can now clone events, triggers, conditions and actions.

The v1.10 update for CMANO will soon be available as a Release Candidate on the MatrixGames forum. Stay tuned!

Tags: no tags

The road to v1.10: Electronic warfare improvements and weight-dependent aircraft kinematics

January 4, 2016 · Posted in Command · Comment

Happy new year!

Command Build 757.12, which had been made available unofficially at the start of December, has now officially been released through MatrixGames and Steam. Barring any emergencies, this is probably the last update released as part of the post-v1.09/NI release support process. The development team’s focus is now the next major public update, designated v1.10. Let us take a look at the some of the major improvements that the new version will feature.

Electronic warfare improvements

Image: Jamie Hunter / www.aviacom.co.uk

A rather consistent piece of feedback we have received since the original release of Command is that the offensive jamming (OECM) systems of many aircraft appeared to be overpowered against their target emitters. The “poster child” for this issue was the EA-18G Growler, which was able to flood with jamming even very modern SAM systems such as the S-400/SA-21, to the point where the aircraft was able to even overfly such a SAM battery with impunity.

We investigated these reports, and concluded that the fundamental problem was that our radar/ECM formulas, while technically quite accurate, failed to take into account the various counter-countermeasures (and counters to them, and counters to the counters, ad naseum…) that are applied by both radars and the jammers that target them. Discretely incorporating these techniques in a public-domain simulation is tricky, not least because non-classified information is scarce, both on the details of these techniques and also as to which system supports which tricks.

However, we already had at our disposal a successful template for abstracting and emulating these factors: The technology generation system, employed already on defensive jammers (DECM). We were also informed of the decisive advantages of phased-array systems (and especially AESAs) in countering most jamming techniques.

So here are the steps we undertook to improve the OECM modelling:

* As described, tech generations are taken into account when preparing the variables used on the radar/ECM formulas. The greater the generation difference between jammer and radar emitter, the more pronounced the effect is; so for example a very modern jammer like the forthcoming NGJ has a fair chance of defeating a modern radar like the 96L6 Cheese Board or the YLC-27, while it will laugh at older systems like (non-modernized) Tall King or Spoon Rest. (The other already-existing factors that affect jamming effectiveness like distance, positional geometry, sidelobes, emission characteristics like beamwidth, frequency band, PRFs etc. etc. are all still there and are critical as ever, but the tech-gen gap adds an extra wrinkle.)

* Phased-array systems get decisive bonuses both on the radar and on the jammer side (NGJ is an example of the latter). AESAs in particular are able to ignore many OECM techniques altogether thanks to their very low sidelobes, high SNR and advanced beamforming capabilities.

As an example of how these refinements affect tactical employment, we ran the popular but artificial “lone EA-18G jam-attacks S-400 battery head-on” strawman setup. In this case the SAM battery was using only 48N6DM missiles (TVM/SAGG guidance) and was supported by a 91N6 (Big Bird D) brigade-level surveillance radar. The 91N6 briefly detected the Growler at 168nm but immediately lost it again. It was able to re-detect it and hold it reliably only at 71nm. The battery’s 96L6 (Cheese Board) acquisition radar detected the aircraft at barely 14nm, and the 92N2E (Grave Stone) fire-control radar was able to achieve missile lock at just under 7nm (…cue the fanboy hordes screaming that our numbers are way off).

(As an aside, the large range gap between firm target track and reliable TVM/SAGG missile lock may help explain the design rationale for fitting both the 40N6 and 9M96 missiles [the other two weapon options for S-400 batteries] with active-radar seekers. In theory, both of those missile types could have been launched against the EA-18G as soon as a reliable track was achieved and the contact entered their respective kinematic envelopes.)

So as we see, modern OECM systems are still quite effective even against modern radar systems but not nearly as omnipotent as was hitherto the case. Against older threats, modern jammers remain overwhelmingly effective as has been repeatedly demonstrated in real-life air operations in the last few decades.

Weight-dependent aircraft kinematics

Fully populating the aircraft loadout entries in the DBs with weight and drag data has enabled us to refine a significant aspect of aircraft kinematics: The effect of weight on agility and manouvering. Until now, although weight and drag were taken into account for fuel consumption puproses (and indeed were re-calculated continously so that e.g. an aircraft that dropped its bombs would immediately experience a benefit in endurance and range), the aerodynamic performance itself (including evasion against attacks) always assumed an “airshow” configuration (minimal external stores, half-full fuel load). This mostly worked for air-combat loadouts but could cause significant distortions in evaluating attacks against heavily-loaded aircraft.

So now the actual aircraft weight, including fuel and stores, is continously calculated as the “weight fraction” (compared against the nominal “airshow” values and the maximum take-off weight) and it has a decisive effect on actual performance. Sustained turn rate, climb/dive rate, acceleration and attack evasion agility are all affected by this.

As an example, a USAF F-16CM Blk52 (2014) with a light A2A-patrol loadout (2x 370USG tanks, 4x AIM-9X, 1x ALQ-184 DECM pod) at 36Kft has a weight fraction of 0.44 with full internal fuel. With this fraction the aircraft has a 16.7 deg/sec sustained turn rate (against the nominal 22.8) and its evasion agility is reduced from the nominal 4.9 to 3.6 (not taking into account any other factor such as crew proficiency, impact angle etc.). In contrast, the very same aircraft in a heavy attack loadout (2x 370USG tanks, 2x GBU-31(V)1 JDAM, 2x AIM-120C-7, 2x AIM-9X, 1x AAQ-33 Sniper-XR pod, 1x ALQ-184(V) DECM pod) has a weight fraction of 0.68, which reduces its turn rate to 13.4 deg/sec and its evasion agility to just 2.9.

As fuel is consumed this fraction steadily decreases and the aircraft performance increases, and of course even more so if the loadout stores are expended.

So if you have been watching the news and see aircraft on actual ops carrying much fewer stores-per-sortie than the “Christmas tree” brochure drawings, part of the reason is range/endurance but a significant consideration is also this: Too much weight can really get you killed.
On the next post, we will take a look at the most significant ScenEdit & Lua improvements that v1.10 brings.

Tags: no tags

« Previous Page — Next Page »