The Elephant Vanishes : obvert (J) vs Historiker_SqzMyLemon_Canoerebel (A)

Post descriptions of your brilliant victories and unfortunate defeats here.

Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition

User avatar
pontiouspilot
Posts: 1131
Joined: Fri Jul 27, 2012 7:09 pm

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by pontiouspilot »

Forgive my Cdn friend he is a little high strung...for a Cndn anyway. Congrats on either the luckiest or most skilled ambush for some time. He did put his lemons into a place they could be squeezed. I avoid that area like the plague since there is no where to go.
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

ORIGINAL: pontiouspilot

Forgive my Cdn friend he is a little high strung...for a Cndn anyway. Congrats on either the luckiest or most skilled ambush for some time. He did put his lemons into a place they could be squeezed. I avoid that area like the plague since there is no where to go.

I'll take luckiest. [;)]

That is true. There is no where to go for a turn once you're there. If you flank out with the combat ships you leave your amphibs with the asses hanging out. This makes me feel better about my shameless grab of the Perth region and West OZ earlier, too. (Which by the way produced 20k supply that I just pulled out supply Dili, where the LBA strikes originated). [:D]
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

ORIGINAL: Lokasenna

99% of the time, I do range 0 CAP. Because I control my TFs down to the last hex. With direct/absolute orders, only cripples that are split off get left behind. If there are any cripples, I either directly order their protection or slow down to maintain protection, depending. But realistically speaking, the only cripples that could occur would be from SCTFs or subs. If I'm doing my job with searches, SCTFs are extremely unlikely - leaving subs. And aside from setting up what ASW I can, there's no point in worrying about whether they will or won't strike because it's out of my control.

Range 0 CAP maximizes your CAP over your forces and prevents silly things like sweeps of the dot base next door bleeding off 40% of your CAP only to have a large strike package literally within sight (you can see 40-80 miles in the air at various altitudes...) sink a bunch of ships.

There have been times when I've known that my forces would be 1 hex apart and I've set a few groups to range 1 CAP, but that's it. Otherwise, I generally prefer to LRCAP with a range setting of 0 for forces that aren't going to be in the CV/CVE hex.

The only thing I wonder about this is for second strikes in a CV clash. If the afternoon comes and your CAP was trashed and damaged in the first strike, but your escort was not, you're sending out a strong escort but leaving your CVs vulnerable. Or vice versa.

It's something I'l probably not do, but it'd be a good test and not too hard to run through a bunch.
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

[font="Times New Roman"]March 25, 1944[/font]
[font="Microsoft Sans Serif"]OZ:[/font] Ok. Back on track.

The lowdown on the 25th is that a lot of transports are sent down but no escorts. The Essex is finished off. I think the escorts are in Darwin judging by the roll over, and I'll bombard tomorrow to get some damage on the fields, blow up some planes, and see if some hits get onto ships as well. I may find a zillion PT boats here, but hopefully those can be negotiated.

The KB will skirt the edge of South New Guinea to avoid direct paths to Ambon and stay in the shallows. LBA will stay on alert at extended range from Biak, Ambon and Dili.

Once we see how he is going to play this, (i.e. if CAP will be introduced at Darwin), then I'll proceed accordingly.
[font="Trebuchet MS"]
--------------------------------------------------------------------------------
AFTER ACTION REPORTS FOR March 25, 44
--------------------------------------------------------------------------------

Day Time Surface Combat, near Darwin at 77,124, Range 28,000 Yards

Japanese Ships
CA Mogami
CA Mikuma
CA Aoba
CL Oyodo
DD Michishio
DD Arashio
DD Arare
DD Yugure

Allied Ships
APA Sheridan, Shell hits 18, Torpedo hits 1, and is sunk
APA Warren, Shell hits 26, and is sunk
APA Wayne, Shell hits 21, Torpedo hits 1, and is sunk


Maximum visibility in Partly Cloudy Conditions: 28,000 yards
Range closes to 28,000 yards...

--------------------------------------------------------------------------------
Sub attack near Darwin at 77,124

Japanese Ships
SS I-18

Allied Ships
AK Cheleb, Shell hits 1, Torpedo hits 2, heavy damage

SS I-18 attacking on the surface

--------------------------------------------------------------------------------
Morning Air attack on TF, near Darwin at 76,124

Weather in hex: Moderate rain

