Quick Load and/or Rest Crash
rectifier
Member Posts: 15
in Not An Issue
After beating the game with a party I've been playing the game solo as a Fighter/Thief and I've been using quick saving and quick loading to make trap setting quicker and less of a hassle.
Basically I quicksave before setting a trap and re-load until successful. When I am, I quicksave again and attempt resting, and re-load until the rest isn't interrupted; and this process is repeated. I pretty much do this to make certain encounters manageable, rather than for pure cheese.
In any case, it appears that when I do this too quickly I crash the game. Problem is, I can't alt-tab to view the crash information, so I can't actually tell if the crash is occurring because of a quickload, resting, or both.
Here's a dropbox link to the four crash dumps that I have so far:
https://www.dropbox.com/sh/29u8y1ml5tdacip/hbSu7MFJAa
I believe one or two the dumps are actually from the final encounter crash, so the two later dumps are probably the most useful to look at.
In summation, quickloading/resting is expected to load or rest, and a crash from doing either of these two actions (or perhaps both) too quickly is the unexpected behavior.
Basically I quicksave before setting a trap and re-load until successful. When I am, I quicksave again and attempt resting, and re-load until the rest isn't interrupted; and this process is repeated. I pretty much do this to make certain encounters manageable, rather than for pure cheese.
In any case, it appears that when I do this too quickly I crash the game. Problem is, I can't alt-tab to view the crash information, so I can't actually tell if the crash is occurring because of a quickload, resting, or both.
Here's a dropbox link to the four crash dumps that I have so far:
https://www.dropbox.com/sh/29u8y1ml5tdacip/hbSu7MFJAa
I believe one or two the dumps are actually from the final encounter crash, so the two later dumps are probably the most useful to look at.
In summation, quickloading/resting is expected to load or rest, and a crash from doing either of these two actions (or perhaps both) too quickly is the unexpected behavior.
0
Comments