Where can I read Command: Modern Operations patch notes?

This page lists official Steam announcements for Command: Modern Operations, including the latest post "Companion to Tides of War: The Command v1.09 Update". Each entry links to the full changelog on Steam.

How many people are playing Command: Modern Operations right now?

Command: Modern Operations currently shows 52 concurrent Steam players on SteamScope. Player counts refresh on a rolling schedule — typically about every 30 minutes for high-priority titles.

How often are Command: Modern Operations patch notes updated on SteamScope?

SteamScope ingests new Steam announcements as they are published. Check back after major updates, seasons, or balance patches to see fresh entries at the top of this feed.

Is Command: Modern Operations patch note data official?

SteamScope republishes developer announcements sourced from Steam's public news feeds. SteamScope is not affiliated with Valve Corporation. Always verify critical gameplay changes on the official Steam announcement.

Command: Modern Operations Patch Notes & News

Companion to Tides of War: The Command v1.09 Update

gislithsteam_community_announcements

123d ago

Tides of War, the new DLC pack for Command, was released yesterday. Make sure you don’t miss its unique new features, such as persistent campaign progression. As is often the case, the DLC release was accompanied by a major CMO engine update—and in the fine tradition of past releases, this one too packs a wallop.

Let’s take a quick look through the major additions & tweaks:

Explicit GNSS jamming and jammer units

This is effectively the follow-on to the abstract GNSS jamming made possible through the “Side Enablers” feature introduced in v1.08. In addition to defining “access/no access” to specific GNSS networks (GPS, GLONASS, BeiDou, etc.) at the side- and area-level, you can now deploy distinct platforms with the ability to jam these critical systems.

Just like radar and communication jammers, these platforms tend to be expensive and scarce, so careful positioning is required to maximize coverage and prioritize the assets you wish to protect (or the area you want to deny). As with other jammer types, their emissions can be detected, localized, and targeted.

In addition, the way GNSS disruption affects terminal weapon accuracy has been improved. Instead of measuring the “time without a PNT fix” and using that to calculate INS drift, the simulation now tracks the last 50 PNT-fix attempts (successful and unsuccessful) and uses a simulated Kalman filter to derive the final internal drift. This provides a more realistic model of disruption—since, for example, a single PNT fix is not enough to fully “reset” navigation accuracy to nominal status.

Salvo simultaneous weapon arrival

“I wish my cruise missiles arrived at the target area in a nice, strung-out line so that the defences could swat them down one by one” — said no strike planner, ever.

The navigation logic on weapons supporting TOT has been tweaked so that, within a salvo, all weapons will closely bunch up in order to arrive at the target simultaneously, overwhelming the defences. (Inter-salvo coordination remains the responsibility of the player, either manually or through the MDSP.)

Launch speed-dependent burnout for air-launched boost-coast AAW missiles

In other words: it is now actually important how fast an aircraft is flying when launching a boost-coast missile.

(This option is enabled by default in new scenarios and quick battles, and disabled by default in existing scenarios.)

When enabled, the burnout speed (per altitude) of boost-coast AAW missiles now varies according to the launch speed (in addition to the already-critical launch altitude). The weapon’s nominal range assumes a Mach 1.5 launch at 36,000 ft.

If the launch speed is lower, the effective burnout speed and kinematic range will be lower. If the launch speed is higher, both burnout speed and reach can increase significantly beyond nominal.

A faster burnout speed provides three key advantages in the BVR “missile joust”, all else being equal:

Your missile flies further, expanding your WEZ and reducing exposure to counter-fire.
Your missile flies faster on average, shortening your commit–engage–disengage cycle.
Your missile reaches impact with higher terminal speed, improving hit probability against an evading target.

If you’ve ever wondered why fighters aggressively go to afterburner before launching missiles, this should make it clear.

Incremental / timestamped saves

A long-requested feature: an easy way to undo or roll back scenario changes.

Instead of overwriting the existing save, the game now creates timestamped copies of the played scenario. This does take more disk space, but makes it much easier to revert to previous versions.

Vast A2AR improvements

A major effort has gone into improving air-to-air refueling:

Improved reliability at high sim speed
Reworked tanker prioritization and fuel reservation logic
Fixed several issues with tanker selection and refuel cancellation
Units now correctly follow refueling orders, even without explicit assignment
Prevents refueling conflicts and incorrect behaviors in complex scenarios

The Flight Plan Editor also received multiple fixes and quality-of-life improvements, particularly around refueling waypoints and doctrine settings.

Improved manual salvo control

A new “Execute” button has been added to the Manual Weapon Allocation window (Shift+F1).

Salvos are now created and scheduled far into the future by default. Only when the player clicks “Execute” (or closes the window) are they re-scheduled to fire as soon as feasible.

This allows full control over planning, editing, and adjusting salvos without units immediately reacting or moving prematurely.

Improved “one-third rule” on patrol/support missions

The patrol logic has been improved to better handle mixed formations.

Aircraft with different loadouts, subtypes, or even varying configurations can now be treated more flexibly under the 1/3 rule, making patrol rotation management significantly easier.

Area & Reference-point Manager improvements

This system has received numerous fixes, usability improvements, and functional enhancements, making it both more powerful and easier to use.

Limpet mines revisited

The mechanics of limpet mines have been reworked:

Can be placed on stationary ships or submarines
Remain attached until detonation
Use impact-style damage rather than underwater shock effects

This makes them a highly effective “sneak attack” naval weapon.

Improved map settings UI

Map settings are now duplicated in a dedicated window, making it faster and easier to adjust multiple options in sequence.

Other bits & pieces:

New doctrine option: Threat Max Distance (default: 50nm)
Aggressive Tile Management option for smoother map performance
Ships can now use dipping sonar
Expanded Lua scripting API
Menu search functionality added
Improved realism for nuclear submarines (Advanced Propulsor)
Drag-and-drop loading of save files
Ability to convert airbases into single-unit airfields
Improved quick battle interface and templates
Expanded UI tooltips
Increased durability threshold for sinking ships
Set orientation now available in normal play for non-fixed facilities
Expanded weapon jettison options
Improved image loading and UI responsiveness
SEAD units now engage both radars and jammers
Units react to illumination as if under attack

And as always, the new update benefits from updated official scenarios and the latest DB3000 and CWDB database releases.

With the decks now clear, the dev team is already hard at work on several new features set to further evolve the Command experience throughout 2026. Stay tuned.

Companion to Tides of War: The Command v1.09 Update

gislithsteam_community_announcements

123d ago

Let’s take a quick look through the major additions & tweaks:

Explicit GNSS jamming and jammer units

Salvo simultaneous weapon arrival

“I wish my cruise missiles arrived at the target area in a nice, strung-out line so that the defences could swat them down one by one” — said no strike planner, ever.

Launch speed-dependent burnout for air-launched boost-coast AAW missiles

In other words: it is now actually important how fast an aircraft is flying when launching a boost-coast missile.

(This option is enabled by default in new scenarios and quick battles, and disabled by default in existing scenarios.)

If the launch speed is lower, the effective burnout speed and kinematic range will be lower. If the launch speed is higher, both burnout speed and reach can increase significantly beyond nominal.

A faster burnout speed provides three key advantages in the BVR “missile joust”, all else being equal:

Your missile flies further, expanding your WEZ and reducing exposure to counter-fire.
Your missile flies faster on average, shortening your commit–engage–disengage cycle.
Your missile reaches impact with higher terminal speed, improving hit probability against an evading target.

If you’ve ever wondered why fighters aggressively go to afterburner before launching missiles, this should make it clear.

Incremental / timestamped saves

A long-requested feature: an easy way to undo or roll back scenario changes.

Instead of overwriting the existing save, the game now creates timestamped copies of the played scenario. This does take more disk space, but makes it much easier to revert to previous versions.

Vast A2AR improvements

A major effort has gone into improving air-to-air refueling:

Improved reliability at high sim speed
Reworked tanker prioritization and fuel reservation logic
Fixed several issues with tanker selection and refuel cancellation
Units now correctly follow refueling orders, even without explicit assignment
Prevents refueling conflicts and incorrect behaviors in complex scenarios

The Flight Plan Editor also received multiple fixes and quality-of-life improvements, particularly around refueling waypoints and doctrine settings.

Improved manual salvo control

A new “Execute” button has been added to the Manual Weapon Allocation window (Shift+F1).

Salvos are now created and scheduled far into the future by default. Only when the player clicks “Execute” (or closes the window) are they re-scheduled to fire as soon as feasible.

This allows full control over planning, editing, and adjusting salvos without units immediately reacting or moving prematurely.

Improved “one-third rule” on patrol/support missions

The patrol logic has been improved to better handle mixed formations.

Aircraft with different loadouts, subtypes, or even varying configurations can now be treated more flexibly under the 1/3 rule, making patrol rotation management significantly easier.

Area & Reference-point Manager improvements

This system has received numerous fixes, usability improvements, and functional enhancements, making it both more powerful and easier to use.

Limpet mines revisited

The mechanics of limpet mines have been reworked:

Can be placed on stationary ships or submarines
Remain attached until detonation
Use impact-style damage rather than underwater shock effects

This makes them a highly effective “sneak attack” naval weapon.

Improved map settings UI

Map settings are now duplicated in a dedicated window, making it faster and easier to adjust multiple options in sequence.

Other bits & pieces:

New doctrine option: Threat Max Distance (default: 50nm)
Aggressive Tile Management option for smoother map performance
Ships can now use dipping sonar
Expanded Lua scripting API
Menu search functionality added
Improved realism for nuclear submarines (Advanced Propulsor)
Drag-and-drop loading of save files
Ability to convert airbases into single-unit airfields
Improved quick battle interface and templates
Expanded UI tooltips
Increased durability threshold for sinking ships
Set orientation now available in normal play for non-fixed facilities
Expanded weapon jettison options
Improved image loading and UI responsiveness
SEAD units now engage both radars and jammers
Units react to illumination as if under attack

And as always, the new update benefits from updated official scenarios and the latest DB3000 and CWDB database releases.

With the decks now clear, the dev team is already hard at work on several new features set to further evolve the Command experience throughout 2026. Stay tuned.

Command: Modern Operations – Tides of War launches today

giuliac1994steam_community_announcements

124d ago

Today we are pleased to announce the release of Command: Modern Operations – Tides of War, a new campaign DLC available now.

Set in the tense waters of the South China Sea, Tides of War places players in command of ASEAN forces as a regional crisis escalates toward open conflict. What begins as a multinational military exercise quickly deteriorates when Chinese maritime militia and coast guard vessels interfere with operations, creating the conditions for a broader confrontation across the theater.

The campaign includes six tightly focused scenarios, each representing up to 24 hours of operations. Players will navigate a structured escalation ladder, moving from gray-zone incidents and non-kinetic encounters to submarine interdiction, precision strikes, and ultimately large-scale air and naval engagements.

A key feature of Tides of War is its Continuous Loss System, where losses and damage persist between scenarios. Decisions made early in the campaign can have significant consequences later, making force preservation and operational planning critical.

Rather than focusing on individual platforms, the campaign emphasizes escalation management, joint operations, and long-term force preservation, offering Command players an operational perspective on crisis escalation in one of the world’s most sensitive maritime regions.

Tides of War is available now and requires the base game Command: Modern Operations to play.

Community Scenario Pack #51 Released

camlo.ksteam_community_announcements

345d ago

Following the release of the v1.08 update for Command, which includes the new v512 databases, Kushan has now also updated the famous Community Scenario Pack (CSP), Command community’s curated anthology of user-created scenarios. The new update refreshes 4 existing works and contains 13 new scenarios:

Aegean Hunting Party, 1968: It came as a bit of a surprise that the main Soviet target was not West Germany, but Turkey. Following missile boat attacks that sank three NATO vessels in the Black Sea, the Soviets and their allies began a massive assault on Turkish air bases and air defenses. At the same time, Soviet and Syrian forces struck Turkish and British vessels in the northeastern corner of the Mediterranean. It is now the second day of the war. As Commander of NATO forces in the Eastern Mediterranean (COMEDEAST), you are responsible for naval operations in the waters surrounding Greece. At the moment, your main concerns are to clear these waters of Soviet forces and to get to safety any merchant vessels trying to reach Greek ports.

Casamance 1 – Arrival, 1986: This is the first of a set of scenarios using the Casamance Conflict in West Africa as their background. The ongoing Casamance Conflict started in the 1970s. Members of certain ethnic groups living in the southern part of Senegal (the Casamance region) believe they are marginalized and oppressed and seek to create an independent state. Fifty years later, they have not achieved this goal, but they have also not given up.

Casamance 2 – Reconnaissance, 1986: This is the second of a set of scenarios using the Casamance Conflict in West Africa as their background.

Chafarinas, 2029: The year 2028 was marked by a serious deterioration of relations between Spain and Morocco. Morocco has escalated the conflict in the gray zone regarding the Spanish cities of Ceuta and Melilla using the usual hybrid tools: migratory pressure, economic isolation, media and social media campaigns. Spain has closed air and naval traffic in the Strait and the Alboran Sea, although there are still some civilian vessels in the area. The Spanish government must successfully resolve the crisis as soon as possible.

Charlie Deuce Takes the Lead, 1970: It is 1970. Yesterday, the Cold War went hot. Winning the war against the Soviet Union will require NATO to protect vital sea lanes. You have been ordered to find and destroy any Soviet submarines in the waters south of the Italian island of Sardinia, a choke point for both military and commercial shipping traffic moving through the Mediterranean.

Defending Northern Turkey, 1968: Even early in the morning it is warm, and it looks like it is going to be another scorching day here in Eskisehir. Unfortunately, you are beginning to think it will not only be the weather that gets hot. In recent weeks the Soviets have moved a lot of military hardware into the Ukraine, Bulgaria and Romania. All this could simply mean the Warsaw Pact is preparing for a large military exercise. Or they could be preparing to attack NATO. The Soviets have been getting away with a lot in recent years. Do they think they could get away with attacking Turkey? Will the other members of NATO fight to defend Turkey if it means war with the Soviet Union?

Invasion Re-Invasion, 2025: It’s early days of the Great South China Sea War and the PLA has finally made its move on Taiwan. Most US and allied forces are tied up further north in that theater. Meanwhile, the Chinese Navy has snuck into Renai islands off Malaysia, a N-S diamond shaped island just outside their 9 (10) dash line near the south end of the SCS. The island would be a key base over 400nm closer to the critical straits of Malacca, Sunda and Lombok than their nearest reef outpost. They have caught us off guard… for the moment.

Khrushchev’s War, Day 3 – Duel Near Cape Verde, 1957: It is the third day of the Third World War. NATO, taken by surprise, is trying to blunt the Soviet advance and to organize counterattacks. The Portuguese colony in Cape Verde would not seem to have much to attract the attention of the Soviets, but it does have an airport that facilitates air traffic between Europe and Latin America. A Soviet surface group on its way back from the Caribbean (and believed to be bringing supplies to the rebels in Cuba) may be getting ready to attack that airport and other facilities on the Island of Sal.

Operation British Harpoon, 1968: It is the second day of the War. As Commander-in-Chief Western Fleet (CINC WF) of the Royal Navy, you also serve as the Commander-in-Chief of NATO’s Eastern Atlantic and Channel commands. At the moment one of your most pressing concerns is to eliminate the threat of any Soviet submarines that may have sortied out of the Baltic Sea and into the waters surrounding the British Isles. The next few days are going to be very busy.

Operation Rising Lion (Improved), 2025: The world holds its breath. After years of shadow wars and diplomatic failures, the crisis with Iran has reached its boiling point. Intelligence is unequivocal: Iran is on the cusp of developing a nuclear weapon, a threat the State of Israel cannot allow to materialize. The time for talk is over. As commander of the Israeli Defense Forces, you are about to launch Operation Rising Lion, the most complex and audacious military operation in a generation. This is a single, decisive strike to dismantle Iran’s nuclear ambitions permanently.

Operation True Promise III, 2025: This is the fictional sister scenario to Operation Rising Lion, from the Iranian perspective.

The C-Team, 1968: 55 days ago, the conflict known by many as World War 3 started. Until now, the Caribbean has mostly remained quiet, except for a few Soviet submarines most of which were sunk while trying to enter the Caribbean through one of its many passages and channels. This all changed 4 days ago when Castro delivered an hour-long speech denouncing the US and its allies, accusing the US of planning to invade Cuba, decrying the continued US ‘occupation’ of Guantánamo Bay and ordering all Cuban forces to be placed at the highest level of readiness. In response, the US heavily reinforced its forces in the area and prepared to take action to remove the Cuban threat.

