Assertion Failed error when loading new turn

[DaveConn]

I am the Spanish player in the Going Again 2 PBEM gain. We played 60+ turns without incident, but recently I have been getting an "assertion failed" error (sorry, I forgot to copy the exact error message, but will if it will help) when loading the new turn generated after the PBEM execution.

To be clear, I am able to combine the turn files from the other players without incident, and do my own turn, and then "end turn", and everything goes smoothly. The error is generated when I (or anyone else, apparently) tries to load the resulting ALL file for the next turn.

This happened a couple of turns ago, and we resolved the problems by everyone redoing their turn and submitting the new files. Everything was fine for one or two turns, but it has just happened. We will try the same solution (redoing the turn); but if anyone has an idea of what is causing the problem is would be very helpful.

Thanks from all of us in the game!

[DaveConn]

Here is the message. I also have the save files (ALL) from both turns if they will help.

[montesaurus]

What would be nice is if the designer could've put in a feature that would have advised what caused the assertion failure!

[DaveConn]

OK, we need some ideas. I have the redone turns from all the players, but the resulting turn (after combining and doing the Spanish turn) still generates the error above. Unless someone has an idea about a solution, I think this brings out game to a screeching halt. Any help appreciated.

[ericbabe]

ORIGINAL: montesaurus
What would be nice is if the designer could've put in a feature that would have advised what caused the assertion failure!

I did! Test!=31 [:)]

[ericbabe]

Would you mind zipping the files and sending them to me at ericbabe@west-civ.com and I can try to see what's going on?

[MorningDew]

ORIGINAL: ericbabe

ORIGINAL: montesaurus
What would be nice is if the designer could've put in a feature that would have advised what caused the assertion failure!

I did! Test!=31 [:)]

[:D] OK. That cracked me up.

Eric, Anything you can do to help us get it working again without going back would be appreciated.

[DaveConn]

Eric, sending right now via email. Thanks!

--Dave

[montesaurus]

quote:

ORIGINAL: ericbabe


quote:

ORIGINAL: montesaurus
What would be nice is if the designer could've put in a feature that would have advised what caused the assertion failure!


I did! Test!=31

Yes, I suppose I should have clarified by adding it would be nice if that feature could provide some useful information! [8|]

[ericbabe]

I looked over the files you sent.  It seems there was a character inserted in the name of one of the units that caused the save file parser only to read half of the unit's name.  The unit in question has the name "Cossack_av_" and probably ought to be "Cossack_Cav_".  I'm not sure whether this character might have been corrupted in-game, during the creation of the save file, or during an attempt to rename the unit.  If it happened during the normal course of play, it must be caused by something very uncommon, as I haven't seen this reported before.

[DaveConn]

I have sent out the turn 68 files, which now load fine for me (and I hope will for everyone else as well).

My public thanks (and kudos) to Eric / Matrix/ WCS for the personalized support on this issue. It is virtually inconceivable to me that any other game company would go to this much trouble for its customers.

Thanks for putting us in a position to continue our game!

--Dave

[montesaurus]

A big round of applause to Eric! To have the game end on an assertion failure would have been a sad thing!!

Thanks again![&o]