Synch Bugs

[Bullwinkle58]

In my second PBEM, Scen 1 stock, we are experiencing massive synch bugs in April 1942. Multiple theaters, air, naval, and ground all three. They have been present on at least three of the last four turns.

We are in the same version of the betas. No hardware changes I'm aware of.

Is there anything I don't know or can't recall that can be tried? We're doing the CR-with-the-turn thing, but it's cumbersome, and it reveals Japan FOW to me, the AFB.

I don't think there's anything but to wait, but if anyone has any ideas I'm all ears.

[btd64]

Moose, Have him send you a picture of the main load screen just to make sure that you both have the same Version number and date....GP

[Yakface]

My preference, when confronted by a persistent sync bug, is for both players to reinstall and patch to appropriate version.

Combat reports for both sides are identical so you will not be getting any extra information. Ops reports on the otherhand are unique to each side. You can still get your own ops and sigint (by running the replay). It won't be the same as if there was no sync bug, but will be of equivalent value.

[Bullwinkle58]

ORIGINAL: Yakface

My preference, when confronted by a persistent sync bug, is for both players to reinstall and patch to appropriate version.

Combat reports for both sides are identical so you will not be getting any extra information. Ops reports on the otherhand are unique to each side. You can still get your own ops and sigint (by running the replay). It won't be the same as if there was no sync bug, but will be of equivalent value.

I thought that land attack casualties had FOW in each CR. Maybe not.

Reinstall may be the way to go.

[Bullwinkle58]

Ever get a head-slap moment just as you hit "Send"?

I think I realize what's happening, and yep, moose can be stupid.

This thread can die.

[witpqs]

Moose, the only advice I can give beyond what is written above is about detecting a sync bug and expands on what yakface alluded to. I also wrote this in earlier threads about sync bugs so search for that in case I stated it better there.

When the Allies player runs the replay the various reports are generated. They are based on the replay.

A change Michael made loong ago is that the turn file has stored within it the combat report as generated by the Japan player during turn/combat resolution. As soon as the Allies player opens the turn, that combat report over-writes the combat report which the Allies player generated by running the reply.

It would be nice if they had different names so one would not over-write the other, but they don't. You can do that yourself easily enough. After you run the replay (but before you open the turn!) simply rename the combat report. My own preference is to append "-replay" to the name. Then, when you open the turn you will have both versions of the report for comparison. No need to scroll through them, just look at the size. If they are different sizes you had a sync bug. If they are the same size chances are great there was no sync bug.

If you want to be more certain, right-click and open "Properties" to see the exact byte count of each file. The combat reports are pretty long, so there is only a 1 in thousands chance of them having the same size AND there being a sync bug. If really in doubt use some tool or text editor to compare the files for you.



Edit to add: Notice how some reports in the above screen pic have different dates? That is because I opened a turn to look at something. It looks like ALL the reports except CombatEvents.txt are stored within the turn and over-written.

[Bullwinkle58]

ORIGINAL: witpqs

Moose, the only advice I can give beyond what is written above is about detecting a sync bug and expands on what yakface alluded to. I also wrote this in earlier threads about sync bugs so search for that in case I stated it better there.

When the Allies player runs the replay the various reports are generated. They are based on the replay.

A change Michael made loong ago is that the turn file has stored within it the combat report as generated by the Japan player during turn/combat resolution. As soon as the Allies player opens the turn, that combat report over-writes the combat report which the Allies player generated by running the reply.

It would be nice if they had different names so one would not over-write the other, but they don't. You can do that yourself easily enough. After you run the replay (but before you open the turn!) simply rename the combat report. My own preference is to append "-replay" to the name. Then, when you open the turn you will have both versions of the report for comparison. No need to scroll through them, just look at the size. If they are different sizes you had a sync bug. If they are the same size chances are great there was no sync bug.

If you want to be more certain, right-click and open "Properties" to see the exact byte count of each file. The combat reports are pretty long, so there is only a 1 in thousands chance of them having the same size AND there being a sync bug. If really in doubt use some tool or text editor to compare the files for you.



Edit to add: Notice how some reports in the above screen pic have different dates? That is because I opened a turn to look at something. It looks like ALL the reports except CombatEvents.txt are stored within the turn and over-written.

This is good gouge; thanks. I don't like getting the Japan player's CR in the turn email as I can never stop myself from peeking on my phone.

I know in this case we have bad bugs as he's "taken" Suva twice now on succeeding turns, and I still hold it. The VP column in Tracker is a dead giveaway even before I open the orders file.

What might have happened: I reused the install from my Lokasenna game. It's stock, and pristine. I just cleaned out the saves, text files, and Archive debris, upgraded it to the last beta and started the new stock game. I completely forgot that four years ago we both inserted the small "Andy Mac" stand-alone file that applied just the DBB changes to Super-Es and DP guns. Still not sure that could hose the version match since no Super-Es exist yet, and I don't think DP guns either. Loka asked if I had ever been asked in the Version box to overwrite the database Y/N and I have not been. So that might not be it. But this wave of bugs is as bad as I've ever seen. ASW sinkings that weren't, air missions flown in Burma that didn't fly (and that showed huge Allied losses on the phantom missions), and the Suva invasion that is just complete fantasy for several days now.