So, you're saying when the game autosaves, that's when the CTD happens? And you say when you turn AutoSave "off" that it still does it?
There shouldn't be any default "path" that the game looks for, when it comes to Vista vs XP. It's still the same game, still the same file structure, etc.
At least I would assume so...
CTDs are almost always SDK related. Python won't give CTDs, just blank/funky screens. XML usually pops up when loading. It's the SDK files that will cause a CTD somewhere. Unfortunately, even if I wanted to, I can't do any SDK work until at least mid-May, because I'm away on business, and my desktop has all the DLL compiling software on it.
Say, that gives me an idea... could one of you Vista users compile a new DLL for me? All the source codes are provided with HiTM, and there is a tutorial on how to do it somewhere on here (that's how I learned).
And here's another idea... those of you Vista users who get CTDs, try taking the v3.00 CvGameCore.dll file and replace the v3.02 CvGameCore.dll file with it (overwriting it).
Both of of the DLL's are the exact same, with the only difference being I moved one line of code to the bottom of a list with the game options (Culturally linked starts, I think).
I remember Cross Cowboy saying he had no CTD issues with v3.00, but as soon as I compiled a new DLL, that's when his problems started. So maybe going back to the v3.00 DLL file will work... maybe?
Which problem would that be.... random CTD?
I really, really, really would like to fix this for the Vista users. But I need the Windows XP users to speak up, too! If you use XP, speak up if you have CTD bugs or not.