Constant Assertion Errors + No Autosave = ANNOYANCE

[MistarOblivon]

First off, this game is awesome, and if I didn't think you had total gem here, I wouldn't bother posting this bug.

That said. I have Auto-save turned off, and whenever I crash at the the start of battles (it happens OFTEN) I lose my game, and often quite a bit of work. Is there a way to turn autosave back on?? Its really frustrating!

I have a hex editor, so even an address in the savegame file would be a huge help.

Alternatively, stop the game from CRASHING half the time I enter battles!

Haha. Honestly though, awesome game.

Tata.

 

[armagan]

Hi,

Thanks a lot for your kind remarks. I would be grateful if you can say what exactly the assertion that fails is. (Just the file name and line number would suffice)

That said, you can press ignore on most assertion failures without consequence. Unfortunately you can not turn autosave on once you start the game.

 

[bdw418]

Although the game doesn't CTD during large battles now, I've started getting more and more assertion errors. The most recent one I got referred to line 327.

 

[Sappo]

hmm, only time i've seen those was when ingame... trying to switch from windowed to fullscreen etc... i think its f1 or f2 brings up the display properties window

after any change it crashes and either brings the game down, or reboots meh pc

 

[Jack Van Burace]

Someone on the Something Awful forums pointed out that if you set up the Start Windowed option in the configuration options then just press Alt+Enter to maximize the game, it doesn't crash much if at all. In fact, I've never had it crash since I started playing it this way.