Thunderbrd
C2C War Dog
I'll be happy to look into it tomorrow but since I have a lot more faith in your abilities, don't let that stop you from doing what you can either if you've got the time for it. 

I'll be happy to look into it tomorrow but since I have a lot more faith in your abilities, don't let that stop you from doing what you can either if you've got the time for it.![]()
You could check the SVN changes that say in the comment that they fix sync or oos issues but I doubt you will be able to properly apply them without understanding what they actually do.A lot of the earth evolution crew who play on gamespy in big mp games have recently gotten into c2c & ROM AND, they like c2c for SP but think its too long for MP (which I kinda agree with). However, ROM AND seems plagued with OOS issues.
I was wondering, are there any simple OOS fixes that were applied to c2c that can easily be stuck into ROM AND, and by simple I mean something that a total noob can do (like me) lol.
Even if its maybe not that easy, if you could point me in the right direction and I could pass on this wisdom to someone who might have a chance of doing it - that'd be great.
Did it write a PythonErr.log?We did find another OOS error but for whatever reason, my wife's computer was giving her reporting errors and did not record the OOS log. What can I do to try and figure out why her machine gave an error/fail and mine did not?
Then post it please.I just checked... yes!
It seems like BugPath fails to find the folder with your CivilizationIV.ini (you can see the error message in your PythonDbg.log) and I use that as base to find the Logs folder to write the OOSLog in.
It seems like BugPath fails to find the folder with your CivilizationIV.ini (you can see the error message in your PythonDbg.log) and I use that as base to find the Logs folder to write the OOSLog in.
Can you investigate what exactly fails in initRootFolder in BugPath.py?
Mainly check PythonDbg.log to see if it still reports an error that it can't find the root directory. If it was a one time happening that it does not find the root dir, then that is ok but if it happens repeatedly it is something that needs to be fixed.Wouldn't have a clue how to look into that (python stuff). But I can say that she must've done something wrong because her ini settings were all reset when she went to reload. Do you think that somehow the file had been erased and then rebuilt when she reloaded?
Ever since I learned what the ini file was and how to adjust it, I've often found ini file settings switching back to defaults on occasion. Perhaps it was nothing she did so much as something happening on occasion that erases the ini file, perhaps even during a game. If that's the case and it happened to her this time, it wouldn't be surprising we'd show this error at some point.
But apparently this OOS problem is rare as we played for another few hrs last night without issue.
Wouldn't have a clue how to look into that (python stuff). But I can say that she must've done something wrong because ini settings were all reset when she went to reload. Do you think that somehow the file had been erased and then rebuilt when she reloaded?
Mainly check PythonDbg.log to see if it still reports an error that it can't find the root directory. If it was a one time happening that it does not find the root dir, then that is ok but if it happens repeatedly it is something that needs to be fixed.