Command video: Making a simple opposed TLAM-strike scenario

January 18, 2012 · Posted in Command · Comment 

Jakob, a member of the Command development group, has been flexing his video-producing muscles lately and Command was bound to offer a tempting vehicle. In this video, Jakob demonstrates how to put together a very simple strike-oriented scenario.

(as always, best watched in HD)

 

This is a simulated exercise in which “Blue” (a single A. Burke-class destroyer) attacks a “Red” airfield (Hazerim airbase in Israel) using Tomahawk TLAM cruise missiles. The primary targets are the base runways. The base happens to be the least-covered by ground-based air defences in Israeli territory (most SAMs and ABMs are eastward-oriented), and for this reason a CAP screen of F-15I fighters and Phalcon-AEW aircraft is provided.

We have shown airfield attacks before, so the heart of the video is the ease & speed with which a simple scenario can be constructed using Command’s built-in scenario editor. The video covers all the steps necessary, from creating sides and defining their postures to loading up installations, creating strike & AAW-patrol missions, equipping the airbase with appropriate aircraft weapons etc.

Jakob has stated that he has more videos in the pipeline. If his first attempt is that good, one can hardly wait.

Tags: no tags

Command video: Realistic satellites

November 12, 2011 · Posted in Command · Comment 

One of the years-long pet peeves of Command’s development team has been the hands-on, realistic implementation & inclusion of air/nav ops-relevant military satellites; their orbital characteristics, systems, abilities and vulnerabilities.

And now, the time has come to make it happen.

 

(As always, viewing in HD is recommended)

This short demonstration depicts three different satellites in orbit:

  • Cosmos-626, a Russian RORSAT.
  • USA-186, a US KH-12-series imaging satellite.
  • USA-200, a US Jumpseat-2 signals-intelligence satellite.

The different trajectories demonstrated are based on publicly available data on these satellites and are, naturally, tailored to their respective missions: Cosmos-626 with its low inclination frequently sweeps the Atlantic, Pacific & Indian oceans as well as the Norwegian Sea, and USA-186 follows a low-perigee (just 264km), near-polar orbit to maximize its daylight coverage. Likewise, USA-200 follows a highly-elliptical Molniya-type orbit that allows it to “hover” over the African continent in order to intercept signals from Europe, Middle East and Asia.

Satellites in Command are treated very much like any other platform, with the obvious exception of their kinematic characteristics. They can be equipped with weapons, sensors and any other components available in the DBs. Because a satellite may shift its orbit one or more times during its active life (and thus have multiple orbital profiles), we plan on compiling a detailed list of historical data on each system’s known orbits. The idea is to provide the scenario author with a minimum-hassle mechanism of adding historically-accurate satellite systems into a scenario: This requires filtering both by operator country and in-service/out-of-service dates (sat gurus will already have noticed that Cosmos-626, a ‘70s system, could have never actually flown in parallel with the two US systems, which were launched in the 2000s).

Props to anyone who can identify the soundtrack, and its relevance, without using a tune-recognition app…

Tags: no tags

HAF celebrates its 100 years

November 4, 2011 · Posted in Uncategorized · Comment 

Join us at Tanagra AFB on November 6!

afisa1_big
afisa8_big

Tags: no tags

Command presented on Serious Games Showcase & Best Practices 2011

October 24, 2011 · Posted in Command · Comment 

041As previously announced, Command was exhibited on Serious Games Showcase & Best Practices 2011, an all-day event organized by the Laboratory of New Technologies in Communication, Education and the Mass Media in cooperation with the Hellenic-American Union. Build 186 was available and running on local PCs, free for visitors to experiment and give it a try (and well they did, particularly those with military background).

The people’s reception was enthusiastic, particularly by visitors who had been informed of Command’s existence only recently through the announcement. The Lab’s head professor (a man not easily impressed, as we were afterwards informed) was left commenting “you guys are dangerous…!”. In another amusing instance, a pair of visitors sat down to have a peek at Command “although we’re not really much into these militaristic games, what with all the violence promotion…”. A few minutes later we were dissecting the optimum engagement geometry for a high-deflection AMRAAM BVR shot – not too shabby!

We would like to thank everyone who took the time to visit us and provide us with invaluable feedback as well as precious encouragement. We hope to present an ever better product at future exhibition opportunities and, of course, there is also the prospect of a public beta on the horizon.

Tags: no tags

Command September 2011 update – Part II

September 28, 2011 · Posted in Command · Comment 

In Part I of this update we looked at progress in underwater warfare, general game mechanics and UI. Here we focus on improvements in air operations, tactical AI, and sensor & weapon modeling.

Air Ops

image- The scenario designer can now mark any aircraft as unavailable (for maintenance etc.), and the aircraft can remain so for the full duration of the scenario or until a specified datetime.

