Reluctant Admiral Mod - CV strike issues (Full Version)

All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Tech Support



Message


Enforcer -> Reluctant Admiral Mod - CV strike issues (10/15/2018 10:09:13 PM)

I cannot get my cv's to launch any more than 30 or so planes can someone help me?

I am uploading 4 images



[image]local://upfiles/5900/F101F7F269594C28AF219CCF071AC3EC.jpg[/image]




Enforcer -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 10:09:42 PM)

second image

[image]local://upfiles/5900/BCFE3C7CBCFC4D438A5C9297538712E3.jpg[/image]




Enforcer -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 10:10:10 PM)

third image


[image]local://upfiles/5900/BC6310FF093A4641A76981011BC02A62.jpg[/image]




Enforcer -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 10:10:29 PM)

forth image


[image]local://upfiles/5900/23FB925CB15F43B3B9BCEE3F4BC757C2.jpg[/image]




Enforcer -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 10:11:06 PM)

does anyone have any idea?




btd64 -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 10:15:26 PM)

I put my squadrons on 20 to 30% search. That seems to help....GP




BillBrown -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 11:07:38 PM)

Were there other targets available? Did your search find them? So many questions.




Enforcer -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 11:11:00 PM)

i will try search but I have Tone, Chikuma, and 2 BB's I generally search with... but I will try some val's on search




BBfanboy -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 11:14:22 PM)

Range could be an issue for Kates armed with torps. They can only do "normal" range, not "extended" with that kind of load. Sometimes weather is an issue for being able to launch torp-armed aircraft too. Vals are much lighter with a smaller weapon load so they can launch in almost any weather (shorter take-off run, less issues with a heaving deck).




Enforcer -> RE: Reluctant Admiral Mod - CV strike issues (10/15/2018 11:19:20 PM)

i was only at 4 hexs from the transports




BillBrown -> RE: Reluctant Admiral Mod - CV strike issues (10/16/2018 1:55:37 AM)

Always keep in mind, it is not what you see or know, it is what the TF commander sees or knows that makes the difference.




Barb -> RE: Reluctant Admiral Mod - CV strike issues (10/16/2018 6:21:15 AM)

1. Detection of the target (via Air search or Float planes, or sub spotting or surface contact)
2. Size of the target (no purpose sending 150 planes against couple of transport)
3. Target priority or threat (CV, CVE, BB, CA, CL, DD, other stuff)
4. Weather (bad weather can affect strike size as well as parcel it out, not to mention it effects DL too)
5. Leader rolls (CV TF leader, Air group leaders - failed roll here could mean 25% of the strike/group strength)
6. Expected opposition (heavy CAP can force strike to seek other targets or not fly at all)

You can effectively affect points No. 1 and 5. Other depends on your opponent or game rolls :)




inqistor -> RE: Reluctant Admiral Mod - CV strike issues (10/16/2018 9:32:59 AM)

All groups should be set to the same altitude (and 5000 is IIRC Low Naval already), for best coordination chance.

But it seems to me, that target TF had too few ships for CVs to send more planes.




BBfanboy -> RE: Reluctant Admiral Mod - CV strike issues (10/16/2018 2:06:34 PM)


quote:

ORIGINAL: inqistor

All groups should be set to the same altitude (and 5000 is IIRC Low Naval already), for best coordination chance.

But it seems to me, that target TF had too few ships for CVs to send more planes.

The threshold for low naval was changed from" below 6000 feet" to "below 2000 feet" years ago, at the same time glide bombing was eliminated from the game's algorithm. I think the change was to put Low Naval in range of IJN light AA, because it lacked much medium AA to engage at 6000 feet.




Lokasenna -> RE: Reluctant Admiral Mod - CV strike issues (10/22/2018 3:16:55 PM)

This seems like a detection level issue.

The problem should be solved with more/better search.




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
9.140625