8.00.00 Huge delay when moving naval units, any workaround?

[Joseignacio]

Thanks, thanks a lot, man. Downloaded.

[Joseignacio]

Although it is not included in the description of the new version:

What's New in v08.02.00.00

Peace
- Removed the request for whether a player wants to liberate a country that has already been liberated. This unfortunately occurred when Italy had already been liberated and the program lost track of that fact.

Supply
- Fixed a problem where the program was not checking for secondary supply sources from all cooperating major powers. This would occur at times when the US was looking for supply for its land units and Commonwealth HQs, which were viable supply sources, were not being found (the search was erroneously terminated early).

it seems the game has stopped lagging by now.

Dont know if the problem has been addressed (dont think so) or with the new install something has resetted and it solves the problem (till next time).

Since it is not in the description, I tend to believe it is the second reason.

[rkr1958]

Although it is not included in the description of the new version:

What's New in v08.02.00.00

Peace
- Removed the request for whether a player wants to liberate a country that has already been liberated. This unfortunately occurred when Italy had already been liberated and the program lost track of that fact.

Supply
- Fixed a problem where the program was not checking for secondary supply sources from all cooperating major powers. This would occur at times when the US was looking for supply for its land units and Commonwealth HQs, which were viable supply sources, were not being found (the search was erroneously terminated early).

it seems the game has stopped lagging by now.

Dont know if the problem has been addressed (dont think so) or with the new install something has resetted and it solves the problem (till next time).

Since it is not in the description, I tend to believe it is the second reason.

Jose, did you try with this latest version the "original" file during RTB that you initially noticed the lag? I (thought) I did & didn't notice any improvement.

[Joseignacio]

I didnt, but I will try right now and report.

Edit:

You are right, with that file the problem persists on 8.2.0 (shouldnt it have been 8.0.2?).

However, in our case, we downgraded to 3.2 following your advice (and our saves were later 3.2), and maybe this solved some problem, that allowed the game to work just fine when we upgraded again from 3.2 to 8.2.0

The only delay I got with all the CW and USA naval units was this transported HQ at the China Sea.

Captura de pantalla 2026-09-24 144414.png (256.43 KiB) Viewed 625 times

Another matter that I think proves not only memory and 32/64 bits is the problem, is that some units get this lag and others no, even at the same seas. I think if it was only a problem of memory and supply trace, it would affect to all those which are in the same location (i.e. sea).

I upload my latest save.

[Joseignacio]

Update: 8.2.0

Lag is back, at least with some air units at sea and many/all HQs, along with (in this case) may Eastern front land units, and TRS carrying HQs

And it seems we got some (maybe many) new bugs.

I break down a Mot Corps into 2 divs... and one disappears before the first impulse.

And I get 1 unit lost in a Blitz attack and the game doesnt let me kill a mot div.

Captura de pantalla 2026-09-27 043135.png (703.28 KiB) Viewed 560 times

[paulderynck]

Update: 8.2.0

Lag is back, at least with some air units at sea and many/all HQs, along with (in this case) may Eastern front land units, and TRS carrying HQs

And it seems we got some (maybe many) new bugs.

I break down a Mot Corps into 2 divs... and one disappears before the first impulse.

And I get 1 unit lost in a Blitz attack and the game doesnt let me kill a mot div.

Captura de pantalla 2026-09-27 043135.png

Where is the motorized division in the picture? I don't see one on either side?

[Orm]

Update: 8.2.0

Lag is back, at least with some air units at sea and many/all HQs, along with (in this case) may Eastern front land units, and TRS carrying HQs

And it seems we got some (maybe many) new bugs.

I break down a Mot Corps into 2 divs... and one disappears before the first impulse.

And I get 1 unit lost in a Blitz attack and the game doesnt let me kill a mot div.

Captura de pantalla 2026-09-27 043135.png

I do not understand the attack picture shown. Looks like there is a US stack with a 6-3 INF attacking a CW PARA Div?!

Is that attack arrow because defensive HQ support?

[Joseignacio]

Update: 8.2.0

Lag is back, at least with some air units at sea and many/all HQs, along with (in this case) may Eastern front land units, and TRS carrying HQs

And it seems we got some (maybe many) new bugs.

I break down a Mot Corps into 2 divs... and one disappears before the first impulse.

And I get 1 unit lost in a Blitz attack and the game doesnt let me kill a mot div.

Captura de pantalla 2026-09-27 043135.png

Where is the motorized division in the picture? I don't see one on either side?

