I'm done with this ridiculous time vampire of a game.

[btd64]

ORIGINAL: afspret

I've only played against the AI, mainly due to my work schedule, and I always save a turn before I run it. That way, if I get battered during a turn, I can always replay the turn after making some changes that will, hopefully, avoid the out come of the previous turn. I know it might seem gamey to some of ya'll, but I've only done this a few times. Besides, I've found that sometimes, no matter how many times I'd replay a turn, the outcome is usually the same (or worse), especially when it comes to naval engagements.

Good way to learn from your mistakes. Then when ready to play a PBEM, your better prepared. When I first started playing AE I did the same. The AI didn't complain and sometimes you can develope strategies that you can use latter on. I'm playing the AI now with a Andy Mac Nasty and I just located a Japanese 2 CV TF that was causing problems for me in the (can't give away the location in case you want to play it) ****** ocean and I intercepted with a combo of British and US CV's and sunk all but 1 (FOW) DD....GP

Sorry Andy.[:D][:D][:D]

[btd64]

ORIGINAL: geofflambert

There was a historical battle (forget which one) where the Enterprise was operating with another CV (in the same hex in game terms) but was hidden by a squall when the attack came and the other CV took all of it.

Midway, I think....GP

[btd64]

ORIGINAL: Endy

While I agree that some of the whining comes from lack of knowledge of how the game works or lack of preparation, there are genuine situations, and quite a lot of them, where luck plays a major role. And it can be very easily checked by simply replaying the turn. I did my share of it with my opponent who was also interested in how stuff could play out with a different dice roll and in a few different scenarios - carrier strike, SAG battle etc. - the results varied from catastrophical to really good ones depending on a dice roll.

And I don't agree that you can plan for everything. Despite your best skills there are always factors you have absolutely no control over. Weather is just one example - absolutely no control over it and no way to plan or prepare for it because the forecasts are not a reliable tool to predict it. And just this one factor can lead to a MAJOR difference in results, for example a carrier battle or a surface action depending if you get nice weather or a thunderstorm in the target hex or hexes. And yes, it's just a matter of how lucky you are with the roll despite everything else you did.

I can name a few other factors but I believe you get my point. Yes, this kind of randomness in some factors is pretty realistic and true to life and most of us have learned to accept them. However, some players are used to something very different and to games, even pretty realistic ones, where the battle outcome just can't vary so much depending on just one factor. Many games, even the more complex or realistic ones, let you predict your chances very well, with only slight variation of the final result. Of course, you might argue that this is more similar to chess than real war but some players react very badly when this kind of control is taken away from them.

I'll say again, yes, WITP has got most of these random things right and yes, stuff you can't control like weather could play a major role in a sea battle and shape history and should do the same in game. The problems start when you realize that if you moved that one squadron somewhere on the West coast or in Japan, then that carrier battle could've been just as easily as it has been lost. And like I said, some other wargames have randomness confined to a much bigger degree and you can predict the results of your actions MUCH better without the wild disparity of results based on a random dice roll.

And some players react histerically to that and have a really hard time accepting it in Witp. Then again, this game is just not for everyone and you need to learn to accept it as it is.

All the more reason to play a PBEM.[8D]....GP

[Endy]

ORIGINAL: geofflambert

No one can know exactly what will happen, and I believe the weather is fixed and won't change if you rerun.

Nope, random weather is random each time you rerun

[Endy]

ORIGINAL: General Patton
All the more reason to play a PBEM.[8D]....GP

Sure, for some, you, me as well as most players on this forum this is a great thrill. But some people are just not prepared for the amount of randomness in Witp and how it affects each game.

Again, just playing devil's advocate here, not complaining personally

[btd64]

ORIGINAL: Endy

ORIGINAL: General Patton
All the more reason to play a PBEM.[8D]....GP

Sure, for some, you, me as well as most players on this forum this is a great thrill. But some people are just not prepared for the amount of randomness in Witp and how it affects each game.

Again, just playing devil's advocate here, not complaining personally

Understood, but for me, its not so much a thrill as much as having the satisfaction of planning out a battle and setting it in motion. The results are the results. Still, even with the occasional disaster, This is THE BEST WAR SIMULATION money can bye....GP

[btd64]

ORIGINAL: Endy

ORIGINAL: geofflambert

No one can know exactly what will happen, and I believe the weather is fixed and won't change if you rerun.

Nope, random weather is random each time you rerun

Die roll....GP

[geofflambert]

ORIGINAL: Endy

ORIGINAL: geofflambert

No one can know exactly what will happen, and I believe the weather is fixed and won't change if you rerun.

Nope, random weather is random each time you rerun

That proves I don't rerun stuff

[wdolson]

ORIGINAL: geofflambert

There was a historical battle (forget which one) where the Enterprise was operating with another CV (in the same hex in game terms) but was hidden by a squall when the attack came and the other CV took all of it.

ORIGINAL: General Patton
Midway, I think....GP

Santa Cruz is what you're thinking of.

The Enterprise and Hornet were operating together at Midway, but the Yorktown was separate and probably 1-2 hexes away in game terms.

At Santa Cruz the Enterprise also had the benefit of operating with a BB which both drew bombers and was able to significantly contribute to the AA defense. The Enterprise still took a couple of bomb hits after the Hornet was out of action which shut down the deck for launches and jammed one of the elevators in the up position, but in one of the best landing operations of the war the LSO crammed planes onto the crowded deck. The Captain ordered him to stop when the planes backed up to the #3 wire, but he kept landing them. He held off the commander of VF-6 until last because he knew he was the best pilot on the ship. With only one wire still open, he directed the Wildcat to touch down a hair above stall speed and the Wildcat finished its run out inches from the tail of an SBD.

The LSO knew aircraft were running short and wanted to save as many as possible.

The Japanese and American strikes crossed each other in flight. The Japanese escorts peeled off and went after the after the US bombers breaking up the formation and shooting down or shooting up quite a few. One TBF that was badly damaged made it to the Japanese fleet, got into drop range, only to find his bomb bay was damaged and the torpedo would not release, nor would the bomb bay doors close. He flew back and was directed to ditch next to the USS Porter. It's believed the torpedo broke free while ditching and hit the Porter. For years it was thought to have been a Japanese sub, but there were none anywhere near the TF.

I once had a Battle of Rabaul with 4 Japanese CVs vs the Yorktowns. I still held Rabaul and had a bunch of fighters there as well as a few bombers. When the Japanese were spotted leaving Turk, the Yorktowns happened to be crossing the Coral Sea on their way to Java. I was able to top up their tanks and move them just south of Rabaul. For the first two days of the battle heavy storms over my carriers prevented flight ops as well as the Japanese knowing I was there. The KB lost a lot of planes ravaging Rabaul and pretty much wiped out the aircraft there. On day 3 the USN had clear skies and they pummeled the KB. I think two carriers lost, one badly mauled (Shokaku) in exchange for a bad torpedo hit on the Hornet. The Hornet spent a few weeks at Rabaul patching up then limped back to Pearl Harbor. The Enterprise and Yorktown air groups were badly mauled and it took a while to replace and retrain pilots.

It was worth it though. the Shokaku was out of action for a year or more and I think it was the Akagi and Hiryu sunk.

I'm sure if I had been on the other side of that one I would have been very upset!

Oh and I don't think the weather is fixed. The rule of thumb is if it can vary in the real world, it probably does in game too.

Bill

[PaxMondo]

ORIGINAL: LoBaron

Nearly all spectacular CV battle loss threads on this forum, where a lot of angry tears are shed about the randomness of the results and the absence of predictability, fall into one of the above categories.

A CV battle lost in a situation where objectively every factor that can be influenced by the player points to victory, and every factor beyond his influence is minimized, is a rare event indeed.

But truthfully, in this era, CV battles were a crap shoot at best. Looking at early war outcomes, getting into a CV battle generally meant both sides took a beating. This is based upon the '42 CV battles through Midway. Yes, IJ had the worst, but most unbiased assessments of each battle fought (meaning not Morison [;)] generally conclude that a few minutes here, a couple of minutes there and outcomes change dramatically. Those razor thin margins are, I beleive, well modeled in the game.

Point being, most air combat, and particularly naval air combat, had a lot of variable NOT controlled by the commanders. Weather being first, but FOW being right with it. Intel was far from perfect. Because of these two factors alone, coordination was measured in double digit minutes, not seconds like today. I think that, more than anything, is what many [younger] players struggle with. They have never been in a situation where absolute, total control was not possible. Products of the digital age, the whole concept of analog is just foreign.

Anyway, just thoughts of an analogue Neanderthal.

OT: I was having a conversation at a picnic this past weekend with an MIT EE graduate (21 yo wunderkind) and we were talking about programming etc. He was expressing his disdain for any language except C#. When I told him my digital programming start with the 4004 and I was happy with any compiled language he looked at me with a blank look. Pretty sure he had no idea what the 4004 was nor that it was programmed with machine language only initially. Nothing else was available at that time. [;)] I wonder what he would have done if I had told him about analogue computers that I programmed? [:D][:D][:D]

[geofflambert]

You're ancient. I started with Fortran and stacks of punch cards five inches thick to simulate a game of tic-tac-toe. [:D]

[Chickenboy]

Feh. I used to program with arrays of rocks. Good ole' rock. Nothin' beats rock.

[geofflambert]

I didn't know you went back to the Stone Age. I thought you were from the Dirt Age. [:'(]

[Chickenboy]

"Dirt"? Feh. That's new-fangled. I go back to random swirling of carbon atoms.

Now AW1Steve? He's from the days of only one element. Hydrogen. Good ole' hydrogen. Nothin' beats hydrogen.

[crsutton]

If we had the ability to micro manage our battles to the point of guaranteed success, then this would quickly become one of the most boring games. It is the total uncertainty that keeps me playing it day after day. Most other computer games have about a three month shelf life with me.

[AW1Steve]

I'm not quite that old. But my 1st computer languages were Pal-d , R-basic , COBOL and Fortran. And of course in the Navy our computer in the airplane was a Univac. A CP-901. (Sad thing, the USN still uses it! State of the art , 1962![X(]). Of course , my 1st computer was a pair of metal wheels bolted together. [X(]

[:D][:D]

[geofflambert]

A pair? I was forced to start on three, then four before I got to two.

[1EyedJacks]

My first computer...

[Chickenboy]

All this high-falutin' number countin' goin' on here...I come from the old school. Just one number back then: 1. Good ole' one. Nothing beats 1.

[1EyedJacks]

Ahhh - but you forgot the zero - 0. You can't have one without the other.

(Damn but that was a beautiful line [:D] )