Page 1 of 1
[FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jun 03, 2026 8:34 pm
by kritter
This device can't see anything even when it is dropped on top of the sub.
It used to work just fine until the last update.
Re: AN/SSQ 125 Broken after update
Posted: Thu Jun 04, 2026 2:43 am
by Raptorx7_slith
Thanks, logged as 0017352
Re: AN/SSQ 125 Broken after update
Posted: Wed Jun 10, 2026 7:20 am
by Dimitris
Fixed for the next update.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Sun Jun 14, 2026 11:09 pm
by Knightpawn
kritter wrote: Wed Jun 03, 2026 8:34 pm
This device can't see anything even when it is dropped on top of the sub.
It used to work just fine until the last update.
This seems to be an issue with other (all?) types of sonobuoys as well. In your test scenario I inserted an S-3B Vicking that dropped AN/SSQ 62E which were equally ineffective. I hope the fix is across the board
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Mon Jun 15, 2026 4:59 am
by Dimitris
Yes. The problem was not with the detection itself, but that the sonobouys were unable to link up with a suitable MPA platform to share their detection data.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Tue Jun 30, 2026 10:39 pm
by kritter
I tested them and they still don't work, and now I can't drop them manually either.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 6:34 am
by Nikel
I think you have to regenerate the scenario in B1892.
The B-21 you created, the sonobuoys or both are broken because they were created in a CMO version with a bug, the datalink is gone just when you start the scenario.
Added a SeaHawk, removed the default sonobuoys and added the AS/ASQ-125 and it worked.
- SB.gif (1.16 MiB) Viewed 380 times
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 1:13 pm
by kritter
I will try that.
Thank you
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 3:41 pm
by kritter
The buoys work, but I can't drop them manually now.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 3:50 pm
by Nikel
I dropped the one in the video manually.
The problem must be related with this new feature the devs added.
ADDED: New doctrine setting: Sonobuoy Use. Available settings:
* Automatic for search and localization (default): Sonobuoys are freely and aggressively used by AI-controlled aircraft for initial submarine search (often "carpeting" entire patrol/search areas). CAUTION: If this is used together with the "limited sonobuoys" realism setting, the force can very quickly run out of sonobuoys!
* Automatic for localization: Sonobuoys are not used for the initial search, but are dropped for firming up an already made contact or prior to attack.
* Manual (player order) only: Sonobuoys are not dropped by the AI at all. (Useful if you're low on them or want to handle it hands-on)
I would create a new thread with the new scenario.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 4:42 pm
by kritter
Yes I thought that so I set the doctrine to manual but it still didn't work.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 10:03 pm
by Dimitris
As Nikel said please open a new thread for this with a suitable save. Thanks!
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 01, 2026 10:20 pm
by kritter
Here you go.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Thu Jul 02, 2026 7:28 am
by Nikel
That B-21 is broken, and overpriced
I added another unit and can deploy them manually.
- MDSB.gif (1.79 MiB) Viewed 260 times
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Tue Jul 14, 2026 10:56 pm
by kritter
This is still broken but I think I figured it out. In the mount I am using it does not deploy any EER's.
However if I put the same number under the loadout it works, however I can not save the unit like that because when I load it the EER's are gone. So the EER's are not deploying with the mount and I have tried different aircraft.
Re: [FIXED] AN/SSQ 125 Broken after update
Posted: Wed Jul 15, 2026 5:27 am
by Dimitris
Thjs is an entirely different issue then. Please post this on a new thread.