- A frequent problem in legacy sims is when an aircraft is unable to take off because, for instance, a single Sidewinder is missing from its strike loadout. Command uses a much more intelligent algorithm to determine if an aircraft has the essential stores for its assigned loadout & mission, and in such a case will send the aircraft on its way. The same algorithm also monitors continuously the remaining stores of all airborne aircraft and will suggest that they RTB if it determines that their "core" weaponry has been expended. For example an F-15 tasked with air superiority and facing multiple bandits will shoot off its long-range missiles and attempt to head home (with its short-range missiles and gun still intact) rather than get into a disadvantageous dogfight. The same aircraft with the same loadout in a different mission (e.g. intercept scramble) may follow different logic. The player can override this decision if he deems that the AI "crew" is making the wrong choice.

- Support missions can follow pre-planned waypoint routes, either one-time or in a loop. This allows players to define much more precise tracks for e.g a stand-off jammer than a general "loiter in this box" assignment. It also makes reconnaissance runs much easier to plan.

- When putting together an airstrike, you can attach support aircraft to the "core" strike group(s). These aircraft may be fighter escorts, jammers, tankers, SEAD shooters etc. They remain separate from the strikers in grouping (which greatly simplifies by-type management) but will stick as much as possible with them in terms of course/speed/altitude and follow them all the way to the target and back. This significantly reduces strike micromanagement and offers an alternative to independent support missions.

imageTactical AI

- Land units no longer simply advance towards their target(s) while firing at them. They now take into consideration their weapons envelope and their own type. For example truly mobile units able to fire on the move (such as armor platoons) will move while firing until they reach a certain percentage of their weapon’s range against the target, whereupon they will halt and continue firing. On the other hand relocatable units like artillery or SSM launchers will not fire while on the move and will halt once they reach just within max weapon range of their target, then deploy and commence firing. Relocatable units are also much more likely than mobile units to retreat under threat of enemy incoming units. These tweaks significantly improve the realism of land combat.

- The crew-AI for underwater operations (both sub-ops and ASW) is being given a thorough overhaul as the sensor & weapon models are falling into place. We should be able to visually present various end-to-end sub-ops & ASW setups in the near future.

 

Sensor modelingimage

- A limitation of the ESM model in legacy sims is that any sensor is able to precisely identify the emissions that it detects. As a result, one can send a MiG-21 with a stone-age RWR on an ELINT mission and get the same results as with a sophisticated ELINT aircraft like the RC-135.
Command changes this. Only certain ESM/ELINT sensors are able to precisely identify the emissions they detect; other less sophisticated sensors will provide only general descriptions like "Long-range air search radar". The emission-based contact filtering (shown on Part I) can be performed only after having at least one emission positively identified. This makes sophisticated ELINT equipment much more valuable, as in real-life operations.

- ESM detections are now resolved much faster. This increases performance in virtually any air/surface ops scenario.

- Magnetic anomaly detector (MAD) sensors and sonobuoys have been implemented.

- Convergence zones and surface ducting have been added to the sonar model.

 

Weapon modelling

- The benefits of brilliant weapons are now properly modelled. A LOAL-capable smart weapon arriving at the target area and detecting other nearby targets may well home on a target different than the one it was launched against, a result both militarily and often politically undesirable. Brilliant weapons (such as AGM-84K SLAM-ER ATA) are able to pick out their intended target even in the midst of others and specifically home on it. This is particularly important for strikes in populated areas or other cases of probable collateral damage. Weapons with active man-in-the-loop guidance (like the AGM-130 glide bomb) also have the same discrimination ability.

- Weapons with terminal semi-active guidance (LGBs, SM-2 SAMs etc.) now have a per-weapon "Paint Time" variable that determines the amount of time they need to have their target illuminated. This amount varies depending on various properties of the weapon (Paveway III bombs need a 10 second paint; SM-2 missiles only need 3-5 seconds etc.) and is an important tactical factor for the platform that must perform the illumination.

image- The dynamic launch zone (DLZ) calculations that determine if a weapon is kinematically able to intercept its target have been tweaked to include an additional buffer against incoming high-speed targets. This allows the shooter platform to exploit the high closure rate to launch the weapon further out than the nominal launch envelope. Common target examples include high-speed incoming aircraft (SR-71, MiG-25/31), supersonic cruise missiles (AS-4/6) or even ballistic missiles and re-entry vehicles.

- Guns and other mounts of unguided weapons (rocket launchers etc.) are now subject to director limitations just like semi-active weapons. A particular gun may have superb accuracy when directed by a radar or laser sensor, but piss-poor effectiveness when aimed with a simple optical device or on full manual control (either because there is no better sensor present or because the better sensors have been taken out). This is a critical differentiator on small-scale skirmishes (e.g. FAC duels, piracy & counter-piracy operations, littoral engagements etc.) because the same weapon systems can often be found on platforms with highly diverse sensor fits. Think that 76mm/62 Oto-Melara works just the same on an western DDG as it does on an oversized speedboat? Think again.

- We have added some tweaks & improvements to the wreckage model; Ships that are destroyed do not "vanish and re-appear as neutrals", they remain on their original side but incapacitated in every way, and they can still act as targets for sensors and incoming weapons. As before, additional hits on an existing wreckage will shorten the time before it sinks completely.

Development of Command continues at a rapid pace. More information and feedback is available on our Command forum.

Tags: no tags

Next Page »