https://bugs.winehq.org/show_bug.cgi?id=37965 Bug ID: 37965 Summary: Dead Space 3 sometimes fails to load checkpoints that are not save points Product: Wine Version: 1.7.35 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Dead Space 3 autosaves the game, and there is no manual save option. While checkpoints in the game are frequent, save points only occur every few checkpoints. In theory, this means your character can die at any time without major consequence. However quitting the game and loading it again may involve replaying maybe 10+ minutes depending specifically where the death occurred. Unfortunately, it seems that death in areas where the previous checkpoint was not a save point causes the checkpoint to fail loading properly - resulting in an instant death before the game even draws your character to the screen. This results in a death/respawn loop that only ends when you bring up the in-game main menu and select the option to exit the game, losing progress in the process. It is also noteworthy that the mouse cursor disappears from the game menu until the option to end the current game is selected - presumably another side-effect of the aforementioned bug. Re-loading the most recent save point gets the game running normally again (until the next time it is triggered). There is a video posted of this behaviour here: https://www.youtube.com/watch?v=KDWbnrcx4Gc While this behaviour was not reported in the Dead Space 3 AppDB entries, I suspect this is the sort of thing that can easily go unnoticed without a complete playthrough under Wine (which I just did) - particularly since I don't think I even died during the first half of the game. I first encountered this in Chapter 13, but it could be an issue in other chapters. I vaguely recall seeing it later in the game somewhere. The game was cracked to work around what I suspect is a variant of bug #34517 (only without an alternative work-around here). To rule out the crack being the issue causing this behaviour, I copied the entire game directory and my save game to a real Windows installation, where the bug could not be reproduced. Observed on 1.7.35 with 8e9e4a6 reverted due to it producing a regression (which I'll report separately momentarily). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.