How to read the Event Log properly (Full Version)

All Forums >> [New Releases from Matrix Games] >> Gary Grigsby's War in the East Series



Message

rainman2015 -> How to read the Event Log properly (5/16/2016 1:01:11 AM)

OK, another question i am just getting round to asking about now. I have been glossing over my lack of understanding of the Event log since the beginning, but now want to fully understand it, so a few questions on what the different column headings mean. I will add in what these columns mean to the condensed rules also. I have good guesses on what many of the columns mean, others i am very in the dark about.

Under the main heading 'Refit Replacement: Segment B'
Germany

What do the column headings 'POOL, USED, BACK, LOST' mean?

Under the next set of column headings, out to the right of 'ELEMENT', what do the column headings
'POOL, READY, DAMAGED, WANTED, BUILT, CONV, ADDED, BACK, LOST' mean?

[image]local://upfiles/51100/FF4F93706E0E47EFA9B887D4D1A79B04.gif[/image]

Like i say, i am pretty sure i understand a number of these headings, WANTED or BUILT for example, but others i am needing clarification on. What is the difference between the POOL and READY columns, what does BACK mean, etc?

Thanks!
Randy
:)



morvael -> RE: How to read the Event Log properly (5/16/2016 9:43:05 AM)

First header:
POOL - number in active pool at start of that replacement segment
USED - number used during that replacement segment to fill up added elements (Manpower, Hiwis) or build new elements (Armaments, Vehicles) or convert existing elements directly in units (Armaments)
BACK - number returned during that replacement segment (they go to transfer pool, and are not available to be used as replacements until next turn), unpaired from returning and destroyed elements
LOST - number lost during that replacement segment (they go to disabled pool, and only a small percentage of these returns every turn), unpaired from returning and destroyed elements

So you had 8941 men in the German active manower pool at start of refit replacements, segment B; 1342 were taken from that pool and added to units refitted in this phase/segment; 24532 were removed from units refitted in this phase/segment, and will be made available next turn; 3092 were removed from units refitted in this phase/segment, and went to disabled pool (from which 0.95% return to active duty per turn, and 0.05% are killed).

The game tries to divide available resources between three replacements phases/segments, so despite 8941 being in the pool, probably only around 1350 were authorised to be used by replacements during that phase/segment. This is done in order to prevent starving units that go last during normal replacement phase by those on refit. Players had trouble with this previously when there were no caps, and found out they have to put even more units on refit every turn, untill entire army was on refit. Of course troops in refit, especially refit A (manual refit), have larger weight than their numbers of missing men suggest, thus are able to replenish faster than units in the last segment.

Second header:
POOL - number in active pool at start of that replacement segment
READY - number of ready elements in units on the map at start of that replacement segment
DAMAGED - number of damaged elements in units on the map at start of that replacement segment
WANTED - number of elements asked for by units on the map in that replacement segment (may be lower than number of really missing elements, because the base value is affected by modifiers like distance to rail)
BUILT - number of elements built during that replacement segment (to fulfill unit needs, will be always equalt to 0 for elements that are produced in factories, and not on demand)
CONV - number of elements converted in units during that replacement segment (shows negative for elements that were converted to other elements, and positive for elements that were converted from other elements)
ADDED - number of elements added to units that wanted them during that replacement segment (ADDED should be always lower or equal to POOL+BUILT)
BACK - number of ready or damaged elements elements returned to pool during that replacement segment (they go to transfer pool, and are not available to be used as replacements until next turn)
LOST - number of damaged elements that were written off and destroyed during that replacement segment

So looking at 37mm Anti-tank Gun you see that:
- you had 19 in the active pool at start of this replacement phase/segment
- units refitted in this replacement phase/segment had 8 ready, 0 damaged and were authorized to ask for 79 replacements
- to fulfill that demand 30 guns were built during this replacement phase/segment (no doubt costing you some of those 1620 armaments spent this phase) - for some elements, especially guns, there are limits to how many can be built per turn
- 49 guns were added to units (19 from the pool and 30 built), costing you 245 men out of those 1342 used during this replacement phase/segment (as each 37mm AT gun required 5 men)
- no guns were returned or lost



rainman2015 -> RE: How to read the Event Log properly (5/16/2016 3:05:29 PM)


quote:

ORIGINAL: morvael

