Reconciling LCU Device Mismatches

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Reconciling LCU Device Mismatches

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 >> Reconciling LCU Device Mismatches

Page: [1] 2 3 next > >>

Message

<< Older Topic Newer Topic >>

Reconciling LCU Device Mismatches - 7/30/2017 7:01:50 PM

Korvar

Posts: 813
Joined: 9/3/2014
Status: offline

I'm playing through a Scenario #009 (Dec 8th Quiet China) campaign as the Allies. It's Dec '42, and I've run into a snag with recombining LCU divisions.

It's a familiar problem based on the searches I did through the forum, although I wasn't able to find clear answers to both of the particular situations - I'll explain:

The issue is clear enough - device mismatches. For the uninitiated, before LCUs can combine into their parent unit, the unit values (i.e. device list) for each subunit must match. When there is a mismatch, the offending device(s) will be marked with double asterisks (**).

So the first situation that can happen is that one of the subunits upgrades a particular device before the others. I found the answers to this situation in my forum searches: freeze upgrades for the applicable LCUs, stockpile the devices in question, and turn on upgrades for one LCU at a time while releasing the stockpile(s), until all LCU devices match. Simple enough.

The second situation that I wasn't able to find a clear answer for is if one of the subunits contains a device which none of the other subunits contain.

I'll use an example from my own campaign to demonstrate. I created the Australian 7th Division (#5975) from its various subunits, then split it into the division A/B/C subunits to let it rebuild. Somehow the A subunit has x2 of the 3.7" Mountain Guns while the B and C subunits do not.

Unit A unit screen w/ TOE displayed:

Unit A unit screen w/ unit values displayed:

Unit B unit screen w/ unit values displayed (TOE matches unit A; unit C also matches unit B):

As you can see, the TOE of the subunits does not contain the 3.7" Mountain Gun, yet the TOE of the inactive parent unit DOES include it:

(from WitPAE Editor)

So the question is - how can I remove the 3.7" Mountain Guns from the A subunit or add them to the B and C subunits? Phrased differently, how do you force an LCU to drop device(s) which are not part of its current TOE?

Thanks for any help!

For reference -

LCUs using the 3.7" Mountain Gun (device #1070):

LCUs using the 3.7" Jungle Gun (device #1069):

