I've confirmed (now that my game seems to crash at least once an hour) that the Autosave issues that have been reported by a lot of people throughout all of time still have not been fixed.  The autosave issues listed as fixed I have not run into, but the following have not been:

1. Monsters that previously attacked you between your turns instead do not attack.

2. Loading an autosave puts you at the beginning of the next turn instead of the end of the turn that it should put you in.

3. If a city would have finished building/training something that turn, it is instead canceled. 

I know you guys are working on the end-of-turn crashing issues, but even if you resolve all of them, there may be situations where I want to reload an autosave, and I'd like my game not be all screwed up because of it.

Reproducing any of the above is really simple.  You don't need me to tell you the steps.  They reproduce very reliably (except 2, but it should only take 2-3 attempts to see that one).  Was something about to finish production?  Did a monster attack you?  There's your test scenarios.

The fix is also relatively simple (although probably a lot more complicated to implement considering how you guys have things going simultaneously between turns):

When a player clicks End Turn or hits Enter, perform the autosave before anything else.  Don't have other things happening while the autosave is running.  Do it before it even registers the end of the turn, so that when you load an autosave, you'll definitely be at the end of the turn in which the autosave was performed, and nothing will have happened yet.