Raid detected at 37 NM, estimated altitude 9,000 feet.
Estimated time to target is 15 minutes

Japanese aircraft
A6M5 Zero x 49
B5N2 Kate x 41
Ki-45 KAIa Nick x 4

Japanese aircraft losses
B5N2 Kate: 2 damaged

Allied Ships
AK Bullock, Bomb hits 1, on fire
xAP Van Diemen, Bomb hits 6, and is sunk
xAP Van Landsberge, Bomb hits 4, and is sunk
AK Charlevoix, Bomb hits 1, on fire
xAP Van Neck, Bomb hits 1, heavy fires
AK Chatham, Bomb hits 1, on fire


Aircraft Attacking:
41 x B5N2 Kate bombing from 5000 feet *
Naval Attack: 2 x 250 kg GP Bomb

Heavy smoke from fires obscuring xAP Van Landsberge
Heavy smoke from fires obscuring xAP Van Neck
Heavy smoke from fires obscuring xAP Van Diemen
Heavy smoke from fires obscuring AK Charlevoix

--------------------------------------------------------------------------------
Morning Air attack on TF, near Darwin at 76,124

Weather in hex: Moderate rain

Raid detected at 65 NM, estimated altitude 13,000 feet.
Estimated time to target is 19 minutes

Japanese aircraft
Ki-45 KAIa Nick x 4
Ki-48-IIc Lily x 22

No Japanese losses

Allied Ships
xAP Camphuys, Bomb hits 8, and is sunk
xAP Le Maire, Bomb hits 2, heavy fires
xAP Siberg, Bomb hits 4, and is sunk


Aircraft Attacking:
8 x Ki-48-IIc Lily releasing from 2000'
Naval Attack: 2 x 100 kg SAP Bomb

--------------------------------------------------------------------------------
Morning Air attack on TF, near Gove at 83,127

Weather in hex: Light cloud

Raid detected at 111 NM, estimated altitude 14,000 feet.
Estimated time to target is 28 minutes

Japanese aircraft
A6M5b Zero x 101
A6M5c Zero x 42
A6M8 Zero x 34
B5N2 Kate x 8
B6N1 Jill x 25
B6N2 Jill x 38
D4Y3 Judy x 54
N1K1 Rex x 12

Allied aircraft
no flights

Japanese aircraft losses
B6N2 Jill: 1 damaged
D4Y3 Judy: 3 damaged

Allied aircraft losses
F6F-3 Hellcat: 1 destroyed
SBD-5 Dauntless: 11 destroyed
TBF-1 Avenger: 11 destroyed

Allied Ships
CV Essex, Bomb hits 4, Torpedo hits 1, and is sunk

Aircraft Attacking:
3 x D4Y3 Judy releasing from 2000'
Naval Attack: 1 x 500 kg SAP Bomb

--------------------------------------------------------------------------------
Afternoon Air attack on TF, near Groote Eylandt at 82,129

Weather in hex: Partial cloud

Raid detected at 30 NM, estimated altitude 12,000 feet.
Estimated time to target is 7 minutes

Japanese aircraft
A6M5b Zero x 75
A6M5c Zero x 7
B6N1 Jill x 9
B6N2 Jill x 8
D4Y1 Judy x 47
D4Y3 Judy x 27

Allied aircraft
F6F-3 Hellcat x 3

Japanese aircraft losses
A6M5b Zero: 1 destroyed
D4Y3 Judy: 1 damaged
D4Y3 Judy: 1 destroyed by flak

Allied aircraft losses
F6F-3 Hellcat: 1 destroyed

Allied Ships
LST-353, Bomb hits 5, and is sunk
LST-204, Bomb hits 4, heavy fires, heavy damage
LST-343, Bomb hits 2, heavy fires, heavy damage
LST-475, Torpedo hits 2, and is sunk
LST-480, Bomb hits 2, heavy fires, heavy damage
LST-87, Bomb hits 5, and is sunk
LST-344, Bomb hits 4, and is sunk
LST-469, Bomb hits 3, and is sunk
LST-464, Bomb hits 4, heavy fires, heavy damage
LST-481, Bomb hits 5, and is sunk
LST-84, Bomb hits 5, and is sunk
LST-472, Bomb hits 4, and is sunk
LST-484, Torpedo hits 3, and is sunk
LST-483, Bomb hits 6, and is sunk


Allied ground losses:
Vehicles lost 410 (331 destroyed, 79 disabled)

