mikkey
Posts: 3142
Joined: 2/10/2008 From: Slovakia Status: offline
|
quote:
ORIGINAL: dusky It is a real game issue, at lest for me :). I believed that the contact and its AOU is completely wrong - checking in the editor proves me right, the sub is actually 100nm away from the edge of the AOU. So, I wanted to drop the contact and wait for it to be reacquired. Also, in an another scenario I saw a ship waste all its ASROCs on such an undroppable & extremely inaccurate contact (it was already marked as hostile). Yes, there are workaround, but none of them really works. a) I can order the ship to hold fire, but then I need to remember to cancel the order when a bogey appears. But anyway, all the other ASW assets will still race to prosecute the contact. To demonstrate this, just mark the sub as hostile (in the save from the original post) -- the F 39 Betwa will switch to Engaged Offensive and will run in circles above the "bad" contact (while the sub is actually 100nm away). b) I can mark it as friendly, but then I must remember to mark it back as hostile when it gets reacquired somewhere else. What is then the indented function of the Drop Contact option (P, PgDn, Num 3) when it is not able to drop a contact that wasn't detected by any sensor for a long time? :) I left the scenario run, the contact is already 45 minutes old, F 39 Betwa is dancing in circles and I'm still not able to drop the contact. Dusan, new Weapon Release Authorization will be very helpful in these situations.
|