The scenarios of Desert Storm – Part 1

March 21, 2019 · Posted in Command, Uncategorized · Comment 

The new “Desert Storm” DLC is now well into production, and is set to launch on March 28 (see the trailer!). The companion v1.15 update has also been released, and the dev team is already tweaking the new features and fixing issues based on early feedback. Let us take a look through the scenarios available in this battleset and explore the historical and hypothetical events that it surveys.


1. Invasion

Coalition vs. Iraq

Date/Time: 1 August, 1990/ 23:00:00 Zulu
Location: Middle East
Duration: 48 Hours
Playable Sides: Coalition

On August 2, 1990, the world watched in stunned surprise as Iraq’s elite armor divisions invaded and conquered Kuwait within two days.

This irrevocable act was the culmination of years of disputes between the two states. During the Iran-Iraq war, Kuwait had made a series of large loans to Iraq totaling over $14b. By the war’s end in 1988, Iraq was unable to repay and repeatedly asked Kuwait to forfeit the debt, arguing that by standing up to Iran it had indirectly protected the small, wealthy state. Furthermore, Iraq accused Kuwait of “drinking its milkshake”, i.e. using slant-drilling techniques to exploit oil reserves from the Iraqi portion of the rich Rumaila field.

The US administration, balancing between its long-standing allies Saudi Arabia and Kuwait, and its desire to continue using secular Iraq as a bulwark against fundamentalist Iran (as it had done throughout the 1980s), had long been trying to mediate a solution that would placate all sides. During the spring and summer of 1990, Iraq’s military preparations were closely observed by western intelligence but were interpreted as a show of force designed to intimidate Kuwait and third-party negotiators rather than as the prelude to action. On July 25, the US ambassador met with Iraq’s leader, President Saddam Hussein, to reaffirm that (a) the US was committed to a peaceful resolution of the disputes between the two states and (b) that they held no opinion or favor towards either side in the disputes themselves. Hussein apparently interpreted the former as a token statement and the latter as a tacit approval of his regional ambitions. He thus finalized his operational plans and, just one week later, set them in motion.

The US Central Command (CENTCOM) had long-prepared plans for the rapid transfer of heavy US forces in the Middle East and Arabian peninsula. The concept of the Rapid Deployment Force (RDF) postulated a sudden threat to the oil fields of Iran or Saudi Arabia, in both cases from a sudden Soviet invasion out of Afghanistan or the Caucasus TVD. To counter such a threat, multiple rapid-reaction forces and schemes were put in place: Elements of the 82nd Airborne Division were on a constant two-hour alert, with a brigade-size commitment scheduled 18 hours later; division-sized army forces were to be airlifted and delivered within 2 weeks; multiple container ships pre-positioned in the Persian Gulf and Indian Ocean carried supplies to be used by the arriving troops; multiple tactical and strategic airwings were earmarked for immediate relocation, and more. CENTCOM regularly practiced these plans in concert with regional allies, e.g. the bi-annual “Bright Star” exercises held in Egypt.

Though nobody on the ground yet knew it, all these plans and preparations were about to be put to the real test.


2. The Thin Red Line

Coalition vs. Iraq

Date/Time: 15 August, 1990/ 20:00:00 Zulu
Location: Middle East
Duration: 38 Hours
Playable Sides: Coalition

 

“I can tell you this, those first few nights were pretty strenuous, we didn’t have very much to stop ’em. [If the Iraqis attacked], the plan was to hit the supplies for the attacking army, slow ’em down that way, and meanwhile we kept a full tank of gas in all of our cars and we were ready to [withdraw] to Jeddah (Red Sea coast).”

– Charles Horner, commander of coalition air ops on Desert Shield / Desert Storm

Emboldened by his army’s swift success in conquering Kuwait and its oil fields, Saddam Hussein considered a possible advance into Saudi Arabia.

US reinforcements had already started pouring into the country, but slower than required, because the Saudi monarch was unconvinced that Iraq would invade (Saddam had privately assured the Saudis that Kuwait was his sole objective). A massive global air/sea-lift operation was well underway, but forces and supplies were by necessity streaming in piecemeal and simply getting the right people and hardware where they needed to be was challenging. In many ways, the rapid-reaction force being assembled in Saudi Arabia during August & September was a rag-tag motley crew of assets. Opposite them, just across the border stood Iraq’s best armored units, flush with confidence, ready to advance on a moment’s notice.

If that armored fist had crossed the border, would the thin red line have held?


3. First Night