Aircraft Attacking:
8 x D4Y1 Judy releasing from 2000'
Naval Attack: 1 x 500 kg SAP Bomb

--------------------------------------------------------------------------------
Afternoon Air attack on TF, near Darwin at 76,124

Weather in hex: Overcast

Raid detected at 103 NM, estimated altitude 11,000 feet.
Estimated time to target is 34 minutes

Japanese aircraft
A6M5 Zero x 8
A6M5b Zero x 49
A6M5c Zero x 28
A6M8 Zero x 10
B5N2 Kate x 17
B6N1 Jill x 16
B6N2 Jill x 31
D4Y3 Judy x 36
N1K1 Rex x 12
Ki-43-IIIa Oscar x 22
Ki-45 KAIa Nick x 4

Japanese aircraft losses
B6N2 Jill: 3 damaged

Allied Ships
xAP Le Maire, Bomb hits 2, and is sunk
AK Brevard, Bomb hits 2, and is sunk
AK Charlevoix, Torpedo hits 1, and is sunk
AK Beltrami, Bomb hits 4, and is sunk
AK Chatham, Bomb hits 4, and is sunk
AK Cabell, Bomb hits 4, and is sunk


Aircraft Attacking:
2 x D4Y3 Judy releasing from 3000'
Naval Attack: 1 x 500 kg SAP Bomb
--------------------------------------------------------------------------------
[/font]

[font="Trebuchet MS"]Gained a few thousand VPs in a few days here. [/font]

Image
Attachments
25th_info.jpg
25th_info.jpg (591.06 KiB) Viewed 227 times
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

[font="Times New Roman"]CV Losses[/font]

Here is the updated version. The Lexington is not sunk. It took only one hit in the recent battle. This does mean damage likely increased before damage control took over, so that is good.

There are probably another 3-4 CVEs that will end up on this list.



Image
Attachments
CVlosses.jpg
CVlosses.jpg (647.85 KiB) Viewed 227 times
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

[font="Times New Roman"]BB Losses[/font]

We are doing well in BB ratio so far. I would have loved to pick a few more old ones off here, but alas, the seem to have scooted out. We'll see at Darwin, though. [;)]

Image
Attachments
bblosses.jpg
bblosses.jpg (408.75 KiB) Viewed 227 times
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
Lokasenna
Posts: 9304
Joined: Sat Mar 03, 2012 3:57 am
Location: Iowan in MD/DC

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by Lokasenna »

ORIGINAL: obvert

ORIGINAL: Lokasenna

99% of the time, I do range 0 CAP. Because I control my TFs down to the last hex. With direct/absolute orders, only cripples that are split off get left behind. If there are any cripples, I either directly order their protection or slow down to maintain protection, depending. But realistically speaking, the only cripples that could occur would be from SCTFs or subs. If I'm doing my job with searches, SCTFs are extremely unlikely - leaving subs. And aside from setting up what ASW I can, there's no point in worrying about whether they will or won't strike because it's out of my control.

Range 0 CAP maximizes your CAP over your forces and prevents silly things like sweeps of the dot base next door bleeding off 40% of your CAP only to have a large strike package literally within sight (you can see 40-80 miles in the air at various altitudes...) sink a bunch of ships.

There have been times when I've known that my forces would be 1 hex apart and I've set a few groups to range 1 CAP, but that's it. Otherwise, I generally prefer to LRCAP with a range setting of 0 for forces that aren't going to be in the CV/CVE hex.

The only thing I wonder about this is for second strikes in a CV clash. If the afternoon comes and your CAP was trashed and damaged in the first strike, but your escort was not, you're sending out a strong escort but leaving your CVs vulnerable. Or vice versa.

It's something I'l probably not do, but it'd be a good test and not too hard to run through a bunch.

Disagree.

Each air phase is separate. If I set 90% CAP, then 90% of the planes are flying in the morning. 90% are flying in the afternoon. Yes, that might be 90% of 24 instead of 90% of 30, but I'd rather have the strongest possible force available to my combats at all times. A weak AM strike isn't going to wear down my PM CAP such that a strong PM strike would get a better go at it than they would if I put up a strong CAP all day. By contrast, a strong AM strike against which a large portion of my CAP has to scramble is undesirable.

