Delayed torpedo launch
Posted: Tue Jan 28, 2014 9:32 pm
Playing Duelists (B486) a Soviet wolfpack is heading south in line abreast, with an Oscar on the extreme west, and a pair of Sierras in the center and east position. The Oscar detects a British sub to the WSW, and maneuvers quietly to avoid it, while the Sierras turn W to fire SS-N-16s at the imperialist lackey (from a safe distance, of course).

The first SS-N-16 misses, but it spooks the SSN up to flank speed, so the Oscar (realizing the SSN can't hear a thing) turns towards it and allocates a single torpedo shot using Ctl-F1 for a Bearing Only Launch. Before the launch can happen the second SS-N-16 kills the SSN. Celebrating, the wolfpack turns south once more. The time is approximately GMT 18:15.

The Oscar is unassigned and not engaged with any targets, is pessimistic, won't engage opportunity targets, and even has Hold Fire orders.
Twenty one minutes later, at approximately GMT 18:36, the Oscar suddenly fires a torpedo down the old bearing to the (now dead) SSN.

The torpedo seeker goes live almost immediately, confirming that this is almost certainly the Bearing Only Launch.
So it looks like a BOL launch can hang around in the queue and does not immediately get cancelled when its target dies, and it can fire off unpredictably at a later time. Unfortunately, I can't think of any good way to cancel it. The sub was already unassigned, disengaged, and with Hold Fire orders, and there is no way to unallocate an allocated weapon.
The behaviour is reproducible after a reload. I've attached a save. If you let it run, does the torp launch for you too?

The first SS-N-16 misses, but it spooks the SSN up to flank speed, so the Oscar (realizing the SSN can't hear a thing) turns towards it and allocates a single torpedo shot using Ctl-F1 for a Bearing Only Launch. Before the launch can happen the second SS-N-16 kills the SSN. Celebrating, the wolfpack turns south once more. The time is approximately GMT 18:15.

The Oscar is unassigned and not engaged with any targets, is pessimistic, won't engage opportunity targets, and even has Hold Fire orders.
Twenty one minutes later, at approximately GMT 18:36, the Oscar suddenly fires a torpedo down the old bearing to the (now dead) SSN.

The torpedo seeker goes live almost immediately, confirming that this is almost certainly the Bearing Only Launch.
So it looks like a BOL launch can hang around in the queue and does not immediately get cancelled when its target dies, and it can fire off unpredictably at a later time. Unfortunately, I can't think of any good way to cancel it. The sub was already unassigned, disengaged, and with Hold Fire orders, and there is no way to unallocate an allocated weapon.
The behaviour is reproducible after a reload. I've attached a save. If you let it run, does the torp launch for you too?
