save issue with the 2 'Week in ....' scenarions

[DanielPaulis]

love the concept of the 2 'week in .... ' scenarios by the way. running into an issue were the engine aborts after saving or sometimes next turn (auto save ON). if you go back in you'll get the attached error and the game seems to continue, but now running both sides as Manual. to get back to a previous turn I have renamed the .btl and then rename the ...OLDER.btl to the current name. Sometimes this works and sometimes it's stuck on the same turn and won't. I've had the error in both scenarios and on 1.00 and latest version 1.11. Installed on a laptop with more RAM (also slowness issue) and same error. Installed on default locations on both.

Hopefully i'm posting to the right location, any ideas?

[berto]

We believe that the soon to be released 1.20 Update will fix issues like this.

Definitely do not use the initial game release, 1.00, as that is known to have a number of faults.

Sorry for the trouble.

[berto]

Thank you so much for following the procedure suggested here:

How to post a bug report

It is a "pleasure" to receive everything we might hope for to analyze/debug your situation.

Indeed, your latest save file is corrupted, showing all the signs of issues that these 1.20 Update (to be released soon) revisions were designed to fix:

• Increased size of some game engine memory buffers to mitigate the possibility of CSEE-related memory overruns.
• Lua Constants – whether set in init.lua, user.lua, or in the scenario.lua file – will no longer be saved in the game file. This will bypass the possibility of saving problematically long Lua constant values, which might overrun some internal program buffers leading to crashes and/or corrupted save game files.

Alas, it is highly uncertain whether resuming your save game (OLDER or OLDEST) with v1.20 will recover the situation. You are welcome to try, but no guarantees.

It is usually best to start and play to the finish any scenario with the same game engine. No changing horses in mid stream. But in your case, of course you can't. You either get lucky and can continue playing with v1.20, else you would need to start over.

Again, sorry.

[DanielPaulis]

ok, thanks for looking into this. just wanted to post something before someone else got stuck playing one of these scenarios, like at turn 419!
definitely a memory issue as it seems to be working on machine with 12G ram

[berto]

In these monster scenarios, a late-scenario, show stopper bug: a player's nightmare, ours too.

It is one of the reasons why Jason is carefully playtesting both of the Week In monsters (Mekong, Binh Long) in his weekly livestreams, also his AAR here at the Forum. To spot bugs and other issues.

Thanks for the bug report, and your cooperation and understanding.