Turkish Warships Join the Fight, 1968: It is 1968 and World War III appears to have started. Earlier this morning, the Warsaw Pact began a series of massive attacks against NATO forces, primarily those in Turkey. While Soviet intentions are not fully known at this moment, it looks as if a major goal of the offensive is to seize control of the Turkish Straits. As Commander Northeastern Mediterranean (COMEDNOREAST), you are responsible for NATO operations in Turkish waters. It has already been a very bad day. You are looking forward to the opportunity to avenge the vessels lost earlier this morning.

The new community scenario pack is, as always, available for download at the Command Team site, and also on the Steam workshop.

The CSP now proudly counts 618 scenarios in its stable!

The Silent Service DLC Returns

camlo.ksteam_community_announcements

380d ago

Many of you have been asking when The Silent Service DLC will return, and we are happy to announce that after significantly reworking the scenarios to bring them up to standard it will be available for purchase and download from 10 AM PST / 6 PM BST today.

We would like to thank you all for your patience and hope you enjoy the content!

Command: Modern Operations v1.08

camlo.ksteam_community_announcements

394d ago

Hello Command fans! We are excited to announce that update v1.08 is now live. This update introduces drone autonomy levels and brings communications jamming from CPE to CMO.

In addition to this we have made improvements to Doctrine & ROE UI/UX and a host of other tweaks. A complete change log is posted below.

Command v1.08 Build 1674 Release Notes (changes from v1.07)

====================================================================

* MAJOR NEW FEATURE: Drone Autonomy Levels. For details see here: https://command.matrixgames.com/?p=5886

