Page 3 of 3

RE: Unit recovery from disablements

Posted: Tue Nov 27, 2018 3:35 pm
by Yaab
ORIGINAL: JoV

Interesting [:)] Look forward to seeing what you are able to demonstrate.

As for my lazy bloody 65th, after a long convalescence at Takao they moped up some of the smaller island and were then shipped to Truk, where they rebounded relatively well. I then moved them all down to Milne Bay. I once read Milne Bay has the highest rate of malaria anywhere in the world. Seemed an appropriate location for them to think about their poor performance for the next few years.

Image


Actually, come to think of it, your unit didnt need healing. If you go with manual which says that support required represents your unit need to perform at full efficiency, the 65th was 100% efficient. Its 204 non-squads devices (the ones that assault or fire) enjoyed 240 support squads. Thus, the unit was 100% efficient at 70% TOE instead of the standard 70% efficient at 100% TOE.

RE: Unit recovery from disablements

Posted: Tue Nov 27, 2018 4:31 pm
by GetAssista
ORIGINAL: Yaab
Actually, come to think of it, your unit didnt need healing. If you go with manual which says that support required represents your unit need to perform at full efficiency, the 65th was 100% efficient. Its 204 non-squads devices (the ones that assault or fire) enjoyed 240 support squads. Thus, the unit was 100% efficient at 70% TOE instead of the standard 70% efficient at 100% TOE.
It is unclear what this "efficient" means in the manual. It certainly is not combat strength. I tested LCUs with zero support and they fight just fine. Support matters during recovery

RE: Unit recovery from disablements

Posted: Tue Nov 27, 2018 4:40 pm
by Yaab
Interesting. I guess you could do a test in which the same unit only has 100 assault squads and 70 support squads, and a copy of this unit which has 100 assault squads and 0 support squads, and see if you can achieve similar assault values.

RE: Unit recovery from disablements

Posted: Thu Nov 29, 2018 3:24 pm
by GetAssista
ORIGINAL: Yaab
The only reason the 48th Div is undisabling is that it uses additional support from an HQ. Thus, its "Support required" number is shown in GREEN colour.

65th Bde cannot undisable because it uses its own organic support squads to undisable itself. Thus, its "Support required" is in WHITE. The unit does so because it has surplus support (240 support squads supporting 204 other devices).

Even if you put 65th Bde in an empty base with 20k supplies, and five HQs with 100 support squads each, the unit will NOT UNDISABLE, because the code will not assign any HQ to heal the 65th Bde.


It is a quirk of the code, and can sometimes happen when a unit is damaged in combat, and emerges from combat with more support squads active than non-support squads (65the Bde) or can be set so by a designer in a scenario (think 74th Corps in Changsha in scen 1 and 100). The problem is, the organic support squad are totally inefficient in undisabling devices from its own unit. Sometimes it is 1-3 devices per turn, and the next turn 1 device may get disabled. In case of 65th Bde, its organic support has yet to undisable 37 infantry sqauds, before support squads from HQ can help with undisabling the remaining 60 squads.

Sorry, no cigar. I ran the tests, and white/green does not matter for disablement recovery

RE: Unit recovery from disablements

Posted: Thu Nov 29, 2018 4:38 pm
by Yaab
Well, I cannot replicate your findings in-game in China. Maybe its low exp/morale thing? Thanks anyway.

RE: Unit recovery from disablements

Posted: Thu Nov 29, 2018 4:52 pm
by GetAssista
ORIGINAL: Yaab
Well, I cannot replicate your findings in-game in China. Maybe its low exp/morale thing? Thanks anyway.
I ran 4 rounds of 12 turn R&R restarting the scenario for each new round, and in 2 of the rounds there was one ID that seemed stuck at low number of healed squads. Like 1-2 squads with others healing ~10 squads on average. It happens sometimes with random numbers. IDs were different, and of different types too.
How many rounds did you do in China?

RE: Unit recovery from disablements

Posted: Thu Nov 29, 2018 5:19 pm
by Yaab
Restarted the grand campaign three times, ran each restart for five turns. Focused solely on 74th and 10th Corps in Changsha.

RE: Unit recovery from disablements

Posted: Thu Nov 29, 2018 5:56 pm
by Lokasenna
Why not look at all of the Chinese units, via Tracker? Yes, you'd have to save every turn, but... with Tracker's multi-turn read, you could load them all in at once.

RE: Unit recovery from disablements

Posted: Sat Dec 01, 2018 3:26 pm
by Yaab
Too many variables.

RE: Unit recovery from disablements

Posted: Sun Jul 07, 2019 5:39 am
by Yaab
Here it comes.

Two HQs in Changsha. Both have support in WHITE (since support squads don't require support, the Chinese HQs have always intrinsically more support than needed). Both HQs consist only of one device - support squads. They differ in two respects - thier experience and the ratio of active to disabled support devices.



First HQ, exp 30

Image



Second HQ, exp 60

Image

The first HQ is stuck in a limbo (undisable one device, than disable one device and so on) and only heals one squad. The second HQ fares better and heals five squads in the same time.


RE: Unit recovery from disablements

Posted: Sun Jul 07, 2019 12:38 pm
by GetAssista
ORIGINAL: Yaab
Two HQs in Changsha. Both have support in WHITE (since support squads don't require support, the Chinese HQs have always intrinsically more support than needed). Both HQs consist only of one device - support squads. They differ in two respects - thier experience and the ratio of active to disabled support devices.

The first HQ is stuck in a limbo (undisable one device, than disable one device and so on) and only heals one squad. The second HQ fares better and heals five squads in the same time.
2 observations doesn't matter squat. The human brain is programmed to seek out dependencies, and random numbers are a trusted source of those fluke ones. Only proper statistics can tell. Means lots of turns in a controlled environment -> forget GC, use special cleaned up scenario