Coalition vs. Iraq

Date/Time: 17 January, 1991 / 00:00:00 Zulu
Location: Middle East
Duration: 48 Hours
Playable Sides: Coalition

Two Soviet generals sit at a café in Paris, watching the Red Army’s victory parade. One of them turns to the other and asks: “By the way, comrade, who won the air war”?

This grim joke, popular in NATO circles in the 1970s and 80s, reflected a common prevailing wisdom distilled from the lessons of WW2, Korea and Vietnam: Airpower alone had never been able to decisively determine the course of a war.

The potential of airpower as a paradigm-shifting strategic weapon had been evident since its inception. Capable of bypassing the front lines to strike at the enemy’s heartland, it might end wars in days, rather than the years of brutal front-line attrition required in past conflicts. A century of failed attempts dispelled the dream; the reality was an attritional war of fighters and flak (and more recently SAMs), as bloody as anything earthbound. The same applied to direct destruction of fielded enemy forces; airpower was important, but as plenty of experience attested, never dominant.

As the US-led coalition air forces prepared for their first round of offensive operations against the Iraqi military, a lot was riding on the men and machines tasked with the job. The machines themselves were a mix of old and tried, and new and untested. The US military still lied in the shadow of the failures of Vietnam, where “a thousand tactical victories” had nevertheless ultimately resulted in strategic and political defeat. The directives from the highest level were clear as crystal: This would not be allowed to turn into another Vietnam. Strategic victory had to be achieved swiftly, massively and decisively – in other words, unlike any previous major conflict the US and its allies had ever fought.

Some students of airpower pointed to Israel’s swift victory in 1967 (and especially the first-day annihilation of the Egyptian air force) as a possible model to emulate. While there was indeed much to learn from the Arab-Israeli conflicts of the past (indeed, Israel’s extensive use of electronic warfare in 1982 did not go unnoticed and was to be intensely replicated), the reality was that the conditions that enabled the IAF to triumph in 1967 had come and gone. Low altitude was no longer a safe sanctuary for strike aircraft; Radars had become more resistant to jamming; Aircraft were no longer parked in long rows in the open begging to be bombed & strafed, each instead now being individually protected by a hardened aircraft shelter (HAS) seemingly impervious to anything but a dead-on nuclear impact. Catching the Iraqi air force on the ground and wiping it out within a few hours was a pipe dream. The Iraqi integrated air defence system (IADS), an odd mix of Soviet-supplied radars and SAMs together with a backbone of mostly French-originated command, control and communication infrastructure (a detail that turned out to be eminently exploitable) appeared to be a very tough nut to crack. Campaign planners, by every right a conservative group, estimated potentially heavy aircraft losses for the first nights of intense airstrikes.

Desert Storm would famously prove the “never dominant” claim invalid, but before airpower savaged the Iraqi army itself, it reached one more time for the first and dearest dream – overwhelming and instant strategic supremacy. The first night’s strikes on Iraq proper saw a dizzying ballet of assets, coordinated by modern AWACS and satellite communications, overwhelm Iraq’s air defenses, plaster its airbases and hammer its C3 infrastructure – simultaneously. Assets ranging from fighters and bombers to attack helicopters to drones to cruise missiles struck their targets with impunity, but none more boldly than the F-117s which braved Baghdad itself, hit their targets, and returned without loss.

To what extent those first-night strikes realized the traditional goals of strategic airpower – especially the shattering of enemy morale – is a question still debated and might never be truly answered. But one promise, beyond a shadow of a doubt, had finally been realized: At long last, the bomber had gotten through.


4. The Gates of Hell

Coalition vs. Iraq

Date/Time: 18 January, 1991 / 04:00:00 Zulu
Location: Middle East
Duration: 36 Hours
Playable Sides: Coalition

Prior to Iraq’s invasion of Kuwait, it had been established that Iraq possessed a significant chemical weapons capability. Iraq’s military had used chemical weapons on numerous occasions against Iran, as well as various rebel groups such as in Kurdistan. By the time of the coalition build-up during Desert Shield, the consensus of western intelligence agencies held that Iraq still had a sizable chemical arsenal, had likely forward-deployed these weapons, and was prepared to use them against coalition forces.

The concern about Iraq using WMDs as a counter to the coalition’s superiority in conventional forces prompted numerous US officials to implicitly or even explicitly state that the US would respond to such an attack with WMDs of its own, probably employing tactical nuclear weapons.

