Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Group fragment move and repair delay

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Group fragment move and repair delay Page: [1]
Login
Message << Older Topic   Newer Topic >>
Group fragment move and repair delay - 6/29/2014 10:06:49 AM   
Gaspote


Posts: 303
Joined: 6/30/2013
From: France
Status: offline
Hi,
Firstly, don't read this Iley.

Secondly, Just to explain a bit better. In my PBEM, scen 2, betaX8, Kirakira airfield level 4 with J2M2(SR3) got bombed and something like 20 on 45 got damaged on the ground or in the air. I immediatly retreat the group on Lunga airfield lvl 8 and send a cargo on Kirakira.
The next day, I load the J2M in Kirakira and send them in Lunga.
One day later, the J2M groups merged and start repairing but I change my mind and send the group in Rabaul airfield lvl 8. Only the flying plane move.
The next day, I looked at Rabaul airfield and the whole group is here with 20 damaged planes, the fragment in Lunga isn't there so I think they move.

What I don't understand is the fact they didn't move from Kirakira to Lunga but they move from Lunga to Rabaul which is farthest. What is the answer ? Bug or big airfield got those sort of capability

Thirdly, I got 9 N1K1-J in Rabaul repairing, the previous turn, 3 N1K1-J were repairing with 2 day, 1 day, 1 day but the next day 2 are still repairing with 1 day delay.
They don't fly so I don't think 2 got repaired and another start repairing this turn. I noticed the same about H6K or H8K but like 4 repairing in 4 day, keeping 4 day the next day. I got 4 times the aviation support needed though.

My question is why those planes need more times in a base full or support ? I understand when there is not enough of support, it's longer but if there is enough and even more support it should be the correct estimation or even less

Post #: 1
RE: Group fragment move and repair delay - 6/29/2014 2:30:17 PM   
czert2

 

Posts: 508
Joined: 2/10/2013
Status: offline
no idea about first case, since i think there is no road conection between lunga and rabaul, but for second case - do you have enough aviation suport ? airfield fully repaired ? since if you have problems here it casusing delays with repairing of planes.
and enough of supplies at base ? i know that actualy only drawing plane from pool cost supply, but if base lack supply many operation which dont consume supply are simply off until is there enough supply again.
And how big is fatigue/organization of land av groups ? if they are tired they work less effective.

(in reply to Gaspote)
Post #: 2
RE: Group fragment move and repair delay - 6/29/2014 5:40:57 PM   
Gaspote


Posts: 303
Joined: 6/30/2013
From: France
Status: offline
I check and some airfield units have a low morale and are set on strategic mode or rest/training because I'm moving them.
Although the AV support need is 136, there is the 11th air fleet fully prep, no fatigue or disruption and in combat mode which give 144 AV support, x2 with AF lvl 8 so 288.

It seems the game is checking the AF units first and it affects the repair so ? But why checking them if I clearly don't deploy them ?


edit : The engineer at the base ask the guy in the port waiting his transport like " Hey buddy, waiting your ships, please repair this plane I need to play poker"

< Message edited by Gaspote -- 6/29/2014 6:43:22 PM >

(in reply to czert2)
Post #: 3
RE: Group fragment move and repair delay - 6/30/2014 5:53:13 PM   
Alfred

 

Posts: 6685
Joined: 9/28/2006
Status: offline
Not a bug but insufficient data given to allow for definitive answer.

1.  No mention of amount of Kirakira airfield service damaged inflicted by bombardment.  This greatly impacts on aircraft repair rates.

2.  Smaller sized airfields have their airfield (and runways too) damaged more easily and more severely than larger sized airfields.

3.  No mention of how many aviation support were disabled by bombardment and hence temporarily unavailable to effect aircraft repairs.

4.  No mention of available supplies at Kirakira.  Again another important factor in effect aircraft repairs.

5.  The distance between the airfields is irrelevant, provided they are within normal range of the aircraft.  Although distance will impact on susceptibility to damage of arriving aircraft.

6.  Presumably Lunga was better resourced and less damaged than Kirakira, thus allowing for the damaged airframes delivered by ship on day 4 to be sufficiently repaired to automatically transfer to Rabaul.


As to the N1K1-J, I don't see what is the problem.  The information given is only an estimate of repair times, not a 100% guarantee.  The factors mentioned above come into play.

Alfred

(in reply to Gaspote)
Post #: 4
RE: Group fragment move and repair delay - 6/30/2014 6:17:10 PM   
Gaspote


Posts: 303
Joined: 6/30/2013
From: France
Status: offline

quote:

ORIGINAL: Alfred

Not a bug but insufficient data given to allow for definitive answer.

1. No mention of amount of Kirakira airfield service damaged inflicted by bombardment. This greatly impacts on aircraft repair rates.

2. Smaller sized airfields have their airfield (and runways too) damaged more easily and more severely than larger sized airfields.

3. No mention of how many aviation support were disabled by bombardment and hence temporarily unavailable to effect aircraft repairs.

4. No mention of available supplies at Kirakira. Again another important factor in effect aircraft repairs.

5. The distance between the airfields is irrelevant, provided they are within normal range of the aircraft. Although distance will impact on susceptibility to damage of arriving aircraft.

6. Presumably Lunga was better resourced and less damaged than Kirakira, thus allowing for the damaged airframes delivered by ship on day 4 to be sufficiently repaired to automatically transfer to Rabaul.


As to the N1K1-J, I don't see what is the problem. The information given is only an estimate of repair times, not a 100% guarantee. The factors mentioned above come into play.

Alfred

Thanks for you answer Alfred.

I don't remember but the damage stop the CAP flying it's why I evacuate. Enough supplies, the airfield fully repaired a few day later. The av support got big disruption, I think it didn't help. Lunga wasn't attacked, it was a big strike to close Kirakira.


For the second point, I recently got the opposite, J2M were still repairing with a lot plane at about 2-3 day but they repair in 1 day. I just didn't got lucky before.


Just to know, what are the conditions for automatic transfer from an airfield to another of damaged planes ? It's the most important point I don't understand. I'm totally unaware of a such capability.

(in reply to Alfred)
Post #: 5
RE: Group fragment move and repair delay - 6/30/2014 6:32:01 PM   
Alfred

 

Posts: 6685
Joined: 9/28/2006
Status: offline
Flyable airframes of a fragment will automatically rejoin their parent if within normal (clean, not using drop tanks) air transfer range.  In your case none of the damaged planes at Kirakira had repaired, hence why you had to pick them up by ship.  But all the damaged airframes at Lunga had repaired.  Then at Rabaul some of your arriving (and perhaps some of the previously ready airframes) became damaged.

If you had waited longer at Kirakira, as the damaged planes became ready they would have flown out to join the parent at Lunga.

Alfred 

(in reply to Gaspote)
Post #: 6
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Group fragment move and repair delay Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.922