![]() |
As best I recall: What I used to do was to focus primarily on target bearing (and I would then relate/orient myself to HIS track, with almost a complete disregard for anything else).
I would typically pop up for a look... every.two minutes or so. I usually did NOT look around much for escorts either, even if I knew they were there. Theu were so fast, there was not much I could do (I migtht take a shot if one presented himself close at hand, but otherwise, I ignored them.) CS |
If you're stalking unescorted merchantment, a great way to check the accuracy of your TDC solution is use infrequent sonar pings.
Set up your solution using whatever method you normally use. Make sure PK is turned on. Then, at intervals of your choosing, and while you're in a screen that shows the TDC so you can watch the projected range, use the orders bar to ask for a 'Range to target' from sonar. When soanr responds in the message box, compare that range with the TDC's computed range. They should be identical to within a few yards. If not, if means your speed or AOB estimates are off. Or perhaps you've misidentifed the target and are using incorrect height measurements to get the range. The important thing is that over time, small innaccuries in your solution will translate into big discrepancies in computed TDC range versus actual range, and active sonar pings will show these errors. Unfortunately,like I said, not advisable when warships are lurking about as they can detect your sonar pings. |
All times are GMT -5. The time now is 10:41 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.