![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#5 |
Sparky
![]() Join Date: Jan 2009
Location: running silent 700 meters off your starboard bow..
Posts: 152
Downloads: 50
Uploads: 0
|
![]()
i wasnt trying to be an ass, i was just teasing you because it was such an outrageous number, put yourself in the reader's perspective.
not to mention id rather be shot at by those torpedoes that the ones helos drop right on top of you. ![]() sonar interpretation is just as important as using the TMA. as far as classification is concerned, the 688 class subs seem to have a more reliable nb classification as opposed to the russian ssn or ssks. dont forget to change frequencies and use the towed sonar array for most of the nb classifying that you do. keep the filter on (at the proper range, first contact in lower frequencies are usually correct, or close) and dont forget to scroll through (arrows) sometimes if you suspect what it first tells you to be incorrect. (known intelligence briefings, visual information, etc) other times, it comes down to two or three and you have to narrow it down even further using other methods... 1. like active sonar intercept frequencies. (compared to the USNI reference ranges under the sensors tab) it may even be a torpedo w/o audio announcemnt from AI if the frequency is real high. 2. reading the demon display after you designate and track it (again see the USNI or game manual) to at least rule out other possibilities... to see how many screws has, if its a high tpk, chances are its a merchant ship. 3. just flat out visually IDing them using the periscope (on surface contacts) 4. just like torpedoes, there are certain ranges that are just too ineffective. try getting closer. also... dont forget that when using narrowband and making course changes this creates the "ambiguous" bearing marks on your sonar. wait until you are done turning (and then the towed array after that) before you go looking at it again. or observe the contacts that dont change bearings while you're turning and then try looking at them through a different array, chances are if they exist on 2 different arrays, its proabably a real contact. dont forget that the towed array turning to match your heading will sometimes produce your OS as a contact. if youre in an akula and just come round to finish a course change and nb shows and akula..its not another akula, its you. if all else fails and youre really unsure, you can just turn the truth filter on until you get the hang of doing sonar manually and observing how the contact behaves on the sonar from there to familiarize yourself with classifiaction. hint: you know you got it right if what you classify in narrowband shows up on the navigation map. as far as separating multiple contacts from the some bearing, pay mind to which of your sensors detected it by the color codes in the LOBS themselves. ( red for visual, purple for the towed array, etc) sometimes its just 1 contact from different sensors, and you can just merge the tracks in the TMA plot, cutting down the clutter and confusion going on in the middle of a potential scenario. again, i encourage this: http://www.commanders-academy.com/wi...sonar_.28NB.29 |
![]() |
![]() |
|
|