At the tactical and operational level, Iraq’s chemical weaponry constituted one of the prime strategic targets of coalition air power. The effort to neutralize it was two-pronged: chemical agents still stored in their rear-area bunkers were attacked before they could be deployed; and ready-forces already outfitted with chemical warheads (Scud missile batteries, artillery units, etc.) were prioritized by coalition airpower. But as frequently happens with such plans, the best efforts still resulted in misses and leakers.

On January 18, the second day of Desert Storm, Iraq’s President Hussein – dismayed by Iraq’s inability to resist the coalition’s massive aerial onslaught – conveyed an ultimatum to CENTCOM headquarters: unless coalition forces immediately ceased offensive actions and withdrew from Kuwait, Iraq would strike coalition troops and/or any city of their choice with chemical weapons.

While US forces scrambled to locate and neutralize the chemical threat immediately, other standing-alert assets prepared to deliver the nuclear response the US had committed to. The gates of hell were about to swing open…


5. Scud Hunt

Coalition vs. Iraq

Date/Time: 19 January, 1991 / 00:00:00 Zulu
Location: Middle East
Duration: 36 Hours
Playable Sides: Coalition

Saddam Hussein’s first serious reaction to the commencement of Desert Storm was to unleash a protracted bombardment of Israel (and to a much lesser extent Saudi Arabia) using Iraq’s considerable arsenal of SS-1C Scud-B tactical ballistic missiles (TBMs). While the strikes against Saudi Arabia were merely punitive gestures, attacking Israel was an astute political gambit: if Israel retaliated, as Hussein hoped, reawakened anti-Israel fervor in the various Arab states that had either remained neutral or actively joined the coalition could fracture the alliance mere days into the campaign.

CENTCOM planners and Schwarzkopf himself had neglected the Scud threat up to that point, correctly considering the missiles as militarily insignificant without WMD warheads (which the US nuclear deterrent would preclude.) Though tactically and operationally ineffective, they had suddenly become a serious strategic/diplomatic threat. Persuading Israel to hold back was no easy task, again demanding multiple parallel measures. First, several Patriot batteries with PAC-2 missiles (optimized for TBM engagements) were hurriedly deployed to key Israeli target areas like Tel Aviv. Secondly, Iraq’s TBMs and launchers became priority targets for air campaign planners.

The missiles installed in fixed launchers at the large H2 and H3 airbases in western Iraq were straightforward enough to attack; however, most Iraqi Scuds were deployed on highly mobile 8×8 transporter/erector/launcher (TEL) vehicles exploiting the vast Iraqi desert to hide themselves. To destroy them, a large portion of available coalition aircraft and special operation forces (SOF) teams were re-tasked to seeking out and eliminating Scud TELs exclusively. This veritable “needle in a haystack” hunt would become the longest operation of the entire conflict and a maddeningly frustrating experience for everyone involved.


6. Reviving a Giant

Coalition vs. Iraq

Date/Time: 24 January, 1991 / 00:00:00 Zulu
Location: Middle East
Duration: 48 Hours
Playable Sides: Coalition

By January 20th, 1991, the initial strikes on Iraq had been highly successful, destroying or degrading much of Iraq’s communication and anti-air capabilities. However, the coalition naval fleets in both the Eastern Med and Persian Gulf had by this point expended most of their long-range land-attack capability. In particular, the Persian Gulf Task Force needed to replenish its stock of Tomahawk cruise missiles as soon as possible.

Historically, two Iowa Class battleships, Missouri (BB-63) and Wisconsin (BB-64), played a part in the Gulf War. Four Iowas were built during WWII and two other keels were laid – the Illinois (BB-65) and Kentucky (BB-66). These two hulls were to be the Iowa’s follow-on class, the “Montana Class” battleships. In real life, the end of WWII halted their construction and they were never commissioned. The BB-65 hull was broken up in September 1958.

In the 1950s, several proposals were floated to complete the Kentucky as a guided missile battleship. This project was authorized in 1954, and Kentucky was renumbered from BB-66 to BBG-1, only to be canceled later.

Conversion of the 73% complete Kentucky would have entailed extensive refits to replace the two original aft 16″ turret barbettes with an assortment of missile launchers and sensor systems. Apart from Phalanx CIWS, quad Harpoon launchers and Tomahawk armored-box launchers received by the four Iowas during their 1980s modernization, the Kentucky would also have room for multiple SM-2 Standard area-defence missile and Sea Sparrow point-defence missile launchers, plus their associated air search and SAM-illumination radars. Its original twin 5-inch gun turrets would’ve been replaced with modern Mk45 guns. If employed correctly, the last of the BBs would have been a fearsome addition to coalition naval power.

