Report any OOS errors or issues with Multi-Player simultaneous games here.
You CAN play Simultaneous Multi-player as a single player and get a semi-real time turn based game that processes turns a bit faster since the AI is moving when you do. We can also try to debug those as well.
If you are trying to play actual multi-player, the IP connection is the most valid but you're likely to hit some OOS errors. To minimize these,
1) Turn off events in the game options when you set things up - yes this negates flammability but you'll have lots of OOS errors all game if you don't.
2) Make sure Rev is off. This tends to cause some as well.
3) Make sure to try to avoid building any wonders other players are building, even if it lets you, especially if you are on the same team.
4) Avoid automating anything at all, including sending units beyond the reach of their movement for a turn. For some reason, this is a known issue.
Beyond that, when you DO get an OOS error (which sometimes happens in the first round even) you should:
1) report the autosave if you have one from the immediate round before the OOS takes place and you find you can repeatedly hit the same OOS error that round.
2) report the logs you get - you should have logging turned on for all systems through the config ini settings.
and more importantly:
3) save the game AFTER the OOS has taken place, have everyone get out entirely to desktop, all reload and reinitialize the game. If you try to shortcut this to get back on track, you will doom yourself to immediate OOS errors again.
If you're having a LOT of OOS errors, please post here to let me know to look into it. A 2 player game is something I can TRY to evaluate somewhat, and just knowing the era and when things are beginning to OOS a lot can help.
CivilizationIV.ini tends to self-destruct itself once a while.
Remember to back up it, file can be found at C:\Users\<username>\Documents\My Games\Beyond the Sword
You CAN play Simultaneous Multi-player as a single player and get a semi-real time turn based game that processes turns a bit faster since the AI is moving when you do. We can also try to debug those as well.
If you are trying to play actual multi-player, the IP connection is the most valid but you're likely to hit some OOS errors. To minimize these,
1) Turn off events in the game options when you set things up - yes this negates flammability but you'll have lots of OOS errors all game if you don't.
2) Make sure Rev is off. This tends to cause some as well.
3) Make sure to try to avoid building any wonders other players are building, even if it lets you, especially if you are on the same team.
4) Avoid automating anything at all, including sending units beyond the reach of their movement for a turn. For some reason, this is a known issue.
Beyond that, when you DO get an OOS error (which sometimes happens in the first round even) you should:
1) report the autosave if you have one from the immediate round before the OOS takes place and you find you can repeatedly hit the same OOS error that round.
2) report the logs you get - you should have logging turned on for all systems through the config ini settings.
and more importantly:
3) save the game AFTER the OOS has taken place, have everyone get out entirely to desktop, all reload and reinitialize the game. If you try to shortcut this to get back on track, you will doom yourself to immediate OOS errors again.
If you're having a LOT of OOS errors, please post here to let me know to look into it. A 2 player game is something I can TRY to evaluate somewhat, and just knowing the era and when things are beginning to OOS a lot can help.
CivilizationIV.ini tends to self-destruct itself once a while.
Remember to back up it, file can be found at C:\Users\<username>\Documents\My Games\Beyond the Sword
