Corrupt replay

[OzorMox]

If I load the automatically saved replay of the scenario 'The Chase' from the 'A Tale of Two Brothers' campaign, I get the message "The file you have tried to load is corrupt. Continue playing?" when I move forward a turn or click play. The replay appears to run ok despite this message every turn. This is with version 1.4.4. Is this a bug?

[SkeleRanger]

The exact same thing happened to me no matter which version of Wesnoth I used. Does anyone know what's going on?

[OzorMox]

If it helps, I collected the terminal output when running Wesnoth and playing the affected replay. It looks as though quite a lot is going wrong.

Code: Select all

Battle for Wesnoth v1.4.4
Started on Sat Aug 16 02:18:18 2008

Checking video mode: 1600x1127x32...
setting mode to 1600x1127x32
set locale to ''
set locale to ''
loadscreen: filesystem counter = 114
loadscreen: binarywml counter = 32476
loadscreen: setconfig counter = 44
loadscreen: parser counter = 244
loadscreen: filesystem counter = 0
loadscreen: binarywml counter = 16869
loadscreen: setconfig counter = 0
loadscreen: parser counter = 4
scenario: '2_The_Chase'
next_scenario: ''
20080816 02:18:34 error display: could not open image ''
20080816 02:18:48 error replay: SYNC: In attack Horseman (7,47) vs Elvish Scout (7,46): the data source says the hit did 24 damage, while in-game calculations show the hit doing 22 damage (over-riding game calculations with data source results)
20080816 02:19:06 error replay: cannot recruit unit: You must have your leader on a keep to recruit or recall units.
20080816 02:19:09 error replay: unit 'Horseman' is too expensive to recruit: 23/17
20080816 02:19:19 error replay: unfound location for source of movement: 6,23 -> 11,30
20080816 02:19:21 error replay: SYNC: In attack Horseman (12,38) vs Elvish Scout (13,38): the data source says the hit did 18 damage, while in-game calculations show the hit doing 27 damage (over-riding game calculations with data source results)
SYNC: In attack Horseman (12,38) vs Elvish Scout (13,38): the data source says the hit did 18 damage, while in-game calculations show the hit doing 27 damage (over-riding game calculations with data source results)
20080816 02:19:22 error replay: cannot recruit unit: You must have your leader on a keep to recruit or recall units.
20080816 02:19:42 error replay: unfound location for source of movement: 11,30 -> 12,37
20080816 02:19:44 error replay: unfound location for source of attack
20080816 02:19:44 error replay: SYNC: In attack Horseman (13,38) vs Elvish Scout (13,39): the data source says the hit did 24 damage, while in-game calculations show the hit doing 16 damage (over-riding game calculations with data source results)
SYNC: In defend Horseman (13,38) vs Elvish Scout (13,39): the data source the unit perished while in-game calculations show the unit survived (over-riding game calculations with data source results)
20080816 02:19:45 error replay: SYNC: In attack Horseman (13,40) vs Elvish Scout (13,39): the data source says the hit did 22 damage, while in-game calculations show the hit doing 16 damage (over-riding game calculations with data source results)
20080816 02:19:45 error replay: unfound defender for attack: 12,38 -> 12,37
20080816 02:19:45 error replay: unfound defender for attack: 12,36 -> 12,37
20080816 02:19:46 error replay: unfound defender for attack: 11,37 -> 12,37
20080816 02:19:46 error replay: unfound location for source of movement: 9,49 -> 9,45
20080816 02:19:47 error replay: unfound location for source of movement: 9,45 -> 8,39
20080816 02:19:48 error replay: unfound location for source of movement: 8,39 -> 10,34
20080816 02:19:48 error replay: SYNC: In attack Footpad (7,33) vs Elvish Rider (6,32): the data source says the hit did 4 damage, while in-game calculations show the hit doing 6 damage (over-riding game calculations with data source results)
20080816 02:19:48 error replay: SYNC: In attack Horseman (7,32) vs Elvish Rider (6,32): the data source says the hit did 27 damage, while in-game calculations show the hit doing 16 damage (over-riding game calculations with data source results)
20080816 02:19:49 error replay: SYNC: In attack Horseman (6,31) vs Elvish Rider (6,32): the data source says the hit did 27 damage, while in-game calculations show the hit doing 16 damage (over-riding game calculations with data source results)
20080816 02:19:49 error replay: recruitment index is illegal: 2 while this side only has 1 units available for recruitment
20080816 02:19:51 error replay: unfound location for source of movement: 10,34 -> 11,33
20080816 02:19:52 error replay: SYNC: In attack Horseman (9,29) vs Elvish Scout (8,29): the data source says the hit did 22 damage, while in-game calculations show the hit doing 27 damage (over-riding game calculations with data source results)
SYNC: In defend Horseman (9,29) vs Elvish Scout (8,29): the data source the unit perished while in-game calculations show the unit survived (over-riding game calculations with data source results)
20080816 02:19:52 error replay: destination already occupied: 9,29
20080816 02:19:53 error replay: SYNC: In attack Horseman (9,29) vs Elvish Scout (8,29): the data source says the hit did 22 damage, while in-game calculations show the hit doing 27 damage (over-riding game calculations with data source results)
20080816 02:19:53 error replay: unfound location for source of movement: 11,33 -> 11,29
20080816 02:19:53 error replay: unfound location for source of movement: 9,49 -> 7,41
20080816 02:19:54 error replay: unfound location for source of movement: 7,41 -> 11,34
20080816 02:19:55 error replay: unfound location for source of movement: 11,29 -> 11,28
20080816 02:19:56 error replay: unfound location for source of movement: 11,28 -> 11,27
20080816 02:19:56 error replay: unfound location for source of movement: 11,34 -> 9,28
20080816 02:19:56 error replay: unfound location for source of movement: 11,27 -> 12,22
20080816 02:19:57 error replay: unfound location for source of movement: 12,22 -> 10,17
20080816 02:19:57 error replay: unfound location for source of movement: 9,28 -> 11,24
20080816 02:19:58 error replay: unfound location for source of movement: 11,24 -> 11,17
20080816 02:19:59 error replay: unfound location for source of movement: 10,17 -> 10,12
20080816 02:19:59 error replay: SYNC: In attack Horseman (9,6) vs Skeleton (9,5): the data source says the hit did 9 damage, while in-game calculations show the hit doing 7 damage (over-riding game calculations with data source results)
SYNC: In attack Horseman (9,6) vs Skeleton (9,5): the data source says the hit did 9 damage, while in-game calculations show the hit doing 7 damage (over-riding game calculations with data source results)
SYNC: In defend Horseman (9,6) vs Skeleton (9,5): the data source says the hit did 8 damage, while in-game calculations show the hit doing 11 damage (over-riding game calculations with data source results)
20080816 02:20:00 error replay: unfound location for source of movement: 10,12 -> 9,9
20080816 02:20:00 error replay: unfound location for source of movement: 11,17 -> 13,12
20080816 02:20:01 error replay: SYNC: In attack Knight (11,6) vs Skeleton (10,5): the data source says the hit did 6 damage, while in-game calculations show the hit doing 5 damage (over-riding game calculations with data source results)
SYNC: In defend Knight (11,6) vs Skeleton (10,5): the data source says the hit did 4 damage, while in-game calculations show the hit doing 6 damage (over-riding game calculations with data source results)
SYNC: In attack Knight (11,6) vs Skeleton (10,5): the data source says the hit did 6 damage, while in-game calculations show the hit doing 5 damage (over-riding game calculations with data source results)
SYNC: In attack Knight (11,6) vs Skeleton (10,5): the data source says the hit did 6 damage, while in-game calculations show the hit doing 5 damage (over-riding game calculations with data source results)
20080816 02:20:01 error replay: SYNC: In attack Horseman (9,6) vs Dark Adept (10,6): the data source says the hit did 22 damage, while in-game calculations show the hit doing 18 damage (over-riding game calculations with data source results)
20080816 02:20:02 error replay: SYNC: In attack Horseman (9,7) vs Dark Adept (10,6): the data source says the hit did 22 damage, while in-game calculations show the hit doing 14 damage (over-riding game calculations with data source results)
20080816 02:20:02 error replay: unrecognized action:
[choose]
	value = 0