Likewise, I use dedicated escort squadrons. I don't know why you would ever not use dedicated escort squadrons. If you run a percentage of CAP at your strike range (say, 7 or 8) not only are you going to be detracting from the number of escorts flying with your strike, but that group will become much more fatigued than if you specialized groups for CAP or escort. It also allows you to set certain plane models entirely for attack or defense, as you see fit.

We've been over this before and you've always brought up this idea about PM CAP being weakened due to AM CAP being worn down when a high percentage of them are flying, but I just don't see how it would ever actually happen in practice vs. in theory. It all comes down to this: if a 90% CAP setting gets thrashed in the early strike(s), how much worse would you fare with only a 50% CAP setting? The number of planes in the air is a critical factor.

Also note that damaged planes are not stood down for maintenance until the end of the day (per the order of things in the ops report).


Of course, if you test and it turns out you are somehow correct and I'm wrong, I'll happily change my ways [:'(]. But my 90% CAP settings are veritable buzzsaws. Ask MM [;)]. A recent example is 21 Helen kamikazes escorted by 85 Franks: 20ish Franks were knocked off of the escorting portion, and 20 of 21 Helens were shot down. My losses were something like 5 planes on the day. Maximum force CAP = quicker/better resolution to the first strike(s) against my stuff, which means more of them are left in the air for later strikes. It takes many raids to burn through 200+/300+/400+ planes on CAP with 40-minute warning or more for each strike.
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

ORIGINAL: Lokasenna

ORIGINAL: obvert

ORIGINAL: Lokasenna

99% of the time, I do range 0 CAP. Because I control my TFs down to the last hex. With direct/absolute orders, only cripples that are split off get left behind. If there are any cripples, I either directly order their protection or slow down to maintain protection, depending. But realistically speaking, the only cripples that could occur would be from SCTFs or subs. If I'm doing my job with searches, SCTFs are extremely unlikely - leaving subs. And aside from setting up what ASW I can, there's no point in worrying about whether they will or won't strike because it's out of my control.

Range 0 CAP maximizes your CAP over your forces and prevents silly things like sweeps of the dot base next door bleeding off 40% of your CAP only to have a large strike package literally within sight (you can see 40-80 miles in the air at various altitudes...) sink a bunch of ships.

There have been times when I've known that my forces would be 1 hex apart and I've set a few groups to range 1 CAP, but that's it. Otherwise, I generally prefer to LRCAP with a range setting of 0 for forces that aren't going to be in the CV/CVE hex.

The only thing I wonder about this is for second strikes in a CV clash. If the afternoon comes and your CAP was trashed and damaged in the first strike, but your escort was not, you're sending out a strong escort but leaving your CVs vulnerable. Or vice versa.

It's something I'l probably not do, but it'd be a good test and not too hard to run through a bunch.

Disagree.

Each air phase is separate. If I set 90% CAP, then 90% of the planes are flying in the morning. 90% are flying in the afternoon. Yes, that might be 90% of 24 instead of 90% of 30, but I'd rather have the strongest possible force available to my combats at all times. A weak AM strike isn't going to wear down my PM CAP such that a strong PM strike would get a better go at it than they would if I put up a strong CAP all day. By contrast, a strong AM strike against which a large portion of my CAP has to scramble is undesirable.

Likewise, I use dedicated escort squadrons. I don't know why you would ever not use dedicated escort squadrons. If you run a percentage of CAP at your strike range (say, 7 or 8) not only are you going to be detracting from the number of escorts flying with your strike, but that group will become much more fatigued than if you specialized groups for CAP or escort. It also allows you to set certain plane models entirely for attack or defense, as you see fit.

We've been over this before and you've always brought up this idea about PM CAP being weakened due to AM CAP being worn down when a high percentage of them are flying, but I just don't see how it would ever actually happen in practice vs. in theory. It all comes down to this: if a 90% CAP setting gets thrashed in the early strike(s), how much worse would you fare with only a 50% CAP setting? The number of planes in the air is a critical factor.

Also note that damaged planes are not stood down for maintenance until the end of the day (per the order of things in the ops report).


Of course, if you test and it turns out you are somehow correct and I'm wrong, I'll happily change my ways [:'(]. But my 90% CAP settings are veritable buzzsaws. Ask MM [;)]. A recent example is 21 Helen kamikazes escorted by 85 Franks: 20ish Franks were knocked off of the escorting portion, and 20 of 21 Helens were shot down. My losses were something like 5 planes on the day. Maximum force CAP = quicker/better resolution to the first strike(s) against my stuff, which means more of them are left in the air for later strikes. It takes many raids to burn through 200+/300+/400+ planes on CAP with 40-minute warning or more for each strike.

Well, I will try it!

Thanks for the full explanation. It does sound like this is a good system. The thing I like is that you also choose the exact number and groups of your CAP and escort.

As I say, I always set some on 0 hex, just not all. I do set those for a high CAP %, usually 80. So I'll have to give it a try. Considering the current situation in game I guess I have a while to do some testing! [:D][:'(]
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

[font="Times New Roman"]CA/CL Losses[/font]

Here are the cruiser losses. Only 8 CA left.

Image
Attachments
CA_CL_losses.jpg
CA_CL_losses.jpg (580.54 KiB) Viewed 227 times
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

[font="Times New Roman"]APA/AP/xAPLosses[/font]

This is an area I wish I was doing better with. I seem to be a day late regularly. Again, maybe some of these are sitting in Darwin port right now. We'll see.


Image
Attachments
AP.jpg
AP.jpg (765.58 KiB) Viewed 227 times
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
crsutton
Posts: 9590
Joined: Fri Dec 06, 2002 8:56 pm
Location: Maryland

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by crsutton »

Truth is that if you throw victory conditions by date out this is actually a very playable game for the Allies. I would gladly take the Allied carrier losses to date in exchange for the Japanese carrier losses. Frankly the loss of three fleet quality Japanese CVs hurts a lot more than all of the Allied losses. 1944 will replace and then double his forces. I would love to play the Allies at this date. In fact, I think it would be a great idea to never activate the Soviets by agreement, you could see a campaign go deep into 1946 with a lot of interesting new toys come into use. This is something that we have yet to see in an AAR. You should propose this. Throw out victory conditions and tether the Russians and see what happens.

As for the 8 hex thing. It is the Allied cross to bear but not a game breaker at all. There are plenty of ways to manage it.

Thing is that after another year of war, barring some seriously mind boggling poor play, the Allied player is just going to be crapping out more resources than he can handle-regardless of what happens now. Been there and seen it. Heck, just the thought that I would finally get to use the A-bomb would make me want to cry with joy like a little girl..[:D]
I am the Holy Roman Emperor and am above grammar.

Sigismund of Luxemburg
User avatar
Lokasenna
Posts: 9304
Joined: Sat Mar 03, 2012 3:57 am
Location: Iowan in MD/DC

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by Lokasenna »

ORIGINAL: crsutton

As for the 8 hex thing. It is the Allied cross to bear but not a game breaker at all. There are plenty of ways to manage it.

It never would have happened in real life, but there have been times when I've just stood my strike planes down and put all my fighters on CAP in case of an 8-hex strike. Worked just fine, but I also had higher priorities than sinking carriers in those instances.
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

ORIGINAL: Lokasenna
ORIGINAL: crsutton

As for the 8 hex thing. It is the Allied cross to bear but not a game breaker at all. There are plenty of ways to manage it.

It never would have happened in real life, but there have been times when I've just stood my strike planes down and put all my fighters on CAP in case of an 8-hex strike. Worked just fine, but I also had higher priorities than sinking carriers in those instances.

As I understand it the range differences of IJN vs USN airframes led to the Japanese trying out the "8 hex strike," or long distance unreturnable strike, at the Marianas. We know how that turned out. That was planes pushing fuel limits to the brink and CVs reacting in to pick them up though, some into the night hours.

I think this feature was added for those reasons and the react choice players have is the built in counter. When the Allies have 15 CV react works.
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

ORIGINAL: crsutton

Truth is that if you throw victory conditions by date out this is actually a very playable game for the Allies. I would gladly take the Allied carrier losses to date in exchange for the Japanese carrier losses.

I'd play the Allied side here without a doubt. I've seen what the Allies can do in 44 when the machine gets rolling. I think payers who haven't been through that before don't know how fragile the Japanese defences are in reality. They see the strong points. Which is what I want them to see right now! [;)]
Frankly the loss of three fleet quality Japanese CVs hurts a lot more than all of the Allied losses. 1944 will replace and then double his forces. I would love to play the Allies at this date. In fact, I think it would be a great idea to never activate the Soviets by agreement, you could see a campaign go deep into 1946 with a lot of interesting new toys come into use. This is something that we have yet to see in an AAR. You should propose this. Throw out victory conditions and tether the Russians and see what happens.

As for the 8 hex thing. It is the Allied cross to bear but not a game breaker at all. There are plenty of ways to manage it.

Thing is that after another year of war, barring some seriously mind boggling poor play, the Allied player is just going to be crapping out more resources than he can handle-regardless of what happens now. Been there and seen it. Heck, just the thought that I would finally get to use the A-bomb would make me want to cry with joy like a little girl..[:D]

I don't see the Russians as a problem to reaching 46. They can have Manchuria by mid 45 when they activate. I'd be more concerned with getting needed fuel and resources to keep an economy working at that point. If that is still happening, yes, the game can go happily into a massive jet fur ball over Japan in 46! [8D]
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
User avatar
obvert
Posts: 14051
Joined: Mon Jan 17, 2011 11:18 am
Location: PDX (and now) London, UK

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by obvert »

Thinking about the state of this game right now I though I'd check into losses for the USN during the war. At this point, in early 44, the losses of CVs was similar with one additional fleet CV lost, but of course more CVE lost in this game.

For BBs the Allies are doing much worse than historical, and for cruisers probably similar to historical. For BBs in game the Allies are suffering much more than in the war.

On the Japanese side Midway happened early! [:D]

After that losses have been light to CVs, but cruisers and DDs have been heavily depleted. BBs are good, with only two lost.

So not too far off historical.
[font="Courier New"]BATTLESHIPS

ARIZONA Pearl Harbor 7 December 1941

OKLAHOMA Pearl Harbor 7 December 1941



AIRCRAFT CARRIERS

HORNET 08 38 S, 166 43 E 26 October 1942

LEXINGTON 15 12 S, 155 27 E 8 May 1942

WASP 12 25 S, 164 08 E 15 September 1942

YORKTOWN 30 36 N, 176 34 W 7 June 1942


ESCORT AIRCRAFT CARRIERS

LISCOME BAY 02 54 N, 172 30 E 24 November 1943


HEAVY CRUISERS

HOUSTON Off Java, N.E.I. 1 March 1942

QUINCY Off Savo I., Solomons 9 August 1942

ASTORIA Off Savo I., Solomons 9 August 1942

VINCENNES Off Savo I., Solomons 9 August 1942

NORTHAMPTON Off Savo I., Solomons 30 November 1942

CHICAGO 11 25 S, 160 56 E 30 January 1943


LIGHT CRUISERS

ATLANTA Off Lunga Point, Guadalcanal 13 November 1942

JUNEAU 10 34 S, 161 04 E 13 November 1942

HELENA Kula Gulf, Solomons 6 July 1943

[/font]
"Success is the ability to go from one failure to another with no loss of enthusiasm." - Winston Churchill
mind_messing
Posts: 3394
Joined: Mon Oct 28, 2013 11:59 am

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by mind_messing »

ORIGINAL: Lokasenna
ORIGINAL: crsutton

As for the 8 hex thing. It is the Allied cross to bear but not a game breaker at all. There are plenty of ways to manage it.

It never would have happened in real life, but there have been times when I've just stood my strike planes down and put all my fighters on CAP in case of an 8-hex strike. Worked just fine, but I also had higher priorities than sinking carriers in those instances.

True, but the only two circumstances where you've pulled it off was against a fragment of the KB.

The battle of Singapore was against 3 CV IIRC, and off Borneo was about the same (1 CV and 3 CVL IIRC). Going 100% CAP to defend against the 8 hex strike is risky.

FWIW, as Japan, I'd happily have my KB airgroups mauled by a buzzsaw CAP in exchange for a shot at Allied carriers free from the prospect of return strikes. In my experiance, there's always at least one carrier strike package that gets through in fairly good shape, even if the rest get mauled. The planes and pilots can be replaced easily enough - the carriers much less so.

Of course, you're 100% CAP has mauled my land-based air groups quite horrifically, but such is the nature of the game.
mind_messing
Posts: 3394
Joined: Mon Oct 28, 2013 11:59 am

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by mind_messing »

Of course, if you test and it turns out you are somehow correct and I'm wrong, I'll happily change my ways . But my 90% CAP settings are veritable buzzsaws. Ask MM . A recent example is 21 Helen kamikazes escorted by 85 Franks: 20ish Franks were knocked off of the escorting portion, and 20 of 21 Helens were shot down. My losses were something like 5 planes on the day. Maximum force CAP = quicker/better resolution to the first strike(s) against my stuff, which means more of them are left in the air for later strikes. It takes many raids to burn through 200+/300+/400+ planes on CAP with 40-minute warning or more for each strike.

Eh, I've just not managed to pull off that thousand plane strike on your carriers just yet.

You'll see, just you wait!
Alpha77
Posts: 2196
Joined: Fri Sep 24, 2010 7:38 am

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by Alpha77 »

ORIGINAL: Lokasenna

The flak updates we're talking about are actually in the scenario updates from Andy. They are in the modding subforum somewhere... Unofficial Scenario Updates I think is the thread title. It basically makes a lot of updates to ships especially, similar to DBB. Changing device numbers and whatnot - no more 8-rack E-class vessels for Japan, for one thing.

The LMG is not in the IJA infantry squad to my knowledge, but what do I know?

In my Scen 1 game, with the database updates, the IJA Infantry '43 has an anti-armor of 25. That is +20 from the previous squad.

Thanks, so I guess I need this update too for scen 2. But maybe I do not make to 43 anyway, so why bother ? However tbh this sounds quite confusing meanwhile scen updates, database updates and mods. I guess you mean scen update is hopefully the same as data update otherwise....[;)] And can it be used in an ongoing game at all ?

