ASW not working

[slimatwar]

I'm on build 1468CIV and the scenario is "Kearsarge Comes to Pemba Island, 1967". The S2 Trackers in my two ASW missions don't attack the two Soviet submarines.
Another annoying issue: I'm continuously getting "new surface contact" messages about the damaged(NO COMM) AO51 which is part of the Kearsarge Carrier Group and reports from the AO51 about newly spotted units on the CVS Kearsarge.
It's ridiculous getting notifications about spotted units that are under my control!

[thewood1]

Where did you get the original scenario? There is something weird going on with that sub. It says its at 400 ft depth, biut the S-2 says it can see it by sight. There is no way to explain that.

[slimatwar]

Where did you get the original scenario? There is something weird going on with that sub. It says its at 400 ft depth, biut the S-2 says it can see it by sight. There is no way to explain that.

What do you mean "original"? I downloaded it from "...ready scenarios for Community" on page 39. Another weird issue in that scenario, is that biologics became HOSTILE to U.S. side.

[thewood1]

How would I know where you got it from? Its not in the community download or boxed scenarios. What you told me is all I needed to know but without the attitude. Frankly, you generally get what you pay for in user built scenarios and you should most likely take it up with the author. The sub is just acting weird and I thought I'd check it out.

[thewood1]

The reason B-130 isn't being attacked is that the contact is over 30 minutes old. The issue seems to be that the contact isn't cleared. The entire encounter between the B-130 and the S-2 broken. The B-130 is listed as having been detected by eyeball 34 minutes before. If its at 422 ft, that can't happen. All the other S-2s attack subs they find. Again, I would take it up with the author first.

[slimatwar]

The reason B-130 isn't being attacked is that the contact is over 30 minutes old. The issue seems to be that the contact isn't cleared. The entire encounter between the B-130 and the S-2 broken. The B-130 is listed as having been detected by eyeball 34 minutes before. If its at 422 ft, that can't happen. All the other S-2s attack subs they find. Again, I would take it up with the author first.

Just to make things clear: By the term "attack" I don't mean just engagement, I mean launching torpedoes. And neither S-2 launched a single torpedo.

[thewood1]

OK, so the one way on the left I already mentioned. The only other Soviet sub I see is the one in the pic. Someone fired a torpedo and the ASW mission WRA says one torp from one platform. And there is already a torp inbound. So the S-2s won't fire.

[thewood1]

I deleted the in the water torp and put all other units on hold fire. The S-2s immediately closed on the sub. After dropping them to 300 ft, It took a couple passes and then one of them dropped a torp and killed the sub.

[slimatwar]

OK, so the one way on the left I already mentioned. The only other Soviet sub I see is the one in the pic. Someone fired a torpedo and the ASW mission WRA says one torp from one platform. And there is already a torp inbound. So the S-2s won't fire.

There's also a Foxtrot (B-130) to the NW. The only torpedoo seen on the picture was fired from FF 1037. Torpedo launching in ASW missions didn't work even for biologics when they turned to hostile, some minutes ago.
The scenario looks a bit buggy so I'm not going to deal with it any more and I thank for your reply.

Another annoying issue : i'm receiving contant notifications about a new surface contact , which is the out of comms damaged AO 51,part of the Kearsarge group. Why does this happen? How can I stop this ?

[thewood1]

Can you at least confirm that the settings weren't correct on the initial two S-2s you clarified?

I already mentioned the B-130 issue.

As to the aux ship notification. This happens sometimes with comms disruption. I would suggest upgrading to the current build. That was an issue that was fixed at one time.

[Nikel]

Another annoying issue : i'm receiving contant notifications about a new surface contact , which is the out of comms damaged AO 51,part of the Kearsarge group. Why does this happen? How can I stop this ?

Also happened to me while testing a previous version of the scenario in a previous build of the game. In this case the cruiser Woerden, only stopped when finally sunk.


https://www.matrixgames.com/forums/view ... 6#p5187246

[thewood1]

This has been an issue off and on with the comms option. Its basically the spotting ship having no memory. It has been fixed before, but its actually doing what its supposed to do as to not communicating and spotting. Its just the spotting unit has to have a memory of the spotted unit. Its the risk of the scenario designer has in setting comms disruption as an option.

Again, you should talk to the scenario designer about disabling comms disruption.

[thewood1]

Since we started this thread around ASW supposedly not working, can we settle that ASW is generally working?

[slimatwar]

Since we started this thread around ASW supposedly not working, can we settle that ASW is generally working?

As I said in my previous post, the ASW mission in that scenario didn't work for me. I'm talking about the previous version 1468CIV. Do I have to test it in the most recent build by restarting the scenario?

[thewood1]

I ran it both 1468 and 1483. Changing the WRA worked in both.