No; the larger debug version of the DLL is not there. I think I must have the stable version. I'll try that patch once somebody answers my question about that.
Also, here's a pertinent question: Might any alterations I've made to the XML have caused any problems? I make a lot of alterations...
Double-posting with a question: Which download do you mean? I've looked all over the Ashes of Erebus download and not found anything related to debug. Did you perhaps mean some core Civilization IV folder?
So, while I wait to be helped hands-on, I figure I should ask of people who might know, if I want to do some troubleshooting myself, is there any sort of thing I can look for in the Python Error logs to determine what exactly went wrong?
Hey Imperator; did you see the files I posted on the "Final Fixes" thread? They include a Python error, which I don't understand but you might. Note that I shared a crashing Lanun game, which worked for many turns. I also have a Doviello game that crashes very early on, if you'd like to see...
So, sorry to delay this stuff months, but I configured my game to track errors, and hopefully now it will be easier. I've attached an Autosave and Python Error log; presumably associated with my crash.
Well okay, but then, what file do I edit? I remember reading a few pages back that in order to help diagnose errors, the game should be configured to auto-save every turn, and display python errors. Where is that configured?
So, sorry to have gone silent in the realm of troubleshooting, and really sorry if this is answered elsewhere, but how (with what program) do I open and edit ini.bak files? I want to try configuring it to track down the Python errors, if any.