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
So, what I've done is to use the 1x sonar setting, but adjust the ambush distance for AI subs to 3000 yds (which is the same as for the player) and disable "all sub encounters are ambushes" because otherwise it leads to a very non-historical frequency of sub attacks on fast moving task forces. To compensate the AI, I don't initiate evasive maneuvers by my ships until after the first torpedo hit. This matches how the AI plays when it is attacked by submarine launched torpedoes.
So, the resultant game play is that there are fewer sub attacks, but those attacks usually result in a hit for the AI, and the AI subs are harder to find because they are further away. To my mind, that's more historical than the way the game is currently set up.
E.g. Detection Range (based on Sea State and Weather) = 64%
Detection Range = 1920 if you're being noisy (i.e. moving at full speed, turning hard, and presenting your side to the AI)
Layers (for subs): If above the layer depth, the duct strength acts as a multiplier (e.g. 1.5), in the case above, detection = 2880. Below the layer might be 74%, so detection = 1421.
A sub speed of 9kns yields full detection range to the AI. I've noticed detection seems linearly proportional to speed, so moving at 2kns means an additional 78% drop in detection range (assuming US subs). There is a minimum detection range of what looks like about 250-300 yds, so stopping completely will not make you invisible. Understanding detection ranges allows the player to make better submarine speed choices during an attack's evasion portion.
I have noticed the newest version has given the AI subs a buff. They get to span in 1500 yds to the port or starboard (usually at 45º to the convoy's base course) and the torps seem to track a target right up to the moment they 'activate' (i.e. 500 yds from launch). It's like they're wire-guided for the first 500 yds. I used to accelerate my lead DD (the usual target) when I first began to see a torp launch i the distance. Given the closer spawn range and the apparent wire-guidance during the initial phase of a torp track by AI subs, this can make torpedo evasion a bit trickier. Use accordingly.
So, I was wrong about the sub being detected by passive sonar (hydrophone) at great distance when in the Duct. It seems to be much more simplistic than that with periscope depth triggering detection. Although, I'll have to run this test in higher sea states to see if sea state is a factor. Subs do have something protruding above the surface when at periscope depth with the scope down. I don't know what that is.
I never go above 10-12 kns when doing ASW. I'll backtrack the torpedos to their source (which is itself 500yds/m from the launch position of the submarine and rush there (typically at about 20kns) but slow to 10kns when I start searching.