'Unseen Attacker' is impossible!

NFunky · 05-17-10, 08:11 PM

Sorry to be starting so many new threads, but I had a free day today, so I've been playing a good amount of DW.

This thread is about a specific mission, Unseen Attacker, which is a Kilo scenario in which you have to transit undetected within 1 nm of an oil rig. At least, that's the first objective, but I haven't been able to get past it. The first problem I have is built into the mission. About an hour or two into gameplay, my sub suffered flooding in the engine room and damage to my propeller and both engines which limited my speed to about a third/half of whatever bell I had set.

I admit, I turned on truth after this event to see if I'd somehow run aground or collided with something, but everything seemed to be in order. I was at about 40 meters depth going 10 kts. Looking in the mission file, I found there is a trigger for this event, but I can't tell whether it's random or if I did something to cause it.

Anyway, that was a pain in the ass, but I thought I could still complete the objective, all-be-it at a much slower speed. This speed would also allow me to track all ships in my path very accurately. I was about 2 nm away from the Oil Rig when I heard "You have been counterdetected." Now, I knew the only enemy ship really close was a Hai Ou PCFG. There was an as yet unidentified suface ship using active sonar, but it was at least 9 nm away and my bow was almost directly pointed at him. Very early on, I had detected an S-2 and a little later a helo on ESM, so I thought it must have been one of them, but when I turned truth on again I saw neither of them withing 20 nm of me and no sonobouys. So how did I get couterdetected?

Anyway, I failed the mission and I still have no idea why. So, have any of you played this mission? Any thoughts/ideas?

TLAM Strike · 05-17-10, 08:33 PM

Been years since I made that mission but as I remember there is a random failure you sub will get- damage, flooding etc and your mission orders are randomized.

Not sure how you were counter detected. Maybe the FF in the mission got you in a CZ. This mission was made a long time ago and may not be adjusted for the latest LWAMI mod.

Were you using LWAMI or stock? or some other mod. If you were using LWAMI the only thing I think might have happened was the PTG got a visual on you if you were at PD.

NFunky · 05-17-10, 09:46 PM

I'm using LWAMI 3.09 with the temporary 3.10 files installed over it. Do you think it's the 3.10 files maybe?

I was at 120 meters depth, so I doubt it was a visual contact, but I hadn't thought of a CZ. The sounding was only about 1200 meters, but maybe that's enough. I also seem to remember that there is a CZ closer than the commonly known 30 nm and I wouldn't be surprised if the active surface contact I was tracking was in that range.

It's a really cool mission concept and I actually really like the randomized events. When my engine room flooded, I had to completely rethink how I was going to approach the Oil Rig which was a cool new twist. But I thought it was caused by something I had done and couldn't imagine what it was. I'm going to try the mission again now that I know a little more about what's going on.

TLAM Strike · 05-17-10, 10:06 PM

At 120 meters it could have been a surface duct. Were you above the layer at that depth?

Hehehe I know someone was going to build a working 3.10 before the release using those files.

NFunky · 05-18-10, 05:05 PM

Damn, a surface duct? The layer was around 310 meters, so I was a little hesitant to go below it as I think the Kilo's crush depth is only a little more. Can a surface duct really increase detection range that much? I mean, I was 9-10 miles away and at a full on front aspect. Maybe it was his passive? I was only going at about 4 kts, but to get that speed I had my bell cranked to two-thirds, so maybe I was a lot louder than I thought.

Are there any ways to make myself more stealthy while remaining above the layer? I mean, going below it really wasn't an option and I had to approach the pinger since he was in the same direction as the oil rig. I guess my other option would have been to just keep my distance and see if he moved away, but I didn't think of it at the time. Oh well.

Thanks for your help TLAM. Every time I think I'm getting a handle on sub-ops, something always comes along to bust my ego down a few pegs.

