[2021] Critical mechanics issue that has been reported and not fixed: CVs detect subs at 80m depth

A) I've reported this up to the proper channel. Will let you know if I hear something back.

B) In the meantime, while this is an advantage a CV player could have in reference to a submarine which is hunting him, a few points.
b1) The likelihood a CV player will notice the defensive fighters took off, or makes the connection as to why that might have happened... is small. You have a niche advantage in understanding this mechanic better than others, which is interesting in a sense. Some small game mechanic interactions can be cool little tidbits you can roll into an advantage.
b2) You can negate the player's advantage by calling to your friendly CV to briefly spot the enemy CV. The Fighters which protect the hull last for 10 minutes, so as long as the enemy CV has been detected within the last 10 minutes would remove this "early warning".

---

Anyway, I'll let ya know if I hear anything. Don't be afraid to remind me in a week or two.

This is actually incorrect.

While I do not know the actually distances/mechanics of the situation, the CV Hull is able to be spotted at a distance from a surface ship without displaying the !Detected indicator.

Example: A Midway has a 15km detection, and a stealthy DD is at 14.5 from the hull.

The Hull is spotted and can be fired at, but the CV Driver may not have an indication that the hull is detected until either

a) the DD is detected by actual spotting

b) the distance to the destroyer is reduced to (unknown value) by planes that have been detected and has started closing in while hunting the DD.

c) the DD closes to (unknown value) away from the CV Hull, which will then automatically give the !Detected warning.

It's one of those weird mechanical things. It's happened to me over a number of battles.

For instance, there are matches where I take off with my planes (which have a 10 km detection) and they are immediately spotted. This means a DD is within 10km of my hull... and yet my hull gives no indication of being lit. When I hunt for the DD, and I get within a range of it, suddenly my hull wakes up and shows "!detected".

To an extent, I always wondered if it was a built-in weakness that was never often exploited. Nonetheless, it's a thing and has been for years.

Yes, so what he's describing is likely a backend coding issue. A Midway might be detected out to 15km on the surface, but maybe 12km Aerial Detection. Instead of making new values, submarines seem to have been keyed into the Aerial Detection ranges at some point in their development.

While submarines can no longer spot to Aerial Detection ranges at Operating Depth, and could never spot that while at Maximum Depth... it doesn't mean that the original code during testing couldn't have used those variables and still cause a deep-in-the-code reaction.

My off-the-cuff guess is that there's something buried in Aerial Detection range stuff, and I've passed the word up and made my guess as far as a place to look. Still, outside of this bizarrely specific example, this isn't an issue that would have any effect on other ship interactions in the game. Kinda like the CV hull not always saying when it's detected.

Never did personally. I assumed it was intended. Like a way to provide long-range shelling safely? Heck, maybe it is~

To be honest, I never really thought much about it. I just knew it was a thing I had to deal with sometimes, and I've spoken on stream about how a DD can light the CV and torp it from near max range without ever giving a detected indicator.

Nope. Open-water conditions. It's a thing.

I believe a recently spotted/lit DD will correctly provide "Detected" even at max surface detect range. It could be something where the server obscures the location of an unknown/dark DD up to a point?

Either way, it's unique enough that I thought it adds flavor, even though it does put the CV at a disadvantage to some extent.