In this hypothetical scenario, the conversion was completed instead of abandoned, and BBG-1 Kentucky has been commissioned into service, receiving subsequent modernization during the 1980s similr to the Iowas. The Kentucky and her accompanying escorts and supply ships have been tasked to reinforce the Coalition’s naval force in the Northern Persian Gulf and relieve the first-strike shooters.


7. Israel Stands Up

Israel vs. Iraq/Gaza

Date/Time: 26 January, 1991 / 23:00:00 Zulu
Location: Middle East
Duration: 36 Hours
Playable Sides: Israel

Desert Storm was arguably the strangest war in Israel’s military history. Even though a nationwide state of emergency was declared, and the Israeli Defence Forces (IDF) were put on alert, the order to commence offensive operations never came.

Saddam Hussein had attempted to turn Iraq’s dispute with Kuwait into a larger Arab-Israeli matter long before the air campaign started. For example, on August 12, 1990, just ten days after the Iraqi invasion, he had publicly suggested that Iraq might withdraw from Kuwait if Israel withdrew from all occupied Arab territory and Syria withdrew from Lebanon. Unsurprisingly this proposal drew considerable praise from the Arab world, even from principals that were otherwise critical of Iraq and its invasion.

Hussein’s order to fire a protracted barrage of Scud missiles against Israel right after the beginning of the coalition air campaign was therefore a step-up in this shrewd political maneuver: he attempted to draw Israel into battle, thus transforming what had started as an Arab-Arab conflict into an Arab-Israeli conflict, one in which Iraq would suddenly find new allies. Realizing this, the US-led coalition urged Israel to “stay down” and take the punches on the chin. It was necessary to keep Israel out in order to keep the Arab states on the side of the coalition. To demonstrate the US commitment to Israeli defence, a number of Patriot missile batteries were hastily ferried to Israel to provide additional ABM cover, and a substantial part of the coalition’s tactical airpower was dedicated to eliminating the Scud threat at its source. The Israeli government understood the stakes and, despite suffering repeated Scud impacts on Tel Aviv and elsewhere, held fast.

In this hypothetical scenario, Saddam’s gamble paid off: mounting public pressure in Israel from the relentless Scud bombardment has reached the breaking point. Rumors are spreading that dissident Arab factions within Palestine and the Gaza Strip are assembling material, supplies, equipment and personnel to launch independent attacks against Israel in support of Iraq’s pressure. The government feels that it has to respond, even in a limited fashion, or completely lose legitimacy. Israel’s gloves are about to come off.

Companion to Desert Storm: The v1.15 Command update is available

March 19, 2019 · Posted in Command · Comment 

So, the free v1.15 update for Command is now available to both Steam & Matrix users. The release notes are currently available here. The Desert Storm DLC is also currently in production and will be released very soon.

This update rolls up all the minor updates that we have released since the launch of v1.14 and the “The Silent Service” DLC, and brings together a lot of small improvements and some big major new features. Let’s briefly walk through them:

  • Personal persistent map profile. You asked for it, we explained to you why it’s generally a bad idea, you understood and insisted, so we are giving you the rope to hang yourselves with once more demonstrating our customer-oriented approach. It is optional and disabled by default, so you actively have to enable it in order to use it and love it (or more likely, hate it).
  • Dynamic ORBAT window: This is a genuinely good idea, and a bit overdue. This makes the ORBAT window more useful as a “live tally” of friendly forces, and also very handy for quickly jumping around a large theater of operations by selecting the desired unit.

It also makes ultra-wide monitors genuinely useful

  • The “Magazines” and “Weapons” window received massive speed optimizations, so they are much easier to use even with units/installations with bazillions of different weapons and magazines (looking at you, Burke DDGs and Incirlik airbase).
  • Visual and IR sensors are no longer precise insta-spotters, except at very short ranges. This removes the overpowering effect of these sensor types and restores the advantage of ranging-capable sensors (radar, laser etc.). They are still very useful, but now they have to be combined with other sensors (or in pairs, e.g. for cross-bearing) to provide useful geolocation for subsequent engagements.
  • No more “blind AMRAAM shots”. We covered this recently, but it is a major improvement so worth repeating. There is a good reason everyone is trying to develop CEC technologies and tactics nowadays.
  • New doctrine setting specifically for BVR engagement behavior: This is a hidden gem, and part of the real reason that western fighters tend to have a better real-world BVR record than their Soviet/Russian/Chinese counterparts so far. Try it out and see what difference the various tactics make.
  • Updated terrain data for Spratlys and other areas.
  • The submarine snorkelling noise penalty is now gradual (depending on sub throttle) instead of a binary yes/no. This can make anti-SSK hunts more challenging if the sub captains are careful.
  • Serious sim-performance improvements on heavily-populated scenarios. Monsters like the 12K+ AU “why the hell not” setups now run significantly faster than real-time.
  • Approximately 2 billion new Lua methods available to scenario authors; including some real teasers like updating satellite orbits, preserving damage on a unit from one scenario to the next, exporting .inst files, enumerating through contact emissions (Wild-Weasel AI!), retrieving cargo properties and much more.
  • Content updates & additions a-plenty; Updated databases & official scenarios, new and updated tutorials, and more.