Device pool (I've already turned stockpile on for both devices):

Post #: 1

RE: Reconciling LCU Device Mismatches - 7/30/2017 7:47:54 PM

BBfanboy

Posts: 18046
Joined: 8/4/2010
From: Winnipeg, MB
Status: offline

I think you can amend the devices in the units (but not the TOE) in the editor to ADD the jungle guns to the Aussie units that do not have them and then they should combine. You must get the slot position of the devices the same in each unit.

You might not even need to wait for some jungle guns to appear in the units that you added to - I think once the device slots are in alignment they should combine. But you might need to run the turn to get the changes to promulgate to the game.

< Message edited by BBfanboy -- 7/30/2017 7:57:10 PM >

_____________________________

No matter how bad a situation is, you can always make it worse. - Chris Hadfield : An Astronaut's Guide To Life On Earth

(in reply to Korvar)

Post #: 2

RE: Reconciling LCU Device Mismatches - 7/30/2017 8:04:29 PM

Korvar

Posts: 813
Joined: 9/3/2014
Status: offline

I looked in the editor for the applicable subunits - but the subunits all have numbers in the 8000 series. The editor stops at 7999 and only contains an entry for the parent unit (under the Locations tab, where all the LCUs are listed).

Maybe I'm not looking in the right place?

(in reply to BBfanboy)

Post #: 3

RE: Reconciling LCU Device Mismatches - 7/30/2017 9:00:56 PM

witpqs

Posts: 26087
Joined: 10/4/2004
From: Argleton
Status: offline

quote:

ORIGINAL: Korvar

I looked in the editor for the applicable subunits - but the subunits all have numbers in the 8000 series. The editor stops at 7999 and only contains an entry for the parent unit (under the Locations tab, where all the LCUs are listed).

Maybe I'm not looking in the right place?

Unfortunately you are looking in the right place. The /A /B /C units are created during the game by dividing the unit during the orders phase, so you won't find them in the editor.

I'm not sure what the best solution is. I suppose you could load the units onto lots of small ships and arrange to lose the one(s) with the target devices. Might be better to just leave them uncombined unless and until nature runs its course (the devices get destroyed in combat).

_____________________________

Intel Monkey: https://sites.google.com/view/staffmonkeys/home

(in reply to Korvar)

Post #: 4

RE: Reconciling LCU Device Mismatches - 7/30/2017 9:25:39 PM

Chris21wen

Posts: 6249
Joined: 1/17/2002
From: Cottesmore, Rutland
Status: offline

quote:

ORIGINAL: Korvar

So the first situation that can happen is that one of the subunits upgrades a particular device before the others. I found the answers to this situation in my forum searches: freeze upgrades for the applicable LCUs, stockpile the devices in question, and turn on upgrades for one LCU at a time while releasing the stockpile(s), until all LCU devices match. Simple enough.

This is the only way I know off. I don't think you can edit the scenario once it's started.

I learnt a long time ago to turn off upgrades to units broken down into sub units for this very reason. It still happens to me even so. In your case just turn off replacements for all units using the mountain gun except for the two 7th Div sub units in question. Once one units gets one turn that one off, then wait until the last gets one to. At this point you should be able to recombine. It shouldn't take very long as you have 4 in the pool, supply willing.

Note that I'd also freeze the jungle gun and turn off upgrades in all three of the 7th DIv sub units thus stopping accidental upgrades.

If it was me I'd turn off upgrades to all units, controlling them manually through freezing/turning on upgrades as needed.

(in reply to Korvar)

Post #: 5

RE: Reconciling LCU Device Mismatches - 7/31/2017 1:11:05 AM

szmike

Posts: 345
Joined: 8/30/2009
Status: offline

That particular division is weird case, as it shows 0 required devices in TOE, yet the device is listed (bug?). And it didn't happen through accidental upgrades, it arrived as 3 brigades of which one had 2x 3.7" Mountain Guns, others none.

(in reply to Chris21wen)

Post #: 6

RE: Reconciling LCU Device Mismatches - 7/31/2017 8:12:00 AM

Chris21wen

Posts: 6249
Joined: 1/17/2002
From: Cottesmore, Rutland
Status: offline

Possibly small bug but I think not.

I did some testing of this problem a long time ago and here's how I believe it works.

The reason a device is not in a TOE is because a TOE for a sub unit is created when the parent is split from whatever makes up the parent TOE at that time, rounding down. If the rounding down creates zero device then the device is omitted from the sub unit's TOE. What sub units get is split equally with any excess going to /A. All this is done on a slot for slot basis. When you recombine units each device slot is checked against the sub unit's TOE equivalent slot any differences prevents recombining into the parent unit. Unit devices that are not in the sub unit's TOE are simply added to the parent unit, again slot for slot.

To complicate the issue you also have to take into account possible TOE upgrades. When the 7th AUS Div enters (all-be-it divided) its TOE is the AIF 41 Inf Div which has no mountain guns. This TOE upgrades in Sept 42 to the Jungle TOE Div which has mountain guns. However this doesn't look important here as the div is clearly still of the AIF 41 Inf. (No mountain guns and it still has M3A1s).

Next complication. The Mountain gun upgrades to Jungle gun in Dec 42. It's now Dec 42.

Now to your problem
So having sat down and looked at it properly my earlier solution won't work.

I noticed that the device usage for /A and /B is the mountain gun while /C usage is the Jungle gun. (Says it already has 3). It's /C TOE that's causing the problem.

You said '... (TOE matches unit A; unit C also matches unit B): ' but the image is for the current composition and not the TOE. I suspect if you look at the /C's TOE you'll find Jungle guns. If so turn off upgrades for all unit with mountain guns. Turn off replacements for /A and /B. Also turn off replacements for any unit that already has Jungle guns and wait. It shouldn't take that long as /A only has 2 x mountain guns and /B zero. You are building 12 Jungle guns per month so I'd say 7 days ish supply willing.

As to why it happened or why /C shows an amount of 3 jungle guns in Current Device Usage yet the device pool says you've used only one??

< Message edited by Chris H -- 7/31/2017 8:13:08 AM >

(in reply to Korvar)

Post #: 7

RE: Reconciling LCU Device Mismatches - 7/31/2017 12:58:13 PM

btd64

Posts: 9973
Joined: 1/23/2010
From: Mass. USA. now in Lancaster, OHIO
Status: offline

Please note that the ** next to the device quantity indicates the jungle gun as the problem. FYI....GP

_____________________________

Intel i7 4.3GHz 10th Gen,16GB Ram,Nvidia GeForce MX330

AKA General Patton

WPO,WITP,WITPAE-Mod Designer/Tester
DWU-Beta Tester
TOAW4-Alpha/Beta Tester

"Do everything you ask of those you command"....Gen. George S. Patton

(in reply to Korvar)

Post #: 8

RE: Reconciling LCU Device Mismatches - 7/31/2017 4:23:05 PM

Korvar

Posts: 813
Joined: 9/3/2014
Status: offline

quote:

ORIGINAL: witpqs

I suppose you could load the units onto lots of small ships and arrange to lose the one(s) with the target devices. Might be better to just leave them uncombined unless and until nature runs its course (the devices get destroyed in combat).

Although it would be a bit of a hassle to get the division out of the jungles of Thailand and back to the coast, that's not a bad idea. I think making them the vanguard of the upcoming assault of Bangkok will also probably do the trick - even though I'd prefer them going in as a complete division.

(in reply to witpqs)

Post #: 9

RE: Reconciling LCU Device Mismatches - 7/31/2017 4:38:59 PM

Korvar

Posts: 813
Joined: 9/3/2014
Status: offline

quote:

ORIGINAL: Chris H

The reason a device is not in a TOE is because a TOE for a sub unit is created when the parent is split from whatever makes up the parent TOE at that time, rounding down. If the rounding down creates zero device then the device is omitted from the sub unit's TOE. What sub units get is split equally with any excess going to /A. All this is done on a slot for slot basis. When you recombine units each device slot is checked against the sub unit's TOE equivalent slot any differences prevents recombining into the parent unit. Unit devices that are not in the sub unit's TOE are simply added to the parent unit, again slot for slot.

After thinking about it for awhile, I believe this is what happened. The division had picked up two of the 3.7" Mountain Guns (possibly from one of the original subunits) before I split it, and since there weren't enough to go around for three subunits, it just assigned them to the /A subunit. It would've been nice for the slot to have been added to the other subunits with 0x devices, or to be able to drop a device to rot in the jungle, but that's just wishful thinking.

quote:

ORIGINAL: Chris H

To complicate the issue you also have to take into account possible TOE upgrades. When the 7th AUS Div enters (all-be-it divided) its TOE is the AIF 41 Inf Div which has no mountain guns. This TOE upgrades in Sept 42 to the Jungle TOE Div which has mountain guns. However this doesn't look important here as the div is clearly still of the AIF 41 Inf. (No mountain guns and it still has M3A1s).

That is correct - here is the 6th Australian, which has not been upgraded yet, as comparison:

What the upgraded TOE will be:

quote:

ORIGINAL: Chris H

I noticed that the device usage for /A and /B is the mountain gun while /C usage is the Jungle gun. (Says it already has 3). It's /C TOE that's causing the problem.

You said '... (TOE matches unit A; unit C also matches unit B): ' but the image is for the current composition and not the TOE. I suspect if you look at the /C's TOE you'll find Jungle guns. If so turn off upgrades for all unit with mountain guns. Turn off replacements for /A and /B. Also turn off replacements for any unit that already has Jungle guns and wait. It shouldn't take that long as /A only has 2 x mountain guns and /B zero. You are building 12 Jungle guns per month so I'd say 7 days ish supply willing.

As to why it happened or why /C shows an amount of 3 jungle guns in Current Device Usage yet the device pool says you've used only one??

I think you got it right before - the /A subunit is the only one that got the 3.7" Mountain Guns (and hence a slot for them) when the division was split.

Here's the TOE for /C:

Plus its unit values:

For good measure, the TOE of /B:

(in reply to Chris21wen)

Post #: 10

RE: Reconciling LCU Device Mismatches - 8/1/2017 4:37:51 PM

Yaab

Posts: 4552
Joined: 11/8/2011
From: Poland
Status: offline

Well, for one, I never ever allow upgrades for split units just to avoid the hassle.

(in reply to Korvar)

Post #: 11

RE: Reconciling LCU Device Mismatches - 8/1/2017 5:27:57 PM

Bullwinkle58

Posts: 11302
Joined: 2/24/2009
Status: offline

quote:

ORIGINAL: Yaab

Well, for one, I never ever allow upgrades for split units just to avoid the hassle.

If you don't you lose immense amounts of time waiting for pool fill.

_____________________________

The Moose

(in reply to Yaab)

Post #: 12

RE: Reconciling LCU Device Mismatches - 8/1/2017 8:05:38 PM

Korvar

Posts: 813
Joined: 9/3/2014
Status: offline

I've learned that lesson - luckily the 6th Australian Div seems to be the only division affected before I could turn off upgrades.

And I think the upcoming meat-grinder in Bangkok will take care of the 6th's organizational problems in short order.

(in reply to Bullwinkle58)

Post #: 13

RE: Reconciling LCU Device Mismatches - 8/1/2017 8:12:43 PM

Bullwinkle58

Posts: 11302
Joined: 2/24/2009
Status: offline

quote:

ORIGINAL: Korvar

I've learned that lesson - luckily the 6th Australian Div seems to be the only division affected before I could turn off upgrades.

And I think the upcoming meat-grinder in Bangkok will take care of the 6th's organizational problems in short order.

The Allies go through a huge squad upgrade on base forces in 1943 I believe. About 12 squads per. You can reuse the same pool over and over if you do it correctly and don't let bigger units steal the pool until the BFs are set. Same with 1/3 size squad pools. You can upgrade a whole division over three turns with 1/3 worth of squads.

_____________________________

The Moose

(in reply to Korvar)

Post #: 14

RE: Reconciling LCU Device Mismatches - 8/2/2017 7:03:27 AM

Chris21wen

Posts: 6249
Joined: 1/17/2002
From: Cottesmore, Rutland
Status: offline

quote:

ORIGINAL: Bullwinkle58

quote:

ORIGINAL: Korvar

I've learned that lesson - luckily the 6th Australian Div seems to be the only division affected before I could turn off upgrades.

And I think the upcoming meat-grinder in Bangkok will take care of the 6th's organizational problems in short order.

The Allies go through a huge squad upgrade on base forces in 1943 I believe. About 12 squads per. You can reuse the same pool over and over if you do it correctly and don't let bigger units steal the pool until the BFs are set. Same with 1/3 size squad pools. You can upgrade a whole division over three turns with 1/3 worth of squads.

Yeh, works for squads and combat eng where they are upgraded and added back to the pool but for other stuff it's 1�x what a unit currently has and they don't, being simple added to the pool. So in the case above for /A above you need 3 in the pool.

(in reply to Bullwinkle58)

Post #: 15

RE: Reconciling LCU Device Mismatches - 8/2/2017 7:06:18 AM

Chris21wen

Posts: 6249
Joined: 1/17/2002
From: Cottesmore, Rutland
Status: offline

I should have added that none of this matters for the Japanese.� If you have enough supply they get upgraded but it's still wise not to upgrade split units unless you have the supply. I think supply needs are based on device size but I stand corrected if not.

< Message edited by Chris H -- 8/2/2017 7:13:01 AM >

(in reply to Chris21wen)

Post #: 16

RE: Reconciling LCU Device Mismatches - 8/2/2017 6:07:33 PM

Bullwinkle58

Posts: 11302
Joined: 2/24/2009
Status: offline

quote:

ORIGINAL: Chris H

Yeh, works for squads and combat eng where they are upgraded and added back to the pool but for other stuff it's 1�x what a unit currently has and they don't, being simple added to the pool. So in the case above for /A above you need 3 in the pool.

Right, but I was responding to Yaab's statement that he never splits. Even if the non-squad devices lag, it's worth it to upgrade to new squads as soon as possible.

_____________________________

The Moose

(in reply to Chris21wen)

Post #: 17

RE: Reconciling LCU Device Mismatches - 8/3/2017 6:11:46 AM

Chris21wen

Posts: 6249
Joined: 1/17/2002
From: Cottesmore, Rutland
Status: offline

quote:

ORIGINAL: Bullwinkle58

quote:

ORIGINAL: Chris H

Yeh, works for squads and combat eng where they are upgraded and added back to the pool but for other stuff it's 1�x what a unit currently has and they don't, being simple added to the pool. So in the case above for /A above you need 3 in the pool.

Right, but I was responding to Yaab's statement that he never splits. Even if the non-squad devices lag, it's worth it to upgrade to new squads as soon as possible.

Me to.

(in reply to Bullwinkle58)

Post #: 18

RE: Reconciling LCU Device Mismatches - 8/3/2017 3:56:13 PM

crsutton

Posts: 9590
Joined: 12/6/2002
From: Maryland
Status: offline

quote:

ORIGINAL: Yaab

Well, for one, I never ever allow upgrades for split units just to avoid the hassle.

I always upgrade infantry squads in brigade sizes. By upgrading a couple or three battalions, then disbanding them, you will then have sufficient numbers in the pools to start upgrading brigades right away. I don't like to wait, especially for the 1942-43 Allied upgrades, (the AT values are critical). The key is you have to go in and manually set stockpiles on for any device that you do not want to upgrade and this involves a little more work. If you are willing to do this then upgrading split division is not an issue and allows you to get the process started much sooner. It is not that hard to pull off.

_____________________________

I am the Holy Roman Emperor and am above grammar.

Sigismund of Luxemburg

(in reply to Yaab)

Post #: 19

RE: Reconciling LCU Device Mismatches - 8/7/2017 2:12:28 AM

Korvar

Posts: 813
Joined: 9/3/2014
Status: offline

Let me check if I'm understanding everyone correctly - the Allied OOB can be upgraded more quickly by upgrading units piecemeal, then disbanding them to return the new devices to the pool. Those same devices are then used to continually upgrade more units (allowing more/larger units to be upgraded as production adds to the pool), while the disbanded units eventually come back as upgraded reinforcements.

And thanks for all the responses!

(in reply to crsutton)

Post #: 20

RE: Reconciling LCU Device Mismatches - 8/7/2017 2:22:10 AM

witpqs

Posts: 26087
Joined: 10/4/2004
From: Argleton
Status: offline

quote:

ORIGINAL: Korvar

Let me check if I'm understanding everyone correctly - the Allied OOB can be upgraded more quickly by upgrading units piecemeal, then disbanding them to return the new devices to the pool. Those same devices are then used to continually upgrade more units (allowing more/larger units to be upgraded as production adds to the pool), while the disbanded units eventually come back as upgraded reinforcements.

And thanks for all the responses!

And this was by design.

_____________________________

Intel Monkey: https://sites.google.com/view/staffmonkeys/home

(in reply to Korvar)

Post #: 21

RE: Reconciling LCU Device Mismatches - 11/26/2021 6:16:02 PM

Yaab

Posts: 4552
Joined: 11/8/2011
From: Poland
Status: offline

Thread resurrection.

I am on 3 January 1942 in my campaign against the Jap AI.

The device in question, 3.7# Mountain Gun (device ID 1070) is not building. The build rate is 6 guns per month starting 12/1941 until 12/1942. My pool is 0, used from pool is also 0. My units use 66 such guns, and need 30 guns to fill their TOEs. By January 1942, I should have at least 4 guns in the pool.

I also found another non-building device: 81mm mortar (ID 935) used by three Philipine units on map.

(in reply to witpqs)

Post #: 22

RE: Reconciling LCU Device Mismatches - 11/26/2021 7:38:15 PM

RangerJoe

Posts: 13450
Joined: 11/16/2015
From: My Mother, although my Father had some small part.
Status: offline

quote:

ORIGINAL: Yaab

Thread resurrection.

I am on 3 January 1942 in my campaign against the Jap AI.

The device in question, 3.7# Mountain Gun (device ID 1070) is not building. The build rate is 6 guns per month starting 12/1941 until 12/1942. My pool is 0, used from pool is also 0. My units use 66 such guns, and need 30 guns to fill their TOEs. By January 1942, I should have at least 4 guns in the pool.

I also found another non-building device: 81mm mortar (ID 935) used by three Philipine units on map.

That sometimes happens, then you may get even more than the build rate. I think of a build rate of 6 for the month as a 6/30 chance of getting open in a day. If Alfred was here, he could probably have the part of the manual quoted or a thread link to refer to.

_____________________________

Seek peace but keep your gun handy.

I'm not a complete idiot, some parts are missing!

�Illegitemus non carborundum est (�Don�t let the bastards grind you down�).�
― Julia Child

(in reply to Yaab)

Post #: 23

RE: Reconciling LCU Device Mismatches - 11/26/2021 8:28:17 PM

HansBolter

Posts: 7704
Joined: 7/6/2006
From: United States
Status: offline

The same variable that will sometimes result in no production on any given day is also built into the aircraft production and transfer model.

_____________________________

Hans

(in reply to RangerJoe)

Post #: 24

RE: Reconciling LCU Device Mismatches - 11/27/2021 3:18:32 AM

Ian R

Posts: 3420
Joined: 8/1/2000
From: Cammeraygal Country
Status: offline

quote:

ORIGINAL: szmike

That particular division is weird case, as it shows 0 required devices in TOE, yet the device is listed (bug?). And it didn't happen through accidental upgrades, it arrived as 3 brigades of which one had 2x 3.7" Mountain Guns, others none.

Where a unit arrives in pieces (brigades, regiments, battalions etc) device mismathces do not prevent combination into a division (or whatever the larger parent unit is). So, the various bits of the 7th division can be combined (once) despite the equipment oddities. Andymac has said that in that situation, the odd bits of equipment are moved to the bottom of the list. So, if of the initial three brigades of the 7th, two have gun X and the other one has gun Y in corresponding data slots, and Y has not yet upgraded to X, they will combine (usual conditions required - in the same hex, same HQ, same move/combat mode etc, and you need all the various other bits of the division), the division can then take replacement gun X's up to TOE, and the gun Y's become supernumeraries until lost/destroyed.

However, when you divide a unit into A/B/C elements, if equipment mismatches develop due to upgrades or in this case, those supernumerary guns being in a data line that is not repeated in the other breakdown units (in this case "wpn-7" in the B element doesn't match and you have 14 lines against 13), it won't recombine until everything is back in place.

The suggestion of loading the A element onto a bunch of small ships is not a bad one, and you may not need to send the ones with the offending mountain guns to assault land at Truk to get rid of them - you could try sending that (those) fragment(s) to Sydney, and checking to see if you can disband them back into the pools.

_____________________________

"I am Alfred"

(in reply to szmike)

Post #: 25

RE: Reconciling LCU Device Mismatches - 11/27/2021 3:27:35 AM

Ian R

Posts: 3420
Joined: 8/1/2000
From: Cammeraygal Country
Status: offline

quote:

ORIGINAL: Chris21wen
...

As to why it happened or why /C shows an amount of 3 jungle guns in Current Device Usage yet the device pool says you've used only one??

Some might have arrived on a convoy which disbanded to the pool. That seems to throw the reported numbers out.

_____________________________

"I am Alfred"

(in reply to Chris21wen)

Post #: 26

RE: Reconciling LCU Device Mismatches - 11/27/2021 3:41:11 AM

Nomad

Posts: 5905
Joined: 9/5/2001
From: West Yellowstone, Montana
Status: offline

Could you click on the unit organization button for one of the 7th div sub units and take a screenshot and post it?

< Message edited by Nomad -- 11/27/2021 3:42:24 AM >

(in reply to Ian R)

Post #: 27

RE: Reconciling LCU Device Mismatches - 11/27/2021 5:43:46 AM

Yaab

Posts: 4552
Joined: 11/8/2011
From: Poland
Status: offline

Well, I was working under an an assumption that a ratio of 6 built devices per 30 days simply means that I get 1 device every 5 days. If that 6/30-chance thing fails for 29 days does that mean the odds somehow switch to a 100% chance and I get 6 devices on the 30 day of a month (last day of production month)?

(in reply to Nomad)

Post #: 28

RE: Reconciling LCU Device Mismatches - 11/27/2021 9:21:43 AM

RangerJoe

Posts: 13450
Joined: 11/16/2015
From: My Mother, although my Father had some small part.
Status: offline

quote:

ORIGINAL: Yaab

Well, I was working under an an assumption that a ratio of 6 built devices per 30 days simply means that I get 1 device every 5 days. If that 6/30-chance thing fails for 29 days does that mean the odds somehow switch to a 100% chance and I get 6 devices on the 30 day of a month (last day of production month)?

No. The only time that you would get more than one per day is when the production rate is 31 per month or more. I have had an aircraft production of 2 per month yet some months I would receive 4 of them.

Any extra devices as described above sometimes may be removed from the unit and put back into storage - at least, if I recall correctly.

_____________________________

Seek peace but keep your gun handy.

I'm not a complete idiot, some parts are missing!

�Illegitemus non carborundum est (�Don�t let the bastards grind you down�).�
― Julia Child

(in reply to Yaab)

Post #: 29

RE: Reconciling LCU Device Mismatches - 11/27/2021 10:47:37 AM

Yaab

Posts: 4552
Joined: 11/8/2011
From: Poland
Status: offline

What about very short production runs lasting i.e. three months? Cany you receive 0 devices in month 1, 0 devices in month 2, and 18 devices in month 3?

(in reply to RangerJoe)

Post #: 30