Check this video for the better LMG "type99" I am taking about: (looks like a Bren, but guy tells us its different actually. But seems quite good too)
https://www.youtube.com/watch?v=ckB3e6IObU4
Drakanel
Posts: 253
Joined: Mon Apr 06, 2015 12:59 pm

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by Drakanel »

Well, you posted losses and I really wanted to know that. I am curious about one thing though.

How are you doing with pilot pools and aircraft pools in this game? Especially in regard to carrier-specific airframes. You did lose quite a few recently, but I don't think you wrote recently how your pools are doing.
User avatar
crsutton
Posts: 9590
Joined: Fri Dec 06, 2002 8:56 pm
Location: Maryland

RE: The Elephant Vanishes :: obvert (J) vs SqzMyLemon (A)

Post by crsutton »

ORIGINAL: obvert
ORIGINAL: crsutton

Truth is that if you throw victory conditions by date out this is actually a very playable game for the Allies. I would gladly take the Allied carrier losses to date in exchange for the Japanese carrier losses.

I'd play the Allied side here without a doubt. I've seen what the Allies can do in 44 when the machine gets rolling. I think payers who haven't been through that before don't know how fragile the Japanese defences are in reality. They see the strong points. Which is what I want them to see right now! [;)]
Frankly the loss of three fleet quality Japanese CVs hurts a lot more than all of the Allied losses. 1944 will replace and then double his forces. I would love to play the Allies at this date. In fact, I think it would be a great idea to never activate the Soviets by agreement, you could see a campaign go deep into 1946 with a lot of interesting new toys come into use. This is something that we have yet to see in an AAR. You should propose this. Throw out victory conditions and tether the Russians and see what happens.

