Invincible Mogami
 

This was frustrating. Initial salvo was 4 forward torps at about 1600 yds, spaced left and right w/1 degree of spread into the targets port flank. With the initial impact the target increased speed and 2 of the following 3 torps hit rearward of the initial impact point making for 3 out of 4. I dove for the thermal and waited it out as there were crazy levels of escorts (7-10). Turns out they were pretty useless, so I popped up for a look, Mogami heavy on fire listing to port 20-25 degrees. I dove for the thermal again, and popped out on the other side and gave him my rear tubes at close range, 900-1100 yds. Both hit; I cheated and went in for a closer look, two gaping holes in the starboard flank to go with the giant holes (3) on the port side. Figured it would only be a matter of minutes...and the waiting game begins. Waited who knows how long, 2-3 hours? Nothing. Target dead in the water making 0 knots. This is where things get fuzzy. Over the next 5-6 hours (time compressed), I suceeded in emptying my torpedo inventory into a stationary, buring (and sinking) target for only 1 additional miss. Of an entire complement of 16 torpedos, 13 went into the Mogami before I gave up and headed home (with one for spare, incase I ran into anything on my way to refit plus for BuOrd to inspect). As I left the scene the Mogami was still merrily burning away, low in the water but with no signs of capitulation. A 9500 ton vessel absorbing 13 torpedos that by all acounts did hit (no prematures--there were clear signs of the hits, gaping holes in the vessel's hull)? Hell, I've sunk a 30,000 ton Kongo with 4 torps before (in minutes I might add).

I snuck in close underneath the Mogami and snapped some pictures as I couldn't believe the level of carnage in the hull for lack of sinkage (5 staggered holes down the port side) but for whatever reason, in my angst, I must have left the lens cap on...:rock:

Ah ha...http://www.mulsannescorner.com/MogamiSwisscheese.jpg

I know the feeling. I hit one last night with 15 out of 16 torpedos and TCed for over 24 hours without it sinking! I later sank one with just 4, go figure.

I use Trigger Maru 1.6.7 with Werner's Natural Sinking Mod. It makes ships sink in a more realistic fashion. Even with it the Mogami is a monster.

http://i214.photobucket.com/albums/c.../missedout.jpg:doh: :doh: :doh:

It took me 9 Mk14s (direct hits showing hull damage) out of 11 fired to sink a Mogami a couple days ago. I even went around to the other side for the second half of them. The hits were spread out on both sides. :huh:


I guess this is a good way to reduce patrol tonnage totals. *shrug*

Games so good it even simulates the frustration real life skippers felt :smug:

Heh!

Also:

Sea Plane tender last night took 6 hits & 5 near hits on one side before I finally gave up (out of fish) and left the area. It sank about 20 minutes later.

Three early hits on a destroyer just before that got it dead in the water. Good enough, it won't chase me while I'm reloading on the Chitose (above). :doh:

Trigger Maru 1.6, right? This is what happens when you mod: unexpected results. The Mogami is one of the msot difficult vessels to sink - unless you know it's weakness: the fore and aft ballast tanks. Yes, ships have them too. A Mogami will eat an absurd number of torpedoes and if you ever try hitting both sides it might never sink properly.

The easy way to sink it is to hit the exteme fore and aft sections of the cruiser - that way you will be floodign the ballast tanks and greatly destabilising the vessel. A normal spread won't hit near the propellers or near the extreme fore section of the ship hence the reason many people find it difficult to sink this blasted vessel. Another piece of advice is to hit the ship directly below the command deck/funnels - thus increasing the chance of the ship capsizing.

Bottom line: hit below the funnel/command deck and neat the fore/aft extremities for an easy kill.

I think the most painfull thing is the 6FPS in Woodstocks photo :rotfl:

I thought I put an earlier zones.cfg back in there. Maybe I missed something else.:hmm: