Reinstalling MWiF

[composer99]

I have to reinstall MWif on a new machine, and I'm wondering what version I should install - I know the most recent beta release (4.something something) has some issues - for my part, I've noticed it doesn't let CW use the NEI oil, for instance - so I think I do want an older version.

After installing the 3.00.02 version off the Matrix Games website, can I leave it at that, or ought I also track down and download one of the patches in between that one and the most recent?

[Angeldust2]

I was able to play and finish several games (scenarios) using 3.2.0. I finished at least one game using 4.2.3.2. I am currently playing one scenario using 4.4.1, the latest patch. Doing so, luckily I did not encounter yet a certain combination of weather roll / supply issues, which aborts the game into an infinite loop.
I would suggest to use 4.4.1 despite its known bugs. Most issues like the one you mentioned you could fix by yourself using a simple text editor. Of course, the best solution would be the developer would release a patch very quickly adressing the documented problems of 4.4.1, some of them stretching back even already to last year.

[Joseignacio]

I am playing two games at the moment, one with 4.4.1 and another with 4.2.2 (we had to recede because we had so many problems with 4.4.1 in this game...).

At the moment both have serious problems, the latest one (from today) the game reassigning surprise in a naval combat (and not efficiently).

If I had to start now, I would go with 3.2.0 which several players have said to be reasonable stable. When/if they deing to solve the multiple problems of the latter versions you can always update.

[Joseignacio]

https://www.matrixgames.com/forums/view ... 5#p4941995

[rkr1958]

My go to version right now is 3.2.0 (public beta) vs the latest 4.4.1 (public beta) and 4.3.2.3 (public beta). Here's my 2-cents (pros & cons) on why I like/use 3.2.0 vs the latest.

Pros:
(1) The supply calculation times in 3.2.0 is so much faster in mid to late game versus the 4.4.1 & 4.3.2.3. So if you're looking to play late into a game without pulling your hair out when moving units; especially HQs, then in my opinion 3.2.0 is the way to go. Being able to finish a full game is the number one reason that I'm sticking with 3.2.0 for now.

(2) Doesn't suffer from the regression bugs apparently introduced and not yet fixed in 4.3.2.3 and 4.4.1. For example, (a) 4.3.2.3, naval units forced to stop in sea areas if intercept is possible even if not intercepted or unsuccessfully intercept, (b) 4.4.1, game crashing supply bug for certain weather/zone combinations.


Cons:
(1) Occasionally 3.2.0 doesn't appear to update (i.e., run the supply calculation code) for some units some times. My experience is that that is relatively rare and the fix is to save your game file, close it and then reload it. When you do that apparently the supply calculation code is run for all units. Note that you can really see the time difference in the supply calculation times on load up between 3.2.0 and 4.4.1 or 4.3.2.3.

(2) Doesn't include additional optional rules coded in 4, (a) City based volunteers, (b) Isolated reorganization limits, (c) don't know of any more. By the way, isolated reorg limits as coded apparently has a supply path length limit, versus infinite, that will incorrectly keep units flipped that have a longer path length than coded. And not to throw stones but I will anyway, for the life of me I don't know why it's coded to check and update whether or not units meet the isolated reorg limit requirements during the turn EXCEPT when it's actually relevant which is at the end of the turn during the reorg phase. If it was only checked at this point then this calculation wouldn't slow down the normal supply calculation and could use an "infinite" length to check the status correctly.

[rkr1958]

Don't mean to beat a "dead horse" here but I will anyway. I've attached two versions of the same game (JF45, Factory Destruction Phase).

I challenge folks to load these two files in their respective versions (i.e., 3.2.0 (Debug) & 4.4.1 (Debug)) and time the load up.

On my setup, which is a new PC, it took: (1) ~12-secords to load with version 3.2.0 and (2) ~62-seconds to load with version 4.4.1 (debug).

That's a stark difference and in my experience indicative of the lags in 4.4.1 that made me want to pull my hair out which I don't encounter in 3.2.0.