First sentence on that article was:
“Tides Of War”, the new DLC pack for Command, is launching very soon .


Sorry. I had misinterpreted the next sentence in the article, which says that the DLC is "accompanied by" the 1.09 game update, to mean that the game update had already been released in ...

Yesterday, the release of Command version 1.09 was announced[1]. I have therefore just tried to update to it.

The version of Command currently installed on my computer, according to the launcher, is 1.08.1728. I first tried using the auto-update tool accessible from the launcher. It claimed that I ...

Could it instead be possible, at the user interface level, to hide the icon (but not the area of uncertainty) of the detected contact so that only the icon of the out-of-communication unit is visible and clickable at that location? This would at least ensure that right-clicking on that unit will ...

I have now installed CMO version 1.08 build 1676. Thank you for your patience earlier.

After some experimentation, I made a new scenario in which the friendly submarine is initially in communication and not detected by the ship. Now, no repetitive contact dropping or repetitive messages occur[1 ...

I am using Command version 1567.6. When I did a check for updates in the launcher, no update was offered.

The attached scenario demonstrates the problem. Upon running this scenario, you will see that the friendly submarine is repeatedly detected and dropped as described in my initial post.

Procedure to reproduce

Create a scenario in which the "realistic submarine communications" feature is enabled. This scenario only needs to have one side, which is controlled by the player.
Add a surface ship with a passive sonar.
Place a submarine close enough to the surface ship for the ...

Understood. I intend to comply with this decision. I will make no further attempt to publish the materials contained in that post, or anything resembling those materials, anywhere in any form.

To avoid further violations of rules, I further ask:

Am I allowed to continue to possess, purely for ...

Earlier today, less than 2 hours ago, I made a rather large forum post titled "A method for interfacing with external software" in the "Lua Legion" section of this forum. Upon returning there, I could not find that post. It also does not appear in my user profile. In general, I do not find any ...

Yes, the speed is the problem in an indirect way: the faster the submarine is allowed to go while intercepting, the closer it is to pointing directly toward the target. Therefore, at an adequately high speed, the target is within the weapon arc while the submarine is on its intercept course, while ...

I have just updated Command to version 1328.18. After the update, I now observe the behaviour you describe.

When making the scenario, I made the frigate auto-detected so that the submarine would enter the "engaged offensive" state and begin moving toward an intercept point almost immediately after ...

Changing the "number of units that investigate" alone, without changing any other setting, has no effect in my testing. It appears that attack speed alone produces the behaviour you describe.

The results when attack speed is set to flank are quite unsurprising. A faster submarine needs to "lead the ...

I have just tried the "opportunity targets" setting. It does not appear to have any effect.

In my testing, I cannot identify any circumstance in which the submarine turns away from its intercept course specifically to unmask a weapon. If the scenario is allowed to run well past the time at which ...

Procedure to reproduce:
Run the attached scenario. The surface ship which acts as the target is made auto-detected for simplicity and reproduceability.

Expected behaviour:
When the target ship comes into torpedo range, the submarine should immediately engage it with torpedoes.

Actual ...

Procedure to reproduce

Create a scenario containing a submarine under the player's control. Start playing that scenario.
Give that submarine a waypoint.
Select that submarine by clicking on it on the map.
Deselect that submarine by clicking on a location on the map not occupied by any units ...

Background
I was inspired by this[1] recent post which showed that I was not the only person with this concern.
The colour of certain parts of certain map layers has very little contrast with the colours of certain unit symbols. As shown by figure 1 below, this is especially true between the ...

Procedure to reproduce
Run the attached scenario as side "aaa".
Make sure that the "targeting vectors" map option is set to "all".
When the submarine's position becomes known with adequate accuracy, command the ship to attack the submarine using an ASROC.
Optionally, perform this procedure in the ...

Procedure to reproduce
Run the attached scenario in the mission editor to allow the control and observation of both sides.
This is the same scenario as used in my previous report[1]. Unlike for that issue, automatic evasion should never be turned off for the ship when reproducing this issue ...

Procedure to reproduce
Run the attached scenario as side "aaa".
Attack the ship with a torpedo.

Optionally, before running the scenario, disable automatic evasion on the ship for reasons discussed below.
Optionally, immediately after the torpedo seeker has detected the ship, switch to the ship's ...

Thank you for your general clarification of how and why certain things in this game work the way they do.

In creating this mission, I never imported a template "into" any existing group; the template import was literally the first action taken when creating the mission. The aircraft affected by ...

Procedure to reproduce
Run the attached scenario as side "bbb".
The single target ship should be quickly detected by the patrol mission.
The strike mission should then launch.
If necessary, manually control the movements of the patrol aircraft to keep the target detected by radar and prevent the ...