Bat 2.1 OOS

[Merkill]

when me and my brother upgraded bat 2.0 to 2.1 we get OOS around 1000ad ish and it happens when i attack a unit or city.
we never got out of sync in 2.0

we play direct ip multiplayer

can this be fixed or do we need to rollback to bat2.0 ?

 

[EmperorFool]

Can you please post a saved game just before this happens? For now I would recommend rolling back to 2.0. I'll have to do some serious digging to figure out what's wrong. OOS errors are the hardest to find.

BTW, are either of you using the Stack Attack feature that has all selected units attack in rapid succession? Or do you attack one unit at a time? If you do use SA, does it still happen if you attack with just one unit?

I ask about this because there was a crash to desktop with stack attack on 2.0 that I fixed in 2.1. Of course, if you used SA you probably got crashes regularly with 2.0 so that's probably not it.

 

[Merkill]

We tried both stack attack and without stack attack.
We have already rolled back to 2.0 and it works fine again

I attached 1 save im playing mali if i remember correctly and are attacking to the left of my empire the khmer are to my right.

 

[EmperorFool]

tgvulcan has found that using Unit Naming causes OOS errors. Did you perhaps start using that when you moved to BAT 2.1?

 

[TheOnlyDJCat]

Only want to add, that I just played with BUG4.2 for the first time (upgraded from 4.0) and got 3 OOS errors during the first 50 turns. In one of the three OOS-turns a random event occured before.
We then both deleted the BUG Mod 4.2 folder and renamed the old 4.0 folder to 4.2
Then we could continue the game without any OOS for 6 hours.

I don't know if there were units builds in the OOS turns, but I had deactivated unit naming for the game - don't know about friend, if he did the same.

 

[EmperorFool]

It looks like the OOS errors are caused by using the Random Name code (^rt^?) in Unit Naming, but I haven't verified it. Or rather I should say Ruff hasn't verified it since UN is his baby.