First header:
POOL - number in active pool at start of that replacement segment
USED - number used during that replacement segment to fill up added elements (Manpower, Hiwis) or build new elements (Armaments, Vehicles) or convert existing elements directly in units (Armaments)
BACK - number returned during that replacement segment (they go to transfer pool, and are not available to be used as replacements until next turn), unpaired from returning and destroyed elements
LOST - number lost during that replacement segment (they go to disabled pool, and only a small percentage of these returns every turn), unpaired from returning and destroyed elements

So you had 8941 men in the German active manower pool at start of refit replacements, segment B; 1342 were taken from that pool and added to units refitted in this phase/segment; 24532 were removed from units refitted in this phase/segment, and will be made available next turn; 3092 were removed from units refitted in this phase/segment, and went to disabled pool (from which 0.95% return to active duty per turn, and 0.05% are killed).

The game tries to divide available resources between three replacements phases/segments, so despite 8941 being in the pool, probably only around 1350 were authorised to be used by replacements during that phase/segment. This is done in order to prevent starving units that go last during normal replacement phase by those on refit. Players had trouble with this previously when there were no caps, and found out they have to put even more units on refit every turn, untill entire army was on refit. Of course troops in refit, especially refit A (manual refit), have larger weight than their numbers of missing men suggest, thus are able to replenish faster than units in the last segment.

Second header:
POOL - number in active pool at start of that replacement segment
READY - number of ready elements in units on the map at start of that replacement segment
DAMAGED - number of damaged elements in units on the map at start of that replacement segment
WANTED - number of elements asked for by units on the map in that replacement segment (may be lower than number of really missing elements, because the base value is affected by modifiers like distance to rail)
BUILT - number of elements built during that replacement segment (to fulfill unit needs, will be always equalt to 0 for elements that are produced in factories, and not on demand)
CONV - number of elements converted in units during that replacement segment (shows negative for elements that were converted to other elements, and positive for elements that were converted from other elements)
ADDED - number of elements added to units that wanted them during that replacement segment (ADDED should be always lower or equal to POOL+BUILT)
BACK - number of ready or damaged elements elements returned to pool during that replacement segment (they go to transfer pool, and are not available to be used as replacements until next turn)
LOST - number of damaged elements that were written off and destroyed during that replacement segment

So looking at 37mm Anti-tank Gun you see that:
- you had 19 in the active pool at start of this replacement phase/segment
- units refitted in this replacement phase/segment had 8 ready, 0 damaged and were authorized to ask for 79 replacements
- to fulfill that demand 30 guns were built during this replacement phase/segment (no doubt costing you some of those 1620 armaments spent this phase) - for some elements, especially guns, there are limits to how many can be built per turn
- 49 guns were added to units (19 from the pool and 30 built), costing you 245 men out of those 1342 used during this replacement phase/segment (as each 37mm AT gun required 5 men)
- no guns were returned or lost


Thanks Morvael for the quick reply! I am sure this has been asked before, but i couldn't find it, and i had always kind of glossed over my lack of understanding of it in the game until now. This explains it. I will add it into the 'condensed rules', and point to it in the forum posts compilation i am about to release too.

2 quick further questions:

1) What is the difference between 'refit A' and 'refit B' segments?

2) Under the 2nd header, 'READY' = number of ready elements in units on the map at start of that replacement segment. If that is the case though, wouldn't there be MANY more 'ready' elements on the map for 'rifle squad 39' than '50' elements. Would be many thousands, right? Why only 50?

Thanks
Randy
:)



morvael -> RE: How to read the Event Log properly (5/16/2016 3:45:08 PM)

1) Some units are treated as being permanently on refit - HQs, air bases, support units attached to HQs - those units for which you can't manually turn refit on or off. It was a problem because these units ate most of replacements, whereas combat units were starved. So the refit replacement phase was divided into two segments - A and B. During segment A combat units and support units attached to them are handled, and during segment B those units on auto-refit are handled. Also, only segment A units are able to get access to greater share of resources than their requirements suggest.

2) But this is only for units included in that segment. Go to "Normal" table and see that most of squads are there.



rainman2015 -> RE: How to read the Event Log properly (5/16/2016 4:11:11 PM)


quote:

ORIGINAL: morvael

1) Some units are treated as being permanently on refit - HQs, air bases, support units attached to HQs - those units for which you can't manually turn refit on or off. It was a problem because these units ate most of replacements, whereas combat units were starved. So the refit replacement phase was divided into two segments - A and B. During segment A combat units and support units attached to them are handled, and during segment B those units on auto-refit are handled. Also, only segment A units are able to get access to greater share of resources than their requirements suggest.

