Save games not loading (stable and development)

[The1exile]

I was first using 1.7.4 to play through delfadors memoirs and when delf finally died on what I think was the third scenario, I was unable to reload. Fair enough, this is a beta - and the same thing happened with NR too. Since I was quite interested in NR, playing it for the first time, and there was a new stable version out, I downloaded that, and I still can't load the saves -.-

My operating system is windows vista 64-bit home premium, the version of wesnoth the attached save come from is an autosave from NR on version 1.6.5

[silene]

Your savefile works fine here. Could you describe a bit more what you mean by "unable to reload"? Was there an error message or something?

[The1exile]

The loading bar proceeds about halfway along, and then flickers and stops roughly in the middle. No further progress takes place, and if you click on wesnoth it greys out and presents me with a "wesnoth.exe has stopped responding" message.

Edit: A picture is worth a thousand words:

[loonycyborg]

There are some other people who get freezes during 'Initializing teams' stage.
It appears that disabling compressed saves helps with the issue.

[The1exile]

Great, I'll try that. Will I have to start the campaign over again?

[loonycyborg]

Perhaps uncompressing the savegame's file will work too. They're gzipped text files. Everything that can uncompress gzip can uncompress them.

[The1exile]

I've disabled the compressing of save games but the problem persists.

[AI]

Disabling compression means *new* saves won't be compressed, old ones won't be affected.

[The1exile]

Yes. I started a new campaign (UtbS) and those saves don't load either. I double checked before starting and the saves are set to be uncompressed.

[Max]

this message has been introduced by vista as a subtle way to force programmers to make their GUIs non blocking (by moving non ui code to separate threads so the message queues can be processed in time). failing to do so not only causes the window to not be redrawn but also in not being able to return to the desktop if you're running the game in full screen mode (although one could argue that this is rather a limitation of windows).

unless some takes the time to post a detailed error log as described here we won't find out what's going wrong...

[The1exile]

I would love to help with the stderr text but I don't know how to go about running the game with --log-info=all switch.

[Max]

you can either modify the link in the start menu (i've got no idea how this looks like in vista) so that the target looks like this:

Code: Select all

"C:\Program Files\Wesnoth 1.6.4\wesnoth.exe" --log-debug=all

or you could launch wesnoth via command line passing this parameter.

[The1exile]

Apart from a few minor changes (1.6.5 and it's "Battle for Wesnoth"), bingo!

It should be viewable at http://www.pastebucket.com/view.php?id=78

Do I need to do the same drill for testing?

[Max]

unfortunately the log only covers the first 2 seconds. if there's a certain limit in pastebucket post the end of the logfile rather than the beginning. or try to zip the logfile and attach it here...

[Soliton]

Alternatively stop telling people to run --log-debug=all...