[Scummvm-tracker] [ScummVM :: Bugs] #13396: Gameplay duration issue with Myst III saves

[ScummVM :: Bugs]

#13396: Gameplay duration issue with Myst III saves
---------------------+----------------------------
Reporter:  dgasaway  |       Owner:  (none)
    Type:  defect    |      Status:  new
Priority:  normal    |   Component:  Engine: Myst3
 Version:            |  Resolution:
Keywords:            |        Game:  Myst 3: Exile
---------------------+----------------------------
Comment (by macca8):

 Apologies. I did indeed respond to the message (which is still relevant
 regarding its expected use) instead of your specific example.

 I'm able to reproduce this issue with Myst III on macOS, though it seems
 to apply to overwriting any existing Myst III save game, including those
 with significantly shorter playtimes. For example, loading my Autosave
 file (with 17 hrs playtime), then attempting to overwrite an earlier save
 game from a different age (5 hrs playtime), generates this message.
 Clearly this is wrong, and the exact opposite of the message.

 Having said that, the save it produces updates with the correct metadata
 (as you've noted). If, instead of overwriting an existing save, I create a
 new save game, no message appears, and the save is still created with the
 correct metadata.

 This behaviour suggests that, for some reason, the playtime is reset to 0
 when the current state is loaded (thus always earlier than any existing
 save game), but not updated to the correct value until after a save is
 performed. Why, I have no idea?

 However, as you've noted, this only applies to using the ScummVM save
 menu, and not the game's own in-game menu, which offers greater flexibilty
 to the user when managing saves.

 An obvious point of difference between Myst III and most other games is
 that Myst III uses a common name for its save game's filename and
 savename, and indeed when the ScummVM menu is viewed in list mode, the
 savename is listed as the filename complete with extension. Pure
 speculation, but I'm wondering if this is somehow interfering with
 registering the correct playtime when the current state is being loaded?
-- 
Ticket URL: <https://bugs.scummvm.org/ticket/13396#comment:3>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM