More Mad Excepts

[joshuamnave]

Increasingly, naval combats are interupted by mad excepts that preclude continuing. Rarely does this happen at the start of the first naval combat of the round - it always seems to happen near the end of naval combats for the turn, meaning that the game has to be reloaded at the start of naval searches, invalidating multiple naval combats that have already happened (unless you keep track of every die roll). Save games, even if I were inclined to provide them, wouldn't help because the bug goes away when the combat gets run (sometimes).

If I had the debug tool, I could at least ensure that earlier combats concluded with the same results even though I don't remember the sequence of dice rolls.

[gw15]

Never encountered this in my games.

[joshuamnave]

ORIGINAL: bommerrang

Never encountered this in my games.

Well goody for you. It's still broken for me.

[bo]

ORIGINAL: Zartacla

ORIGINAL: bommerrang

Never encountered this in my games.

Well goody for you. It's still broken for me.

Gee goody for me too, I never encounter those problems either, maybe you need a new computer [;)]

Bo

[Shannon V. OKeets]

I'm working on fixing a problem with naval interceptions (not attempted or failed) of naval moving stacks during the Naval Movement phase. In fact it took me two days of effort to figure what was causing the problem.[:@][:@] That root cause may have an effect on other naval moving stacks. I'll fix all that this morning now that I know what was going wrong [a routine to determine viable moves for a naval moving stack was being executed twice instead of once, which would mess up some internal variables].

I want to get this fix included in a replacement for the public beta 1.4.1.0 ASAP. But speed always has to be balanced versus certainty that new problems aren't being introduced by the changes.[:(][:-]