[1.0] Bug - Champions path selection unavailable after autosave

I had a battle where my Champion went to level 2 so I could chose which of the 5 paths he should follow.

After the fight my turn was over (playing with auto-turn) and it was one of those generating an autosave.

When I reloaded the autosave (because I actually wanted to take a look at all the paths, first game) my champion was level 2, but neither had a path selected nor could I choose one for him.

Seems to be some problem with the order of, auto turn end <-> autosave <-> champion path select popping up in another turn and isn't triggered again when loading.

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Publius of NV

Join Date 08/2002

+231

Yes, there are known problems with loading from an autosave, including the one you posted. At least one of those known problems (cities generating income every time an autosave is loaded) is supposed to be fixed in the upcoming 1.1 patch.

In the meantime, try using quick save (control-s) to create a save that doesn't suffer from any of these problems.

Successfully updated karma reason!

Publius of NV

Join Date 08/2002

+231

Here's another thread describing some other issues with loading autosaves.

Successfully updated karma reason!

I don't understand why an autosave should be different from any other save. Isn't it doing the same thing only automatically? I never manual save unless I am quitting the game. Any time I remember to do it I realise the last time I did was two days ago and I might as well start a new game as reload..

Successfully updated karma reason!

Publius of NV

Join Date 08/2002

+231

Quoting Necaradan666,

reply 3

I don't understand why an autosave should be different from any other save.

As far as I know, it has to do with the multi-threading that the game uses, and the point in time that the game kicks off the autosave. It seems to me that the autosave should be done as soon as the turn button is pressed, before the turn counter is incremented, and serialized so that none of the other threads start their turn processing until the autosave is complete. But that doesn't appear to be what happens.

Successfully updated karma reason!