replay and combat report different

[seille]

Hi,

The subject seem to sound like classic case of FOW, but i have my doubts here.
Let me explain what happened.

I´m in a PBEM of scenario 2 (Beta 1.123.d) as Japan.

During my last turn i had ordered two airfield attacks to Cocos Island.

In my replay in the AM phase a unescorted Nell unit attacked, 5 Nells were damaged destroying 2 planes on the ground.
In my PM phase a Betty unit attacked the same airfield (again unescorted). ONE training mission started and downed a lot of my Betties.
So far so good:
Now my opponent watched the replay on his side !
He got totallly different results which imho are not to explain with FOW.

In his AM phase UNESCORTED NELLS attacked Cocos with two trainingsflights attacking my Nells downing a lot.
In the PM phase ESCORTED BETTIES attacked Cocos without any opposition. Only one OPS loss on my side.
Two different replays. His ingame combat report and air losses show my version with high Betty losses while
the his combatreport.txt file shows his version.

How can this be ? That can never be FOW ! We did our last update in february. No problems so far.
Any ideas what this is and how to fix it ?

edit: corrected beta version used.

[wdolson]

It sounds like the "sync bug" which is most often caused by one player running a different version from the other.

Bill

[seille]

Thanks Bill. We updated in february the last time and i don´t think we run different versions.

[seille]

Here is the whole mess in pictures.

My (The japanese) replay showed what his internal combat report showed.

@Bill
I forgot: Even for the Betas wouldn´t i get a message when i try to load a file that was done with a different game version ?

[Bullwinkle58]

Dumb question maybe, but are the dates of the combat report the same? Did somebody send the wrong movie file?

[seille]

No, the files were the right with the right date.

We now updated to the latest beta and keep looking at that problem.

[Bullwinkle58]

Also possibly dumb comment, but you know there is a specific way and order in which updates have to be done in order to avoid the synch bug?

[seille]

Yes, i know. Already updated numerous times. And i explained my opponent very well.
And last update (before we installed the latest beta today) was in february. Until today we had no serious problems.
Wouldn´t the Sync-Bug had hit us earlier already or is his occurence more random ?

[witpqs]

Once in a great while I see the sync bug in a 1x1 game where we are both running the same version. Very rare now, but it does still happen.

[Bullwinkle58]

ORIGINAL: witpqs

Once in a great while I see the sync bug in a 1x1 game where we are both running the same version. Very rare now, but it does still happen.

Once you eliminate the types of issues I raised this is what's left.

[quertice]

I and my opponent are having same problem, and we have always used same beta patch version of may


our last combat reports are different after about half part, I have pasted down where they become different:

my report:

--------------------------------------------------------------------------------
Morning Air attack on TF, near Torokina at 107,130

Weather in hex: Moderate rain

Raid spotted at 14 NM, estimated altitude 14,000 feet.
Estimated time to target is 3 minutes

Allied aircraft
B-26 Marauder x 6

Allied aircraft losses
B-26 Marauder: 2 damaged
B-26 Marauder: 1 destroyed by flak

Japanese Ships
DD Sazanami
CL Kinu

Aircraft Attacking:
5 x B-26 Marauder bombing from 9000 feet
Naval Attack: 6 x 500 lb SAP Bomb



--------------------------------------------------------------------------------
Afternoon Air attack on TF, near Port Moresby at 98,130

Weather in hex: Partial cloud

Raid detected at 148 NM, estimated altitude 18,000 feet.
Estimated time to target is 52 minutes

Japanese aircraft
G4M1 Betty x 16

Allied aircraft
Kittyhawk IA x 6
P-39D Airacobra x 8

Japanese aircraft losses
G4M1 Betty: 4 destroyed, 1 damaged

No Allied losses

Allied Ships
xAK Willimoto
DD Warramunga
AM Launceton

Aircraft Attacking:
11 x G4M1 Betty bombing from 15000 feet *
Naval Attack: 2 x 250 kg AP Bomb

CAP engaged:
No.76 Sqd RAAF with Kittyhawk IA (2 airborne, 0 on standby, 0 scrambling)
(6 plane(s) diverted to support CAP in hex.)
2 plane(s) intercepting now.
0 plane(s) not yet engaged, 0 being recalled, 4 out of immediate contact.
Group patrol altitude is 10000
Time for all group planes to reach interception is 46 minutes
8th FG/35th FS with P-39D Airacobra (0 airborne, 0 on standby, 0 scrambling)
(8 plane(s) diverted to support CAP in hex.)
0 plane(s) not yet engaged, 4 being recalled, 4 out of immediate contact.
Group patrol altitude is 10000
Time for all group planes to reach interception is 41 minutes

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

his report:

Morning Air attack on TF, near Torokina at 107,130