05-17-10, 08:11 PM	#1
NFunky Machinist's Mate Join Date: Dec 2007 Posts: 127 Downloads: 3 Uploads: 0	'Unseen Attacker' is impossible! Sorry to be starting so many new threads, but I had a free day today, so I've been playing a good amount of DW. This thread is about a specific mission, Unseen Attacker, which is a Kilo scenario in which you have to transit undetected within 1 nm of an oil rig. At least, that's the first objective, but I haven't been able to get past it. The first problem I have is built into the mission. About an hour or two into gameplay, my sub suffered flooding in the engine room and damage to my propeller and both engines which limited my speed to about a third/half of whatever bell I had set. I admit, I turned on truth after this event to see if I'd somehow run aground or collided with something, but everything seemed to be in order. I was at about 40 meters depth going 10 kts. Looking in the mission file, I found there is a trigger for this event, but I can't tell whether it's random or if I did something to cause it. Anyway, that was a pain in the ass, but I thought I could still complete the objective, all-be-it at a much slower speed. This speed would also allow me to track all ships in my path very accurately. I was about 2 nm away from the Oil Rig when I heard "You have been counterdetected." Now, I knew the only enemy ship really close was a Hai Ou PCFG. There was an as yet unidentified suface ship using active sonar, but it was at least 9 nm away and my bow was almost directly pointed at him. Very early on, I had detected an S-2 and a little later a helo on ESM, so I thought it must have been one of them, but when I turned truth on again I saw neither of them withing 20 nm of me and no sonobouys. So how did I get couterdetected? Anyway, I failed the mission and I still have no idea why. So, have any of you played this mission? Any thoughts/ideas?

05-17-10, 08:33 PM	#2
TLAM Strike Navy Seal Join Date: Apr 2002 Location: Rochester, New York Posts: 8,633 Downloads: 29 Uploads: 6	Been years since I made that mission but as I remember there is a random failure you sub will get- damage, flooding etc and your mission orders are randomized. Not sure how you were counter detected. Maybe the FF in the mission got you in a CZ. This mission was made a long time ago and may not be adjusted for the latest LWAMI mod. Were you using LWAMI or stock? or some other mod. If you were using LWAMI the only thing I think might have happened was the PTG got a visual on you if you were at PD. __________________

05-17-10, 10:06 PM	#4
TLAM Strike Navy Seal Join Date: Apr 2002 Location: Rochester, New York Posts: 8,633 Downloads: 29 Uploads: 6	At 120 meters it could have been a surface duct. Were you above the layer at that depth? Hehehe I know someone was going to build a working 3.10 before the release using those files. __________________

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

05-17-10, 09:46 PM	#3
NFunky Machinist's Mate Join Date: Dec 2007 Posts: 127 Downloads: 3 Uploads: 0	I'm using LWAMI 3.09 with the temporary 3.10 files installed over it. Do you think it's the 3.10 files maybe? I was at 120 meters depth, so I doubt it was a visual contact, but I hadn't thought of a CZ. The sounding was only about 1200 meters, but maybe that's enough. I also seem to remember that there is a CZ closer than the commonly known 30 nm and I wouldn't be surprised if the active surface contact I was tracking was in that range. It's a really cool mission concept and I actually really like the randomized events. When my engine room flooded, I had to completely rethink how I was going to approach the Oil Rig which was a cool new twist. But I thought it was caused by something I had done and couldn't imagine what it was. I'm going to try the mission again now that I know a little more about what's going on.

05-18-10, 05:05 PM	#5
NFunky Machinist's Mate Join Date: Dec 2007 Posts: 127 Downloads: 3 Uploads: 0	Damn, a surface duct? The layer was around 310 meters, so I was a little hesitant to go below it as I think the Kilo's crush depth is only a little more. Can a surface duct really increase detection range that much? I mean, I was 9-10 miles away and at a full on front aspect. Maybe it was his passive? I was only going at about 4 kts, but to get that speed I had my bell cranked to two-thirds, so maybe I was a lot louder than I thought. Are there any ways to make myself more stealthy while remaining above the layer? I mean, going below it really wasn't an option and I had to approach the pinger since he was in the same direction as the oil rig. I guess my other option would have been to just keep my distance and see if he moved away, but I didn't think of it at the time. Oh well. Thanks for your help TLAM. Every time I think I'm getting a handle on sub-ops, something always comes along to bust my ego down a few pegs.