Opened 7 years ago

Closed 7 years ago

#7156 closed defect (invalid)

SCI: Quest For Glory 4, autosave crash (kCheckFreeSpace)

Reported by: SF/blazingstix Owned by: csnover
Priority: normal Component: Engine: SCI
Version: Keywords:
Cc: Game:


Having a problem with Quest For Glory 4 autosave.

Running ScummVM 1.9.0git2584-g79b0309 (Jul 3 2016 04:58:03) daily build on Win10 x64 (32-bit scummvm build).

Whenever the game tries to auto save, it crashes with: ERROR: parameter 0: 000f:0000 (reference), should be reference parameter 1: not passed, may be any (more may follow) [VM] kCheckFreeSpace[3f]: signature mismatch in method Glory::save (room 720, script 0, localCall 0xffffffff)!

This happens in english CD-ROM and german and english diskette versions. CD-ROM is the from Anthology edition (as is german diskette version), and english diskette is v1.1a from original floppies.

(In diskette versions, error is slightly different... parameter 0 is 000f:003c, and room is 710).

In CD-ROM version this happens when trying to leave the first room, and in diskette version it is when trying to leave the second.

Ticket imported from: bugs/7156.

Change History (3)

comment:1 by m-kiewitz, 7 years ago

Quest for Glory 4 is currently not officially supported, but work in progress.

comment:2 by SF/blazingstix, 7 years ago

I've noticed bug reports filed for other unsupported games (GK1, for example), as well as a lot of recent development activity on SCI32. If it's not appropriate to file bug reports for unsupported (but actively developed) engines then I'll refrain from submitting any further.

comment:3 by csnover, 7 years ago

Owner: set to csnover
Resolution: invalid
Status: newclosed

While SCI32 support is improving daily, for the moment there are just too many things that are known to be broken or incomplete for individual bug reports to be very useful. (For instance, savegame code is already on the TODO list! 🙂) When this changes there will be an announcement, and then it will be great to receive individual reports about any bugs you encounter. Thanks!

Note: See TracTickets for help on using tickets.