subb
04-18-2007, 11:08 PM
When the map finally started showing signs of good health and stability, these AARs were created in an effort to gauge in-game dynamics. I think I have more stashed away somewhere. I'll keep looking.
SESSION 1 AAR
******************************
MP tests / LWAMI 3.06 / CM detonation 0%
Session 1 AAR
Divers - suBB (kilo), Mr. E (akula-I)
Tasking: intercept 688 and prevent 688 from reaching dive point
AI tasking: Assist 688 in reaching dive point.
AI platforms(in the absence of human players): ffg, 688, helo
******************************
Comments:
About 2 hours after spawn we finally made contact with the ffg after I set possible intercept course based on intelligence we did gather and agree on followed by routine comms check on the interval. Positive ID was made by periscope and link was promoted to Mr. E. Based on the situation, the ffg was in a crossfire between the ‘wolf pack’ and too close for an ASM attack.
After initial contact I set an attack run course, eventually closing the distance until ffg was on HF. forcing a LAG situation on the ffg. The attack started with a salvo of wake homers and a spread of test71 combo 20 degrees over ffg bearing. Immediately afterwards I clear datum trying to gain final position of the ffg on periscope. The wake homers missed but the test71 spread caught up with him. After 1 test 71 detonated I re-route the other test71 to intercept, the ffg returns fire with a few salvos, Mr. E follows suite with 2 staggered salvos of wake homers which both missed.
After clearing datum I re-gain visual on ffg but he’s hurt, there is smoke and flames pouring out of the ship, port side. Mark final bearing and range, moments later I activate the last test71, which detonates on the ffg, witnessing the explosion before going under. The torpedoes from the ffg goe active and are closing based on ‘early warning’ measures. I basically had to disengage and ‘hand-off’ the ffg to Mr. E. for my own safety. I’m hoping he is going down at this point.
I seem to be the center of the ffg and helos’ attention entering and completing evasion up to 3 times, and still no sign of the 688. The 4th time resulted form a helo dropped torpedo of which was running circles around ownship. I run all stop and bottom the boat to try and let the fish run out of gas, or run aground, before continuing on. Luckily it paid off this time around. The torpedo disappeared from NB.
All of a sudden another TIW report from acoustics, and after checking NB it’s the ADCAP and not a mk46 or mk50 – I’ve found the 688. But the situation I was in didn’t allow enough time to start a track and promote link plus tubes were reloading from the torpedo attack on the ffg. Starfish torpedoes were loaded but the SNR of the ADCAP was very strong – he is close. ADCAP goes active and takes the CMs for the 5th time. After clearing data I go all stop scanning NB for the 688. Shortly afterwards Mr. E finally finishes off the ffg, but the helo quickly returns the favor – Mr. E is hit and he’s going down. Another TIW from acoustics but this time over a very wide bearing range – the 688 advanced and tried to attack from the starboard side closer to the rear. This time he caught up with me with my pants down and the fish failed to acquire the CMs dropped.
Mission results – all threats neutralized and area secure for safe passage of the 688.
SESSION 2 AAR
******************************
MP tests / LWAMI 3.07 / CM detonation 0% / ATMA off
Session 2 AAR
Divers - suBB (akula-I), Mr. E (kilo)
Tasking: intercept 688 and prevent 688 from reaching dive point
AI tasking: Assist 688 in reaching dive point.
AI platforms(in the absence of human players): ffg, 688, helo
******************************
Comments:
At spawn we had visuals and sonar contacts on non-important targets (neutral contacts) and without hesitation I immediately start patrolling. As the akula I wanted to make full use of the TA detection capabilities. We agreed on a comms check interval of 30 mins or so, and I assumed a cruise speed of 7 kts with TA at full scope to try and determine some general direction to start looking. I tried various patrolling methods, some standard, some out of creativity and in a general direction due east, checking TA baffles every so often. According to frags’ ESM data the helo has been searching in my general area, less than 20nm south of frag. Because of that I missed two comms checks, where the 1st attempt at the 30 minute mark nearly compromised my boat. Also any sort of intel I missed on those intervals, is now one hour old, and still no sonar contacts of interest yet.
I decide to patrol S / SE and attempt comms check as necessary and not on the interval, hoping the helo will finally decide to search elsewhere. After some time (about 3 hours it seems) contact was made on a faint 60 hz signal. To avoid risk of compromising my boat I resolve bearing on contact and determine the contact is not hostile, since the true bearing didn’t originate from the direction of the naval base, supposedly where the 688 and escort departed from, as mentioned in tasking.
Frag made note that the coast is clear on my end for comms check, while in the same token the helo entered his area and he went under to avoid visual detection. I’m now one and a half hours behind on intelligence reporting, hoping that this next comms check will reveal something to make up for all of that.
Finally, visual was made on the ffg, and it’s safe for me to promote link to frag. Frag streamed his wire to receive the data without compromising his boat either. I prep tubes for an ASM strike followed by stagger salvos of USGT and wake homers. Looking through the periscope the ffg CIWS was handling the ASM salvo nicely and entered a course due south, forcing his stern to point directly towards the bow of my boat. I should have not bothered with the ffg in fear of losing the possible element of surprise in case the ffg was pulling ahead of the 688, but the opportunity presented itself.
The 1st UGST detonates and I clear datum, update final mark on ffg, re-route the other UGST, and fire another salvo of wake homers. Avoiding being spotted by the helo, Frag warns me of the helo returning in my direction, and shortly after the helo starts dipping search – he is basically right on top of me. I drop an active CM and shortly afterwards acoustics reports TIW on a bearing between the two of us. I’m thinking it’s the helo but the fish didn’t go active for quite sometime – it has to be the 688. Frag diverts the helo attention away from me (thanks for that :D) enticing it with radar to attack, only to realize that frag had other intentions, frag shoots down the helo with the SAM launcher.
The TIW generated was the 688 attempting to attack frag, of which frag successfully evaded and his CMs convinced the 688 torpedoes to consider another target – the cruise ship aft of frag. We figure where the 688 is, and after slowing down I make one last visual on the ffg followed an ASW salvo on the 688s’ suspected position. Frag fired a spread of test71s at the 688 and the wake homers from me had the ffg running away from us, making use of that will buy us time to start working on the 688.
The 688 managed to evade our torpedoes with CMs and was running loud enough for a broadband TA contact, yet out of sphere range. A rough TMA of 4 lines revealed that the 688 was about 7nm north of ownship between the two of us on a westerly course. I went active hoping to draw the 688 away from frag, and even though the returns were pretty bad, still I managed to confirm range of the 688 and fire another salvo of UGSTs. Based on the TA sonar contact, the 688 was trying to shoot his way out and attempt to reach dive point. By traveling west and based on the orientation of own ship, the 688 moved into my TA baffles.
After an immediate course change and the UGST spread shot went active, one the UGSTs acquired, while I re-routed the other. Shortly afterwards the UGST detonates on the 688, I disable the other UGST to avoid friendly fire, and we receive orders to disengage and attempt to reach distance. Frag was picking up the ffg on ESM, he located the FFG and determined he was still too far away to do anything about anything.
Mission results – 688 was intercepted and destroyed, at least one RU sub reached safe distance.
SESSION 3 AAR
******************************
MP tests / LWAMI 3.07 / CM detonation 0% / ATMA off
Session 3 AAR
Divers - suBB (688i), Fragmaster (seahawk)
Tasking: 688i - reach dive point / seahawk - Assist 688 in reaching dive point
AI tasking:. intercept 688 and prevent 688 from reaching dive point
AI platforms(in the absence of human players): ffg, kilo, akula-i
ROE – weapons hold do not fire unless fired upon
******************************
Comments:
As 688 I was tasked to leave port on a westerly course from one of several shipyards and attempt to reach dive point. The ffg spawned at another shipyard assuming a westerly course as I did, but some 20 nm north from me. Frag spawned at the airport and assumed patrol in-between us, conducting a mix of passive and active buoy and dipping sonar searches. However frag confirms the 1st 10nm stretch of water ahead of me as clear before his search. I then proceed to dive point at 12 kts, max scope, occasional TA baffle checks and data downloads from 125 ft.
Frag also classified and promoted surface contacts to ownship. The pickings were slim this time around. If I chose to navigate through surface traffic there wasn’t much to choose from and the nearest cluster of surface traffic was too far away to even bother with. Frag dropped a wall of buoys spanning over 13 nm, and on occasion I would hear active transmissions from dicass buoys, although faint. I’m hoping there isn’t anything laying in wait for me on my projected course to ‘safe haven’ compliments of frag. Ambient SNR was terrible at this shallow depth, bound to improve farther from the coastline.
Few hours pass and the ffg is closer to the wall of buoys than I am. I receive a radio message to be advised of possible hostile submarine, although intentions of the submerged contact were not clear. Although frag was unclear of the contacts intentions, he promotes link as hostile and ffg opens up with a salvo of torpedoes, violating ROE assigned in mission tasking. Frag did in fact attempt to promote link as unknown, but it was too late.
Mission results – mission can’t be completed for both sides due to violation of ROE on false information.
SESSION 4 AAR
******************************
MP tests / LWAMI 3.07 / CM detonation 0%
Session 4 AAR
Divers - suBB (kilo), Mr. E (akula-I)
Tasking: intercept 688 and prevent 688 from reaching dive point
Opposing side: MaHuJa (688i), Beaver eater (FFG and helo)
******************************
Comments:
At spawn I go flank to try to position myself farther away from frag in the event of helo dipping search with some distance between us, that way if the helo is right on top of any one of us, we would hopefully have some safety cushion against detection. Comms check interval set for 1 hour. Shortly afterwards frag detected the ffg on active intercept and attempts to attack ffg with a 3 salvo ASM and missies terribly, but this also cost us dearly as we’ve been compromised very early on.
Moments later I start receiving active intercepts on buoys from the NE, frag is much closer to the NE than I am. Frag didn’t even have is TA deployed and was running blind for the 1st hour of the session and any attempt to inform him of checking TA baffles was for not. And the more he wouldn’t ‘listen’ and use common sense, the more irritated I became, especially when we triangulated the FFG based on surface ping ‘right in front of him’ but still wouldn’t deploy his TA and / or check TA baffles. At this point I’m becoming more concerned that frag is becoming a liability to the mission early on in the session and really isn’t aware how crucial the akula is, nor cares to even realize how crucial she is to the mission. Plus I’ve been running close to flank in the kilo more often than I should, as it will sooner or later catch up with me. Emissions came and went from the FFG both ESM and active but not enough to really pinpoint it’s whereabouts, plus the fact active buoys were emitting didn’t help us either, but it gave me a better feel for the 688’s whereabouts. Frag is our only means of listening and with his TA secured we were behind 1 hour in any possible contact, even more so he was not checking TA baffles on a regular basis.
Still no sign of the 688 - even more so after frags 2nd ASM attempt of which I can’t recall a confirmed kill on the FFG, but because of our close proximity this is the 2nd time we revealed ourselves to the 688 making things more difficult for us, let alone lack of cooperation on frags part for not checking TA baffles regularly. I didn’t include UUVs in the load out, and at this point I really wish I did. Shortly after we were pinged by dipping search and I’m at 17 kts as I change to a course S / SE to reduce surface area while maintain speed to reach comms point. Even more buoys are emitting from the NE but I don’t think it really sank into frags mind set. He decides to emit, asking me if we should, but in response I say it’s his call since we already compromised ourselves twice. I suggested using uuvs instead of active sonar, but obviously he didn’t have the patience for them to load. He transmits and no returns on active sonar. That is the 3rd time now.
By now my battery is dead in the kilo and I’m running on diesel and transmitting, figuring that hopefully I can find the 688. After batteries charged slightly, I tried various depths where SSP was better while going active but nothing came from it. Frag starts concerning himself with anything other than the 688 (promoting surface contacts, the helo) but I quickly remind him what does surface traffic have to do with the 688?? And messing around with the helo is a waste of time, but frag chalks up as ‘situation awareness’. I wondered if he really was aware of the situation we put ourselves in at this point. Frag then tries to entice MaHuJa to attack by ‘cavitating’ at flank, and considering the fact we compromised ourselves 3 times now, what convinced him that MaHuJa would fall for that, I could never imagine.
On a technicality (map glitch) MaHuJa reaches dive point with no sign of the 688 on our end.
Mission results – 688 mission objective complete.
SESSION 1 AAR
******************************
MP tests / LWAMI 3.06 / CM detonation 0%
Session 1 AAR
Divers - suBB (kilo), Mr. E (akula-I)
Tasking: intercept 688 and prevent 688 from reaching dive point
AI tasking: Assist 688 in reaching dive point.
AI platforms(in the absence of human players): ffg, 688, helo
******************************
Comments:
About 2 hours after spawn we finally made contact with the ffg after I set possible intercept course based on intelligence we did gather and agree on followed by routine comms check on the interval. Positive ID was made by periscope and link was promoted to Mr. E. Based on the situation, the ffg was in a crossfire between the ‘wolf pack’ and too close for an ASM attack.
After initial contact I set an attack run course, eventually closing the distance until ffg was on HF. forcing a LAG situation on the ffg. The attack started with a salvo of wake homers and a spread of test71 combo 20 degrees over ffg bearing. Immediately afterwards I clear datum trying to gain final position of the ffg on periscope. The wake homers missed but the test71 spread caught up with him. After 1 test 71 detonated I re-route the other test71 to intercept, the ffg returns fire with a few salvos, Mr. E follows suite with 2 staggered salvos of wake homers which both missed.
After clearing datum I re-gain visual on ffg but he’s hurt, there is smoke and flames pouring out of the ship, port side. Mark final bearing and range, moments later I activate the last test71, which detonates on the ffg, witnessing the explosion before going under. The torpedoes from the ffg goe active and are closing based on ‘early warning’ measures. I basically had to disengage and ‘hand-off’ the ffg to Mr. E. for my own safety. I’m hoping he is going down at this point.
I seem to be the center of the ffg and helos’ attention entering and completing evasion up to 3 times, and still no sign of the 688. The 4th time resulted form a helo dropped torpedo of which was running circles around ownship. I run all stop and bottom the boat to try and let the fish run out of gas, or run aground, before continuing on. Luckily it paid off this time around. The torpedo disappeared from NB.
All of a sudden another TIW report from acoustics, and after checking NB it’s the ADCAP and not a mk46 or mk50 – I’ve found the 688. But the situation I was in didn’t allow enough time to start a track and promote link plus tubes were reloading from the torpedo attack on the ffg. Starfish torpedoes were loaded but the SNR of the ADCAP was very strong – he is close. ADCAP goes active and takes the CMs for the 5th time. After clearing data I go all stop scanning NB for the 688. Shortly afterwards Mr. E finally finishes off the ffg, but the helo quickly returns the favor – Mr. E is hit and he’s going down. Another TIW from acoustics but this time over a very wide bearing range – the 688 advanced and tried to attack from the starboard side closer to the rear. This time he caught up with me with my pants down and the fish failed to acquire the CMs dropped.
Mission results – all threats neutralized and area secure for safe passage of the 688.
SESSION 2 AAR
******************************
MP tests / LWAMI 3.07 / CM detonation 0% / ATMA off
Session 2 AAR
Divers - suBB (akula-I), Mr. E (kilo)
Tasking: intercept 688 and prevent 688 from reaching dive point
AI tasking: Assist 688 in reaching dive point.
AI platforms(in the absence of human players): ffg, 688, helo
******************************
Comments:
At spawn we had visuals and sonar contacts on non-important targets (neutral contacts) and without hesitation I immediately start patrolling. As the akula I wanted to make full use of the TA detection capabilities. We agreed on a comms check interval of 30 mins or so, and I assumed a cruise speed of 7 kts with TA at full scope to try and determine some general direction to start looking. I tried various patrolling methods, some standard, some out of creativity and in a general direction due east, checking TA baffles every so often. According to frags’ ESM data the helo has been searching in my general area, less than 20nm south of frag. Because of that I missed two comms checks, where the 1st attempt at the 30 minute mark nearly compromised my boat. Also any sort of intel I missed on those intervals, is now one hour old, and still no sonar contacts of interest yet.
I decide to patrol S / SE and attempt comms check as necessary and not on the interval, hoping the helo will finally decide to search elsewhere. After some time (about 3 hours it seems) contact was made on a faint 60 hz signal. To avoid risk of compromising my boat I resolve bearing on contact and determine the contact is not hostile, since the true bearing didn’t originate from the direction of the naval base, supposedly where the 688 and escort departed from, as mentioned in tasking.
Frag made note that the coast is clear on my end for comms check, while in the same token the helo entered his area and he went under to avoid visual detection. I’m now one and a half hours behind on intelligence reporting, hoping that this next comms check will reveal something to make up for all of that.
Finally, visual was made on the ffg, and it’s safe for me to promote link to frag. Frag streamed his wire to receive the data without compromising his boat either. I prep tubes for an ASM strike followed by stagger salvos of USGT and wake homers. Looking through the periscope the ffg CIWS was handling the ASM salvo nicely and entered a course due south, forcing his stern to point directly towards the bow of my boat. I should have not bothered with the ffg in fear of losing the possible element of surprise in case the ffg was pulling ahead of the 688, but the opportunity presented itself.
The 1st UGST detonates and I clear datum, update final mark on ffg, re-route the other UGST, and fire another salvo of wake homers. Avoiding being spotted by the helo, Frag warns me of the helo returning in my direction, and shortly after the helo starts dipping search – he is basically right on top of me. I drop an active CM and shortly afterwards acoustics reports TIW on a bearing between the two of us. I’m thinking it’s the helo but the fish didn’t go active for quite sometime – it has to be the 688. Frag diverts the helo attention away from me (thanks for that :D) enticing it with radar to attack, only to realize that frag had other intentions, frag shoots down the helo with the SAM launcher.
The TIW generated was the 688 attempting to attack frag, of which frag successfully evaded and his CMs convinced the 688 torpedoes to consider another target – the cruise ship aft of frag. We figure where the 688 is, and after slowing down I make one last visual on the ffg followed an ASW salvo on the 688s’ suspected position. Frag fired a spread of test71s at the 688 and the wake homers from me had the ffg running away from us, making use of that will buy us time to start working on the 688.
The 688 managed to evade our torpedoes with CMs and was running loud enough for a broadband TA contact, yet out of sphere range. A rough TMA of 4 lines revealed that the 688 was about 7nm north of ownship between the two of us on a westerly course. I went active hoping to draw the 688 away from frag, and even though the returns were pretty bad, still I managed to confirm range of the 688 and fire another salvo of UGSTs. Based on the TA sonar contact, the 688 was trying to shoot his way out and attempt to reach dive point. By traveling west and based on the orientation of own ship, the 688 moved into my TA baffles.
After an immediate course change and the UGST spread shot went active, one the UGSTs acquired, while I re-routed the other. Shortly afterwards the UGST detonates on the 688, I disable the other UGST to avoid friendly fire, and we receive orders to disengage and attempt to reach distance. Frag was picking up the ffg on ESM, he located the FFG and determined he was still too far away to do anything about anything.
Mission results – 688 was intercepted and destroyed, at least one RU sub reached safe distance.
SESSION 3 AAR
******************************
MP tests / LWAMI 3.07 / CM detonation 0% / ATMA off
Session 3 AAR
Divers - suBB (688i), Fragmaster (seahawk)
Tasking: 688i - reach dive point / seahawk - Assist 688 in reaching dive point
AI tasking:. intercept 688 and prevent 688 from reaching dive point
AI platforms(in the absence of human players): ffg, kilo, akula-i
ROE – weapons hold do not fire unless fired upon
******************************
Comments:
As 688 I was tasked to leave port on a westerly course from one of several shipyards and attempt to reach dive point. The ffg spawned at another shipyard assuming a westerly course as I did, but some 20 nm north from me. Frag spawned at the airport and assumed patrol in-between us, conducting a mix of passive and active buoy and dipping sonar searches. However frag confirms the 1st 10nm stretch of water ahead of me as clear before his search. I then proceed to dive point at 12 kts, max scope, occasional TA baffle checks and data downloads from 125 ft.
Frag also classified and promoted surface contacts to ownship. The pickings were slim this time around. If I chose to navigate through surface traffic there wasn’t much to choose from and the nearest cluster of surface traffic was too far away to even bother with. Frag dropped a wall of buoys spanning over 13 nm, and on occasion I would hear active transmissions from dicass buoys, although faint. I’m hoping there isn’t anything laying in wait for me on my projected course to ‘safe haven’ compliments of frag. Ambient SNR was terrible at this shallow depth, bound to improve farther from the coastline.
Few hours pass and the ffg is closer to the wall of buoys than I am. I receive a radio message to be advised of possible hostile submarine, although intentions of the submerged contact were not clear. Although frag was unclear of the contacts intentions, he promotes link as hostile and ffg opens up with a salvo of torpedoes, violating ROE assigned in mission tasking. Frag did in fact attempt to promote link as unknown, but it was too late.
Mission results – mission can’t be completed for both sides due to violation of ROE on false information.
SESSION 4 AAR
******************************
MP tests / LWAMI 3.07 / CM detonation 0%
Session 4 AAR
Divers - suBB (kilo), Mr. E (akula-I)
Tasking: intercept 688 and prevent 688 from reaching dive point
Opposing side: MaHuJa (688i), Beaver eater (FFG and helo)
******************************
Comments:
At spawn I go flank to try to position myself farther away from frag in the event of helo dipping search with some distance between us, that way if the helo is right on top of any one of us, we would hopefully have some safety cushion against detection. Comms check interval set for 1 hour. Shortly afterwards frag detected the ffg on active intercept and attempts to attack ffg with a 3 salvo ASM and missies terribly, but this also cost us dearly as we’ve been compromised very early on.
Moments later I start receiving active intercepts on buoys from the NE, frag is much closer to the NE than I am. Frag didn’t even have is TA deployed and was running blind for the 1st hour of the session and any attempt to inform him of checking TA baffles was for not. And the more he wouldn’t ‘listen’ and use common sense, the more irritated I became, especially when we triangulated the FFG based on surface ping ‘right in front of him’ but still wouldn’t deploy his TA and / or check TA baffles. At this point I’m becoming more concerned that frag is becoming a liability to the mission early on in the session and really isn’t aware how crucial the akula is, nor cares to even realize how crucial she is to the mission. Plus I’ve been running close to flank in the kilo more often than I should, as it will sooner or later catch up with me. Emissions came and went from the FFG both ESM and active but not enough to really pinpoint it’s whereabouts, plus the fact active buoys were emitting didn’t help us either, but it gave me a better feel for the 688’s whereabouts. Frag is our only means of listening and with his TA secured we were behind 1 hour in any possible contact, even more so he was not checking TA baffles on a regular basis.
Still no sign of the 688 - even more so after frags 2nd ASM attempt of which I can’t recall a confirmed kill on the FFG, but because of our close proximity this is the 2nd time we revealed ourselves to the 688 making things more difficult for us, let alone lack of cooperation on frags part for not checking TA baffles regularly. I didn’t include UUVs in the load out, and at this point I really wish I did. Shortly after we were pinged by dipping search and I’m at 17 kts as I change to a course S / SE to reduce surface area while maintain speed to reach comms point. Even more buoys are emitting from the NE but I don’t think it really sank into frags mind set. He decides to emit, asking me if we should, but in response I say it’s his call since we already compromised ourselves twice. I suggested using uuvs instead of active sonar, but obviously he didn’t have the patience for them to load. He transmits and no returns on active sonar. That is the 3rd time now.
By now my battery is dead in the kilo and I’m running on diesel and transmitting, figuring that hopefully I can find the 688. After batteries charged slightly, I tried various depths where SSP was better while going active but nothing came from it. Frag starts concerning himself with anything other than the 688 (promoting surface contacts, the helo) but I quickly remind him what does surface traffic have to do with the 688?? And messing around with the helo is a waste of time, but frag chalks up as ‘situation awareness’. I wondered if he really was aware of the situation we put ourselves in at this point. Frag then tries to entice MaHuJa to attack by ‘cavitating’ at flank, and considering the fact we compromised ourselves 3 times now, what convinced him that MaHuJa would fall for that, I could never imagine.
On a technicality (map glitch) MaHuJa reaches dive point with no sign of the 688 on our end.
Mission results – 688 mission objective complete.