[/choose]
20080816 02:20:20 error engine: player not found!

[Max]

replays from campaign are broken for me as well since at least 1.4.2.
multiplayer replays work fine.

[Iris]

Replays of campaigns starting from their second scenarios are broken since 1.2.x AFAIK. I think I speak for us all that we would appreciate aboard a developer who could understand the old replay code and fix or rewrite it.

[peileppe]

Hi All,

As a hobby I started to put my Wesnoth's replay into comics (if you're interested its on http://peileppe.wordpress.com where 4 pages are related to the Elves besieged mission) - but lately (version 1.4.4) it seems that i can't load other replays

it says the file is corrupted see attachment

and the log reports :

Code: Select all

Battle for Wesnoth v1.4.4
Started on Wed Sep 10 21:16:17 2008

open /dev/sequencer or /dev/snd/seq: No such file or directory
Checking video mode: 1016x715x32...
setting mode to 1016x715x32
set locale to ''
set locale to ''
loadscreen: filesystem counter = 107
loadscreen: binarywml counter = 32476
loadscreen: setconfig counter = 44
loadscreen: parser counter = 244
loadscreen: filesystem counter = 0
loadscreen: binarywml counter = 29689
loadscreen: setconfig counter = 0
loadscreen: parser counter = 4
scenario: '02_Blackwater_Port'
next_scenario: ''
20080910 21:16:41 error engine: player not found!
20080910 21:16:41 error engine: player not found!
20080910 21:16:41 error display: could not open image ''
20080910 21:16:58 error replay: unfound location for source of movement: 28,23 -
> 24,21
20080910 21:17:14 error replay: illegal recall
20080910 21:17:16 error engine: SYNC: In recruit Orcish Archer: has checksum bda
a3>lIRvgIRJM.COpAStqqsFuywVtHyRuNFMAmrE7tVzsxEyFtFnIVPrAAywEPxypqIr+HvMSxVvGDKE6
DRtPQ,CwLuI>sNFvyTGF0uiRDBAzyUuH5Qm,nqnQCwyAq while datasource has checksum DtLK
ywMBy3LZKfrLcxI,5hz1p,,57f9biij44Y.529j>.c6Eh9ohr4cgln82d6-d>+9,d,lfd4o5e1oZoZ1<
2cj--n+3F68bk<wX+,oh9Xnc88acpj<cg4dm4c8h>zTc