2) But this is only for units included in that segment. Go to "Normal" table and see that most of squads are there.


Ah-ha to both questions, thanks Morvael! I wonder how many others have been glossing over these things and not fully understanding them, since there is no explanation at all in the rules about them. I will fix that in the condensed rules at least.

Randy
:)



WilliSaenger -> RE: How to read the Event Log properly (5/16/2016 7:21:48 PM)

I had also problems in understanding the event log, thank you for your question!



NotOneStepBack -> RE: How to read the Event Log properly (5/16/2016 7:42:39 PM)

So the units on auto-refit, does it matter if you set all your HQ's to MAX TOE 50 to save manpower? Is there any detriment to doing this for administrative units?



morvael -> RE: How to read the Event Log properly (5/16/2016 7:48:45 PM)

HQ has TOE%/1000 chance to add 1 to leader admin skill. That's why I prefer to keep mine up to strength.



NotOneStepBack -> RE: How to read the Event Log properly (5/16/2016 9:13:40 PM)

I prefer men with rifles, but thanks for the answer, gonna keep them at 50 :)



rainman2015 -> RE: How to read the Event Log properly (5/16/2016 9:17:03 PM)

On this same kind of note, if you lower your artillery to say TOE 50%, do the now over TOE guns and men get then sent ASAP back to the pool to get the artillery unit down to TOE 50%, or does the artillery unit keep its full compliment of guns/men (the original TOE 100% total of guns/men) until they lose those guns/men thru combat/attrition/etc?

As i have been reading about how the German masters are lowering their units TOE%, i have been wondering how that part of it would work.

Thanks
Randy
:)



morvael -> RE: How to read the Event Log properly (5/16/2016 9:21:13 PM)

It's blocked. Units return only elements from slots above 125% of MAX TOE, but MAX TOE below 80 is treated as 80. And 125% of 80 is 100. So you can only hasten returns of elements above 100% TOE by reducing MAX TOE to 80, but not more.



uw06670 -> RE: How to read the Event Log properly (5/16/2016 10:12:18 PM)

rainman, thanks for asking the question :-)



WilliSaenger -> RE: How to read the Event Log properly (5/16/2016 11:58:07 PM)

Im playing operation typhoon and I noticed something in the production section of the event log I don't understand.

It says it can't produce a certain amount of supplies because of resource shortages and cant produce a certain amount of armaments, vehicles and aircrafts because of supply shortages even though supplies and resources are abundant.
Are this shortages caused by resources and supplies that do actually exist but do not reach the factories because of weather conditions for example or is there another reason?

It also says 0 manpower recruited locally in 0 isolated manpower centers.
What does this mean? What is manpower recruited locally and what are isolated manpower centers?



WilliSaenger -> RE: How to read the Event Log properly (5/17/2016 12:01:02 AM)

The event log attached



39battalion -> RE: How to read the Event Log properly (5/17/2016 4:06:01 AM)


Thank you rainman2015 for asking this question and thank you morvael for your very clear explanation.

I have always found the event report to be the part of the game I least understand.



morvael -> RE: How to read the Event Log properly (5/17/2016 10:09:36 AM)


quote:

ORIGINAL: WilliSaenger

It says it can't produce a certain amount of supplies because of resource shortages and cant produce a certain amount of armaments, vehicles and aircrafts because of supply shortages even though supplies and resources are abundant.

It also says 0 manpower recruited locally in 0 isolated manpower centers.


1) There was not enough resources in one or more cities, so factories located there could not produce. Do you have a city with industry that is currently disconnected from rail network? This may also show up if new factories come online, expand or are repaired, because the game is not good at predicting how many resources it will need in a city for the next turn.

2) If a city is isolated, but still owned by you, manpower recruited there will not go to the active pool. It will be cached in the city, and added to the pool only when the city will be no longer isolated.



WilliSaenger -> RE: How to read the Event Log properly (5/17/2016 11:19:10 AM)

ok, thank you for the clarification



rainman2015 -> RE: How to read the Event Log properly (5/17/2016 3:03:06 PM)


quote:

ORIGINAL: morvael

It's blocked. Units return only elements from slots above 125% of MAX TOE, but MAX TOE below 80 is treated as 80. And 125% of 80 is 100. So you can only hasten returns of elements above 100% TOE by reducing MAX TOE to 80, but not more.