The MOT ART (counts as a Div although in strict meaning it would be a brigade.

[Joseignacio]

Update: 8.2.0

Lag is back, at least with some air units at sea and many/all HQs, along with (in this case) may Eastern front land units, and TRS carrying HQs

And it seems we got some (maybe many) new bugs.

I break down a Mot Corps into 2 divs... and one disappears before the first impulse.

And I get 1 unit lost in a Blitz attack and the game doesnt let me kill a mot div.

Captura de pantalla 2026-09-27 043135.png

I do not understand the attack picture shown. Looks like there is a US stack with a 6-3 INF attacking a CW PARA Div?!

Is that attack arrow because defensive HQ support?

O My, that must be another (probably only visual) bug. Of course, it was all Axis units in the attack. Or I intended so, dunno in detail what the game did ...

After a Check, I think that it was HQ support, yes, that stack had an HQ.

Captura de pantalla 2026-09-29 105456.png (208.96 KiB) Viewed 501 times

And the odds reflect it

[Joseignacio]

I have also experienced a supply bug in Turkey, but I overcame it following your (Betatesters) advice, and exiting and loading again. All Turkis units are now OOS, but most of them weren't earlier.

Captura de pantalla 2026-09-29 105937.png (524.38 KiB) Viewed 496 times

And I will try to post these bugs soon each in its thread. They dont really belong here.

[Orm]

Update: 8.2.0

Lag is back, at least with some air units at sea and many/all HQs, along with (in this case) may Eastern front land units, and TRS carrying HQs

And it seems we got some (maybe many) new bugs.

I break down a Mot Corps into 2 divs... and one disappears before the first impulse.

And I get 1 unit lost in a Blitz attack and the game doesnt let me kill a mot div.

Captura de pantalla 2026-09-27 043135.png

Where is the motorized division in the picture? I don't see one on either side?

The MOT ART (counts as a Div although in strict meaning it would be a brigade.

No. The ART, even if motorised, does not count as an MOT. A MOT is a motorised infantry unit and nothing else. Thus, the ART is not counted as a first loss when the 2f140 blitz table demands it.

[Joseignacio]

Just checked the rules and it seems it is like that.

I need to tell my WIF groups in Madrid, everyone does it the way I was trying to. Most people dont know that "Clarification".

Thanks

"Q11.16-35 11.16.6 Blitz loss can be taken by what? Can it be taken by MOT ENG, ARM ART, etc? Or just the named types (MOT, MECH, ARM, HQA)? Are DIV OK too?

MOT, MECH, ARM, HQ-A corps, armies or divisions. Date 29/11/2007

11.6.6 (chart) : 3d) When using the Blitz table no matter who called the blitz, the attacker’s first loss must be a MOT, MECH, ARM or HQ-A if any of these attacked (even before the winterised unit lost, but after ENG loss)."

[rkr1958]

From https://forums.matrixgames.com/viewtopic.php?p=5295285#top

(1) MWIF game play note ... [thought I'd pass my workaround along for folks also experiencing DUMB-LAG]
(2) I've encountered the "Dreaded Unit Move Bug - Let's All Groan" (DUMB-LAG)!!!
(3) So my workaround is (which I used this impulse movement phase) is to switch to version 3.2 at rail movement and then back to version 8.1.0.1 (debug) at land combat declaration (LCD).
(4) I will note that I did experience DUMB-LAG with 8.1.0.1 with a couple of LCDs and land combat resolutions (LCRs); specifically involving HQs in LCD or LCR advance after combat.
(5) While I didn't time them I estimate these lags were 30 to 60 seconds each.
(6) Also, I estimate I encountered maybe a half dozen or so (6+) of them from LCD to LCR.
(7) While frustrating, it was not a severe as the maddening several dozens of DUMB-LAG that I would have encountered if I stuck with 8.1.0.1 (debug) instead of using 3.2 during land movement (LM).
(8) Please note that 8.1.0.1 (debug) is one version less that the last version 8.1.0.1 (beta) release.
(9) However; 8.1.0.1 (debug) was the last version released to us beta testers and includes debug features not included in 8.1.0.1 (beta) released to the general public.
(10) So, I'm sticking with 8.1.0.1 (debug) except for those phases I need to retrograde to 3.2 to avoid DUMB-LAG from driving me absolutely insane!
(11) FYI - switching between 8.1.0.1 (debug) (or any version 4.0+) & 3.2 scrambles trade agreements.
(12) So I handle that by extracting & saving the trade agreement records in 8.1.0.1 (debug), saving them & then copying them back over in my game file when I switch back from 3.2 to 8.1.0.1 (debug).

999-LM-Version-Conversion.png (49.28 KiB) Viewed 63 times

999-ver8-1-0-1-Debug.png (48.62 KiB) Viewed 63 times

999-ver8-Trade-Agreements.png (28.76 KiB) Viewed 63 times

[Joseignacio]

Happy for you, Ronnie.

Common players only have 8.00.00 or 8.02.00. I guess we can do this as well, cant we?

And we shouldnt need to do this each time, but just at turn's end, I understand. I mean the Trade Agreements thingy.

Thanks for this workaround of the DUMB-LAG