[AVGWarhawk]

Originally Posted by Fragtzack

Thanks for the reply. Think your missing a key point about the "no contact" message I posted.

The message in game is saying "No contact on bearing XXX", which is not correct. The sonar man is actively tracking the target just fine, however the text message is saying "No contact on bearing XXX". If the sonarman was not tracking the target due to periscope or war/merchant tracking, the message should be "No contact found", however the mesage is "No contact found on bearing XXX". The sonar man keeps sending me contacts, but when I go to the sonar station to manually listen to the screws myself...there is nothing there. Yet, I can see the ship with in 5000 feet and the sonarman is tracking the ship with "no contact on bearing XXX" messages. The "no contact on bearing XXX" is just part of the message, the sonarman is also saying the estimated speed of the target. The bugged messages look more like this

"No contact on bearing XXX, slow speed, closing."


I know for sure this is a bug, tested this for many hours last night. Further proof that this is a bug:

When a vessel is encountered that is missing the sound data (I think the hydro and mix sounds of the props), if I save the game with that problem ship in sonar range, the game crashed to desktop every time I try and reload that save game. I went through the ship configs with Silent Editor, but am not seeing anything that looks wrong.

The problem seems to be limited to the ships from RSRD where there is 2 entries in the recognition manual for the same ship type. Ie, there is a normal HogTypeA ship, but RSRD also adds another ship that is identical to HogTypeA but is called MARU SOMETHING. Note, that in this campaign where I am testing, I sunk the MARU SOMETHING on my first patrol and the sound worked correctly. However, the MARU SOMETHING is now gone from the recognition manual and everytime I encounter a ship type like the MARU SOMETHING (THe Hog Island type) the sound is now broke. The Hog Island type is still in the recognition book.

I have encountered this bug on more then one occasion for the HogTypeA merchant ship in particular.

Not sure. One way to test is deactivate RSRD and see if this problem stops.