45°38'N-13°47'E
Deity
Well, I guess the time has come for some serious multiplayer testing if someone wants to help. For those who can't play in multiplayer but still want to help in fixing bugs, we'll also soon resume single player testing.
So are there people willing to test the game in multiplayer? I think Sgtslick is already trying it, and so am I with my wife when we have time and baby is sleeping.
I'll update this post later with some necessary info if you want to help with testing and spotting what's causing some OOS. In my current game we're at the start of Renaissance and after250 280 over 600 turns we had 4 or 5 OOS. There will be more, probably, but so far we're enjoying the game. So everyone is welcome to try the game, I'll explain some basic testing rules probably tomorrow here below.
Here are some instruction on what you need to do if you want to test the game for me:
1. Remove any previous revision of RoM or AND
2. Install the latest revision (we'll discuss which one we will use)
3. Clear your cache deleting all files manually (if you have Win Vista/7 it should be under C:\Users\[USERNAME]\AppData\Local\My Games\Beyond the Sword\Cache)
4. Make sure you both have the same BUG options
5. Both players need to change their own civilization.ini like this
Start playing, no matter what options you're using (I use Revolution too, for example, and have no problem whatsoever with it, although it's been blamed a lot in the past as a source of troubles: believe me, it is not). Just to make testing quicker, please only use Blitz gamespeed for testing purposes.
When the game goes OOS please save logs of both players into a zip and upload them here. I mostly need the OOSLog (there's the name of the player) and the RandomLog.
I could upload in the next weeks some testing dll in this thread (in this post), which should help locate OOS or possibly solve some of them. I'll let you know when we can start testing. Thank you in advance to those who will try the game in MP.
Things that are probably needed to make a MP game somewhat safer from OOS point of view:
1. Set the game to single-threading, i.e. inside A_New_Dawn_Globaldefines.xml use
With Afforess latest changes, this should be automatically triggered, although I haven't tried yet.
2. Make sure you have same options in BUG and in Civilization.ini
3. Don't use Archer Bombardment
4. Always use New Random Seed on Reload
5. Don't exchange units via diplomacy screen (but you can gift them moving them into your opponent's territory).
So are there people willing to test the game in multiplayer? I think Sgtslick is already trying it, and so am I with my wife when we have time and baby is sleeping.
I'll update this post later with some necessary info if you want to help with testing and spotting what's causing some OOS. In my current game we're at the start of Renaissance and after
Here are some instruction on what you need to do if you want to test the game for me:
1. Remove any previous revision of RoM or AND
2. Install the latest revision (we'll discuss which one we will use)
3. Clear your cache deleting all files manually (if you have Win Vista/7 it should be under C:\Users\[USERNAME]\AppData\Local\My Games\Beyond the Sword\Cache)
4. Make sure you both have the same BUG options
5. Both players need to change their own civilization.ini like this
Code:
; Enable the logging system
LoggingEnabled = 1
; Enable synchronization logging
SynchLog = 1
; Overwrite old network and message logs
OverwriteLogs = 0
; Enable rand event logging
RandLog = 1
; Enable message logging
MessageLog = 1
Start playing, no matter what options you're using (I use Revolution too, for example, and have no problem whatsoever with it, although it's been blamed a lot in the past as a source of troubles: believe me, it is not). Just to make testing quicker, please only use Blitz gamespeed for testing purposes.
When the game goes OOS please save logs of both players into a zip and upload them here. I mostly need the OOSLog (there's the name of the player) and the RandomLog.
I could upload in the next weeks some testing dll in this thread (in this post), which should help locate OOS or possibly solve some of them. I'll let you know when we can start testing. Thank you in advance to those who will try the game in MP.
Things that are probably needed to make a MP game somewhat safer from OOS point of view:
1. Set the game to single-threading, i.e. inside A_New_Dawn_Globaldefines.xml use
Code:
<DefineName>NUM_CITY_PIPELINE_THREADS</DefineName>
<iDefineIntVal>1</iDefineIntVal>
2. Make sure you have same options in BUG and in Civilization.ini
3. Don't use Archer Bombardment
4. Always use New Random Seed on Reload
5. Don't exchange units via diplomacy screen (but you can gift them moving them into your opponent's territory).