Weather in hex: Moderate rain

Raid spotted at 14 NM, estimated altitude 14,000 feet.
Estimated time to target is 3 minutes

Allied aircraft
B-26 Marauder x 6

Allied aircraft losses
B-26 Marauder: 2 damaged
B-26 Marauder: 1 destroyed by flak

Japanese Ships
DD Sazanami
CL Kinu

Aircraft Attacking:
5 x B-26 Marauder bombing from 9000 feet
Naval Attack: 6 x 500 lb SAP Bomb



--------------------------------------------------------------------------------
ASW attack near Kirakira at 115,146

Japanese Ships
SS I-1, hits 2

Allied Ships
BB South Dakota
CA Minneapolis
CA Pensacola
CL Achilles
CLAA San Juan
CLAA Juneau
DD Gwin
DD Swanson
DD Gridley
DD O'Brien
DD Welles
DD Barton

SS I-1 is sighted by escort
DD Gridley attacking submerged sub ....
DD O'Brien fails to find sub and abandons search
DD Welles attacking submerged sub ....
SS I-1 eludes DD Welles by hugging bottom
DD Welles loses contact with SS I-1
DD Barton fails to find sub and abandons search
Escort abandons search for sub






in his game, bettys haven't raided port moresby...

[DHRedge]

"Sounds like a distortion of the input output carrier wave" - Matrix

[GreyJoy]

In my very recent allied game (pbem) i just had Ambon garrison holding a shock attack and keeping the base, while when i opened the turn i saw it was conquered.... Happens all the time to me, despite we're always using the same version of the beta

[quertice]

i was convinced that out of sync bugs have been fixed in an early patch

[michaelm75au]

... so was I

[quertice]

ORIGINAL: michaelm

... so was I

out of sync issue came back with beta patch? will it be fixed in next beta patches?

I and my opponent have upgraded pbem to last beta(june), and our reports are become identical, so at the present moment replays are synchronized

[witpqs]

ORIGINAL: qwetry

ORIGINAL: michaelm

... so was I

out of sync issue came back with beta patch? will it be fixed in next beta patches?

I and my opponent have upgraded pbem to last beta(june), and our reports are become identical, so at the present moment replays are synchronized

You are misunderstanding what some of us are saying. We still see the sync bug but very, VERY rarely. I doubt that it came back at all. Remember that 'the' sync bug was actually various bugs that had the same effect, and they (mostly Michael) fixed a bunch of them. Now that the sync bug is so rare, I suspect that there is some very obscure bug still hiding in there. But take heart - it happens very, VERY rarely! [8D]

[quertice]

ORIGINAL: witpqs

ORIGINAL: qwetry

ORIGINAL: michaelm

... so was I

out of sync issue came back with beta patch? will it be fixed in next beta patches?

I and my opponent have upgraded pbem to last beta(june), and our reports are become identical, so at the present moment replays are synchronized

You are misunderstanding what some of us are saying. We still see the sync bug but very, VERY rarely. I doubt that it came back at all. Remember that 'the' sync bug was actually various bugs that had the same effect, and they (mostly Michael) fixed a bunch of them. Now that the sync bug is so rare, I suspect that there is some very obscure bug still hiding in there. But take heart - it happens very, VERY rarely! [8D]

so, it happens rarely, and by the way if it happens, it isn't a serious problem because out of sync will disappear in next turns without need to do anythings?


i was worried about it because I seem to remember that in old witp if it was appeared, then the pbem game was lost, that pbem will always have out of sync [&:]
unrecoverable(but was it really so? I don't remember) out of sync in old witp is just a vague memory in my mind, but it was enough to make me worried about my current grand campaign pbem [:)]

[witpqs]

ORIGINAL: qwetry

ORIGINAL: witpqs

ORIGINAL: qwetry





out of sync issue came back with beta patch? will it be fixed in next beta patches?

I and my opponent have upgraded pbem to last beta(june), and our reports are become identical, so at the present moment replays are synchronized

You are misunderstanding what some of us are saying. We still see the sync bug but very, VERY rarely. I doubt that it came back at all. Remember that 'the' sync bug was actually various bugs that had the same effect, and they (mostly Michael) fixed a bunch of them. Now that the sync bug is so rare, I suspect that there is some very obscure bug still hiding in there. But take heart - it happens very, VERY rarely! [8D]

so, it happens rarely, and by the way if it happens, it isn't a serious problem because out of sync will disappear in next turns without need to do anythings?

Yes, this is my experience so far.

i was worried about it because I seem to remember that in old witp if it was appeared, then the pbem game was lost, that pbem will always have out of sync [&:]
unrecoverable(but was it really so? I don't remember) out of sync in old witp is just a vague memory in my mind, but it was enough to make me worried about my current grand campaign pbem [:)]