![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#16 |
Ace of the Deep
![]() Join Date: Jan 2006
Posts: 1,140
Downloads: 5
Uploads: 0
|
![]()
I personally wonder at times whether we should just eliminate that bearing ambiguity. With the frigate, the signal will resolve with a tiny, weeny turn and the false signal won't bother you again. With the subs, you might somehow resolve the false contact and squelch it, but the auto crew just plots it again in my experience.
I'm sure the disadvantage can be reduced by upping sensitivity as one sees fit (I've already proceeded to try that privately so Russian sonars progress from -8 to -10). And there is no point in pretending the Akula is as good as the Seawolf in either silencing or sonar. Something else one can try is change the torps of those ASW missile dropped torps from Circle to Snake. Overall, it is a more useful setting. Imagine when Seawolf shoots you, and you send off ASW missiles down the bearing line in 5nm increments, all of which start homing... To forestall stupidities like deploying the missiles every nautical mile with a 14 SS-N-27 launch, try this. Put the new -27 torp on the Stallion (it is just a torp carrier, changing the torp carried shouldn't be outside the realm of possibility), and change that one's homing logic to Snake. Leave the SS-N-27 as is. That gives people a real reason to use it (right now, its slow torpedo and the limited utility of 100km class ASW ranges makes it not too attractive). Another option, give them the Resolve Bearing thing, but on the -16, and drop sensitivity by two points, justified by: 1) They need contact on both arrays to do this. 2) They probably need more than a minimal signal on the weakest array to do the resolve automatically. This turns the -16 into a Bearing Resolving sensor, and more people will deploy it. |
![]() |
![]() |
|
|