Mad Except

Post bug reports and ask for game support here.

Moderator: Shannon V. OKeets

Post Reply
User avatar
TeaLeaf
Posts: 451
Joined: Wed Nov 05, 2014 3:08 pm

Mad Except

Post by TeaLeaf »

Following the advice given, here is my most recent madexcept (txt-file and PNG-image)
Attachments
MadExcept.zip
(289.02 KiB) Downloaded 10 times
Shannon V. OKeets
Posts: 22165
Joined: Wed May 18, 2005 11:51 pm
Location: Honolulu, Hawaii
Contact:

RE: Mad Except

Post by Shannon V. OKeets »

ORIGINAL: TeaLeaf

Following the advice given, here is my most recent madexcept (txt-file and PNG-image)
From the report I see that you are running version 1.3.3.0. I am pretty certain that I fixed this in more recent versions.

I recommend either downloading the public beta 1.4.3.0 or waiting for the official update 1.4.5.0 [which should be available this week].

---
Changes for version 1.4.1.0:

Naval Operations
 Fixed a fatal error when emptying a sea area of combat naval units for one side (e.g., during
a Return to Base phase).
 Added a check to avoid a possible fatal error moving naval units after some had stopped
in a sea area.
 Enabled loading units from a coastal hex when a naval unit is moved from a higher section
box to a lower section box in a sea area.
 Fixed a problem with initiating naval combat during the naval combat phases when the
US Entry Options for US Refutes Naval War Zones and/or Unrestricted Naval Warfare
have been selected.
 Fixed a problem with multiple digressions returning to the correct place in the sequence of
play after the following series of events: multiple land combats, advance after combat
with multiple units capable of advancing, overrun of multiple naval units, attempted interception
of naval units fails (or is not attempted), naval units move into a friendly port.
Previously the program returned to selecting the next land combat to resolve. Now it correctly
returns to the advance after combat subphase so more units can advance.
 Corrected the code so the restrictions on which convoys can merge are fully enforced. For
example, Netherlands convoys controlled by the Commonwealth can no longer be merged
with United Kingdom convoys. Similarly, disorganized convoys cannot be merged with
organized convoys.
 Fixed a problem where a damaged game might prohibit a convoy to stay at sea even
though it had Sentry status.


---

Changes for version 1.4.0.0:


Naval Operations
 Fixed a problem with intercepting aborting naval units causing a fatal error.
 Fixed a problem with sometimes being able to use air units to initiate naval combat in a
sea area experiencing Storm or Blizzard weather. After the changes, air units are never
permitted to initiate naval combat under those weather conditions.
 Fixed a problem with naval interception combats when all the moving units were either
destroyed or aborted from the combat.
 Fixed a fatal error in Naval Interception Combats following a digression (e.g., naval combat
abort from an earlier naval combat).
 Fixed a problem with units in the Naval Abort Queue remaining at sea after: Vichy is collapsed,
some overrun French units escape, are intercepted, engage in naval combat, are
aborted correctly to a port, and then a second group of overrun French naval units are intercepted,
engage in combat, and are aborted. After that long sequence of events, the second
group of aborted naval units were remaining at sea instead of the Naval Abort Queue
form appearing so the aborted units could continue moving - and completing their rebase
to a another port. With the changes to fix this, processing continues correctly through
multiple groups of overrun naval units being forced to rebase/being intercepted/engaging
in combat/aborting/etc.
Steve

Perfection is an elusive goal.
User avatar
TeaLeaf
Posts: 451
Joined: Wed Nov 05, 2014 3:08 pm

RE: Mad Except

Post by TeaLeaf »

Thanks for the suggestion, but I'm fine for now ;-).
I am just posting these errors for you guys to see if there is something new to fix, or not (if it's already fixed in a public beta or even an upcoming official update).
Barring very obviously similar cases, it may even be possible that I'll post a crash caused by the same MadExcept multiple times, because I can't make a study of each crash, to see if it's caused by the same error or perhaps a different one... But I'll do my best to avoid it, ofc!

The alternative would be not to post/send, thinking the new upcoming patch would probably deal with the error anyway, but I don't think that is the right mindset if MWiF is to come closer to perfection ;-).
Post Reply

Return to “Tech Support”