Matrix Games Forums

ORIGINAL: Admiral DadMan

Here's another thing I haven't seen mentioned. BOTH players MUST have the same settings.

The Allied Player MUST have the SAME game settings (on or off) as the Japanese Player in the Realism Options (i.e. PDU, Sub Doctrines, Allied D/C, Reinforcement, etc.) and Game Options section (i.e. Facilities Expanding, Auto Subs, Auto U/G, etc.).

I found it happening a few weeks ago when I started playing 2 different PBeM players. It's abit of a pain in the arse, but re-setting my prefs stopped it cold.

i'll add an obvious (and probably previously mentioned point): Both players have to have the same version of the game (i.e. - expect problem if someone is running 1.8.01 and their opponent is running 1.8.04.).

yep, same settings are a must.
I usually mail my opponent a screeny of all my options.

rtrapasso, I also hit ESC as Japan, but my opponent did not report any out of synch in the first 8 months of war.

Bump!

ORIGINAL: mc3744

yep, same settings are a must.
I usually mail my opponent a screeny of all my options.

rtrapasso, I also hit ESC as Japan, but my opponent did not report any out of synch in the first 8 months of war.

Like many bugs in this game, certain players can be affected while others seem immune... i can only postulate that (a) differences in the computer hardware and (b) differences in Windows (esp. registry stuff) plays a role in this.

I have written a quick and nasty, vb app. it can quickly check both text files ... outputting inconsistencies ... should I put it up on spooky's or is it another wasteful utility? or do people think that FOW is inherent in this ? ... I was going to improve it to look at a/c / combat losses collate and display. What I really want is a utility that eventually, shows production & production changes (more specific than witpdecoder) ... but that is beyond the scope of this easy vb app ... and this thread.

ORIGINAL: n01487477

I have written a quick and nasty, vb app. it can quickly check both text files ... outputting inconsistencies ... should I put it up on spooky's or is it another wasteful utility? or do people think that FOW is inherent in this ?

There's no FOW between the Allied and the Japanese combatreport.txt - they should be identical (same FOW for both sides). So your application would indeed be very helpful in order to find the out-of-synch bug!

... I was going to improve it to look at a/c / combat losses collate and display. What I really want is a utility that eventually, shows production & production changes (more specific than witpdecoder) ... but that is beyond the scope of this easy vb app ... and this thread.

Where is the data for your application coming from? A/C losses in combatreport.txt can be very different from the actual outcome (as displayed in 'air losses' in-game). What is the source for the industry data? Manual input? Save games?

I'd like to hear more about your application. [:)] Maybe you can introduce it in a new thread?

Here is my current standard writeup (some more wrinkles discovered, elucidated):

One thing that can at least reduce the frequency of the problem is to make absolutely sure you both are using the same EXE file ... you can compare byte count ... date time stamp (which will usually be adjusted by time zone) or even use a CRC utility, there are a number of easily downloadable ones.

As Allies (or Axis) - there are a couple of things you can do to try and prevent sync bug... it is related to the amount of memory you have.

SO - run the file from a (preferably cold) boot, ie - don't load anything else before you finish running the turn. Make sure you have any memory hogs in the background turned off (i had some problems with things like screensavers, esp things like SETI@HOME).

Set your virtual memory settings up to maximum.
Control panel -> System -> Advanced (tab) -> Perfomance (click on Settings button) ->
Advanced (tab) -> Virtual Memory (click on the Change button) -> select Custom Size and make the size as large as you can make it

This can SOMETIMES get rid of problems.

You can also ask your IJ opponent to not use the ESC key during replays - some people insist that this can cause (or intensify) the bug.

Actions with PT boats seem to also cause problems, esp. strafing PTs. One game i had would invariably start a replay problem when this happened.

Otherwise use the Pompack Patented Procedure to restore sync:


1. Japanese player, receives Allied turn.

2. Japanese player turns off COMBAT REPORTS

3. Japanese player watches combat, enters orders and sends to Allied Player. (Japanese player does without combat reports and SIGINT for one turn; take good notes during combat)

4 . Allied player watches replay with COMBAT REPORTS ON (AFAIK)

5. Allied player enters orders and sends to Japanese Player

6. Japanese Player receives allied turn, turns ON COMBAT REPORTS

7. Japanese player watches combat, enters orders and sends to Allied Player.

Doesn't WITPDecoder have a feature relating to the sync bug? Or perhaps I remember wrong.

ORIGINAL: Grotius

Doesn't WITPDecoder have a feature relating to the sync bug? Or perhaps I remember wrong.

Don't know - haven't been able to get that to run... [:(]