Now, onwards to the Desert Storm battleset!

More realistic restrictions on remote-cued AAW engagements: Small change, big ramifications

February 16, 2019 · Posted in Command · Comment 

So, one of the subtle changes we recently introduced as part of our regular service updates to Command has generated something of a spike on tech support questions. Here is a fresh example:

 I am having a problem: When my units attack with [AAW weapons] it says “Firing unit most obtain from itself or another CEC-enabled platform a high-quality track on the target before firing”. What is the meaning of this? I never encountered this message before.

So let us backtrack a bit and examine this in detail.

What the above report is describing is actually the correct behavior, a result of a major simulation improvement introduced in Build 998.14 last November:

MAJOR FIX: Resolved the long-standing issue of “blind AMRAAM shots“: 
– Units firing AAW ARH weapons (e.g. AMRAAM) must now actively detect the target on their own radar before being able to fire the weapon (ie. it is no longer enough to receive offboard contact from e.g. AWACS and fire based purely on that). This makes it much more challenging to employ AMRAAM-class weapons against stealthy targets or in a heavy-OECM environment. 
– After launching an AMRAAM-class weapon, the unit must still keep detecting the contact in order to provide mid-course guidance to the missile. If radar contact is lost for more than 5 seconds, the missile goes into a “blind” state and flies straight ahead (similar to SARH weapons who lose guidance). (Appropriate AI/EMCON logic has been added to encourage this). 
Note that CEC-capable weapons can still be launched and mid-guided by a suitable outside datalink-parent platform, as before. 

Now of course most players don’t read release notes (or manuals), but the importance of this change is hard to overstate. This is in some ways another important step towards more faithful modelling of the limits of side-wide command & control of operations, as well as cooperative engagements.

In previous versions of Command (as well as all other similar titles), once a unit has a hard contact on a target, the contact information is immediately shared with all other units on the same side (unless they are off the comms grid) and is considered “fire control grade”: Based on this information, even units that have no sensor contact with that target can engage it with any suitable weapons, especially those have a lock-on after launch (LOAL) capability or terminal guidance. While this is usually “good enough” for a typical Harpoon/Exocet salvo or non-precision artillery fire, anti-air warfare (AAW) tracks have much higher precision & accuracy requirements, due to the speed and agility of the targets being engaged. This created a sim realism flaw, and a game exploit: It was possible, for example, for fighters to use offboard tracks provided by EW/GCI radars or AWACS to fire weapons like AMRAAM at targets without having to detect them themselves (this allowed players to deal with stealthy opponents much more easily than they should). In reality this is a major aspect of cooperative-engagement capability (CEC), and is a feature that most air arms still lack.

The B998.14 update fixed this problem: Offboard contacts are still disseminated but, in the case of air contacts, are by default considered as “not fire-control grade quality”. In fact, even on-board detections by non-FC sensors are insufficient: For example, a Su-27 detecting a target on its IRST can use that information to manouver against the target and maybe launch an infrared missile like the R-73/74, but it can no longer blind-fire an ARH weapon like the R-77 or PL-12: It must now first gain a solid onboard radar track on the target.

Here is a common off-board track example:

An orbiting KJ-2000 has made a detection on an incoming intruder. A nearby J-11B has been directed to investigate, and using its IRST has identified the contact as a hostile F-35A. However, if we instruct it to engage it with its PL-12 missiles, we get this:

 

So, how can we verify that this is indeed happening because the J-11B cannot get a radar lock on the target? We select the contact and use the “Last detections” panel, a UI addition introduced with Command v1.14 & The Silent Service:

We see that, indeed, the target so far is detectable only by the AEW radar and the ISRT on the J-11B. This is why we cannot engage it yet.

