Omaha Beach - Scen #9

[Mobhack]

Try replaying the turn from a previously saved game point and see if it crashes on you again (or not).

If it does crash again, try attaching a save game from immediately prior to the crash event and then we can have a look at it and see if we can spot the problem.

Otherwise a message saying "it crashes!" is not particularly helpful in and of itself.

(One thing you may want to do is to do a disk check with Windows disk maintenance utilities and see if there are any lost clusters that need recovering, those can lead to a file error (and hence crashes) - and if it is your save game, that could be why...). If there were any lost clusters - then probably best to redo the turn from the last save again in case of that.

[Second-Maître Laurent]

Originally Posted by Mobhack

Try replaying the turn from a previously saved game point and see if it crashes on you again (or not).

Thank you Mobhacl for your help.
I do that yet! No change.
Here you are the attached file of the saved game at the end of my turn, just befor to launch the Germann turn.

[DRG]

Originally Posted by Second-Maître Laurent

Thank you Mobhack for your help.
I do that yet! No change.
Here you are the attached file of the saved game at the end of my turn, just befor to launch the Germann turn.

Running this now and on turn 8. The scenario involves a multitude of exchanges of fire per turn and I will let it run overnight if need be

NO junk on the west edge.......

[DRG]

Originally Posted by Second-Maître Laurent

Here you are the attached file of the saved game at the end of my turn, just befor to launch the Germann turn.

I let that run AI vs AI. When I went to bed it was on turn 21. Got up at 2:30 am and checked it and the game had ended on turn 61




So......... NO Junk........ NO crashing

Andy put his finger on the cause first try after a number of tests were run to elliminate other causes and the fix WAS in the smoke code

We will run some more checks then apply the fix to MBT and run some checks. That will take time to do and then probably issue a replacement EXE but it has not been decided if we will do that now or wait until the next official patch / update

To be determined . We know it fixed the edge junk and stops the crashes but now we need to test to see if there are any unintended consequences..... that can take time because initially we knew what to look for......with the "unintended consequences"........ we don't

That said I did not see anything odd happening with this save game running but I wasn't specically looking for things other than the known issues

Don

[dTerm]

Originally Posted by DRG

[...]
Andy put his finger on the cause first try after a number of tests were run to elliminate other causes and the fix WAS in the smoke code

We will run some more checks then apply the fix to MBT and run some checks. That will take time to do and then probably issue a replacement EXE but it has not been decided if we will do that now or wait until the next official patch / update

To be determined . We know it fixed the edge junk and stops the crashes but now we need to test to see if there are any unintended consequences..... that can take time because initially we knew what to look for......with the "unintended consequences"........ we don't

That said I did not see anything odd happening with this save game running but I wasn't specically looking for things other than the known issues

Don

Have you thought about "field testing" the fixed binary? Some of the crashes the players have encountered, were hard to reproduce on your computer, if I remember correctly.

Chances would also increase some more exotic, but easy to spot, consequences are found, I guess.