More corrupted save games in jHexen

edited 2011 Dec 16 in Technical Support
I'm getting a "Corrupt Save game" message in jHexen with the . I'm trying to get from the "Caves of Circe" to "Shadow Wood". I can move through either of the other portals in the Caves (one goes to "Wasteland", the other goes to "Darkmere"), but the game crashes when trying to enter a portal from any of these places to Shadow Wood.

The full crash message is as follows:

"Load ACS scripts
Precaching took 0.90 seconds. [This timer is variable between the crashes I've gotten]
Map 7 (13): SHADOW WOOD
Con-Busy: Was busy for 4.23 seconds. [Also variable]

Corrupt save game: Segment [107] failed alignment check"

I can't find the .hxs files in the usual place for Vista/7 users.

I tried posting the doomsday.out readout in a codewrap, but it exceeds the text limit by about 50000 characters, so I've attached it as a .zip.

Comments

  • IIRC, this 1.9 beta bug (essentially, saving a game while an ACS script was running) was fixed in a branch of the code that has yet to, but will be, merged, into the main code for 1.9.7 before release.

    As such it's been fixed, but the fixed code has yet to make it's way into the unstable builds.
  • Fine, but how do I restore my game? Is the game trying to autosave while moving through portals? Is that what's causing the crash?
  • edited 2011 Dec 14
    Upon checking, I may be mistaken that it's been fixed; none of the several bug reports (it's been posted several times with different wording, some of which appear to date back 2+ years) about the issue over at Sourceforge indicate it has.

    http://sourceforge.net/tracker/index.ph ... tid=542099

    I get the impression that the plan mentioned in this report by DaniJ about the save game code being rewritten for beta 7, won't make it in to 1.9.7. (what is now 'beta 7'). Maybe Deng team can be politely asked to look into fixing the old save game code for 1.9.7. As this is arguably a major issue.
  • I'll complain about it right now. I wasn't bumping anything. I was starting a new thread in the main tech support sub-board when the thread in the jHexen sub-board failed to receive any support.
  • Whoops my apologies. I was miscounting somewhere. With Predcon's permission, I would like to suggest deleting his post above and this one?
  • I'll check out the issue described in bug report 2862377. It certainly sounds reproducible enough to warrant immediate fixing.

    And yes, we won't be revising the savegame system for 1.9.7 (see roadmap).

    EDIT: After some investigation, I discovered a bug in the Hexen savegame loader and fixed it for tomorrow's build. The good news is that it seems the saved data is in reality not corrupted, but the loader was misreading it, making it believe that the data that came after moving floors was invalid.

    It should not have taken this long to fix this bug... But given the extremely messy state of the savegame code, it's not surprising.
  • But the savegame was already loaded. It was just an issue with traveling to one particular area (via portal). And I don't think there are any moving floors in it, unless you count the cavern with the elevating/collapsing floors and ceilings, but those stop moving after a while, and there's a switch inside that cavern to reset them to their original position (after which they never move again).
  • HeXen saves the state of a map in the same hub (each area in a hub is a completely isolated map) as a form of save game, when you leave and reloads it when you return.

    This is why nothing happens on other maps in a hub while you aren't there, as they don't exist while you aren't there.
  • The new build certainly fixed the issue, for now.
Sign In or Register to comment.