Command v1.07 Update - Build 1567.6

[LiamR]

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).

You can download the update here.

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/1dPLTsb ... sp=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: [B1468] 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

[Mgellis]

Excellent work! Thank you.

Quick question...were you able to fix the issue with the database entries for submarines not showing? I didn't see it mentioned.

Thanks again.

[HalfLifeExpert]

Excellent work! Thank you.

Quick question...were you able to fix the issue with the database entries for submarines not showing? I didn't see it mentioned.

Thanks again.

Unfortunately it's not fixed, as I am unable to see that part of the DB after installing this patch

[Mgellis]

Yes, the bug is still there. And it seems to be sporadic through a lot of my scenarios now. I never noticed it before (of course, I wasn't checking for it) and it seems to stay with a scenario even when I upgrade it to a new database.

I can look at the specifics for the individual vessels that are already in the scenario--for example, with the Charlie II in one scenario, I can open up its sensors, etc. and look at them. But if I click the submarine type on the right-hand panel and open up the database viewer, there is no record for it. Or the whole game crashes.

I'll add more about it that I've been able to find out in the Tech Issues forum.