Had to re-read that one about 5 times, but finally got it. So, no, reducing units to max TOE 50% will not cause the units to shed elements, they will instead lose elements eventually due to combat/attrition, etc, and then simply not build back up past 50% TOE with replacements. Got it.

Thanks! [&o]
Randy
:)



morvael -> RE: How to read the Event Log properly (5/17/2016 3:17:58 PM)

Yes, it's possible only to force them to immediately shed elements above 100% of original TOE (as defined by the game), instead of 125%, by setting MAX TOE to 80. Lower setting of MAX TOE will have no effect on shedding.



WilliSaenger -> RE: How to read the Event Log properly (11/28/2016 9:00:59 PM)

Hi,

I was taking a look at the event log again..

ARMY STATUS

COUNTRY ACTIVE TRANSFER DISABLED UNITS TOE BALANCE
Soviet Union 7468 32614 25138 614056 906234 -292178

Active should be the number of men in the pool after the replacements right?
If that's correct the number doesn't add up unfortunately because if I detract
51513 from 59869 I have 8356 left

NORMAL REPLACEMENTS

RESOURCE POOL USED BACK LOST
Manpower 59869 51513 12827 30687
Armaments 139352 11407
Vehicles 8000 0

Can someone also explain me what the TRANSFER column in the army status (above) means?

Thank you for your help.



morvael -> RE: How to read the Event Log properly (11/29/2016 8:45:02 AM)

Some men are taken from the pool outside of replacement phase, for example when squads are delivered to partisan units via air drops. That's why they are not accounted for in the USED column, and thus POOL-USED does not equal to ACTIVE (this info is dumped at different time - the very end of logistics phase).

TRANSFER is transfer pool, these men are returning from the front, and will make it to ACTIVE pool at the start of your next logistics phase (so there is a week delay, men returning are not available to be used in the same turn). Your TRANSFER is mostly made of those men listed in the BACK column in replacement phase (but there may be some men returned outside of replacements phases). Default production screen view shows numbers for ACTIVE+TRANSFER thus giving false impression that you have unused men in the pool. It can be switched to show either ACTIVE or TRANSFER (or both).




WilliSaenger -> RE: How to read the Event Log properly (11/29/2016 10:09:21 AM)

ok, thank you



MrBlizzard -> RE: How to read the Event Log properly (11/29/2016 10:41:42 AM)

One question:
Why ready elements go from front to transfer pool and then they go back to the pool?
What is it modeling?



morvael -> RE: How to read the Event Log properly (11/29/2016 10:51:01 AM)

Time to dispatch them to new owners. It's a simplification and averaging of time spent away from the front. For some elements it could mean servicing, replacing some used up parts etc. It is also helpful in replacement procedures not going crazy with items appearing in the pool magically mid-phase and throwing distribution calculations off.



Nix77 -> RE: How to read the Event Log properly (11/30/2016 12:54:32 PM)

quote:

ORIGINAL: morvael

HQ has TOE%/1000 chance to add 1 to leader admin skill. That's why I prefer to keep mine up to strength.



Is this stated somewhere in the rules?

Here's a direct quote from the rules 11.3.1 Leader Rating Check Procedure

quote:

Approximately one admin point is subtracted from the leader's admin rating for every ten percent the HQ unit is below its TOE support squad strength, with a max reduction of five points.


Which one is correct, or do they both apply?

In any case, I'd keep my HQ ToE above 90% when possible :)



morvael -> RE: How to read the Event Log properly (11/30/2016 12:59:35 PM)

Only the chance to add +1 applies.



Nix77 -> RE: How to read the Event Log properly (11/30/2016 7:17:13 PM)


quote:

ORIGINAL: morvael

Only the chance to add +1 applies.


Are you 100% sure about that? I can only find the penalty from the manual, and no signs of +1 chance either in the manual or patch notes?



morvael -> RE: How to read the Event Log properly (11/30/2016 9:21:37 PM)

I'm sure, I have written down detailed rules for leader rolls in a post some time ago.
Manual is very badly outdated.



EwaldvonKleist -> RE: How to read the Event Log properly (11/30/2016 9:27:55 PM)

Anyone has a link to this? In which section morvael?



morvael -> RE: How to read the Event Log properly (11/30/2016 9:43:57 PM)

Search is not working on the dev forum. I can't find it, and I don't have time for manual search [:(]



Page: [1] 2   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
2.421875