[Build 1900.24] Command-guided AShM midcourse updates ignoring the launcher state

Post bug reports and ask for game support here.

Moderator: MOD_Command

Post Reply
vexxedcrinoid99
Posts: 1
Joined: Sat Nov 14, 2026 4:00 am

[Build 1900.24] Command-guided AShM midcourse updates ignoring the launcher state

Post by vexxedcrinoid99 »

Version v1.10.02 / Build 1900.24
Database - DB3K v519

Subject: Command-guided AShM midcourse updates ignore the state of the launcher; they seem to depend only on in-comms side tracking.

Description: Command-guided anti-ship missiles seem to take midcourse updates from any side unit that is tracking the target and in comms. The launching platform doesn't appear to play any role post-launch; datalink, channel count and depth don't appear to have any effect. Have tried with Realistic Submarine Comms on, and no change was seen.

Setup: Had 12x isolated lanes, each on its own side, so no track gets shared between them. An example lane looks like the following: 1x Echo II (Sub ID 279) firing 2x P-6 (Weapon ID 1681) at a SL-7 (Ship ID 240) ~200nm away at 30kt; the ship turns hard after launch, with the turn ending around ~8nm from the launch-time pos. Tracker is a Tu-16RM Badger D (Aircraft ID 1321 w/radar ON, no ASM datalink). Setup replicated across the three .scen files; 1x with Realistic Submarine Communications (RSC) and Communications Disruption (CD) off (A), 1x with RSC on and CD off (B), and 1x with both RSC and CD on (C). All are attached in the .zip.

Got the following results: missiles follow the turn whenever an in-comms tracker holds the target, and otherwise fly to the launch-time aim point. Also, in a separate manual test, a Gabriel V from a Saar 5 (Ship ID 2497) behaved the same way; it corrected from the Badger D's track while the Saar 5's radar was off. The Saar 5's command link (Comms ID 148) has 'WeaponLinkRequiresSensor = 1', unlike the Echo II's (Comms ID 49, = 0), so that flag doesn't change the behaviour either from what I could test.

RESULTS (target hit, out of 4 runs)

Results (target hit, out of 4 runs; identical under all three settings A, B and C, so 12 runs per lane):

Missiles corrected and hit:
  • Tracker on, Echo II surfaced (control): 12/12
  • Tracker on, Echo II dived to 100-300 m: 12/12
  • Tracker on, Echo II deleted after launch: 12/12
  • Tu-95RTs Bear D tracking, Echo II deleted: 12/12
  • 4 fired from 2-channel launcher (Comms 49): 12/12 (damage in several runs consistent with more than 2 missiles hitting)
  • Juliett (Submarine 278, no command link): 12/12
Missiles did not correct (flew to launch-time aim point and missed):
  • Tracker radar off after launch: 0/12
  • Tracker set outOfComms via Lua (radar still on): 0/12
In reality, the P-6 (SS-N-3 Shaddock) needed the launching platform (in this case the Echo II) to be surfaced and guiding it until the seeker lock-on, and should really only take updates while its guiding platform (the launcher or a unit with compatible offboard link like the Tu-95RTs (Comms ID 276)) is: 1.) alive, 2.) in comms (surfaced or at the mast depth for subs where applicable), 3.) within the limits of the channel link, and 4.) holding the track itself or receiving it over a link that carries it. If these can't be met, it should really be flying to its last updated aim point and search from there.

Supplementary Info: Updates would appear to come from any in-comms side tracker; doesn't appear specific. Also, doesn't appear that the channel limits for the missiles are enforced (in this instance, that I could test anyway).

Therefore, wondering if this is an intended feature or not? If not, is it possible to tie updates to the guiding platform and its datalinks?

Apologies in advance if I have left anything out/approached this wrong - first time posting here, but loving the game - amazingly fun and exceptional attention to detail! Thanks in advance to anyone who can shed some light/look into this.
Attachments
AShM Scenarios.zip
(132.81 KiB) Downloaded 3 times
Post Reply

Return to “Tech Support”