[DB ISSUE] Tango-class (Project 641B) MGK-100 sonar appears useless compared to older Foxtrot MG-10M
Posted: Fri Jun 19, 2026 5:45 am
I've been testing the Tango-class submarine in CMO and I believe the MGK-100 Kerch sonar may be incorrectly modeled compared to the older Foxtrot-class MG-10M.
Observed behavior:
Foxtrot (MG-10M)
Passive detection range (database): ~10 nm
Passive detection range (in practice, shallow/coastal waters): Works consistently
Active detection range (database): Reasonable
Tango (MGK-100 Kerch)
Passive detection range (database): ~4 nm
Passive detection range (in practice, shallow/coastal waters): Drops to ~2 nm or less, often detects nothing
Active detection range (database): ~0.5 nm (suicidal and useless)
The problem:
In most scenarios (Baltic, Barents Sea, coastal waters), the Tango is blind. I cannot detect anything unless the target is practically on top of me. The active sonar is completely useless at 0.5 nm — it serves no purpose, not even for final targeting.
This makes the newer, more advanced Tango (digital sonar, better processing) consistently inferior to the older, simpler Foxtrot in actual gameplay. This does not seem historically accurate. The real MGK-100 was not a downgrade from the MG-10M.
My questions:
Is this intentional? I may be using the Tango incorrectly (although I can use the Foxtrot correctly/efficiently)? A 2 nm practical detection range makes the platform unusable in most scenarios.
Is the 0.5 nm active range correct? Even for an "attack sonar" meant for final targeting, this seems extremely low.
Are there any plans to review these values, or does anyone have a workaround?
Thank you.
Observed behavior:
Foxtrot (MG-10M)
Passive detection range (database): ~10 nm
Passive detection range (in practice, shallow/coastal waters): Works consistently
Active detection range (database): Reasonable
Tango (MGK-100 Kerch)
Passive detection range (database): ~4 nm
Passive detection range (in practice, shallow/coastal waters): Drops to ~2 nm or less, often detects nothing
Active detection range (database): ~0.5 nm (suicidal and useless)
The problem:
In most scenarios (Baltic, Barents Sea, coastal waters), the Tango is blind. I cannot detect anything unless the target is practically on top of me. The active sonar is completely useless at 0.5 nm — it serves no purpose, not even for final targeting.
This makes the newer, more advanced Tango (digital sonar, better processing) consistently inferior to the older, simpler Foxtrot in actual gameplay. This does not seem historically accurate. The real MGK-100 was not a downgrade from the MG-10M.
My questions:
Is this intentional? I may be using the Tango incorrectly (although I can use the Foxtrot correctly/efficiently)? A 2 nm practical detection range makes the platform unusable in most scenarios.
Is the 0.5 nm active range correct? Even for an "attack sonar" meant for final targeting, this seems extremely low.
Are there any plans to review these values, or does anyone have a workaround?
Thank you.