Yugo SSMs are hard to kill!
 

Greetings all,

I put together a little scenario involving two North Korean Yugo SSM midget subs trying to attack a three ship cargo convoy protected by one AI controlled Burke DDG and a Perry FFG controlled by me.

Let me tell you it is almost impossible to pick up the scent of these things, at least in the shallow water off of the Korean penisula (depth around 400 feet). Even the AI-controlled Burke, which I find to be often aggressively used by the AI, only managed to narrow the location of one of the Yugos to about two square miles (it never did get a good enough solution to fire a shot). I did manage to kill one Yugo by dumb luck: my helo was en route to drop a sonobuoy when it spotted one of the Yugos surfacing(!?). :doh: It dropped a torp right on its head and killed it. If it wasn't for that bit of dumb luck, we never would have hit a single enemy sub! The TA was useless, likewise the bow sonar, and the sonobuoys only managed to get a brief sniff every now and then.

What a surprising challenge this turned out to be! If DW is accurate in modeling the stealthiness of a Yugo sub, then I fear the NKs may have found a cheap way to harass shipping in a time of war.

All things considered, interesting results.

The midget subs? Among the most noisy in the world. And they don't have any sensors beyond their periscopes, either, so pinging is safe.

If you couldn't detect them with 400ft of water, you must have been doing something wrong. What were the distances like? Was the bottom type the default rock, or was it the more sonar-limiting sand or mud?

Are you sure you were not dragging the TA on the bottom?

And the case of spotting one, was possibly a MAD detection from the helo. If it dropped a torp on its own that's very probably the case, since that only happens in lwami on a mad contact.

The hull sonar, in passive mode, is infamous for being useless.

im not so sure about sensors being just the periscope, i put on truth and watched a midget sub blow me up from 80 feet....:huh:

Last time I looked in the database, that was the only sensor listed. It's possible that it acquited the solution with the periscope, then went down and fired.