Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I don't think this is specifically a Yu-5 issue though, I believe this issue is AI-specific and affects any wire-guided torpedos... We're seeing more reports of this now because of the frequency in which the Yu-5 is encountered in the new campaign.
Months ago I reported the same issue with the TEST-71 fired from a Tango. I had killed the sub after they shot a torpedo at me first. *That* seems to be the trigger... killing a parent sub while they are wire-guiding their torpedo.
At that point, instead of the wire being cut and the torpedo going into its standard homing mode, it gets locked into an AI "wire guided" routine and tracks its target regardless of countermeasures.
Yeah I finally found the post! In fact I have a distinct memory of your initial topic started about this with a TEST-71 torp fired by Kilo I believe it was. So this maybe a broader issue with enemy wire-guided torpedos!
Yep, there were a couple different encounters I had with the bug, one of which was a Kilo that I had killed after it fired, the other was the Tango. Given that both subs carry TESTs and they were both killed after launching their torps before I saw the bloody things ignore all countermeasures... I put two and two together.
I do wonder, however... if the torpedo had not "gone active" yet before I killed the parent sub. If this is the case, it may mean that the AI updates the torpedos steerpoints via the wire, but once the torpedo goes active, the wire is cut, and it follows its normal homing routine.
I mention that because I have killed the parent subs before and not experienced the "Night of the Living Wire Torp"... so in that regard it is inconsistent... unless it has to do with whether or not the AI chooses to cut a wire prior to death, rather than the AI dying with it active.
There's only a few possibilities left, I think we're close to pinpointing the root cause of the issue...
I would suggest evade those Yu-series torps before they get a lock on you. These subs no longer use wire guidance to follow you once they are running away from you (i.e. unable to track your movement via sonar), so you can start evading as long as you see them starting to run away.
If it's intetional, I love the fact that torpedoes don't fall for the knuckle and decoy all the time!
But maybe there should be a better balance?
Right now we have the majority of torpedoes, all spoofable with the knuckle and the decoy...
All the time...
And then we have the occasional wireguided, 100 % un-spoofable torpedo, which never ever falls for knuckles or decoys... not even after the wire is cut...
- Dolphin 48
Yeah, I have heard other report this in the 1984 campaign in patch 1.09 e as well.
I played the 1.09 e to death, but never experienced this issue on that patch myself.
- Dolphin 38
One fired by a chinese Kilo just killed me.
The Yu-5 seems to be tough but possible to evade.
On the other hand ADCAPs are a total monster. I barely ever missed, even with a bearing only shot.
(Same thing when one gets to home-in on me)