* NEW FEATURE: Communications jamming (previously only in CPE, excluding scripting) is now also available in CMO. (See original article on comms disruption & effects: https://command.matrixgames.com/?p=4454)

* NEW OPTIONAL SCENARIO REALISM FEATURE: ASCM terrain-following restrictions. When this (off by default) feature is active, early ASCMs who lack TF capability cannot overfly land with elevation higher than their cruise altitude (unit is actively blocked from firing, both in auto-fire and also through the manual weapon allocation window). If the weapon is fired nevertheless (e.g. BOL shot) and encounters terrain higher than its cruise altitude, it smashes into it. ( < This means that is possible, but risky, to fire such missiles over very low-elevation land terrain such as atolls etc.)

Non-TF ASCMs with waypoint capability (e.g. Harpoon Block 1C) can be fired with a plotted course around landmasses, to avoid the "land between shooter and target" restriction when this feature is active. On the manual weapon allocation window, if the selected salvo has a suitable complex course that avoids landmass, non-TF ASCMs show up as "green" (can fire).

* NEW SIM FEATURE: "Depressed trajectory" capability for certain ballistic missiles (Requires v512+ DBs). Missiles who have this capability will use the "low" trajectory option in any less-than-maximum range shot (the default behavior for most BMs is to use the "high" trajectory leg).

(Currently only the Russian Iskander-M/E and its North Korean analog KN-23 are flagged as such in the database. If you have sources for other systems having the same capability, feel free to share them on the DB tracker: https://github.com/PygmalionOfCyprus/cmo-db-requests/)

* MAJOR REVISION: Revised user interface and new capabilities for Doctrine/ROE window.

- Instead of concentrating doctrine options on a single crammed window, they are now separated into per-category tabs. This makes it both faster to find a specific option and also affords more space for adding more options in the future: https://imgur.com/a/VKM1F8s

- Doctrine settings may be automatically filtered/excluded if they are not applicable to the selected unit(s). In this example, a single ship is selected, and only the doctrine settings that are relevant to surface ships are displayed: https://imgur.com/a/lCv9k9j

- The "mini display" of doctrine options in the right UI column has been removed, and replaced by a semi-automatic system of "doctrine deconfliction". The game attempts to detect common doctrine & mission conflicts (e.g. having WCS "hold" on a weapon while being a patrol with that weapon) and suggest to the player fixes for them; the player can then approve the fix change or ignore the suggestion. Example: https://imgur.com/a/c7DTRAB

- Improved simulation stability & performance on doctrine-related paths

- More responsive doctrine UI sections

Includes the new v512 databases.

- DB3000 v512 additions: https://drive.google.com/file/d/1PvOV1NivFzh_vrXKW-i_LIW0dlMIcQDC/view?usp=sharing

- CWDB v512 additions: https://drive.google.com/file/d/1mB2Ko3DnI4Lfql-PZGdEFqjd105NAmaW/view?usp=sharing

* Includes the thoroughly reworked & revised edition of "The Silent Service" DLC. All known scenario issues have been fixed, and a host of various tweaks and improvements made on each scenario.

* Includes updated versions of Fail-Safe #1, #2 and #5.

* Includes updated DB description files by Steve Lohr and KGambit

* ADDED: Chainsaw/Grinder Movement Style for Patrol Missions (see: https://x.com/RSE_VB/status/1897710024937365913)

* ADDED: Ability to select what datablock information is shown for units & contacts (just track number & name, or also kinematics, or everything)

* Added: UI elements that give information on time passed and identifying unit for last reported position of out of comms units

* ADDED: Banner with information about CPE shown at startup (can be disabled by checking the checkbox "Do not show on startup")

* ADDED: New message type: Comms-related message. This handlesd all messages related to comms (suffering comms jamming or other disruption, re-jioning the comms grid etc.). Messages about events happening while the unit is off-grid (sensor detections etc.) are still covered by the "Comms Isolated Message" type.

* ADDED: Added support for additional windows to Tool_UIWindow() Lua function: 'airops', 'boatops', 'readyarm', 'mounts', 'sensors', 'emcon', and 'magazines'

* ADDED: \ New unit wrapper property to show aircraft flight range: :flightRange(throttle, speed, altitude). Setting parameters to nil implies using the current values.

Example:

local u = ScenEdit_GetUnit({name='Looking #1', guid='207d76e0-e5be-4012-bbc8-93a142bb5b7b'})

print(u:flightRange(nil,nil,nil))

Result = { endurance = 21863, range = 1214.61108398438 }

* ADDED: \ "tracknumber" read-only property on contact wrapper-object

* ADDED: \ Added ability to migrate scenarios:

- Example for single use: print(Tool_Scen_Migration({scenario='D:/CMO/Scenarios/mine lua test.scen', config='D:/CMO/Scenarios/mine lua test.ini',dbfile='DB3K_510.db3'}))

- Example for batch file: print(Tool_Scen_Migration({scenario='D:/CMO/Scenarios/batchfile.xml', config='batch',dbfile='DB3K_510.db3'}))

* ADDED: \ Add loadout enums to Lua table

* ADDED: \ New property .ToString for "Event" wrapper object (shows basic event info in a print statement)

* TWEAK: The Sentinel-2 map layer now uses per-zoom-Level tile packing, which allows increased performance and also faster download and installation

* TWEAK: The unit-status thumbnail and the DB-viewer now use webp (instead of jpg) as the image format. (You may temporarily have a shortage of shown images as these are repopulated from the server on-demand)

* TWEAK: Re-enabled sluggish rudders

* TWEAK: Various sim-speed tweaks

* TWEAK: Various speed tweaks on map tile rendering

* Tweak: no trails are created for ActiveUnits that are not operating

* TWEAK: Removed "WRA cannot be fulfilled" messages since it might be causing confusion

* Tweak: no trails are created for Groups to avoid artifacts

* Tweak: \ ScenEdit_RunScript returns True if execution is succesful, False if execution fails, nil if execution does not even start or an exception is encountered

* Tweak: Unit that goes out-of-comms now self reports an identified contact for itself, aiding other allied units in tracking its position

* TWEAK: Tweaks on the Lua Console for better visibility of methods selection

* TWEAK: Various tweaks & improvements on barks mechanism

* Tweak: Passing through a support mission RP while refueling counts as having passed through

* TWEAK: On contact datablocks, show the track number distinctly from the rest of the contact name

* TWEAK: "Show Diagnostics" is now "True" by default

* TWEAK: Faster and more efficient sorting of messages on message log window

* TWEAK: Tweaked datablock rendering of contact track number according to NATO APP-6D symbology ("TN:XXX")

* TWEAK: Significant threading & performance improvement on simulation engine

* TWEAK: \ VP_GetContact now also supports track-number as the search key

* TWEAK: \ ScenEdit_GetContact can now also use a contact's track number as the search key

* TWEAK: \ The summary list provided by ScenEdit_GetContacts now also includes each contact's track-number

* TWEAK: No-comm drones shouldn't engage targets when "drone autonomy levels" scen feature is not active

* TWEAK: Enforced a more rigid waypoint altitude check in MDSP

* TWEAK: #16623: Reduced the sidebar scrollbar size

* TWEAK: #16636: Strike mission now defaults to focusing on target instead of engaging opportunity targets

* TWEAK: When running in interactive-GUI mode, the simulation thread gets set to "Lowest" priority (This reduces raw sim-engine performance, but has two UX benefits: (a) It reduces the impact of sim execution on UI responsiveness (map zoom/pan lag, general UI lag etc.) (b) It reduces the impact of sim execution on the overall OS responsiveness)

* TWEAK: Force the application at startup to run as DPI-unaware, and log this on the exception log as part of the startup info. (This is independent of the DPI setting stored on the registry, so if this works reliably players should no longer need to manually use the 4KFIx tool)

* TWEAK: Air intercept missions have "Engage Opportunity Targets" ON and "Focus Entirely On Strike Targets" OFF by default

* TWEAK: Updated collapse section code in DB viewer

* TWEAK: Map refresh is now both smoother and more performant (higher FPS)

* TWEAK: Reduced the impact of large message log refresh on the UI

* TWEAK: Revised how ' targeted ' messages are added to the log

* TWEAK: Increased accuracy on weapon time calculation in Mission Planner

* TWEAK: \ Changed patrol mission 'none' altitude to 'unspecified' for UI consistency

* TWEAK: "Filter by Keyword" check boxes eliminated on Add\ type panels

* TWEAK: Improved framerate / UI response for large scenarios

* TWEAK: QoL addition for showing next waypoint in "Unit Status" when on plotted course

* TWEAK: Flights with a mission profile that requires too much fuel are generated and a visual warning allows the user to tweak the flight plan (no changes when the side is not human controlled)

* TWEAK: Cruise missiles have no boresight launch limits

* TWEAK: Various sim-speed tweaks

* MAJOR FIX: "Message Log" window still showing log items that are no longer in the simulation's in-memory log ( << This solves cases of past problem reports like "UI & sim getting incrementally more sluggish as number of log messages increases")

* FIXED: Deserialization of last reported information for out-of-comms units

* FIXED: #16469: (1567.5) Flight lead doesn't RTB when hitting bingo fuel while following plotted course, wingman does

* FIXED: Number of flights for "investigate unknown contacts" and "engage contacts" in Mission Settings for Patrol.

* FIXED: End of turn turn overswing for fast rudders

* FIXED: #16550 Flight plan editor window is empty, shows no wps

* FIXED: Fixes to rendering issues on "Day/Night Shading" layer and Z-fighting between foreground layers

* FIXED: DB viewer error when showing a submarine entry

* FIXED: handling of unguided weapons in endgame report

* FIXED: Issue with Lua doctrine

* FIXED: \ ScenEdit_RunScript always returning "" even in case of error

* FIXED: Contact creation spam when tracking friendly out-of-comms units

* FIXED: Doctrine parent link was showing up despite being topmost doctrine

* FIXED: #16586: ASW aircraft on ASW patrol fly straight when target is uncertain

* FIXED: #16510: Detection AoU was not properly computed when an ESM sensor's resolution was >180deg

* FIXED: #16027: \ AAR refueling inside Flight Plans are not working

* FIXED: Aircraft always attempt refuel from same tanker, causing an RTB order or the aircraft to crash

* FIXED: \ Explosions not catering for Lua generated ones via AddExplosion

* FIXED: #16595: Command Freezes as weapons detect targets

* FIXED: Aircraft still heading to refuel point after tanker destruction

* FIXED: #16418: \ Different issues on Air to Air Refueling point 3

* FIXED: #16387: \ Aircrafts ignoring refuel WPs in strike plan

* FIXED: Out-of-comms unit not receiving position updates when detected by allied units

* FIXED: Contact being dropped when still needed to track an out-of-comms unit

* FIXED: #16576: AC group widely separated while performing standoff attack

* FIXED: Erratic wingman movements when heading to refuel point state, making aircraft to burn all their fuel before being able to reach tanker

* FIXED: #16484: \ Cannot set manual speed while refueling

* FIXED: #16660: Ships out of formation in a patrol mission

* FIXED: Lead and wingmen may split up during group stand-off attack

* FIXED: #16663: Ships weaving back and forth in formation

* FIXED: Strike flight plan AC never go engaged offensive and fire few weapons

* FIXED: Aircrafts failing to connect to Tankers

* FIXED: #16655 AIM-120D fired at wrong direction + DL issue (Also optimized the way to check if a contact was auto-detected or not)

* FIXED: Group members do not keep formation

* FIXED: Ship group lead not being able to delete reached waypoint from plotted course

* FIXED: Aircraft after completing a manual course, RTBs, the status doesn't say anything until the AC is on the final approach

* FIXED: #16649: DF-4 Missile TELs do not fire (For focused strike mission, when unit is not an aircraft on a flight plan, we no longer drop valid opportunity targets or player's manually assigned targets)

* FIXED: Exception fuse after aircraft drop many unguided bombs

* FIXED: Aircraft checking wrong doctrine for group member RTB decision

* FIXED: Strike aircraft on flight plan fly to target after expending all weapons

* FIXED: Message log may be spammed with 'failed to set home base

* FIXED: #16620: Aircraft switching constantly from RTB to On Patrol

* FIXED: #16447: Incorrect waypoint desired altitude clamping to weapon release window (Clamped weapon altitude for waypoint, when a desired altitude was specified by user, was not being clamped when above max and was always forced to max when in the correct range)

* FIXED: #16670: Unit in Patrol with a Flight Plan ignores Weapon State RTB

* FIXED: Aircraft on strike flight plan ingress may go RTB after disconnecting from tanker

* FIXED: Aircraft on strike mission flight plan egress may RTB instead of refueling

* FIXED: Air group disconnects from tanker before stragglers can refuel

* FIXED: #16661 :All weapons WRA doesn't work correctly - Extended group aware shooter count to other unit class

* FIXED: #16361 - SEAL using a ContactBomb also kill SEAL units

* FIXED: #14342 - Fixed contact exiting exclusion zone doesn't return to default stance

* FIXED: Flickering "Heading To Refuel Point" status not allowing wingman to catch up with a slightly ahead leader that was already refuelling

* FIXED: #16613 - Wingman don't follow flightplan

* FIXED: Message spam for synchronizing of hosted-unit recon updates

* FIXED: Patrol missions never launch more aircraft after first fight(s) land

* FIXED: #14688 - Underground Explosion Shockwave Damage to Surface Targets

* FIXED: #16611 - AAW missiles loft unnecessarily at very close range

* FIXED: \ QueryBaseUnit not working if providing base name instead of GUID

* FIXED: WRA not being followed

* FIXED: #16612: Patrol w/loadout attack altitude keeps ac at max altitude

* FIXED: AAW missile on datalink doesn't activate sensor when in range of target

* FIXED: Asynchronous image & map-tile calls were causing soft-deadlocks & slow replies

* FIXED: Exception changing emission interval after opening Doctrine via 'EMCON' button

* FIXED: #16591: High autonomy drones don't engage targets if no-comm

* FIXED: #16591: Patrol no-comms unit always switches to closest possible target

* FIXED: Retroactive fix for Weapon launch WP min altitude error

* FIXED: "RTB - Mission Over" status was interfering with the plotted course

* FIXED: Wingman not following leader's altitude in case of patrols missions with plotted course

* FIXED: Cargo weapons stacking calculation incorrect when container is empty

* FIXED: \ In some case waypoint altitude was set to minimum

* FIXED: \ Wingmen separation & rejoining issues

* Fixed/Improved: The "unit considers itself to be under attack?" check has been refactored and improved

* FIXED: #16641: Tanker AAR settings empty

* FIXED: DLZ computation could crash

* FIXED: Missing waypoint selection for FP using initial point

* FIXED: If the leader has reached weapon release point and you are within the prescribed separation you are good to fire

* FIXED: edge case exception related to AAR preventing AC destruction

* FIXED: #16622 - Issues in reaching fast and maneuverable tankers

* FIXED: Wingmen using navigation turns when forming up causes weaving (Also tweaked speed decision to avoid overshoot of formation station)

* FIXED: Exception fuse when aircraft is on non-strike mission

* FIXED: Aircraft may stop engaging target when strike mission specific target is active unit (Needed to evaluate against existing contact for the strike target AU (if there is one))

* FIXED: Strike flight plan waypoint with bad data was setting desired alt to AGL alt (Caused AC to be too low (AGL) to release weapons)

* FIXED: Lua INST export not setting the type of DB used

* FIXED: Strikes that start with no targets get deactivated (the targets are not yet added to the target list but the mission is not deactivated)

* FIXED: Units not engaging ANY targets if they were not in their strike specific targets and "Engage Opportunity Targets" was set to false

* FIXED: Aircraft status goes back and forth between refueling and RTB

* FIXED: #16677: Ships on ASW patrol attacking land targets

* FIXED: #16675: Support missions not launching flights to maintain coverage even if current flights in the air are RTBing

* FIXED: Blast misses some facility aimpoint mounts that should be hit

* FIXED: No message or indicator shown for EMP attack on aimpoint facility unit

* FIXED: Flickering between "Heading To Refuel Point" and "Refueling" status at start of refuel while on support missions

* FIXED: Recovery from "dirty" state in which tanker thinks it's still connected but client thinks it's not

* FIXED: \ Secondary targets further then weapon max range * 0.9 are not automatically added to the strike

* FIXED: Wingmen on strike flight plan go to wrong waypoint if engaged offensive before weapon release point (Wingmen continue following lead in this case)

* FIXED: Aircraft failing to use laser designator during group standoff attack

* FIXED: Group icon not rendered at correct altitude when pin-cushion view is enabled

* FIXED: Updated signature of the beta Tacview executables not recognized correctly

* FIXED: #16705: Consistent "object reference not set to an instance of an object" error when attempting to play quick battle scenarios

* FIXED: WRA shows 'not implemented' for land structure soft bunker and underground

* FIXED: Doctrine UI shows "-2" for self defense range for some weapons

* FIXED: #16701: Flight plan not being generated when there is a No-Nav Zone present

* FIXED: Pathfinder request never runs for flight plan generation

* FIXED: #16703: 1/3rd Rule not followed by CAP missions when using flight plans with Time-on-Station value

* FIXED: #16689: Aircraft on patrol flight plan with very low waypoint altitudes unable to adapt altitude

* FIXED: #16706: Ships switch back and forth from patrol to offensive

* FIXED: #16351: ASW Mortar can't fire

* FIXED: Mortar rounds follow the same trajectory as gun rounds

* FIXED: #16697: Chainsaw CAP flights fly north instead of flying to CAP patrol area

* FIXED: #16707: Docked boats are able to launch aircraft

* FIXED: #16689: Yet another case of aircraft on CAP with flight plan unable to adapt altitude

* FIXED: #16542: SEAD patrol aircraft won't target radar without precise emission ID

* FIXED: #16710: Aircraft enters RTB after take-off

* FIXED: Sim thread may deadlock if Lua console script causes an error

* FIXED: Weapons were not fired against by units in strike missions with TOT

* FIXED: Non-AC unit assigned to strike mission drops incoming hostile aircraft & missile contacts

* FIXED: #16715: Command hard-crashes when clicking mission hyperlink in "unit status" panel when unit is not selected

* FIXED: #16709: Manual flight-plan generation with NFZ incorrect

* FIXED: In some cases units were firing at the target immediately

* FIXED: #16725: \ ASCM Crashes into sea

* FIXED: #16728: Mission clone not working

* FIXED: Exception when opening any submarine entry on DB viewer

* FIXED: Logic flaw in calculating the cruise altitude of non-TF ASCMs

* FIXED: Mission editor inconsistent strike min/max response radius placement

* FIXED: #16714: Suicide-USVs not engaging targets when assigned to mission

* FIXED: Various WRA-related issues

* FIXED: Various aircraft RTB-related issues

* FIXED: Setting aircraft patrol attack/transit/station altitude to 'none' showed wrong UI

* FIXED: #16712: Wrong attack altitude setting for patrol missions

* FIXED: #16730: Naval units on patrol unable to plot route through Bosporus strait

* FIXED: In some cases aircraft do not follow egress path for flight plan

* FIXED: #16729: Submarine guiding torpedo while under attack constantly switches between engaged offensive and defensive

* FIXED: #16712: Aircraft A2A attack altitude issues

* FIXED: Null-exception fuse in bistatic radar pipeline when jammers are present

* FIXED: #16721: Escort aircraft engage until they run out of fuel and crash

* FIXED: #16761: Aircraft running out of fuel and crashing on strike mission

* FIXED: #16474: Ships not firing within self-defense range

* FIXED: #16755: Spacebar/Run button doesn't work when using the "Advance X time" buttons

* FIXED: #16669: Custom Environment Zone not parsing strength and intervals with decimals --- Fixed CTD when using comma as separator in CEZ UI

* FIXED: #16759: Intermittent Emcon UI not saving values when immediately closing the Doctrine window

* FIXED: Helicopters With No Mission RTB After Take Off

* FIXED: #16535: \ Unable to use Time-on-Station modifier with support missions

* FIXED: #16751: IR Seeker lost track

* FIXED: Manually unassigned aircraft not maneuvering towards station

* FIXED: #16713: In case mission-Profile of loadout is empty, return MaxAltitude for Loadout Altitude Settings

* FIXED: #16676: Warheads occasionally do too much damage

* FIXED: Datablocks Setting "Show Everything" not working

* FIXED: Datalinked weapon not currently on datalink may skip overshoot check

* FIXED: #16494: Loitering munitions get stuck, fly erratically until out of fuel

* FIXED: Aircraft on Ferry Mission Attempt to RTB if there is no plotted course and the host has no actual destination

* FIXED: Bridges (water structures in general) could not be targeted by cruise missiles

* FIXED: Aircraft could crash (running out of fuel) in patrol mission (When member of aircraft group (wingman) landed, the new leader was resuming route to the last patrol waypoint, disregarding its fuel state or the current RTB. At best, it was leading the aircraft to do an unwanted back and forth to the patrol area while RTBing. At worst, this behavior led to a crash if fuel reserve was insufficient to cover for this behavior)

* FIXED: Mission was automatically deleted for task pool after first RTB (This "auto-purge" behavior \ is now conditioned to the usage of a flight plan)

* FIXED: #16723: ASUW Weapons turning extremely off-boresight to attack

* FIXED: Unit icon flickering due to asymmetrical side postures

Command v1.07 - Build 1567.6

Severus Lupussteam_community_announcementspatchnotes

510d ago

A small update has just released for Command: Modern Operations. This update includes many small fixes and tweaks to Fail Safe (thanks to the community for all their feedback on Fail Safe). Command v1.07 - Build 1567.6 Release Notes ======================================================================== Fixed and updated versions of the following official scenarios: * Fail Safe - 1. Down Bird: Replaced Norwegian F-105s with F-104s. Also changed loadout on 2x Scimitars as Tankers and amended briefing to point that out so they can refuel the F-104s. * Fail Safe - 2. Knock Knock: Removed the Nike sites in Northern Norway * Kashmir Fire - 6. Shoreline : Further reduced the available SAMs on the Indian carrier group. * Northern Inferno - 9. Fox Two 22 Sept 1975 : Turned Soviet NFZ back on, pregenerated Soviet strike flightplans. * Red Tide - 2. Kobayashi Maru : Fixed Italian submarine not being assigned to a mission. * Red Tide - 9. Deja Vu : Added the correct AIM-9 variant for the F-4s to the USS Midway magazine. * Standalone Scenarios - Operation Lightning Strike, 2014 : Fixed Pakistani IADS units not being set to out of comms when the associated HQ is destroyed. Includes the v511 release of the DB3000 database. DB3000 v511 additions: https://drive.google.com/file/d/1dPLTsbUD4GnBl0KgLiC1OOsBe4hhQyku/view?usp=sharing Tweak: Slugtrails for units that are out-of-comms are now only shown up to the last position update received for the unit TWEAK: Tooltip: Mission settings tooltips for "Investigate outside patrol area" and "investigate within weapon range" checkmarks. TWEAK: Facility patrol missions check within weapon range now evaluates the targets outside area + best-weapon range TWEAK: Submarine patrol missions check within weapon range now evaluates the targets outside area + best-weapon range TWEAK: Surface patrol missions check within weapon range now evaluates the targets outside area + best-weapon range TWEAK: No trails are created for Groups to avoid artifacts TWEAK: Relaxed the 0.4nm drop range restriction for ASW torps to 1nm (gives more time to the shooter to engage) TWEAK: Removed "WRA cannot be fulfilled" messages since it might be causing confusion FIXED: #16548: Clicking on "Plotted Course Info" causes unit duplication FIXED: Out-of-comms Units Still showing current position and heading FIXED: #16553: SAM shouldn't use direct flight vs distant, low altitude target FIXED: Endgame report exception, report not shown in log FIXED: Aircraft not switching primary target to aid fired guided weapon and not cranking FIXED: Unit leaving "Engaged Offensive" status while in a patrol mission and guiding a weapon towards a mission-relevant contact FIXED: Escort aircraft not following weapon state RTB doctrine during strike FIXED: #16557: AI missions do not generate flightplans to strike pre-planned (autodetected) targets FIXED: Typo and wrong kind of message-box used when warning user that flight plan could not be generated with direct-path due to no nav zones FIXED: #16560: Manual attack order against submarine with air launched torpedo displays "code error" in manual attack window FIXED: #16310: Aircraft in ferry missions can't refuel due to aircraft switching status FIXED: TOT is broken in case where AC start firing while in the marshalling phase (and thus do not wait until they reach the Weapon-Fire Waypoint) FIXED: ASuW missiles running in circles when the target is destroyed FIXED: Number of flights for "investigate unknown contacts" and "engage contacts" in Mission Settings for Patrol FIXED: #16569 ASW helis not engaging subs with torpedoes on ASW strike

Command:MO - Fail Safe out now!

Severus Lupussteam_community_announcements

523d ago

Fail Safe is the newest DLC for Command: Modern Operations. Set in 1965 - one of most fraught periods of the Cold War - Fail Safe features period accurate weapons and vehicles that will guarantee an authentic wargaming experience. Guided missiles, early supersonic fighters like the F-104 Starfighter and MiG-19 Farmer, and naval vessels like the Soviet Sverdlov-class cruiser are just a small sample of the military platforms available in Fail Safe. A 10% launch discount is up now on Steam. From an opening scramble to recover a downed aircraft, ASW activities off the coast of Newfoundland, and the final battles of World War 3 where atomic weapons are finally unleashed - 12 missions will run you through the gamut. Fail Safe is the pinnacle of 1960's Cold War air and sea wargaming. The closest you can get to seeing what would have happened if Western and Soviet naval and airpower had fought the war that truly would have ended all wars. Good luck Commander, and remember to duck and cover.

Command: MO - Fail Safe out February 25th

Severus Lupussteam_community_announcements

537d ago

Exciting news today as we announce Fail Safe, the next DLC for Command: Modern Operations. Fail Safe is set in 1965 - during one of the most fraught and perilous periods of the Cold War. A Yak-27 has just crashed on the Svalbard Islands after a daring reconnaissance mission over Greenland. As Soviet and NATO forces race to the downed aircraft, a tense standoff is about to escalate into an all out shooting war. Fail Safe will see you command both old and new platforms. F-86 Sabers and F-104 Starfighters will take on Mig-15's and 21's. Old ships like the HMS Victorious, a carrier veteran of World War II, will take on the newest ships of the 1960's like the Soviet November-class submarines and Sverdlov-class cruisers. Old naval guns serve next to the newest anti air and anti ship missiles - every ship and air-frame in service will be needed. The 12 mission campaign will see World War 3 fought out from the Arctic circle and the Atlantic to the Aleutians and the Pacific. Nowhere is safe from the Atom Bomb. Fail Safe will be out on the Matrix Store and Steam February 25th.

Article - Modern warfare comes knocking: Side-enablers and GNSS disruption

Severus Lupussteam_community_announcements

538d ago

Command team lead Dmitris Dranidis has a new article out on signals, drones, and the disruption of satellite navigation on the modern battlefield. The Command team is working on implementing mechanics drawn from real-life examples of the interplay between orbital infrastructure and the ability of belligerents to deny and disrupt those assets. These new phenomenon in warfare are being modeled as a feature we call side-enablers. You can read the full article here.

Command: Modern Operations v1.07 - Build 1527

Severus Lupussteam_community_announcementspatchnotes

592d ago

Hello everyone. A small update today as Command takes the step to Build 1527. A good number of fixes and tweaks are included with this release, with the main features being the addition of a repeatable loop order for laying minefields. In addition, this update takes us to the v509 release of the DB3000 and CWDB databases. You can find all the units added to the database in the changelog below The full changelog is available below, happy hunting everyone! Command v1.07 Build 1527 release notes (changes from Build 1487) ==================================================================== ADDED: Option for Repeatable-loop movement style for mining mission ADDED: Added waypoint wrapper to unit.course ADDED: Added "Max Range" option to WRA firing-range selections. This allows differentiating between the weapon's explicit max range and the system default (which might be e.g. 50% of max). Includes the v509 release of the DB3000 and CWDB databases. DB3000 v509 additions: https://drive.google.com/file/d/1-SDvh64tihP-WhEAQpMQs1m7HeoFObE3/view?usp=sharing CWDB v509 additions: https://drive.google.com/file/d/1-hKp9pGycHZ6eRZj1c6-2UfGxz5pKZsF/view?usp=sharing TWEAK: Various tweaks for contrails: - Contrails cannot be formed outside the atmosphere - The temperature-at-altitude is now calculated dynamically from the sea-level temperature, using the US standard atmosphere model, so the altitude threshold for contrails forming now varies with the time-of-day and local surface temperature. (The temperature can vary widely with altitude: https://apollo.nvu.vsc.edu/classes/met130/notes/chapter1/graphics/vert_temp.gif ) - Airships and other craft using non-combustion propulsion (e.g. pure-coasting or nuclear) do not generate contrails - Weapons using boost-coast propulsion generate contrails only during their boost duration. Weapons using "cruise" propulsion (e.g. turbojet or piston/turboprop) can generate contrails throughout their flight - There is a "transition" layer between -40C and -50C temperature at which contrails can be formed but are weaker than at lower temperatures; this is reflected by lowering the visual size of the generated contrail by one magnitude (e.g. medium to small). TWEAK: Tweaks to AdvancedDialog TWEAK: "Load From File" now displays an error in case it fails to load. Extra checks applied. TWEAK: Modified the styling on the EMCON / WRA / Sensors buttons on the right column, to align them more with pre-existing format TWEAK: Adjusted Add/Set reference methods to be relative to RP and contacts too TWEAK: Changed style of WPF buttons ("EMCON WINDOW (Ctrl + F9)", "WRA Window", "Sensors Window (F9)", "Doctrine Window (Ctrl + F9)") TWEAK: Altitude poles are rendered as dashed lines for easier differentiation from other UI elements TWEAK: Various tweaks on the display of navigation points in pin-cushion view. Also the selected weapon's (estimated) intercept point is displayed in its true altitude. TWEAK: Speed improvement on showing the Doctrine-ROE window TWEAK: Numerous sim-engine and map/UI performance tweaks TWEAK: Button padding in mission editor so text is not cut off TWEAK: Raised the minimum camera altitude to 500m (instead of 10m) TWEAK: Push firing unit to unguided weapon wrapper TWEAK: Add data binding to SpecialMessage TWEAK: Render HTML messages without adjusting if a DOCTYPE TWEAK: Enforce a hold and hold end WP/time for missions that DON'T have a TOT. TWEAK: Area Clipper tweaked for more reliable shape intersections TWEAK: Various tweaks to missile loft autopilot logics TWEAK: Tweaks to post-loft terminal dive behavior, to maximize duration at higher altitude (shed as little speed as possible) TWEAK: The Defining of RP areas will result into an error if there is not Side created to avoid crashes. TWEAK: Drawing a Polygon RP will allow you to not create a zone. TWEAK: Replaced infinite random selection to cumulative-weight random selection for component damages TWEAK: Removed altitude blending (ie. fade-out on zoom-in) for borders and coastlines layer. TWEAK: Added package list to Lua mission wrapper Various sim-speed and map-rendering speed tweaks FIXED: Typo in "Northern Inferno" campaign file causes error when advancing from first to second scenario in campaign mode FIXED: Repeated while path-finding across International Date Line FIXED: "Edit" buttons in Docking Ops window were too small FIXED: Added Message Error box when Scenario-Load fails in "Campaign Continue" FIXED: At-altitude slug-trails artifacts FIXED: Pre-unit slug-trails causing save corruption in certain cases FIXED: Precise WP estimation for flight with no time constraints FIXED: Precise flightplan ETA calculation for patrol missions FIXED: #16105: Weapons DLZ issues FIXED: #16370: Error Fuse when an aircraft is evaluating threats FIXED: Exception when checking for distance from launch-point for torpedo self-destruction FIXED: arrow keys not working for moving maps FIXED: WRA issues FIXED: #16292: Duplicated Mk1 eyeball when saving + loading FIXED: #16378: Aircraft not firing mobile decoys at strike mission targets FIXED: Weapon turns toward (0,0) when intercept becomes impossible FIXED: Cluster weapon reporting miss when weapon's explosion radius < dispersion radius of the unit FIXED: #16381: Aircraft not firing (engaged defensive while on flight plan) FIXED: #16353: Applied an .ini during a scenario deep rebuild crashed FIXED: #16396: Aircraft increase altitude when defending against higher-altitude missiles instead of decreasing FIXED: #16305: Ships in formation do not change speeds properly to return to formation FIXED: #16372 Units assigned to a plotted course enter defensive status FIXED: Aircraft go defensive vs. distant missile clearly not engaging them FIXED: Target Speed Modifier (in weapon endgame messages) is being Repeated in Message Window FIXED: Label about PTL not anchored correctly FIXED: Custom station/transit alt in mission causes min-alt WPs in FP FIXED: Patrol aircraft on FP return to FP after engaging one target FIXED: Patrol mission area rendered as a solid box (instead of path across waypoints) when movement style is "Repeatable Loop" FIXED: Possible exception in GetContact() FIXED: #15796: Active Units from scenario still show killed ships FIXED: #15863: Unlock reference point not working FIXED: Sporadic exception when opening mission editor FIXED: #16373: Show unit behavior bark setting not working. FIXED: Prosecution area of patrol mission not rendered FIXED: Really low-to-the-ground trails not being rendered FIXED: mining mission not showing correct UOM FIXED: Weapon Launch point was showing latitude and longitude in text FIXED: Plotted course preview not visible when extending an existing plotted course FIXED: Generate Flight Plan button must never be disabled for Strikes even if they have no TOT or TOS FIXED: DLZ checks & burn calcs always use standard weather conditions FIXED: Boost-coast missiles shouldn't increase loft after burnout FIXED: ActualTempAtAltitude_CurrentScenarioTime() needs to return degrees C FIXED: Multiple issues in FP generation + ACs reverting to "follow plotted course" before having shot all the necessary missiles FIXED: Various tweaks & fixes to the way drag is calculated during DLZ checks FIXED: Various tweaks to "loft autopilot" logics for lofting AAW missiles. This should prevent them from using too-low a trajectory (energy-wasteful, fair chance of premature petering-out) on middle-of-range and short-range shots. FIXED: "Group of groups" behaviors not working FIXED: Borders & coastlines layer rendered inconsistently / "spotty" FIXED: Mining mission properly uses the defined mining parameters FIXED: RP not being marked relative if didn't have a bearing/distance FIXED: SetMission not correctly handling some presets on altitude/depth FIXED: Non-side firing range wra linking max range option to system default, which isn't always true as system default can be different from max FIXED: WRA default firing range not showing actual system default value FIXED: Null-reference exception in ScenEdit_SetUnit FIXED: Manual Weapon Alloc window broken (was not providing human-readable feedback) FIXED: #16441: Aircraft ignoring tankers and AAR

Command: Modern Operations v1.07

Severus Lupussteam_community_announcements

647d ago

Hello Command fans. We are happy to announce that update v1.07 is now live. A complete changelog is posted below. In addition to a mountain of bugfixes, tweaks, and scenario updates - we have a few key new features to mention. First off is true altitude/pin-cushion view. Aerospace units can displayed at their true altitude on the map. This is by default off but can be turned on by going to "Game Options --> Map Display --> Draw units at true altitude". This will hopefully help players visualize just where their aircraft are relative to one-another. We have also revised the HTML-rendering backend using Microsoft's new WebView2 rendering engine, added contrails and wakes to aircraft and submarines, and added new fuel flow rate restrictions in air-to-air refueling. These features are covered in more detail in the changelog below, so give that a good read if any of these new options and game rules strike your fancy. Until next time, happy hunting everyone! ================================================================================ Command v1.07 (Build 1487) Release Notes (changes from v1.06 - Build 1328.xx) ================================================================================ * NEW FEATURE: Show aerospace units in their true altitude (a.k.a. "pin-cushion view"). Disabled by default (for now), it can be enabled in "Game Options --> Map Display --> Draw units at true altitude". When enabled, air & space units are shown in their true altitudes rather than as "ground-tracks" on the planet surface. To help visualize their vertical placement, a gray vertical pole is drawn from the unit to the surface (similar to Tacview's "Display Object Height" setting). If a unit is out of the visible viewpoint but its ground-track is still visible, the unit's icon is ghost-drawn at the ground-track position, to indicate the unit's horizontal location. * ADDED: Revised HTML-rendering backend, using Microsoft's new WebView2 rendering engine. You should notice improved HTML rendering on the DB-viewer and other UI elements that use HTML sources. This also allows richer custom UI elements at the beginning of a scenario (e.g. to define custom options for the scenario, difficulty settings etc.) * ADDED: Aircraft fuel on-load rate restriction (requires v508+ DBs). When activated, the bottleneck on A2A fuel transfer is not just the offload capacity of the tanker, but also the onload capacity of the aircraft. Also the calculation for transfer rate is now the same for CMO & CPE. * ADDED: Indicators for aircraft contrails and ship/submarine wakes can be displayed on the map, under a unit's datablock. This makes it easier for the player to be more aware that his units may be visually detected at significantly longer ranges because of these factors. These indicators can be disabled on the "Map Settings" menu if they clutter the map unacceptably. (Clarification: Contrails and wakes have been part of the simulation engine since CMANO's original 2013 release. This change adds visual indicators for them) * ADDED: New method "ScenEdit_WeaponAllocation" to show weapon allocation from attacker to target. Syntax: ScenEdit_WeaponAllocation(attackerGUID, contactGUID, attackingSideGUID) 1. supply attacker and contact GUIDs to see salvos generated between the 2 2. supply attacker GUID and empty contact to see salvos from the attacker to anyone 3. supply contact GUID and empty attacker to see salvos against contact. Note in this case, you MUST supply the side from which attacks are coming from. * ADDED: Possibility to copy and paste zones through the zone context menu (Shift+RMB) * ADDED: Notification bark to let the player know if the AC reached the weapon release point too early (explanation for the occasional "hover on waypoint" behavior) * ADDED: Added TimeZulu to the flightplan WP wrapper * ADDED: Formation Editor accessible in unit mode when group member is selected * ADDED: Function for resetting the message log: Tool_ResetMessageLog(). If the optional "print first" value is set to True, the message log will first be written out to \Logs\AALog.txt before being purged. * Includes updates & fixes to these official scenarios: - Standalone - Chasing Aphrodite, 2019 - Standalone - Iron Hand, 2014 - Kashmir Fire - 2. Retaliation - Kashmir Fire - 4. Doomsday Clock - Kashmir Fire - 8. Flaming Dragon - Kashmir Fire - 12. Thunder From The Sea - Showcase Ford Class * Includes the v506, v507 and v508 releases of the DB3000 & Cold-War DB databases. This concludes the months-long China national overhaul, one of the most ambitious projects undertaken by the DB team (details: https://github.com/PygmalionOfCyprus/cmo-db-requests/issues/4131). The Command database is now arguably one of the most comprehensive open-source compilations of information on modern Chinese military equipment (excl. small arms). DB3000 v506 additions: https://drive.google.com/file/d/1n0UWMUiqniOgaqt7NrbvaRvBPjg4b82P/view?usp=sharing CWDB v506 additions: https://drive.google.com/file/d/1n8oSgftzyF3Jw9lUxuyMCh-c_wBnICH2/view?usp=sharing DB3000 v507 additions: https://drive.google.com/file/d/1myeLWrzWbGBE5Ddwhrz7uX4yIPn5j78c/view?usp=sharing CWDB v507 additions: https://drive.google.com/file/d/1nBHZT2mQiUg74AvyZPXiPTbFnro5SKfr/view?usp=sharing DB3000 v508 additions: https://drive.google.com/file/d/1wD5-lO4K_jUS4yuQ6BLpQqd_vRcV6490/view?usp=sharing CWDB v508 additions: https://drive.google.com/file/d/1w4IIuX_glHk9SGpnPT6jW7JR47SybvOp/view?usp=sharing * TWEAK: The Sentinel-2 map layer is now disabled by default * TWEAK: Better formatting for camera altitude text * TWEAK: Speed boost in DLZ calcs if the target is higher than the weapon's ceiling * TWEAK: Weapon Endgame reports with more specific wording * TWEAK on lofted AAW weapon trajectory: If climbing post-burnout and getting close to stalling, begin terminal dive towards the target * TWEAK: Improvement on secondary targets management for bombing + WRA check * TWEAK: On "Head To First Waypoint", start the climb/dive to the next waypoint's desired altitude only when we are within the horizontal distance needed for the climb/dive (this prevents aircraft from starting their climb/dive too early) * TWEAK: The flight planner will now always set the weapon release altitude according to the mission profile's "attack altitude ingress" value - allowing for minimum safe height * TWEAK: Force sim to pause on File-> StartMenu * TWEAK: Removed the obsolete "Test Scripts" top-level menu * TWEAK: scenario duration color on Begin Scenario Button set to white * TWEAK: Spread the OpenTopoMap tile calls to the three different known servers, to increase download throughput (and bypass throttling blocks) * TWEAK: The slug-trails are now rendered as an actual fading trail instead of unselected ref-points * TWEAK: Rotated icons and vectors at the edge of the globe will no longer show heading as if they were looked at directly from the top, but will instead be rendered as pointing to the heading they are actually moving towards * TWEAK: On Docking Ops window, list the hosted units of each platform in natural-sort order * TWEAK: Do not draw the mouse cursor databox if the mouse cursor is pointing outside the planet * Numerous significant sim-speed improvements. * A large number of miscellaneous issue from B1328.xx have been resolved. FIXED: Outline not being rendered and overlapping text for caption bar FIXED: Contact vertical speed was not recomputed each pulse FIXED: Exception when Primary Target isn't a unit (aimpoint, etc.) FIXED: #16156 Cold War DB possible matches for emission detection incorrect (if previously played a DB3000 scenario) FIXED: Nooo! Manually plotted courses disappear when units fire FIXED: Name of selected GPU not displayed on caption bar FIXED: ACs flying north and not RTB due to trying to maintain standoff while following a FP FIXED: Scenario "Canary's Cage" forcibly deleted on startup FIXED: Severe slowdown in salvo creation with AAW missiles when the WRA-range setting is "No Escape Zone" FIXED: In some cases a weapon would resolve its impact twice, before and after the target's point-defence resolution, thus ignoring the point defence's outcome FIXED: Aircraft climbs to maximum altitude (when at weapon release point) instead of FP or weapon release altitude FIXED: #16174: Rapid Dragon strike behavior: Ordering the target in descending distance order ensures that the Wpn launching point is valid for all the targets. Also fixed an issue that was preventing the generation of a FP with multiple targets if the targets were too spread out. FIXED: Crash when trying to import units due to missing "folder exists?" check FIXED: Aircraft armed with AIM-174B descend to surface level FIXED: AC stucked looping in place FIXED: Formation type list not being cleared properly when reloaded. FIXED: #16118: The formation type index 0 is being ignored as a formation type FIXED: #16093: Manually allocate MALD, clears unit plotted course FIXED: ACs in a patrol mission persists to the FP instead of engaging FIXED: The message window was not correctly parsing LOADDOC directives if they were preceded by any other text & tags (e.g. ) FIXED: Harpoon not being fire due to altitude FIXED: #16197: Weapons with HE blast-frag warheads would have an excessive effective frag radius, thus easily wiping out multi-aimpoint faciities (e.g. TLAM vs SA-10 battery) FIXED: ASuW bomb not engaging due to altitude issue FIXED: #15838: SS-N-27 variants do not deploy supersonic final stage FIXED: Concurrency-caused DB freak exception FIXED: TerrainFollowingFlag not set FIXED: Satellite names not listed correctly on Losses & Expenditures FIXED: Special messages with external HTML content not displayed on the message log FIXED: Aircraft with flight plan fly away without guiding weapons onto target FIXED: Helicopters following flight plan may hover forever after take-off FIXED: ACs were not respecting the zulu time of the mid-flight WPs FIXED: Sometimes the wrong weapon was retrieved for FP weapon engagement check FIXED: Winchester ACs were not RTB if there were some leftover targets FIXED: Filter-by-keyword causing crash to desktop (unable to add weapon/sensor) FIXED: Unit cloning not working for anything having a coverage arc definition (weapons, sensors) FIXED: ToT was calculating Weapon range as part of the flightleg for ACs FIXED: Aircraft on flight plan miss window to create salvos on double-flame speed FIXED: #16154 Air-Intercept aircraft fly off in random directions FIXED: Individual aircraft ignoring flight plan when engaged offensive FIXED: Crew quantity not retrieved correctly when instantiating facilities. (This led to the Mk1 Eyeball sensor not being present on manned facilities) FIXED: #16212: UE migration scenario FIXED: AC using the next waypoint altitude instead of the current one FIXED: Navigation issues (added a little slack to WP reach threshold + missing PC length check) FIXED: #16216: Doctrine mission reset when units assigned on air FIXED: ACs in separate targets were hovering at waypoints FIXED: Keyword-search method when adding a sensor was case-sensitive FIXED: #16220: JDAMs, aircraft getting stuck in mid-air and circling target/waypoint FIXED: Support missions not generating TOT for all flights FIXED: Aircraft circle at waypoints indefinitely with unreachable altitudes FIXED: WRA Winchester issue (erroneous "Follow Plotted Course" for winchester ACs ignoring leader) FIXED: #16237: DLZ check causing soft-lock and exception fuse FIXED: #16215: Wrong WRA Allocation FIXED: #16239: SAMs engaging targets below their engagement floor FIXED: #16241: Ordering manual refuel clears the selected tanker's plotted course FIXED: Multiple improvements on Flightplans altitude managment FIXED: "Horizontal distance needed to climb/dive to desired altitude" was sometimes returning a negative value FIXED: Issue when closing window with hotkey (Escape And/or dedicated) FIXED: ACs reverting back to "Altitude Before Engaged Offensive" even if they had a flight-path to follow (and thus should ignore this value) FIXED: #16230: Boats cannot dock at a port that is part of a group FIXED: Mission Profile values are always used for determine weapon release altitude - UNLESS AC loadout is null (in such case Upper Release Altitude Limit (ASL) - 100 is used) FIXED: Aircraft Minimum Safe Height value is used instead of Profile Altitude value if if the latter is lower than the former (this protects aircraft from getting self-blasted/fragged on low-level delivery) FIXED: Adding minimum weapon altitude and land altitude taken into consideration (with 0 as min value) FIXED: Aircraft must finish firing weapon salvos before continuing flight plan FIXED: WebView2 cache/user folder now uses Command's WritableRoot folder (fixing I/O issues on some computers) FIXED: Weapon endgame being reported as a miss if intended target was a miss even if another unit was hit FIXED: ACs were heading to the target ignoring the fact that they had not reached weapon-release WP + ACs were circling weapon release target after weapon launch FIXED: #16247: ABM missiles flying inefficient/impossible paths, fail to intercept BMs FIXED: Game-Mode not being preserved during scenario migration to different DB FIXED: #16268: Aerial Refueling taking priority over RTB even if aircraft are in range of airbase (units RTB not in bingo toward the base ignore bingo doctrine and do not refuel) FIXED: Fixed case of empty list when trying to find units FIXED: The MDSP had issues plotting flight paths around no-nav zones. FIXED: #16181 Rapid Dragon pallet was being destroyed before it could fire FIXED: Constant exception thrown when landing aircraft was on a strike mission FIXED: #16234: Different airbase composition (single-unit vs complex) causing issues FIXED: #16224: Wrong Bingo fuel calcs depending on base type FIXED: #16280: BOL-Launched torpedoes disappear immediately upon being launched FIXED: Saved window size of multi-unit sensors form may cut off controls FIXED: #16284: Flightplan WPs don't update position of moving base (e.g. carrier) causing aircraft to fly to wrong position while RTB and crash FIXED: Unimplemented method involving WRA FIXED: #16286: Group members do not follow group leads speed while lead is engaged offensive during patrol mission FIXED: Fixed case of SBR Platform List being written under app directory (not logs path) FIXED: Reference points adapting to the zone visibility settings once they have been added to the no navigation or exclusion zones FIXED: Aircraft emergency diversion logic only after tanker checks failed FIXED: Tacview not updated when Contact ID status changes FIXED: Cropped text in Area Editor FIXED: NoNavZones and ExclusionZones Window Layout FIXED: #16289: Reference points visibility state not saved properly FIXED: #16297: Aircraft (no FP) not adjusting pitch to meet boresight limit on target FIXED: #16303: Weapons dissapearing if firing unit is Out-Of-Comms FIXED: Gameplay Freezes, possibly due to Strike Missions FIXED: External (LOADDOC-provided) side-briefing and scenario-description texts broken after saving campaign scenario to somewhere other than its original campaign folder FIXED: Stationary ship group never changes throttle when given an new plotted course FIXED: #16305: Ships in formation do not change speeds properly to return to formation FIXED: Added weapon min-range check to avoid creating salvos that cannot be fired FIXED: The UI was changing the status of the AC when drawing the targeting Vector FIXED: Resolve unguided weapon defensive shot (CIWS) before target weapon impact FIXED: #16009: Escorts engage targets at altitude/speed of aircraft they are escorting FIXED: #16287: Aircraft circle weapon launch after firing during strike mission if target list contains unengaged target FIXED: #16291: CAP mission FPs not generated because "currently generated flight profile requires too much fuel" FIXED: #15705: Mission Deactivation checkboxes are non-functional FIXED: Wrong leg time estimation when climb time is present FIXED: Engagment was wrongfuly dropped if one of the weapon was incapable of fire FIXED: Hellfire Won't Shoot - Not Authorized to use SAMs Against Surface Targets FIXED: Target detected due to omniscience not correctly inheriting its unit-side posture FIXED: Some UI element anchoring issues on Docking-Ops window FIXED: Various issues related to area-effect explosions and aimpoint-facilities FIXED: Exception in Numeric Up-Down control when opening "Satellite Pass Prediction" window FIXED: Inconsistent application of "Use SAMs on ASuW" doctrine when selecting weapons FIXED: ACs following a non-FP course were not changing the altitude accoridng to the WP request FIXED: #15156: Fixed dual-mode ARM not seeing the target as radiating FIXED: #16173: Some elements of UI menu are greyed out FIXED: #16277: Upgrading a scenario scrubs side-is-human missions FIXED: #16293: Special Message window "previous" & "next" buttons not working FIXED: #15906: SBIRS don't detect LRBM FIXED: Ship not always engaging incoming missile with CIWS FIXED: Fixed case where closure speed was not calculated in AAW weapon lofted flight trajectory FIXED: Movement vector issue for ground units right before or after being stationary FIXED: Movement vector issues related to "old altitude" not being updated for contacts in certain cases FIXED: #16348: Aircraft evade missiles even when they should intuit they are out of threat range FIXED: #16337: Aircraft immediately losing control when spawned in airborne through editor FIXED: #16322: ScenEdit_AddExplosion not working FIXED: #16342: Scenario rebuild error, all aircraft airborne FIXED: Groups not properly exposing GroupLead's CurrentSpeed_Vertical

Home of Wargamers Live Event announcement

sofia.csteam_community_announcements

689d ago

We are proud to announce our new Home of Wargamers live event, which will take place on September 26th at 5 pm UK time. Join us on our Twitch channel to know more about our biggest franchises. You can set a reminder here. We will talk about a lot of important updates for some of our Matrix Games best sellers and coming soon games, such as:

Modern Naval Warfare
Armored Brigade 2
Nuclear War Simulator
Command Modern Operations
Flashpoint Campaigns
Rule the Waves 3

And much more. Stay tuned!

Command Beta Test Sign-up

Severus Lupussteam_community_announcements

738d ago

Hello Commanders! The Command: Modern Operations team is looking for beta testers. This is your chance to get the first look at our newest piece of DLC and have a role in shaping it's development. Feedback and bug reports are a crucial part of game development, and we are looking for beta testers to do just that. If you're interested all you need to do is click this link, log in with your Matrix account, and apply as a beta tester. Happy testing everyone!

Command: Modern Operations v1.06.1328.18

Severus Lupussteam_community_announcementspatchnotes

842d ago

Good news for you Command fans, we have an update out today. v1.06.1328.18 is mainly focused on bugfixes and tweaks, no new major features have been added. There has however been a significant change to the radar model. Until now, radars with an air-search capability and those with space-search (ie. ASAT & ABM) capability were separated in their target detection capacity by altitude and target type; ie. air-search radars could detect aerodynamic targets within the atmosphere, whereas space-search radars could detect BMs and RVs outside the atmosphere. While broadly accurate, this abstraction left a lot of unrealistic cases: For example a fighter radar could detect an RV in its terminal phase, or endoatmospheric guided weapons such as hypersonic missiles where not detected by BMD radars. In real life, radars use velocity filters (in addition to altitude ceilings) to specialize in their search task and minimize false contacts etc. Command now correctly replicates this behavior, with some assumptions for the minimum and maximum velocity values: Air-only search radars may detect any target from 0 knots (hover) up to Mach 5. Space-only search radars (ie. BMD/ASAT) can detect any target from Mach 2 up to "unlimited" velocity. Combined air & space-search capable radars use the full velocity spectrum. This addition allows more realistic representation of the capabilities and limitations of each type of radar, against the full gamut of endo- and exo-atmospheric targets. You can read the whole changelog here. Enjoy the update, and good hunting everyone.

Command: Showcase - Icebreakers Out Now

Severus Lupussteam_community_announcements

913d ago

Command: Showcase - Icebreakers is out now on Steam. To show off this new release, developers Jacob Keyes and Kushan will be streaming the scenario over on the Slitherine Twitch channel from 11:30 AM -1:30 PM EST. As the globe warms Arctic ice retracts, turning the frozen Siberian coastline into the worlds next great shipping lane. Ships transiting the Northern Sea Route (NSR) from Shanghai to Copenhagen travel only 1/3rd of the old distance, and avoid strategic bottlenecks like the Suez Canal and strait of Gibraltar. It is in this new, thawing theatre that the Russian President and MoD see an avenue of restoring national pride, a theatre which most in the west feel comfortable cropping out of their maps. Investments and military constructions are initiated turning this barren sea lane into an arctic kill-zone, emboldening the Russian parliament to declare that their laws regarding this new waterway supersede the United Nations Law of the Sea. In response, the U.S. President and Canadian Prime Ministers decide to challenge Russia’s claims in the region. In Showcase: Icebreakers it's up to you to lead a Freedom of Navigation operation in one of the most inhospitable climates on earth, the Arctic circle. Leading the fleet is the Polar Star, an icebreaker capable of plowing through the sheets of sea ice. Following behind her are several allied surface action groups including Zumwalt and Arleigh Burke Destroyers, along with Harry DeWolf patrol ships, and more. While there is no carrier as a part of the fleet, you will have the support of Air Force units stationed in Alaska. Information is ammunition, and with Russian satellites active you will need all the help you can get to control the flow of information. US CYBERCOM has prepared an attack package code named “Widowmaker" which will help deal with the Russian satellites. War has not been declared, but hostilities could begin at any moment. The Russian response to your actions will dynamically change according to the level of hostility you display. This is made possible by our new "Road to War" script that models gradual escalations from harassment and skirmishing, to outright warfare. With this release we also have a small update primarily to support this DLC. The changelog is posted below. * New weapon type: Laser dazzlers. (Background: https://en.wikipedia.org/wiki/Dazzler_(weapon)) Dazzlers differ from high-energy lasers as they have a deliberately wider, more dispersed (and less powerful) beam pattern. This reduces the destructive effect but makes it easier to hit their intended target. They are used primarily to damage/destroy visual/EO/IR sensors, on manned as well as unmanned platforms and weapons. When used against manned aircraft, they can cause temporary blindness and even lead to the aircraft crashing if at low altitude. * ADDED: #15453: Add ability to place reference points relative to any unit or any reference point * ADDED: Show if comms being jammmed on unit.components wrapper * TWEAK: #15475: Weapons in final phase always redirected to target * TWEAK: Rudder turn speed and overswing prevention logic * TWEAK: Show if comms jammed on Comms window * TWEAK: Setting "WCS free" now explicitly informs that neutral targets are excluded from engagements * FIXED: Patrol & prosecution zone issues * FIXED: ACs where blocked in refuel loop * FIXED: #15485: TimeToReady inside event not working * FIXED: Do not perform expensive "Terrain type effects - Advanced" checks for satellites * FIXED: #15502: Aircrafts RTB if WP 2 it's close to WP #8 * FIXED: Weapon ETA cache was cleaned every second + Weapon ETA recalc logic * FIXED: SM-6 Blk IB (fired against ground target) petered out way short of max range * FIXED: Cater for BOL-attack when checking for water-surface targets * FIXED: Restore visibility to :methods (fixes several reported issues in B1328.13) * FIXED: #15488: RPs relative to a unit not being saved * FIXED: #15486: Dipping sonar not detected by subs * FIXED: #15445: Wrong position of contacts in scenario * FIXED: RPs relative to units where not working correctly * Added support for the "Showcase #4 - Icebreakers" scenario. * Includes updated versions of all official scenarios. All scenarios were updated to the v504 DBs, in addition there have been fixes & tweaks to the following scenarios: - Falklands - Cry Havoc Bluff Cove: Added Saint Julian Air Base - Live - No BREXIT, no Problem!: Fixed USS Missouri Doctrine, should no longer RTB at scenario start - Live - You Brexit - You Fix It!: Fixed USS Missouri Doctrine, should no longer RTB at scenario start. Updated Russian AAW loadouts and Swapped German NH90 DBIDs - Live - Pole Positions: Fixed US submarines not being assigned to missions when playing as Russia - Standalone - South China Sea Clash: Swapped USA LCS DBIDs, CCG WHEC DBID, and Updated UnitDestroyed events

Command: Modern Operations - v.1.06.1328.13

Severus Lupussteam_community_announcementspatchnotes

926d ago

Hello Commanders, a new update has gone live. The big new feature for this update is water-surface facilities. These are facilities and structures located on the surface of the ocean that can be targeted by both anti-ship and anti-land weapon systems. Examples of this are piers, bridges, and offshore drilling facilities. The full changelog for this patch is listed below. v1.06.1328.13 – 12th January 2024 • NEW FEATURE: Water-surface facilities (supported only on v504+ DBs). Such facilities are placed on the water surface (not on the sea bottom) and can be attacked with both land-attack and anti-ship weapons. Examples of such facilities include bridges (both single-unit and multi- segment), offshore platforms, piers etc. • ADDED: Unit Status panel (right column) shows primary target name for selected unit • ADDED: Display a red X-crosshairs symbol and ETA on the calculated interception point when a weapon is selected • ADDED: Added 'Unpack all containers at destination' option for Cargo Transfer Mission • ADDED: Added aircraft emergency diversion to new host base when fuel is too low • ADDED: Contact wrapper - markedAsDecoy property • ADDED: Add time on target and takeoff time to mission wrapper • TWEAK: Significant performance improvement on game startup and scenario loading time • TWEAK: Fixes & enhancements on mine-laying mission • TWEAK: Losses & expenditures: Don't attempt to show stores with an empty name • TWEAK: Map appears at slightly higher resolution at lower altitude, reducing OpenTopoMap pixellation • TWEAK: OpenTopoMap layer does not stop rendering tiles at very low altitude. Virtual Earth layer renders tiles at higher resolution at very low altitude. • TWEAK: When bubbling up message-box messages from sim-core to UI, check if the originator side is the current side on the UI; if not then don't show them • TWEAK: Nuclear detonations begin appearing immediately upon detonation instead of after a slight delay and their circles expand with internal fill that fades out over time. • TWEAK: Event balloons render properly again with outlines and elliptical background fill around them. • TWEAK: Various refinements on the "throttle down to avoid wierd things" logics active during double-flame time accel • TWEAK: List Packages in order by name • FIXED: #15458: Various aircrafts don't have a correct WRA Classification • FIXED: #15447 : Ballistic missiles erratic trajectories • FIXED: Comms-jammer was jamming low-frequency radar • FIXED: Bark for "weapon hold" status and "switching to opportunity targets" were visible even if the unit was not from the player side • FIXED: Cached datatables access issue causing DB-Viever and "Add Unit" dialog to not behave correctly • FIXED: Decoy icon not being shown for decoy UAVs • FIXED: OECM jamming other bands • FIXED: #15468: No Navigation Zones Prevent Flights from Launching • FIXED: Missiles were handled as air contacts and so they where not always targeted + there was an hardcoded limitation of 10NM when identifying an incoming weapon as a threat. • FIXED: #15469: BM detonating into the ground • FIXED: #15250: Port/dock 'blue area' (pier lane) not working properly • FIXED: Keep plotted path on map when WP selected • FIXED: Pier-lanes not being rendered • FIXED: #15462: Units on inactive missions don't perform manual attack • FIXED: #15407: SAMs not working against Guided Weapons and BM • FIXED: #15466: HAAWC from Osprey not seen • FIXED: Non-Functional Air-to-Air Missiles in Helicopters, CMO v1.06 Build 1328.12 • FIXED: Suicide craft not auto-attacking water-surface facilities, also manual suicide attacks do not generate damage • FIXED: Various fixes on submarine damage from shaped-charge torpedoes: o The secondary-explosion damage of such torpedoes was not affecting the target sub o The explosion standoff was too small for all types of ASW torpedo impacts (generated too high shock factor) o Fire/flood effects are now cumulative (e.g. major + major --> step up to "severe") • FIXED: "ASW optimized" warheads not producing secondary blast effect • FIXED: ASW-optimized torpedo warheads were not getting their designed penetration & flooding bonus • FIXED: Unit assigned to cargo mission waits for pending cargo when it won't be able to load it • FIXED: #15396: (1328.11) Illumination and targeting vectors not appearing properly • FIXED: Weapon losses not recorded • FIXED: Unit icons "parallaxing" against map layer at extremely close zoom • FIXED: QuickSink-fused weapon was impacting non-ship target and the impact logics had not accounted for this case (fallback to normal impact) • FIXED: Weapon ETA calculator did not consider carried-dispenser weapons (JP233, MW-1 etc.) • FIXED: in some cases Aircrafts where circling around WP 6 • FIXED: #15310: CEZ Terrain Pathfinding Bug? • FIXED: Explosion crater only damaging the first hit unit • FIXED: #15253: 64-bit slowdown when launching mass amount of bombs • FIXED: Calculation of ABM intercept point did not take into account max weapon altitude • FIXED: Tanker-to-tanker aerial refueling issue • FIXED: #15440: Diesel/electric submarine extremely loud if electric engine is destroyed • FIXED: #15414: Aircraft not following flight plan speed • FIXED: #15077: The DISPLAY of Flight Plan Paths seems off • FIXED: #15402: Prosecution Area not working • FIXED: (Double-flame mode rudder behaviour) Wobbling ships, boats and submarines • FIXED: Broken ESM for negative altitude • FIXED: (Double flame mode) Some weapons type overshooting targets • FIXED: #15415: Aircraft not firing all their standoff weapons • FIXED: #15127: MDSP & WRA Issues • FIXED: Some ACs where not RTB • FIXED: #14926: ATO does not show all packages under a task pool when the pool is selected • FIXED: Units with a phased-array radar boresighted well away from the unit's heading (e.g. SLAR) incorrectly suffered the "phased array degradation due to off-boresight angle" • Fixed/Tweaked: Effectively decayed satellite (moving along a decayed orbit) will destroy it • FIXED: #15431: AOU miscalculates for very high altitudes and sensor range (e.g. GEO SIGINT satellites) • FIXED: #14925: Sorting ATO by mission/package greys out all buttons except "Create flight" • FIXED: #15374: Can't assignt a ship from a group to a Strike mission • FIXED: Group leash transparency • FIXED: 0014882: Extreme wingman separation • FIXED: Leftover UI-only code (from the pre-CMO days) stating that HGVs & D-EMP weapons could only be used in CPE • FIXED: ABM interceptor activation point too low vs. ascending target • FIXED: #15430: Command Blocked with Error • FIXED: UAVs visual/icon classification fix • FIXED: #15418: DB viewer exception Log • FIXED: #15413: Aircraft taking off to0 soon • FIXED: Issue with the new HPM weapon type that doesn't let you attack an UAV if it's a weapon (ie. loitering munition) but if it's an aircraft you can attack it • FIXED: #15410: Aircraft flying off into space (point 1) • FIXED: #14923: Cloning missions with generated flightplans messes up some references in ATO • FIXED: #15406: Parabolic trajectory on guided projectiles wasn't taking into account altitude delta • FIXED: UI is more responsive for H and L initial mission dropdown when adding a mission concurrently • Numerous general fixes • Numerous sim-performance tweaks • Includes the new v504 release of the DB3000 and CWDB databases. o DB3000 v504 additions: https://drive.google.com/file/d/1InvoyJJJnRGfCpDJgU9cNOAxMNCCw1P9/view?usp=sharing o CWDB v504 additions: https://drive.google.com/file/d/1Ip8AM2y1EZbQgQusUC6BFPzlKwxU6Cgt/view?usp=sharing

Command: Showcase - Icebreakers Coming Soon

Severus Lupussteam_community_announcements

936d ago

Today we are announcing our newest piece of Command DLC. Showcase - Icebreakers will take you to the arctic circle, commanding a naval task force in a F.O.N. exercise gone hot. Icebreakers will be out February 1st, 2024. {STEAM_CLAN_IMAGE}/35764183/c417fb69e6b5d75a669a5958c0786b97ebec1ec1.png Hypersonic missiles are launched to attack Russian surface units As the globe warms Arctic ice retracts, turning the frozen Siberian coastline into the worlds next great shipping lane. Ships transiting the Northern Sea Route (NSR) from Shanghai to Copenhagen travel only 1/3rd of the old distance, and avoid strategic bottlenecks like the Suez Canal and strait of Gibraltar. It is in this new, thawing theater that the Russian President and MoD see an avenue of restoring national pride, a theater which most in the west feel comfortable cropping out of their maps. Investments and military constructions are initiated turning this barren sea lane into an arctic kill-zone, emboldening the Russian parliament to declare that their laws regarding this new waterway supersede the United Nations Law of the Sea. In response, the U.S. President and Canadian Prime Minister decide to challenge Russia’s claims in the region. {STEAM_CLAN_IMAGE}/35764183/e0260d8a25cf95cc2548a65c96bfd9066020c611.png The Polar Star smashes it's way through an ice flow, creating a corridor for the fleet In Showcase: Icebreakers it's up to you to lead a Freedom of Navigation operation in one of the most inhospitable climates on earth, the Arctic circle. Leading the fleet is the Polar Star, an icebreaker capable of plowing through the sheets of sea ice. Following behind her are several allied surface action groups including Zumwalt and Arleigh Burke Destroyers, along with Harry DeWolf patrol ships, and more. While there is no carrier as a part of the fleet, you will have the support of Air Force units stationed in Alaska. {STEAM_CLAN_IMAGE}/35764183/78e187814a1a36a154a600d3dc8062291763b981.png Russian units harass the combined Canadian/U.S. fleet as they make their way through this new northern passage Information is ammunition, and with Russian satellites active you will need all the help you can get to control the flow of information. US CYBERCOM has prepared an attack package code named “Widowmaker" which will help deal with the Russian satellites. {STEAM_CLAN_IMAGE}/35764183/0c1c0aeddc8a352efe6822fdc73f92fc15b0b883.png With Alaska and Siberia nearby, land-based missiles and aircraft become a major factor in operations War has not been declared, but hostilities could begin at any moment. The Russian response to your actions will dynamically change according to the level of hostility you display. This is made possible by our new "Road to War" script that models gradual escalations from harassment and skirmishing, to outright warfare. {STEAM_CLAN_IMAGE}/35764183/77bee0ca32869a7a15cf64742a4826608b0b1069.png In brutal Arctic conditions, personnel won't survive long in the water without a rescue Good luck Commander, control of this new sea lane is crucial. Icebreakers will be out on Steam February 1st, 2024

Command: Modern Operations - v1.06.1328.12

Severus Lupussteam_community_announcementspatchnotes

965d ago

Hello everyone, we have a Command: MO update for you today with several tweaks and bugfixes along with new UI options. v1.06.1328.12 – 6th December 2023

ADDED: New map display option (Game Options window): Draw black outlines on icons & text to make them easier to stand out against background map (ON by default; disable if it is slowing down rendering)
ADDED: Added target property to unit wrapper
TWEAK: Map appears at slightly higher resolution on average by loading higher zoom levels at higher altitudes.
TWEAK: Updated built-in callsigns list
FIXED: Crash issue on startup
FIXED: #15340: Sensor mounts were not being attached to parent platforms when added by Lua - SE_UpdateUnit; this led to incorrect illumination-arc calculation
FIXED: #15335: Palletized munitions with Nan altitude and other issues
FIXED: Rapid Dragon weapons pallets transcending altitude, accelerating infinitely, and migrating to North Pole
FIXED: Exception error in weapon wrapper
FIXED: Strikers and Escorts Not Working Together
FIXED: Lofted ASW weapon (SS-N-15) was considering the target altitude (underwater) instead of the desired impact altitude (water surface) for the lofted trajectory calculation
FIXED: Aircraft egressing off flight plan to the east and west for some distance
FIXED: #15386: Aircraft selected not transfer to Target list on air strike mission
FIXED: Missiles where not splashing on water
PARTIALLY FIXED: #15375: DF-26 No altitude and weird behavior
FIXED: #15304: Air Intercept, low altitude in transit
FIXED: Escorts flying in circle ignoring the escorted unit
FIXED: Setting sub/ship throttle causes sonar signature to increase even if vessel doesn't move
FIXED: #15377: Speed override causes Sub to keep moving after course is cleared
Numerous general fixes
Numerous sim-performance tweaks

Includes the new v503 release of the DB3000 and CWDB databases.

DB3000 v503 additions https://drive.google.com/file/d/1CfqVLnl4pR1oSHbD4hUOYPzPLzgyx7Ou/view
CWDB v503 additions: https://drive.google.com/file/d/1CgAWCjDxyugeB609KRSldtq9scUnTFkA/view

Command: Modern Operations - v1.06.1328.11

Severus Lupussteam_community_announcements

1003d ago

Hello everyone, today we have a new Command update for you. Included are numerous bugfixes and minor tweaks. We also have implemented new features for unguided rocket artillery and counter-battery fire. Check out the full changelog below. * NEW FEATURE: Counter-RAM mechanics (currently only for unguided rockets). Here is some general background information. Unguided rockets are now no longer auto-detectable, instead they need to be explicitly detected by sensors. Rockets above 100mm in caliber can be detected by general air-search sensors if the physics are right; smaller-caliber rockets can be detected only by CRAM-specialized sensors such as counter-battery radars (e.g. TPQ-36/37, Zoopark-1/2, ARTHUR, COBRA etc.). They can also be engaged by weapons possessing a CRAM capability, such as the Centurion CIWS or Iron Dome. If a counter-battery optimized sensor detects one or more rockets, it is able to backtrack their trajectory and generate a rough-location contact for the unit that fired them. This allows modelling real-life counter-battery hunting tactics. * ADDED: Added actual roll and pitch to unit wrapper * ADDED: Add the name of the causing event/trigger/etc to generated Lua-error messages * Numerous performance tweaks on map/UI and simulation engine * TWEAK: Restored the "Placenames" map layer, using a subset of the Stamen Labels layer (cached on MG servers, not Stamen's). * TWEAK: Ballistic missile and RV contacts are marked as "FIREBALL" (instead of MISSILE) * TWEAK: Enhanced CallAdvancedDialog to handle HTML as input and return Lua table of values * TWEAK: Tweak on aircraft acceleration physics: The accel rate drops due to exponentially-rising drag as approaching the maximum speed for given alt & throttle (practical effect: planes accelerate really fast from an initial low speed, but take forever to reach the maximum speed). * TWEAK: In ABM DLZ checks, consider the interceptor's ceiling when attempting to calculate the seeker-activation point * FIXED: #15079: ToT not working for single unit firing on multiple targets * FIXED: #15372: TALDs not being rendered on map * FIXED: #15334: Weapon allocations by default? * Fixed: Torpedo contact impact crashing for undefined primary target * Fixed: Crash when fetching time of day * FIXED: #15359: Issue with text measurement on info bar * FIXED: WPN MAX quantity onboard was miscalculated in some occasion + in some cases the unit was focused on fire against a low priority target * FIXED: AAW range-ring flickering * FIXED: ACs not dropping their bombs on the first pass * FIXED: ACs not dropping their bombs due to altitude * FIXED: AEGIS ships not auto-firing SAMs * FIXED: #15365: SA-21 blocking issue * Fixed: Wrong behaviour of ground unit slider and Icon zoom not being saved and shown in interface * FIXED: Climb Time was not calculated correctly for HoldStart and HoldEnd WP 1/X * Fixed: DLZ failure for ABM intercept * FIXED: #15314: Intercept Mission * FIXED: #15338: Duplicate row when selecting "preset" in WRA Range * FIXED: #15355: Copy&Paste a decoy unit add DECOY word every time. * Fixed: #15357: S-400 Peters out vs. target at medium range * FIXED: (1328.10a) Naval unit not auto engaging ground mobile * FIXED: #15361: Priority in land ship weapons * FIXED: MDSP issues regarding TOTs and Wpn Altitude * FIXED: Cargo Package not in Pool * FIXED: Repeatable Exception Error During Bomb Impacts * FIXED: Very Straightforward Strike Mission Errors and not meeting TOT * FIXED: #15353: AA-12 Tailchase * FIXED: Allow Ferry missions to use flightplan only in "One Way" Setting * FIXED: Aircraft Not Following Flight Plan * FIXED: No MDSP message if the correction if the altitude function is not called from the UI * FIXED: Logic flaw in determining units stacked under the map-click point * FIXED: When firing to an incoming weapon if the weapon is within the min range (plus some slack) drop it + Message feedback for unit not firing * FIXED: Low-DP but nevertheless "valid" (in terms of armor penetration) hits were not destroying ground-vehicle units (this can happen frequently with e.g. cluster munitions). * FIXED: the Turning point Ingress just before weapon release has to follow a different default altitude, the "strike" one and not the "cruise" one * FIXED: Taking into account mission template when generating or fixing flightplan altitude

Command: Modern Operations - Map Layer News Update

Severus Lupussteam_community_announcements

1005d ago

So, this was not the best communication attempt ever... When we initially set out to explain the situation with the Stamen map layers going away, we referred to them as satellite imagery. This was a mistake, and created a lot of unnecessary confusion and anguish among some users. So let's try this again. As we wrote on that piece, we were forced in a hurry to drop support for three map layers externally provided by the kind people at Stamen Maps: "Stamen Terrain" (a topography layer, see sample) "Stamen Roads and Cities" (a variant of Terrain optimized for displaying road & urban networks) and "Stamen Labels" (a layer dedicated to displaying placenames). These layers are moving to a paid-access system from Oct 31. As part of our pre-release coverage of CMO, we presented the various map layers included in Command in this article. With the exception of the Stamen layers, all of these layers still remain available as always. In addition: 1) Beginning with the upcoming v1.06 / Build 1328.11 update, we are restoring the placenames layer. Stamen have kindly provided a very liberal usage license on their map tiles, so we can re-host the placename tiles on our own servers and provide them on-demand to CMO users. So this useful to many map layer is coming back, free of hosting concerns. To pre-empt the reasonable question of "Why aren't you doing the same with the other two layers": We use only up to the level-10 zoom on placenames, which keeps the number and size of the fileset at fairly small levels. The other two layers go all the way to level-17 zoom, and at that scale the file numbers and sizes are GIGANTIC. Let alone the challenges of hosting such a set; we cannot obtain it from Stamen in the first place. 2) Serendipitously, we recently added support for the third-party OpenTopoMap layer in Command. This is an excellent map set offering both topography and road+urban network data, thus easily rivalling the functionality offered by the retired Stamen layers. Thus, at the end of the day users of Command still have an excellent, high detail topography layer at their disposal. And as previously noted, all the other existing layers are offered directly by MatrixGames and are not going anywhere. At the same time, this turn of events has motivated us to start exploring additional map layers & services out there which may be of good value to users of CMO and CPE. We are evaluating some possible candidates but we are also open to suggestions from the user community. We hope this clarification eases the legitimate concerns of many players caused by our initial announcement.

Command: Modern Operations Satellite Imagery Removal

Severus Lupussteam_community_announcements

1025d ago

Dear Command users, We’re usually here to tell you good news about new features but unfortunately today we have some bad news. For the last 5 years we’ve been using, with permission, a satellite imaging company's map tiles for the inner zoom levels of the satellite imagery in Command. This company has decided to put these map tiles behind a pay wall as of October 31st. We only just became aware of this when the map tiles started disappearing in the game so the short-term solution is to remove these map tiles. This is the course we have elected to take and the team are testing the build before we release it. This will replace the previous higher resolution imagery with lower resolution layers. {STEAM_CLAN_IMAGE}/35764183/de4741c5f6163c73cec9387c8beff4cdf4b0bb56.png An example of the missing map data We know how much the Command community likes this kind of high res imagery and so we will be looking for an alternative solution for the future. Increasingly, these types of services are behind paywalls so we may be unable to find a free option. For now we just wanted you to know it is something we will be looking in to but we don’t have a plan in place just yet. We were not warned this was going to happen. We’re sorry for any inconvenience this causes and we hope it does not have too great an impact on your enjoyment of the game. Thanks again for your understanding and support. The Command Team

Command: Showcase - Operation Desert Falcon Out Now

Severus Lupussteam_community_announcements

1027d ago

Command: Showcase - Operation Desert Falcon is out now The year is 2027 and France's position in the Sahel has become untenable. A coup d'état in Chad has brought an anti-colonial regime to power. Militant groups are seizing foreign assets and government security forces have gone over to the United Sahel Liberation Front. With militants advancing on Massenya Airfield, the main base being used to evacuate French and foreign nationals, only the French air force can provide the necessary support to prevent a massacre. The closest fighter squadron equipped to support the evacuation is staged over 2,000 nautical miles away in southern France. Equipped with the Rafale multirole fighter and the A330 tanker, you have the range to reach out from the Metropole to touch the Sahara. You will need to manage multiple air-to-air refueling's, synchronized multidomain strikes, and the logistics of evacuating Massenya. The 500 civilians the will only be safe once they have landed at Libreville, in Gabon. Operation Desert Falcon uses the Multidomain Strike Planner, Ops Planner, Cargo 2.0, and Palletized Munitions to give you all the tools you need to execute a difficult mission, the evacuation of an airbase under siege. Features:

Playable as the French and focused on the Rafale C and the A330 Phenix, along with other supporting platforms like the C-130 and C-17.
Multiple political factors in play. Libya is the most direct route but will you risk flying your strike mission over an active conflict zone?
Plan for zero losses. With Frances position in Africa already teetering, any loss of aircraft or national humiliation will be considered a mission failure.
Plan for the unknown. Chad has an arsenal of MiG-29’s, Su-25’s, and JF-17N’s that could disrupt your plans.
Race against the clock. Militants are closing on the Massenya Airfield and the evacuation must be conducted quickly and with proper security.
Utilizes new Command features like the Ops Planner, Multidomain Strike Planner, Cargo 2.0, and Palletized Munitions. It is highly recommended that the player completes the MDSP tutorials before playing.

This operation demands nothing less than perfection. Bonne chance, Commandant. https://store.steampowered.com/app/2516840/Command_Showcase__Operation_Desert_Falcon/

Command: Modern Operations - Desert Falcon Release Date/Ten Year Anniversary

Severus Lupussteam_community_announcements

1039d ago

Hello Command fans, we have two pieces of news for you about our upcoming new Showcase DLC and our 10th anniversary. First off, the DLC. Command: Showcase - Operation Desert Falcon is now confirmed to go live October 10th, 2023. This near future mission will see you conducting long range airstrikes from the French Metropole into Chad with Rafale's, Phenix's, and C-17's equipped with RAPID DRAGON. This scenario is a great choice for learning how to get the most out of Cargo 2.0, the Mission Planner, and Aerial Refueling. {STEAM_CLAN_IMAGE}/35764183/683198bd662f4d06431a6ad80cbd474dde718774.png A flight of Rafale's on the long trip from the Metropole to Chad {STEAM_CLAN_IMAGE}/35764183/e27c93646de6e1f7f763ec7a9c455b0452376a9c.png A race against the clock as rebels attack French assets {STEAM_CLAN_IMAGE}/35764183/04511382e09c24a047b5981a52d0ca27a4b86187.png The riskier but more direct route over war-torn Libya {STEAM_CLAN_IMAGE}/35764183/d002d8ec22b723a81f29856c1814d9aac979a86e.png Aerial refueling is key in this long distance strike mission The future of Françafrique depends on your success. The symbolic value of even a single fighter lost could spell doom for France's future in the Sahel. This challenging mission demands nothing less than perfection. We are looking forward to seeing how our community tackles this Showcase. And onto the other news we have... {STEAM_CLAN_IMAGE}/35764183/01c553f66990e32a3b2488cbe5abbecf88d8d8e0.jpg Time flies when you're having fun Command just passed it's Tenth Anniversary! Over the past ten years we have seen several massive updates and changes to Command. *New features and improvements like Cargo 2.0, the Multi-Domain Strike Planner, and the Mission Planner. *Modeling of cutting edge new technology like RAPID DRAGON in our massive database, which just passed over 500 updates and iterations. *Introducing our 64-bit update and DirectX 11 map render. I am sure I am forgetting other milestones we passed but the last year alone has been a whirlwind of new features and updates. We would like to take a moment to thank our fans for joining us on this long journey to make the premier modern military simulator. Your feedback and suggestions have been essential in making Command what it is today.

Command: Showcase - Operation Desert Falcon Coming October

Severus Lupussteam_community_announcements

1055d ago

We are pleased to announce that the next Command Showcase is on the way, and will be available early this October. Operation Desert Falcon will take the player to the year 2027 and place them in command of a French Air Force squadron. A coup in Chad has brought a hostile regime to power. Foreign nationals are fleeing to the protection of small force of French marines holding out at the Massenya airfield. Only the French air force can provide the necessary security to prevent a massacre. The closest fighter squadron equipped to support the evacuation is staged over 2,000 nautical miles away in southern France. You will need to manage multiple air-to-air refuellings, synchronise multi domain strikes, and coordinate the logistics of evacuating Massenya. Operation Desert Falcon uses the Multidomain Strike Planner, Ops Planner, Cargo 2.0, and Palletized Munitions to give you all the tools you need to execute a difficult mission, the evacuation of an airbase under siege. Good luck, the future of Francafrique depends on your success. {STEAM_CLAN_IMAGE}/35764183/e27c93646de6e1f7f763ec7a9c455b0452376a9c.png {STEAM_CLAN_IMAGE}/35764183/683198bd662f4d06431a6ad80cbd474dde718774.png {STEAM_CLAN_IMAGE}/35764183/d002d8ec22b723a81f29856c1814d9aac979a86e.png {STEAM_CLAN_IMAGE}/35764183/04511382e09c24a047b5981a52d0ca27a4b86187.png

Home of Wargamers Live Event announcement

giuliac1994steam_community_announcements

1066d ago

We are proud to announce our new Home of Wargamers live event, which will take place on September 12th at 5 pm UK time. Join us on our Twitch channel to know more about our biggest franchises. You can set a reminder here. We will talk about a lot of important updates for some of our Matrix Games best sellers and coming soon games, such as:

Modern Naval Warfare
Nuclear War Simulator
Command Modern Operations
Flashpoint Campaigns
Rule the Waves 3
Strategic Command
Combat Mission
Valor & Victory

Command: Modern Operations - 64-Bit Update

Severus Lupussteam_community_announcements

1090d ago

We have big news for Command: Modern Operations. Today we are going live with a major update that upgrades the engine to 64-Bit architecture. The full changelog and notes on new features and performance are available below. * MAJOR NEW FEATURE: 64-bit architecture. Command is now a 64-bit application. * MAJOR NEW FEATURE: New DirectX 11-based map renderer. The existing DX9-based map rendering engine has been wholly replaced with a new one based on DirectX 11. You should observe significantly improved zoom/pan performance, as well as reduced latency and increased throughput when rendering map layer tiles. * NEW SIM FEATURE: Per-sensor mast height (optional) Apart from the existing ability to specify an overall mast-height for a platform/unit, it is now possibly to specify the mast-height value per sensor. This can be useful in modeling the different height placement (and thus horizon coverage, and the now-critical ability to clear the local skyline, see below) for each individual sensor in a platform. * NEW MAJOR SIM FEATURE: Terrain type-dependent skyline / land-cover height. The simulation now clearly distinguishes between terrain elevation height (ie. the actual ground) and the "skyline" height outlined by either natural features (forest trees, plantation etc.) or man-made structures (buildings, bridges etc.). This is critical for a number of different sim features, from land close-combat (e.g. land forces need to poke their sensors above local features to get sufficient LOS) to low-level flight (some aircraft can fly between the trees/buildings, most cannot). Several new land-cover types have been added to the existing ones. The overall list of land-cover types and their associated skyline-height values is as follows: Water => 0 Evergreen Needleleaf forest => 5 Evergreen Broadleaf forest => 5 Deciduous Needleleaf forest => 5 Deciduous_Broadleaf forest => 5 Mixed forest => 5 Closed shrublands => 1 Open shrublands => 1 Woody savannas => 5 Savannas => 1 Grasslands => 1 Permanent wetlands => 1 Croplands => 1 Cropland Natural Vegetation Mosaic => 1 Snow And Ice => 1 Barren Or Sparsely Vegetated => 1 Urban And Built Up => 9 Urban - Close Inner City => 30 Urban - Spaced High Rise => 45 Urban - Attached Houses => 6 Urban - Close Industrial => 9 Urban - Spaced Apartments => 20 Urban - Detached Houses => 6 Urban - Spaced Industrial => 9 Urban - Shanty Town => 4 Custom Environment Zone UI changes and new land-cover Types The Custom Environment Zone window UI has been re-arranged, with sonar environment overrides grouped together on one side and land-cover overrides grouped on the other. You can now set a custom land cover height (skyline), which will override the default land cover height for the CEZ: https://i.imgur.com/vFSlpUn.png The cover type ‘Use_Underlying_Values’ allows you to create a CEZ that doesn’t override land cover at all (for example if you only wanted to override weather and/or sonar conditions.) If you do select a specific land cover type, you can then check the ‘Set custom height’ checkbox to override the cover height for that CEZ. The height value is in whole meters. Aircraft ‘Land Cover Masking’ Flight Mode ‘Land Cover Masking’ (aka "fly between the trees/buiildings") is a new flight mode for aircraft. Only aircraft with the DB capability flag for ‘land cover masking’ set will be capable of this flight mode (DB v499+ required). In DB3000 v499 all rotorcraft (incl. some UAVs) have this capability. To set an aircraft to use this flight mode you use the Speed/Altitude window to set an aircraft (or aircraft waypoint) to use terrain-following mode. Once you set terrain following (and assuming the aircraft is capable of land-cover masking), a new check box will appear in the UI to set ‘Land Cover Masking.’ This can also be done via Lua (see below.) https://i.imgur.com/ZQJkFib.png Aircraft flying ‘land cover masking’ will fly much lower than the existing terrain following mode, as low as 10 ft AGL at loiter speed in open terrain with good visibility. If the scenario has the ‘Terrain Effects’ feature enabled, an aircraft flying ‘land cover masking’ will fly just low enough to be inside the land cover when possible. For example if land cover at the aircraft’s location is ‘urban/built up’ with a height of 9m then the aircraft will fly at 8m. This allows the aircraft to receive concealment from the land cover (see sensor changes below) while still exposing any mast-mounted sensors it may have (a good example is OH-58D with its mast-mounted optics). Land Cover and Sensor Detection Ranges The effect of land cover on the maximum sensor detection ranges for visual, IR, and radar sensors has been changed. (NOTE: as before, land cover only effects sensor detection range when the ‘Terrain Effects’ feature is enabled in the scenario settings.) Previously, only the land cover at the target’s location influenced sensor detection range. Now the sensor itself is checked to see if it is ‘within land cover’ (ie. it clears the skyline or not) and this applies an additional reduction in detection range if the height of the sensor is below the local skyline. In addition, the land cover along the ‘line of sight’ between the sensor and the target will also reduce sensor detection range whenever the LOS point is below the local skyline. These changes can result is significantly shorter detection ranges for ground-to-ground sensor detections when there is ‘high’ land cover in the area (e.g. woods and/or urban terrain.). Very low-flying aircraft (using the ‘land cover masking’ mode) can also have reduced detection ranges if they are flying below the local skyline (and dodging telephone poles or power lines, probably). Lua Changes New Lua support has been added for the features above: Land Cover Masking Flight Mode ‘Land cover masking’ mode can also be set via Lua using the Unit wrapper. Set the ‘unit.TF’ property to ‘true’ to turn on terrain following and then set the new ‘unit.TFType’ property to 1 (for land cover masking) or ‘0’ (for traditional terrain following AGL flight.) Custom Environment Zones Lua support for custom environment zones has been expanded. The ScenEdit_AddZone, ScenEditRemoveZone, and ScenEdit_TransformZone functions now support CEZs. CEZs are always added to/removed from the ‘nature’ side. CEZ values are set via the CEZ wrapper object (see below.) Lua Side wrapper has a new property and a new method: Side.Customenvironmentzones read-only property – returns a table of CEZ guid/name/description. Note: only the ‘Nature’ side will have CEZs normally. Side:getcustomenvironmentzone(guid or name or description) method – returns the CEZ as a zone wrapper object. Lua Zone object wrapper: Zone.landcovertype property – get/set integer land cover type. Zone.hascustomlandcoverheight read-only property – returns true if CEZ has custom land cover height set. Zone.landcoverheight property – get/set integer land cover height in meters. Zone.thermallayerceiling property – get/set thermal layer ceiling in meters. Zone.thermallayerfloor property – get/set thermal layer floor in meters. Zone.thermallayerstrength property – get/set thermal layer strength as floating point value. Zone.convergencezoneinterval property – get/set convergence zone interval as floating-point value. Zone.weatherprofile property – get/set weather profile as a Lua table with ‘temp’, ‘rainfall’, ‘undercloud’, and ‘seastate’ table fields with the same values as the weather model. * NEW SCENARIO REALISM FEATURE: Weather and day/night cycle affect air sorties. Aircraft that are not suitably equipped (either built-in or through their loadout, e.g. LANTIRN pods) for flying at night or in bad weather, will not be able to take off. If such aircraft are already airborne when the unsuitable conditions occur, they run a high risk of crashing on landing. This is an optional realism feature, enabled by default for new scenarios but disabled for existing ones, to avoid disrupting existing scenarios. * NEW MAJOR FEATURE: Targeting Priority (part of Doctrine/ROE settings): A new ‘Targeting Priority’ tab now appears on the Doctrine/ROE window. This tab allows the user to create a Targeting Priority List to control how a unit prioritizes engaging known targets. Targeting Priority is a component of a Doctrine, and thus follows all the existing conventions for Doctrines in Command – they can be assigned at the unit, group, mission, or side level and will inherit from higher-level Doctrines: https://i.imgur.com/peJ48KI.png The Targeting Priority List UI will display the Targeting Priority that applies to the Doctrine you’re currently viewing. You can only edit the Targeting Priority List if it is a part of the current Doctrine – i.e. not inherited from a higher-level Doctrine. Every Targeting Priority List will contain a single ‘default’ priority entry. Entries above the ‘default’ entry in the list will be considered ‘immediate’ priority targets, to be engaged before any other targets. Entries below the default entry in the list are considered ‘delayed’ priority, to be engaged only if no higher priority targets are available. The ‘default’ priority entry will automatically match any target(s) that do not match any other entry in the Targeting Priority List, allowing the player to prioritize (or de-prioritize) individual target types while leaving all other target types to fall into the ‘default’ category. Create: Allows you to create a Priority Target List for the current Doctrine. This will override any inherited Targeting Priority. Remove: Removes the Targeting Priority List from the current Doctrine. The Doctrine will automatically inherit from higher level Targeting Priorities, if they exist. Move Up: Move the selected item up one row in the list. Move Down: Move the selected item down one row in the list. Add Item: Add a new item above the currently selected item in the list. Delete Item: Deletes the currently selected item from the list. NOTE: You cannot delete the default priority item. Doctrine Targeting Priority applies as one of the final criteria when a unit is selecting a target. Other Doctrine settings (Rules Of Engagement, Weapon Release Authorization, etc.) and general AI targeting considerations (side posture, mission applicability, weapon effectiveness, etc.) are applied before the Doctrine Targeting Priority is checked. So for example, if a unit does not have a weapon to engage a given target, or that target is not considered relevant to the unit’s current mission, the target will not be considered as a potential target regardless of Targeting Priority. Each entry in the Targeting Priority List is evaluated in turn against a unit’s final potential targets. If an ‘immediate’ priority entry is matched, the unit will engage the target(s) that match that entry, ignoring lower priority targets. If a ‘delayed’ priority entry is matched the unit will engage the target(s) that match that entry only if there are no higher priority targets. If there are multiple potential targets remaining after the Targeting Priority is applied the Command AI will select one of those targets based on its general AI and/or mission target selection behavior – typically closest-first, while attempting to spread attackers across multiple targets. NOTE: In some cases the unit AI will evaluate a nearby hostile unit as an immediate threat and engage it in preference to all other targets. The Priority Targeting List is ignored in this case. Targeting Priority Doctrine can be changed via Lua using the Doctrine wrapper object. The Doctrine wrapper can be obtained from a unit, group, mission, or side wrapper object via its doctrine property. See ‘Lua Changes’ below for further details. Lua additions for Targeting priority feature: ActiveUnit wrapper: ActiveUnit.doctrine read-only property – returns the Doctrine wrapper object for the unit’s Doctrine. Group wrapper: Group.doctrine read-only property – returns the Doctrine wrapper object for the group’s Doctrine. Mission wrapper: Mission.doctrine read-only property – returns the Doctrine wrapper object for the mission’s Doctrine. Doctrine object wrapper: * Doctrine.TargetPriority read-only property – returns a Lua table with the contents of the doctrine’s priority target list, if any. Fields for each item in the table are: -- unit_type (integer) = ActiveUnitType -- unit_subtype (integer) = AircraftType, ShipType, SubmarineType, FacilityCategory, WeaponType, MobileGroundUnitCategory, depending on unit_type. -- Isfixedfacilitysubtype (boolean) = For fixed facility unit_type, ‘true’ indicates the unit_subtype is a value from FacilityCategory, ‘false’ indicates the unit_subtype is from MobileGroundUnitCategory. -- dbid (integer) = the specific DBID. -- priority (integer) = 0 (delayed), 1 (default), 2 (immediate) engagement priority. * Doctrine:deleteTargetPriorityEntry(index) method – deletes the corresponding item from the priority target list, if it exists. NOTE: index value is 0-based. Returns the list as a Lua table. * Doctrine:addTargetPriorityEntry(type, subtype, isfixedfacilitysubtype, dbid, index) method – all arguments are integers save for ‘isfixedfacilitysubtype’ which is a boolean value. ‘type’, ‘subtype’, ‘isfixedfacilitytype’, and ‘dbid’ are as explained for the TargetPriority property above. ‘index’ is the location in the list where the new entry will be inserted, with the existing entry at that location moving down. NOTE: index value is 0-based. * NEW FEATURE: Decoy platforms. Summary description: https://docs.google.com/document/d/1aG1sirF06rpGXyxiVD2CD57_T2e1Yy1f/edit?usp=sharing&ouid=110077162694891335144&rtpof=true&sd=true * NEW FEATURE: Weapon-deployable platforms (initially aircraft). Some aircraft can be carried as payloads from other platforms and released to fly. This allows moddeling various systems that are carried as payloads (with the full penalties of drag, weight etc.) and are launched weapons, but are actually recoverable platforms. The DB3000 v499 database contains one such example the Altius 600 UAV, carried as a loadout option for the XQ-58A Valkyrie UCAV. More systems (like the D-21 and WZ-8 Mach-3 UAVs) are to be added in the future. The UAVs are launched just like tactical decoys, using a BOL launch mode. * ADDED: Zone selection paradigm for all types of mission areas, triggers, actions, nonav & exclusion zones, and flight plans. Example: https://i.imgur.com/QJDYlGZ.gif * ADDED: New quick mission (Patrols) creation with Shift+RMB on clicked zones. This allows to select one or more units and quickly create a patrol mission on a zone (supports zone overlap). The selected mission will be automatically created to the zone's RPs and selected relevant units or hosted unit will be assigned to the mission. The mission editor will also open, allowing the player to further refine it. How-to guide: 1-Make sure to create at least 1 zone (with the area & ref point manager) 2-Select 1 or more units then shift+RMB on a zone to select the mission to create. Example: https://imgur.com/jLSMZXs * ADDED: Various features to easily create usable zones: -"Define area" now prompts the user to automatically create a standard zone and requests for a name, expanding the area-centric changes. -Added a circle-shaped "define area" in addition to the rectangle-shaped one (shortcut ctrl+O) -Reorganized the Refpoint Manager UI for reference points and areas -Added a general text input dialog Returns the user's input, returns null if canceled * ADDED: Added persistent UI+Lua layer control over standard zones and env. Zones (Can also be extended to other zone type, it has been intentionally disabled for other zone types) * ADDED: Special kinematic behaviour for hovercrafts (LCAC, for instance); they no longer behave like Martian flying saucers capable of hovering above trees. * ADDED: Traction system for ground units (also fixes units getting stuck in sloppy area and adds collision bounce). Also improved how a land unit's speed is computed given slope, terrain type, and the unit's traction system (tracked, wheeled, foot). * ADDED: Formation editor now supports "hot reload" of the templates file. Also added button to quickly open the file for editing. * ADDED: Added support (incl. damage mechanics) for new "blimp" airship type * ADDED: Added support for "multi-staged missile" flag. Multi-staged AAW missiles (e.g. SA-5) have a lower burnout weight in proportion to their overall launch weight. This helps them achieve better climb performance post-burnout, but if they loft it also means that they are less able to use their mass to re-energize on their post-loft dive. * ADDED: Indication of which AC is the group leader * ADDED: Special kinematic behaviors for hovercrafts (LCAC, for instance); they no longer behave like Martian flying saucers capable of hovering above trees. * ADDED: Traction system for ground units (also fixes units getting stuck in sloppy area and adds collision bounce). Also improved how a land unit's speed is computed given slope, terrain type, and the unit's traction system (tracked, wheeled, foot). * ADDED: Formation editor now supports "hot reload" of the templates file. Also added button to quickly open the file for editing. * ADDED: Added new map layer: OpenTopoMap. This is a map layer optimized for displaying natural topography (see also: https://opentopomap.org/) . This can be useful for better evaluating the terrain around a given unit (and thus better understanding visibility, movement and damage effects). This layer is externally-provided, so tile-download reliability and speed are beyond our control. * ADDED: Support for new "blimp" airship type * ADDED: Implemented rudder as factor in ship/sub turn rate, and rudder damage (stuck). Ships and subs are now more "sluggish" in their turns (especially large ones) as it takes time for the rudder to fully deflect to the desired position. Additionally, the rudder can be damaged (stuck) or destroyed, leaving the boat directionless (e.g. Bismarck in WW2). * ADDED: New trigger type: "Air/Dock Ops Status Change". This trigger fires whenever the air/dock ops status of the selected unit(s) changes - e.g. an aircraft takes off, a boat returns to its host unit, an aircraft shifts from "being turned around" to "ready and waiting" etc. The UI allows selecting which of the available states will cause the trigger to fire. This was available until now only through scripting but can now also be configured through the EE. * ADDED: Add speed and altitude to file * ADDED: Interpolation function for zones; Also added Shift+RMB zone interpolation options (1, 2, 3, 4, 9) in the UI * ADDED: Added a new Shift+RMB interaction on zones: Highlight all RPs of a zone exclusively * ADDED: Shift now allows to move multiple RPs while keeping relative position. This makes it possible to move a selected zone in one go. * ADDED: Zone creation by polygon * ADDED: Button to change cargo transfer destination unit in mission editor * ADDED: #15024: "Unit in Zone" in the lua template for operation planner triggers * ADDED: Added the ability to view/edit the assigned cargo for cargo missions using a list of cargo consolidated by unit type. This is done with a new check box "Show items grouped by unit type" under the cargo item list in the cargo settings tab. (So for example if you have 1500 individual rifleman units in your cargo, you can click this to see one "0/1500 Rifleman" entry in the list instead of 1500 individual Rifleman list entries) * ADDED: #15049: A button to clear all slug trails * ADDED: Relinkable decoys: https://i.imgur.com/QKl41zf.png * ADDED: #14903: Allow Rapid Dragon use with missions * ADDED: Integrated IsDecoy property (to existing unit-wrapper object) with new logic + displayed decoy info into print(unit). Example: https://i.imgur.com/Q3C2SqZ.png * ADDED: Several new type-specific icons for ground units * ADDED: You can now customize the size of unit icons, per-type and per-shape: https://imgur.com/a/3tVU6cr * ADDED: The QuickSink-configured JDAMs (background: https://www.youtube.com/watch?v=41bCXburV2s) now correctly dive in front of the target ship and (try to) detonate under its keel (due to the CEP-based accuracy, the exact detonation point can vary). The underwater blast usually delivers much more severe damage than direct impact to the target ship. * ADDED: Added 'Add Reference Point at...' menu item and dialog (on "Missions and Reference Points" menu); this allows placing a reference point with great precision, using known lat/lon coordinates. * ADDED: #15173: SBR Add Support for Sensor Groups * ADDED: Added Lua wrapper support for cargo mission assigned cargo list. * ADDED: Mission-level integration for "AC landing/takeoff weather/night limitation" feature: A per-unit check is performed on the takeoff and landing locations, to check if the AC will be able to take-off & land without any issue. At the end a warning is shown to the user (No hard-lock prevention). * ADDED: #14985: Opacity validation by "enter" key in area & ref point manager * ADDED: Added placeholder properties for AC flights * ADDED: Added 'All ground units attempt self-transfer' option to cargo missions * ADDED: Property 'leadSlowsDown' for group wrapper object • ADDED: Added mechanics for proximity-fuzed warheads on AAA rounds (such as flak rounds). General background on the proximity fuze: https://en.wikipedia.org/wiki/Proximity_fuze Proximity flak greatly boosts the effective "hit" probability against aerospace targets - whereby "hit" no longer means just a direct impact, but detonating withing a lethal sphere around the target. The dimensions of the lethal sphere depend on: • The shell caliber: big shells like 85mm or 127mm have much larger lethal spheres than 35mm or 40mm rounds. • The target speed: faster targets severely reduce the effective lethal sphere; this is a large part of why flak fell out of fashion post-WW2 as jet engines sharply increased the speeds of frontline aircraft. It's also why flak has seen a resurgence as an anti-UAS solution: drones generally are slow, flimsy air vehicles, and flak rounds are much cheaper than missiles. When a proximity round "hits" an air target, we break down the detonation distance into five logical "distance slots" (20% probability on each), each representing a different distance from the target: 1) Point-blank ie. direct hit: The target receives the full warhead damage 2) A very near miss: The target receives 80% of the warhead damage 3) A less close miss: The target receives 40% of the warhead damage 4) Further out: The target receives 20% of the warhead damage 5) Edge of the lethal sphere: The target receives 10% of the warhead damage (Notice that received damage falls sharply with distance; this represents the expanding frag pattern of proximity rounds). • ADDED: On the "Scenario Migration" window, you can now customize the default WRA-range for AAW missiles when migrating a scenario • ADDED: The Sentinel-2 map layer now uses an improved custom-tuned tileset. This has several improvements: - It is hill-shaded, and thus relief (terrain elevations) stand out much more prominently: https://imgur.com/a/urc9XXL - Because of the shading, desert regions are less eyeball-melting: https://imgur.com/a/TTPUZOW - It is water-masked, so coastal outlines are a lot crisper: https://imgur.com/a/RzDE4yZ - Also because of the water-masking, water regions are transparent, so now you can combine it with bathymetry: https://imgur.com/a/PXOYLiY - The tiles themselves are compressed to higher quality, so you should see less compression-artifacts on high zoom. * Includes improved graphics for the depiction of mount/sensor coverage arcs. Example: https://imgur.com/a/M4cZsm8 • Includes updated and corrected versions of the following official scenarios: - Chains Of War #1 - Blue Dawn - Command LIVE - Kuril Sunrise - Command Showcase - Queen Elizabeth - Choking Halifax - Raid On Kismayo - Falklands #8 - Pebble Island Raid - Falklands Bonus #1 - The Empire Strikes Back - Falklands Bonus #2 - Operation Mikado - Kashmir Fire #13 - Over The Hump - Desert Storm #3: First Night (Fixed grammatical errors) - Command-LIVE: Aegean In Flames (Fixed a number of issues: Airbase magazines, missing mounts and weapons, turned off unlimited airbase magazines) - Command-LIVE: Don of a New Era (Adjusted description and briefing text style) - Command-LIVE: Broken Shield 300 (Fixed airbase magazines, various other fixes) - Command-LIVE: Pole Positions (Fixed broken links in scenario description) - Command-LIVE: The King of the Border (Adjusted description and briefing text style) • Includes all official scenarios rebuilt to DB v499, with their default AAW WRA-range set to 75% of maximum range. DB3000 v499 changelog: https://drive.google.com/file/d/1XmuwnZgf1f2drXA2R3cB5oR-fV_slwul/view?usp=sharing CWDB v499 changelog: https://drive.google.com/file/d/1Y-vuNJ0A_gr5ufleBxicrmUNpTJwaK2f/view?usp=sharing DB3000 v500 content changelog: https://drive.google.com/file/d/1ukywMOnA6qWpKpD7K0aw9BhEAl0fGPK2/view?usp=sharing CWDB v500 content changelog: https://drive.google.com/file/d/1uupIaQia3qHF_YPxEuUAk_TkkeIjKFvp/view?usp=sharing DB3000 v501 changelog: https://drive.google.com/file/d/1--wRLPWp0AHyu_oWhcUdzaucvI8GmXJo/view?usp=sharing CWDB v501 changelog: https://drive.google.com/file/d/1-6II6vMwT4u9QvYn-9lltj0YkEXwpJG3/view?usp=sharing

Command: Modern Operations - "Operation Desert Falcon" Beta Sign-Up

Deathsteam_community_announcements

1091d ago

We are glad to announce that sign ups for Command’s next Beta, for the upcoming Showcase DLC - Operation Desert Falcon are now open!! Please sign up here and don’t miss this opportunity to get a first glimpse of what’s next for Command. As a member of the closed beta team, you will be granted early access to the scenarios development, giving you an opportunity to get your hands on the scenario and Command the battlefield earlier than anyone else. We look forward to receiving your feedback, insights and suggestions - to help test and shape the scenario for it’s release. Operation Desert Falcon, is designed to Showcase some of the newest features and gameplay Command has to offer. While you may be able to complete the scenario without them, you should do so at your own risk!! Navigate your way through an emerging crisis. Utilizing the Multi Domain Strike planner, Ops Planner, Cargo 2.0 and palletized munitions, you will have to manage multiple air to air refuellings, synchronized multi domain strikes, as well as the logistics involved in evacuating civilians out of harms way in a constantly evolving scenario

CMO Update - v1.05.1307.19

Severus Lupussteam_community_announcementspatchnotes

1101d ago

We have a new update out now for Command: Modern Operations. Besides bugfixes and tweaks we have added additional support for sensor groups. The complete changelog is available below: Change History: v1.05.1307.19 – 28th July 2023 * Added: #15173: SBR Add Support for Sensor Groups * TWEAK: Minelaying behavior (Assume if a mine is nearby and not active, and the unit is a ML type, then it laid the mine and it can ignored for now) * TWEAK: UAV/UCAVs of small size can be catapult-launched and retrieved on platforms without dedicated air facilities * TWEAK: Restored TO/LA check box on Edit A/c form * TWEAK: Aligned "Add AC" and "Add boat" window layouts * FIXED: Submerged contacts never engaged by AI * FIXED: No fire inside no-nav zone (Added a flag to the NoNavZone that designate it as a no fire zone (default is true) so that the user can decide if allowing the unit to fire in the zone or not) * FIXED: Docking Facilities Issue on DDG 125 (if the first dock facility was unable to host the boat the other ones were not checked) * FIXED: Deployed mines not appearing in weapons fired export * FIXED: Missing implementation of "Drifting Mine" behaviour * FIXED: Mission Editor Causing Reproducible Crashes * FIXED: "Hidden" Thermal layer/databox info broken * FIXED: Missing illumination arcs on DB viewer * FIXED: #15188: Extreme wingman separation * FIXED: SBR with MCM failing * FIXED: Strike mission escort flights can not be generated * FIXED: WRA Different Weapon Allocation * FIXED: CEZ transparency was not serialized and deserialized * FIXED: CEZ custom altitude was not able to be set to a value < 0 * FIXED: MPAs and Helis not dropping Sonobouys * FIXED: #15139: Mission Level WRA GUI: Choices Revert Back to "Various Settings" * FIXED: .Phase in mission wrapper * FIXED: PCLS broken by incorrectly applied intermittent-EMCON clause * FIXED: ACs were RTBing without fire (specific case) * FIXED: CEZ Trannsparency was not set rendered correctly. Transparency value was not set if changed via text and not via up down arrows * FIXED: #15172: SBR Generate Delta Template Errors * FIXED: crash on scenario reload * FIXED: Add sub unit a 0 kts (not at creep) * FIXED: Mk1 eyeball is now operational at periscope depth if no other visual sensor are on platform and scenario is using CWDB * FIXED: Clicking on "sensor" hyperlink in contact recent detections list does not bring up the DB-viewer as expected if the sensor is in a loadout * FIXED: Logic flaw in Priority Target List doctrine evaluation may lead to infinite loop (ie. sim freeze) * FIXED: Weapon "Max Downrange" calculation returning infinity if MaxAltitude_AGL = 0 and MinAltitude_AGL = 0

Command Open Beta v1.05.1328.6

Samsteam_community_announcementspatchnotes

1124d ago

The latest Command Beta is available on the Open Beta branch. It is available on Steam only currently, via the open beta branch. Please use the following Guide as reference if you need assistance in accessing the beta branch on Steam. Build 1328.6 release notes (changes from B1328.5): ------------------------------------------------------------------ * TWEAK: Numerous tweaks on map engine & tile handling * FIXED: Strike mission escort flights can not be generated * FIXED: Command "run to absolute time" was caried accross mew loaded scenario * FIXED: BMNG Layer constituent BMNG and Relief layers render in alignment at high altitudes. * FIXED: Convergence zones render properly * FIXED: CEZ transparency was not serialized and deserialized * FIXED: CEZ custom altitude was not able to be set to a value < 0 * FIXED: MPAs and Helis not dropping Sonobouys * FIXED: #15151 - ALT+S in WEGO closes Multiplayer Window * FIXED: Null reference when retrieving altitude with a weapon selected * FIXED: Submerged contacts never engaged by mission-driven AI * FIXED: HGV trajectory issues (glider not terminal-diving early enough if it has a seeker activation point) * FIXED: #15139: Mission Level WRA GUI: Choices Revert Back to "Various Settings" * FIXED: Backwards orientation on Hermes 900 Tacview 3d-model. * Includes the new v501 releases of the DB3000 and CWDB databases. DB3000 v501 changelog: https://drive.google.com/file/d/1--wRLPWp0AHyu_oWhcUdzaucvI8GmXJo/view?usp=sharing CWDB v501 changelog: https://drive.google.com/file/d/1-6II6vMwT4u9QvYn-9lltj0YkEXwpJG3/view?usp=sharing

CMO Update - v1.05.1307.18

Severus Lupussteam_community_announcementspatchnotes

1152d ago

We are happy to announce the latest version of Command is ready for you to download and play. Included are bugfixes, tweaks, and QoL features added for customizing Weapons Release Authorization. Change History: v1.05.1307.18 – 6th June 2023 • ADDED: WRA shortcut-button in unit status panel • ADDED: On the "Scenario Migration" window, you can now customize the default WRA-range for AAW missiles when migrating a scenario • TWEAK: Aligned Editor "Set Unit Property" menu items: Replaced 'Set unit fuel & airborne time' with a new 'Set Unit Properties' which does fuel, air/sea time and alt/depth. Replaced the 'Set time at sea' with call to the above. • FIXED: #15168: Bug opening formation editor • FIXED: In some cases the units where requested to fire more weapons then they are carrying, causing fewer weapons to be delivered • FIXED: #15158: GUI Bug: Mission level EMCON depends on previously selected tab • FIXED: Do not drop the target if there is a salvo in place but you have to fire infinite weapons • FIXED: Kinzhal missile flies into space • FIXED: The Mission was looking for a new target if the previous one moved, instead of trying to reacquire it • FIXED: Strike Plan doesn't work as expected • FIXED: In some cases ACs where RTB before Winchester or target destruction • FIXED: Issue in retrieving the proper weapon based on the target type • FIXED: #15127: MDSP & WRA Issues • FIXED: #15048 "Unit is Damaged" Trigger goes off multiple times for the same unit • FIXED: #15061: Ford Showcase: ScenEdit_SetEMCON doesn't toggle sensors • FIXED: #14918: Strike Mission WRA not discriminating between Escort and Striker munitions • FIXED: Un-assigning unit changes condition of a non-operating unit. • FIXED: Un-assigning unit changes condition of a non-operating unit. • FIXED: LuaSetTigger() not using correct area RPs for relative bearing • FIXED: Lua ScenEdit_SetReferencePoint not changing bearing type unless 'highlighted' is present • Includes all official scenarios rebuilt to DB v499, with their default AAW WRA-range set to 75% of maximum range.

Command: Modern Operations news & patch notes

Explicit GNSS jamming and jammer units

Salvo simultaneous weapon arrival

Launch speed-dependent burnout for air-launched boost-coast AAW missiles

Incremental / timestamped saves

Vast A2AR improvements

Improved manual salvo control

Improved “one-third rule” on patrol/support missions

Area & Reference-point Manager improvements

Limpet mines revisited

Improved map settings UI

Other bits & pieces:

Command: Modern Operations news & patch notes

Explicit GNSS jamming and jammer units

Salvo simultaneous weapon arrival

Launch speed-dependent burnout for air-launched boost-coast AAW missiles

Incremental / timestamped saves

Vast A2AR improvements

Improved manual salvo control

Improved “one-third rule” on patrol/support missions

Area & Reference-point Manager improvements

Limpet mines revisited

Improved map settings UI

Other bits & pieces:

Steam news for Command: Modern Operations

Frequently asked questions

Explore SteamScope

Command: Modern Operations

Discovery

Deals & Pricing

Game Rankings

Browse by Genre

Browse by Studio

Tools & Database