OoS Bug Hunting

lol :lol: fine fine i'll go change my nick :sad:

how does.... "Schrodinger's cat" sound?



well jokes aside, XD
ushram did say that the OOS error popped out just when that gnosling popped out of the gate, and he was the guy who was OOS from the two of us.
we are unsure if that's somehow caused by nate using lolvista and rogue being on windows server (essentially xp) and I on xp.
From what we read from previous OOS threads, the OS might have an (placebo?) effect on the OOS rate.
Nate's gonna go install xp (hopefully soon =P) on his partition and we'll see if it kinda helps...
thanks again for the work ^^

btw Kael-san if you'll add an OOS logger into 0.34 as well I'm sure there's quite a few of us here who would gladly test it out in MP for you as well =D
 
btw Kael-san if you'll add an OOS logger into 0.34 as well I'm sure there's quite a few of us here who would gladly test it out in MP for you as well =D

Yeah, thats probably a pretty good idea but I dont know about including it in a major release. I'd probably put out a one off version to multi-players for testing. We will see how 0.34 goes and what we need to do.

I checked through the FF code and the code that summons Gnosling's has some Feat checks in it. If there is a feat overflow issue like Xienwolf was mentioning it could effect Gnosling summons.
 
Feats were all cleaned up (ideally). So I am guessing for now that isn't the issue. But the Khadi gate code could have a decent shot at containing some bad function calls, like a sorenrand buried inside an ActivePlayer if statement. Ideally not, but I haven't checked it out quite yet.


Really wished that we'd get an OOS log that had a single value out of alignment instead of a couple dozen ;) But oh well. I'll check out the gnosling a bit since it is really the most likely cause (if combat was the issue, then we'd see a lot more problems, far more often). Another question occurs then: Was this your first gate critter?
 
well heres the trick xien, me and them will probly be playing together more. So you will probobly have multiple OOS logs to crossrefernace and narrow it down within the week(The logs within the week, you can take your time narrowing it down... this isnt a very bad OOS, just requires a reload) XD

Edit: Also, considering the feats caused OOSes in 3 player the one time I got to see it, caused 3 different values for all 3 players. I do not belive this is remotely related to them ^.^ Atleast one could hope. Two of us WERE still syncornised.
 
Well, I didn't see anything suspect for OOS in the gnosling code, but I did find that it isn't counting ALL mana types for the Djinn limitation. But that is to the Khad's advantage since more mana means fewer Djinn (if I am reading it properly).
 
That made me laugh more than the actual joke. :)

LOL :lol:

and yes, the OOS happened right after the gnosling spwnd. Did not see anything else that popped that turn. I also remember this happening once before. ( and earlier that game if i remember correctly)
 
Just to be clear, Player 1, as in Not the host (Player 0), but the guy who joined right after him?

EDIT: Nice, you named the OOS logs Player 0, 1 & 7. Clears that question right up. Oddly enough, Player 0 & 7 disagree on the location of one of player 0s workers. Player 7 agrees with Player 1 as to where it should be.

Tons of differences again, but this time even the Map random number sequence is off. But that could possibly be cascaded from a different basic random and such a long time between occurances.
 
Were they playing broken for a while with this? There are a ton of differences with player 1.
 
I saw these differences to player 1 too and I have to admit it wasn't the first OOS in this particular game. I'm pretty sure it was the third one. After the first OOS we could go on some more turns before it went OOS for a second time. The third OOS error came almost immediately after reloading the game. I'm sorry, I should have remembered earlier to collect the ooslogs from the other players, but I was too buisy with a war going on. Next time, I'll post right after the first time an OOS occcurs. I was always assuming a game is in sync again after reloading it completely, by reloading all the relevant data from the hosts save, but maybe I was wrong.

EDIT: Btw, player two was human in the beginning but died because of a huge raging barbarian onslaugt. He rejoined the game as player 7. Just to clear this up. I don't think the OOS has anything to do with this. It happened much later.
 
I'd have to doublecheck, but I think individual unit location cannot cause OOS (hence 1 & 7 had same checksum). Thus you can remain non-synch for quite some time without it hitting your total unitcount (which is in the checksum)
 
hallo everybody,
I am playing frequently with a friend of mine, we always get oos. Its frustrating and we no longer play. Xienwolf advised me to put our oos logs here, which I plan to do as soon as I have access to my pc again - 2 days at max. However, I can already now summarise our game options (in 034 h) that we always use in the 2pl games: no tech trading, no tech brokering, debug, most times agressive AI, simultaneous turns, map settings differ (lately often donut), vict cond: conquest, altar, tower (rest off).
that is basically all that is activated. We always play in a team, mostly lanum & ljosalfar.
(typically, the oos occur +- turn 170-180. we normally get adepts & priests by then and it was my suspicion so far that it is related to either young forest planting, tsunami, the way XP is granted randomly to adepts & priests, or the many upgrades with a % to disappear at end of turn that are available with adepts.
As said, the oos logs will follow in short. Many thx
 
lol. I wonder how many people will get the joke....

Note that by asking the question you've made people consider it more, and thus changed the answer.
 
Ugh... hit one OOS here after weeks of relative peace :cry:

FF 043, patch D.
I'm player 1 as Illians, Ushram was player 2 as the Sheaim.
Not sure if this is caused by the old XP/vista compat issues--i'm on XP, he's on lolVista. :lol:

The OOS logs are attached.

Occurred around turn 200ish, nothing particularly noticable, just started when we had an astrologer event, and then every turn after that even after we reloaded each turn, and even appeared again after we loaded a quite a few turns back.

If you need any other info I'll be lurking around the thread to check it, or you could usually find me (Hei) or ushram (kraken121) on the erebus channel.
 

Attachments

think it was around turn 204 or 206 Hei :mischief:
 
This is the first OOS log, or one from after a few reloads and re-OOSs?

EDIT: Wow, this must be from the first OOS. The only difference is that Nate thinks that Player 9 has an extra Sons of Asena and the random seed is off.

Tired of having to guess if a unit was just built and roughly where it is, so I modified the OOS logger to also output the location, name, and a few other details about each city. So next patch should include a new OOS logger to utilize (basically, if I knew the location of Player 9's cities I would know if he just built the warrior for Nate, or just lost it for Hei.
 
yeah , you are correct xien, that was from the first OOS. No matter how much we reloaded it kept happening for another 10-15 turns before we gave up on the game, was quite enjoying that game too :lol: any clue what is causing the problem?
 
Random seed is off, so something random happened which used the number in a wrong way. You said Sheiam were involved again, so I would suspect their gates, but we checked that last time and all of the calls for a random number did seem to be done properly.

Don't suppose you could load up a save of the game and tell me who the players were (what order they show up for you to select your leader on joining the game)? The 10th listed player should be Doviello, I am curious who is before & after them.
 
Back
Top Bottom