Nikademus
Posts: 25684
Joined: 5/27/2000 From: Alien spacecraft Status: offline
|
[QUOTE]Originally posted by bhdhtx [B]OK, I agree with you all BUT make the **** AI think like a freakin admiral and not an ensign on his first day! Who in the heck lets injured carriers get away? The AI would rather go after a CA and CL and even DD's letting a SPOTTED, injured CV go on his way home. How idiotic is that? Why send a squad of 4 SBD’s strike against a CV force with full CAP? Come on! You guys say let the computer handle it, well OK I would love that but once again make it smarter, not so **** stupid that I have to worry about trying to get LUCKY in sending my US carriers against an out ranged Jap CV that I almost send them to their death every time I take them in for an airstrike. I have been playing war games for 25 yrs now and just because it’s a nuisance to some how to program the CV targeting capability, it can make this game a flop because we have to worry where our Admirals will send an airstrike, the Soryu or a DD!!!!! Appreciate the feedback and how someone can be so **** rude! B [/B][/QUOTE] Hi B Correct me if i'm wrong but it sounds alot like you play (as most of us do) with your carrier TF's set to "no reaction"/no retire. If thats the case, i feel it should be pointed out that while such a setting does give players minute control of their TF's movement and positioning, it can also set yourself up for a long range strike if an enemy TF is spotted. For the Japanese player this is not a major issue as theirs is the longer ranged airpower. (Not always though....the AI tried a long range IJN strike on me and it got disjointed and i slaughtered an unescorted Val strike in my current SC19 game) However for the USN player it can mean the difference between an escorted and an unescorted strike, with a greater chance of dispersion of the flight elements in the process. I've seen the AI take alot of flak about "unescorted" or "broken" raids against heavily defended targets. However in this situation at least we must remember that the AI is only trying to fight the battle under the contraints that WE the players have placed on it prior to that battle. I rarely see broken or unescorted strikes when carrier TF's are set to "react" because they close the range sufficiently to minimize such disruptions. However as all players know....you take your chances with react on......as it almost assures a mutual set of strikes that may or may not go your way. Hardly an AI problem in this case. Also, one thing that puzzles me in all this type of complaining (strikes hitting well defended CAP targets), is how is a real life commander to know just how well defended a target is before getting there? In all the carrier battles i've researched of late, i've never seen a reference made to CAP strength of enemy target. They find the target, a decision is made whether to launch a strike or not and if so, they go. Escort levels are more influenced by the commander's desire to keep fighter assets back to protect their own home base than in anticipation of enemy resistance. Lastly, frustrating as it might be, the simple fact of the matter is that during the real live war, misidenitifcations, flight disruption and dispersion and a slew of other mishaps did happen. We have to deal with it, because it really happened. (This should not be confused with the seperate issue of LBA based craft attacking powerful ports at extreme range protected by CAP which i feel can be resolved by a "range" button for LBA bases.....carrier aircraft dont need it because their range is far shorter)
|