[FIXED] Issue with torpedo re-attack & impact (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support



Message

rmunie0613 -> [FIXED] Issue with torpedo re-attack & impact (4/16/2019 5:33:27 PM)

Running through the AAR on a scenario I am trying to perfect... I came across the following. I am wondering how this submarine sank with a weapon damage of 0...was it somehow related to critical hits? Has anyone seen anything like this bfore?

11/25/2022 11:37:19 AM - [USN] New contact! Designated TORPEDO #11394 - Detected by SSN 793 Alamosa [Sensors: AN/WLY-1] at 233deg - Estimated 2nm

11/25/2022 11:37:29 AM - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 793 Alamosa is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #51511). Final probability: 45%. Result: 86 - FAILURE

11/25/2022 11:37:29 AM - Decoy (ADC Mk4 Mod 1 Sonar Jammer; Tech: Early 2000s) from SSN 793 Alamosa is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #51511). Final probability: 45%. Result: 15 - SUCCESS

11/25/2022 11:37:29 AM - All weapon seekers were spoofed - weapon missed target

11/25/2022 11:37:30 AM - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 793 Alamosa is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #51511). Final probability: 45%. Result: 19 - SUCCESS

11/25/2022 11:37:30 AM - All weapon seekers were spoofed - weapon missed target

11/25/2022 11:37:31 AM - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 793 Alamosa is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #51511). Final probability: 35%. Result: 1 - SUCCESS

11/25/2022 11:37:31 AM - All weapon seekers were spoofed - weapon missed target

11/25/2022 11:37:32 AM - Torpedo AT-2M #51511 is attacking SSN 793 Alamosa with a base PH of 65%. Final PH: 65%. Result: 35 - HIT

11/25/2022 11:37:32 AM - Weapon: AT-2M #51511 has impacted SSN 793 Alamosa.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa has suffered weapon damage: 0 DPs

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa is being hit by an underwater explosion at 7 ft!

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa has suffered blast damage: 48.1 DPs

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: AN/BLQ-10(V)1 has been lightly damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: NSSN VLS [2 Cells, 12 Missiles] has been heavily damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: CSA Mk2 Mod 2 [Mk151] has been heavily damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: Tomahawk Command Datalink has been heavily damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: 533mm TT has been lightly damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: AN/BVS-1 LLTV Component has been destroyed!

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: AN/BQS-15 has been lightly damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: AN/TB-29 has been heavily damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: VLF Radio [Unsecure] has been heavily damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: CSA Mk1 Signal Ejector has been lightly damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: Tomahawk Command Datalink has suffered additional light damage.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: AN/WLY-1 has been lightly damaged.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa damage report: Virginia has been heavily damaged.

11/25/2022 11:37:32 AM - Event: 'Points lost for US Submarine lost' has been fired.

11/25/2022 11:37:32 AM - [USN] SSN 793 Alamosa has been destroyed!



rmunie0613 -> RE: Curious damage result (4/16/2019 5:58:32 PM)

Also note in several of these that these weapons re-attack again and again, despite being decoyed away several times...eventually the odds are that they will ALWAYS win against the sub- in fact I have never yet played through a scenario in which I found and localized a submarine to attack it, and it survived...finding it IS a challenge often... but should there perhaps be a limit s to how often a weapon can re-attack?



Dimitris -> RE: Curious damage result (4/16/2019 8:27:58 PM)

Well the 0-damage impact is followed by blast damage, which means that the torpedo failed to penetrate but the external detonation (right beside the hull) was enough to fatally damage the submarine.

I'm more alarmed by the "All weapon seekers were spoofed - weapon missed target" message followed right afterwards by a weapon impact. Do you happen to have a pre-impact save of the engagement? Thanks.



Zanthra -> RE: Curious damage result (4/16/2019 8:58:52 PM)

I managed to create a scenario with the torpedo immediately reattacking every tick and attached it. It seems highly sensitive to the speeds and angles of the attack.



dcpollay -> RE: Curious damage result (4/16/2019 11:54:46 PM)


quote:

ORIGINAL: Dimitris

Well the 0-damage impact is followed by blast damage, which means that the torpedo failed to penetrate but the external detonation (right beside the hull) was enough to fatally damage the submarine.

I'm more alarmed by the "All weapon seekers were spoofed - weapon missed target" message followed right afterwards by a weapon impact. Do you happen to have a pre-impact save of the engagement? Thanks.

It appears as though the torpedo attacked a fourth time after the last spoof, but with no decoy attempts to stop it. 11:37:32 on the clock. That does not seem alarming to me....



Ancalagon451 -> RE: Curious damage result (4/17/2019 10:02:23 AM)

What I found weird is that there is only one second delay between each spoofing and the following attack attempt.

Shouldn't a spoofed torpedo have to overtake the target, start a looping pattern, reacquire the target, and then close again against it, before the next lot of endgame dice rolling starts?

All that sounds like it would take much more than a second to do.

Ancalagon



michaelm75au -> RE: Curious damage result (4/17/2019 12:09:22 PM)

Was time compression on?
Sometimes actions can be taken in sequence, but the last time update recorded can be at the start of the time compression.



rmunie0613 -> RE: Curious damage result (4/18/2019 6:27:01 PM)

D... thank you. No, I did not save prior to this on this run through, but have the same submarine in another save of the same scenario...same units...and that one is having a lot of strange things as well...HVPs flying backwards after their target destroyed..."Spy" unit does not move on course, instead only goes straight north or straight E (O or 90 degree bearing) etc..
I have not posted files on here before so not certain how, there seems to be no option, though I have posted more than 10 times lol, and much more than 7 days.

Edit...got it here



Dimitris -> RE: Curious damage result (4/21/2019 12:46:08 PM)

Thanks, logged and we'll take a look.



Dimitris -> RE: Curious damage result (4/23/2019 6:10:51 AM)

quote:

ORIGINAL: rmunie0613

D... thank you. No, I did not save prior to this on this run through, but have the same submarine in another save of the same scenario...same units...and that one is having a lot of strange things as well...HVPs flying backwards after their target destroyed..."Spy" unit does not move on course, instead only goes straight north or straight E (O or 90 degree bearing) etc..
I have not posted files on here before so not certain how, there seems to be no option, though I have posted more than 10 times lol, and much more than 7 days.

Edit...got it here


Can you please post that on a separate thread. Piling multiple issues on a single thread makes it MUCH harder for us to keep track of what is resolved and what remains to be examined. Thanks.



Dimitris -> RE: Curious damage result (4/23/2019 6:19:39 AM)

Just gave this a try, using B1009.27.9. Multiple runs. In each run, the torpedo behaved as expected: It attempted to engage, it was seduced or missed, and came around for re-attack before running out of fuel.

Here is an example of the last run (oldest messages on bottom):

quote:


9:34:22 PM - 9:34:22 PM - Weapon: AT-2M #8 has run out of energy... self-destructing

9:33:57 PM - 9:33:57 PM - All weapon seekers were spoofed - weapon missed target

9:33:57 PM - 9:33:57 PM - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 35%. Result: 8 - SUCCESS

9:33:57 PM - 9:33:57 PM - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 35%. Result: 50 - FAILURE

9:33:01 PM - 9:33:01 PM - All weapon seekers were spoofed - weapon missed target

9:33:01 PM - 9:33:01 PM - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 27 - SUCCESS

9:32:26 PM - 9:32:26 PM - Torpedo AT-2M #8 is attacking SSN 774 Virginia [Flight I] with a base PH of 65%. Final PH: 65%. Result: 66 - MISS - REATTACK

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 35%. Result: 95 - FAILURE

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 35%. Result: 66 - FAILURE

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk2 Mod 0 Torpedo Decoy; Tech: Late 1970s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 20%. Result: 96 - FAILURE

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk4 Mod 1 Sonar Jammer; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 87 - FAILURE

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 64 - FAILURE

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk4 Mod 1 Sonar Jammer; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 97 - FAILURE

9:32:26 PM - 9:32:26 PM - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 87 - FAILURE


So, at least with the current public version, I am unable to reproduce the original wierd circumstance.

Anyone else having better luck ?



Zanthra -> RE: Curious damage result (4/23/2019 8:17:57 AM)

It still seems to happen in the scenario I attached in post 4 although only in 1 second pulse mode. The torpedo passes by and goes around with high fidelity mode enabled.

quote:


21:32:30 - 21:32:30 - Contact AT-2M #8 has been lost.

21:32:30 - 21:32:30 - SSN 774 Virginia [Flight I] damage report: AN/BQS-15 has been heavily damaged.

...

21:32:30 - 21:32:30 - SSN 774 Virginia [Flight I] has suffered blast damage: 29.6 DPs

21:32:30 - 21:32:30 - SSN 774 Virginia [Flight I] is being hit by an underwater explosion at 7 ft!

...

21:32:30 - 21:32:30 - SSN 774 Virginia [Flight I] damage report: AN/TB-34 has been moderately damaged.

21:32:30 - 21:32:30 - SSN 774 Virginia [Flight I] has suffered weapon damage: 0 DPs

21:32:30 - 21:32:30 - Weapon: AT-2M #8 has impacted SSN 774 Virginia [Flight I].

21:32:30 - 21:32:30 - Torpedo AT-2M #8 is attacking SSN 774 Virginia [Flight I] with a base PH of 65%. Final PH: 65%. Result: 35 - HIT

21:32:30 - 21:32:30 - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 35%. Result: 36 - FAILURE

21:32:30 - 21:32:30 - Decoy (ADC Mk2 Mod 3 Torpedo Decoy; Tech: Late 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 35%. Result: 99 - FAILURE

21:32:29 - 21:32:29 - All weapon seekers were spoofed - weapon missed target

21:32:29 - 21:32:29 - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 21 - SUCCESS

21:32:28 - 21:32:28 - All weapon seekers were spoofed - weapon missed target

21:32:28 - 21:32:28 - Decoy (ADC Mk4 Mod 1 Sonar Jammer; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 26 - SUCCESS

21:32:28 - 21:32:28 - Decoy (ADC Mk3 Mod 1 Torpedo Countermeasure; Tech: Early 2000s) from SSN 774 Virginia [Flight I] is attempting to seduce sensor: Torpedo Seeker (Tech: Early 1970s)(Guiding weapon: AT-2M #8). Final probability: 45%. Result: 89 - FAILURE



Dimitris -> RE: Curious damage result (7/9/2019 6:55:04 PM)

Thank you, this was very useful.

Fixed for the next update release.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.90625