45°38'N-13°47'E
Deity
Hello guys, I've recently tried some multiplayer games with my wife with A New Dawn which, as you know, uses most of the C2C dll; but after a few turns it becomes impossible to play due to OOS almost every turn. I've had a look in your forum and I've seen that the same applies for those brave enough to try a MP game with C2C (not a PBEM game, of course, which requires more patience than bravery
).
Now, I'd really like to try to fix some of those OOS bugs but I'm not sure where to start from. I mean, I have or I can have tons of logs but no experience in OOS bug fixing. Is there any help that any of you can give me on how to debug an OOS error? I guess I can't even tell the source of an OOS error, either dll or python problems.
I'm asking help here because i know that some OOS bugs have been fixed in C2C before, I think maybe AIAndy was the OOS guru, correct? And since AND shares a good part of the dll with C2C, if I'm able to track some OOS bugs in AND, it could help you here too; and it should be easier to track bugs in AND because it has less features than C2C. AND dll is very similar to C2C dll, the only things I've left out completely when importing code in AND were Traits and TB Combat Mod. I hope I can get some help or some advice from you guys.
P.S. I've tried enabling/disabling multithreading and it hasn't done any difference in terms of OOS. I remember some months ago AND was pretty stable in MP, so I think I could repeat the import process from C2C to AND dll starting from the last OOS-free revision of AND to check were problems started. I hope I can get some help and help you at the same time.

Now, I'd really like to try to fix some of those OOS bugs but I'm not sure where to start from. I mean, I have or I can have tons of logs but no experience in OOS bug fixing. Is there any help that any of you can give me on how to debug an OOS error? I guess I can't even tell the source of an OOS error, either dll or python problems.
I'm asking help here because i know that some OOS bugs have been fixed in C2C before, I think maybe AIAndy was the OOS guru, correct? And since AND shares a good part of the dll with C2C, if I'm able to track some OOS bugs in AND, it could help you here too; and it should be easier to track bugs in AND because it has less features than C2C. AND dll is very similar to C2C dll, the only things I've left out completely when importing code in AND were Traits and TB Combat Mod. I hope I can get some help or some advice from you guys.

P.S. I've tried enabling/disabling multithreading and it hasn't done any difference in terms of OOS. I remember some months ago AND was pretty stable in MP, so I think I could repeat the import process from C2C to AND dll starting from the last OOS-free revision of AND to check were problems started. I hope I can get some help and help you at the same time.