As for the 8 hex thing. It is the Allied cross to bear but not a game breaker at all. There are plenty of ways to manage it.

Thing is that after another year of war, barring some seriously mind boggling poor play, the Allied player is just going to be crapping out more resources than he can handle-regardless of what happens now. Been there and seen it. Heck, just the thought that I would finally get to use the A-bomb would make me want to cry with joy like a little girl..[:D]

I don't see the Russians as a problem to reaching 46. They can have Manchuria by mid 45 when they activate. I'd be more concerned with getting needed fuel and resources to keep an economy working at that point. If that is still happening, yes, the game can go happily into a massive jet fur ball over Japan in 46! [8D]

I think it is more that when the Russians come in Manchuria will fall very quickly along with Korea-putting a lot of level 9 airbases right next door to Japan. Considering that the Allies will get 100 B17s a month-not to mention all those lancasters, I just see the Japanese air force getting suppressed very fast. (jets or no) I would tether the Russians completely to stop that. Even that may not work as the American as so powerful but it would be very fun to watch and find out. But you are right. I really don't know how the industry thing would play out but as it stands now, your oil pipeline is not threatened so you might be in pretty good shape.
I am the Holy Roman Emperor and am above grammar.

Sigismund of Luxemburg
Post Reply

Return to “After Action Reports”