For me it's a pain (relatively) because the way I build the comics is :
1. I play the mission
2. I use the replay to get screenshots
3. Then I build the storyline from the mission events, and then add the texts and arrange the page layout

So without the replay ... its a bit more challenging

I wonder if there was a way to manually fix the replay file so he could work again ?
Should I consider the replay (2nd attachment) hopelessly corrupted or should I keep it (because in the future a bug-fix will allow to read it again ?)

Otherwise the game is great, the graphics are getting better and better (thanks to Kitty)
At some stage I wanted to post some of my creation (based on the Jason Lutes model cf. [w]Making_portrait_art_in_vector[/w])

[Anonymissimus]

*bump*

the same thing happens for me, BfW 1.4.2
manually saved replays are also affected
it seems to me that it has something to do with recruiting or recalling...in the replays recruited units are of different types than that one which i actually recruited, for example
and on scenarios without recruiting, like "Into the darkness" in HttT, replays are ok
anyway, sometimes replays are also ok or nearly ok for unknown reasons...

on BfW 1.2.8 it seems that this problems is not yet present...

this is really annoying in scenarios with shroud/fog, and think of campaign authors who want to watch an enemy ai fighting an allied ai in a shroud scenario, wether the fight goes the way they want it to...

[Yogibear]

Err - yes, there is a problem. I am sorry i didn't realize it a lot earlier. I investigated a little and there seems to be two problems:
1. Gold carryover between scenarios doesn't work (that one is easy to fix).
2. Recall list issues. Those are much more difficult to deal with.

I am very short on time at the moment (partly, because i have found new interest in playing mp lately ), but i assure you i haven't forgotten you.

Stay tuned, i will notice you about any changes.