Obviously, this has significant ramifications for AAW engagements with modern ARH weapons. Stealthy aircraft, or assets covered with heavy ECM interference, are now particularly difficult to engage even with early warning (this, BTW, is one more reason that the SR-71 was notoriously difficult to engage – even when the missile geometry was right, its jammers were very effective). Fighters with ARH missiles and in a networked environment can remain EMCON-silent for the majority of their patrol, but to actually engage their assigned targets they have to emit even for a short duration – and for non-LPI sets this can be a dangerous tactical decision.

This also highlights one more decisive benefit of CEC. In addition to enabling engagement geometries hitherto impossible and bypassing LOS blocks, CEC also removes the “mandatory onboard FC-quality track” as a requirement from the prefire checklist. First introduced in Swedish Viggens in the mid-90s as part of their AMRAAM upgrade, this capability has also been adopted by the JASDF’s AAM-4 missile and MBDA’s Meteor, while service-wide adoption of weapons like the SM-6 and AIM-120D is spreading this capability to the USAF/USN.

This change is part of an ongoing series of improvements in CMANO’s air combat model; more changes are coming in future updates, which will introduce even greater fidelity and force players to rely even more on real-life tactics and procedures to succeed in the virtual arena.

Debrief: A week of Command PE training at the Luftwaffe Officer School

February 2, 2019 · Posted in Command · Comment 

During the week of January 14 to 18, select members of WarfareSims and MatrixGames LLC presented Command PE at the Luftwaffe Officer School and trained officers of various branches of the German armed forces in its use and capabilities. It was a very successful event, and we would like to thank the entire staff of the academy, and especially Maj Silier, Lt Col Lochner, Lt Fleischmann and Lt Scholz for their coordination of the event and the above-and-beyond hospitality that they extended to us.

Following is the English translation of the official description of the event, as presented on the Luftwaffe website (original here).


“Command” – Digital practice for the real world
Berlin, 21.01.2019

Many factors determine the outcome of a battle: from the logistics and the deployment of the soldiers, to the morale of the troops or the supply of equipment. Ultimately, it is crucial to consider all factors and to deduce the right tactics from them. For this purpose, course participants at the Officer School of the Air Force use the simulation software “Command: Modern Air / Naval Operations”.

The program is used to represent air operations. The trainees get a fictional scenario by considering all the factors relevant to a battle and then having to plan their operations. “We then integrate the planning of the course participants into the software and see if their plan works,” explains Major Thomas Silier. He is a specialist in air force doctrine & tactics, and also the project manager for the introduction of Command at the Officers School of the Air Force (OSLw).

In fact, the software was originally designed not for the military but as a publicly available game. However, battles, and especially various air operations, are depicted so realistically that “the German and even the American armed forces have realized that Command has the potential to be used by them” explains Silier. For example, the software provides a comprehensive database of every aircraft from any armed forces back to 1946.

Down to the smallest detail: from planning to simulation

The course participants are divided into different groups. All teams get different tasks that they have to plan for. For example, a group is responsible for protecting the airspace above the operational area. Another, in turn, is responsible for Close Air Support, which is the frontline aerial support of ground forces, ” says Silier. Then it’s about achieving common coordination. The fuel for the aircraft used must be determined, tankers must be on site in time and the respective operating times of the forces must be deduced.

“I am very impressed by how complex the program is,” says Lieutenant Markus Kribelbauer. He used the program as a participant in the last officers’ class. In addition, he was fascinated by how much work Silier and his team have invested in addition. “From creating custom Excel spreadsheets to determine operating times to calculating the fuel consumption of the respective aircraft – I found that extremely impressive,” he says enthusiastically.

Kribelbauer is certain that, for the Luftwaffe, the program definitely offers added value: “Whereas previously you had to present lessons with Power Point or othertools, and now you can present everything actually simulated, the software offers a great deal of added value.”

Therefore, it is now being examined whether the software can also assist other areas of the Air Force. The program will be tested in a three-month trial period. Representatives of the various branches were recently briefed in Fürstenfeldbruck about the program. If Command makes a positive impression here as well, then the software could soon be used not only at the Luftwaffe Officer School, but in wider parts of the Air Force.

Command LIVE: The King of the Border is released

January 31, 2019 · Posted in Command · Comment 

Buy on Steam: https://bit.ly/2CUQhVf

Buy on MatrixGames: https://bit.ly/2DpaLHe

« Previous PageNext Page »