LoBaron -> RE: Why won't my CV TF attack a BB? (5/28/2012 9:07:43 AM)
|
quote:
ORIGINAL: koniu quote:
ORIGINAL: Puhis quote:
ORIGINAL: koniu quote:
ORIGINAL: jmalter hi TheOx, the short answer is, "sometimes they don't attack." the long answer is trying to discover why they didn't. 1st, i don't think that bases/CVTFs communicate w/ each other, each one must detect the target separately. your LBAs won't share target info w/ your CVs. 2nd, weather is a big factor - storms in both launch & target hexes will lower the ability to detect the target & launch an attack. 3rd, there's a lot of 'checks' that the game makes - the air skill of the CVTF commander, the skills of his subordinate sqn commanders, ordnance availability, sqn morale & exp, NavSearch %age on the threat axis, etc. but sometimes the game just decides not to attack, it seems it doesn't let your assets recognize the target as a potential threat. have you set a reaction range for your CVTF? You are wrong. I am 99.99% sure that there is no separate search for units/basaes. If planes from one base detect enemy all friendly bases and TFs see that enemy as he was detected by them. So you can have search planes in one base and attack planes in second an they will attack even if they do not search for enemy. What max range have your CV air groups? One time i accidentally set them on range 0 and that was reason they not fly. I think jmalter is right, carrier TF have to fly their own search. Ok. I will test it when i back home. I was sure that there is no separate DLs for base and TFs and game do not recognize from what source search plane was. Probably someone with game code knowledge can answer for that. There is no connection between strike assignement and the source of the DL increase. A DL is a DL, thats it. This means, the source of the detection can be a floatplane launched from a CA, still the carrier planes would launch a strike. BUT: (and thats a big but to consider) There is a connection between strike assignement and the timing and the quality of a DL increase. If the source of the DL increase is much further away from target than the CV TF ordered to NavB/T, this means that the DL increase only happens after the strike has already been assigned to a target (or a secondary target), resulting in low priority or no targets being attacked. And if the search is carried out by LBA with NavS in the low 20´s, well, you´re asking for 'it'. So, as an example, it is a bad idea to have a CV TF on naval attack only (without search) and assigning the NavS task to Catalinas 400nm 'behind' the carriers. Edit: In general I prefer to use NavS originating from my CVs for a couple of simple reasons: - cruise speed and range of the searching planes ensure that the search is done before the strikes are assigned (which could be otherwise for low cruise speed floatplanes like Seagulls for example) - weather is the same for the searcher as for the striker, preventing the big ooops situations where the base/ship of the searchplanes is covered in thunderstorms unable to launch - in general the NavS skill of the CV based planes is well above average, inreasing chances for a good detection This neccesarily does in no way imply that its a bad idea to enhance the CV based search with every other asset available... [;)]
|
|
|
|