Dsync

[macpharlan]

Got this game with my friends, all using the latest client, no mods and we are dsyncing every game.

Followed all the steps I have seen on this forum, no luck. Here are my game files

[PhilipJFry]

what steps did you take?

desync means that the game simulation between you and whoever you are not synced with is different

this is usually caused by different game files (base game/faf patch/mod/map files)
so first thing is to make sure that you as well as all the other people you play with use the same files

you can validate (and thus fix) the base game files via steam (assuming you used steam to install fa)
you can wipe the faf patch files by deleting everything in C:\ProgramData\FAForever\bin and C:\ProgramData\FAForever\gamedata\
you can delete sim mods/maps and then download them anew from the mod vault

[macpharlan]

Thanks for the reply.

These steps:
1) Validated steams files
2) deleted c:\programData\Faforever
Still same issue

1) Uninstalled both Supreme Commander and Supreme Commander Forged alliance
2) Uninstalled FAF forever
3) Deleted c:\programData\Faforever
4) Reinstalled 0.9.3 beta FAFforever

Same issue.

Interestingly we can play SC Forever main game don't have an issue. Also, can play FAFever Co-op with no issue.

[PhilipJFry]

then the issue is with the faf patch files

do you always have that issue or does it only occur with specific people?
if it only happens with specific people then tell them to wipe the faf patch files and redownload them by hosting/joining a faf game lobby

[Uveso]

Code: Select all

warning: Checksum for beat 300 mismatched: 98401aa9baaac217f66b8b322f487042 (sim) != 6c8e5b631548b8384bb88d2c1085fa4c (thane101).
warning: Checksum for beat 300 mismatched: 98401aa9baaac217f66b8b322f487042 (sim) != 6c8e5b631548b8384bb88d2c1085fa4c (Cryptik).


The log does not show what the desync caused.
But thane101 and Cryptik had the same game checksum,
so the desync was caused by macpharlan's game.

[macpharlan]

then the issue is with the faf patch files

do you always have that issue or does it only occur with specific people?
if it only happens with specific people then tell them to wipe the faf patch files and redownload them by hosting/joining a faf game lobby

Where are the patch files? Shall I remove the entire C:\ProgramData\FAForever


Thanks for the help folks.

[PhilipJFry]

faf stores its patch files in C:ProgramData\FAForever\bin and C:\ProgramData\FAForever\gamedata (the .nx2 files are the ones from the regular faf patch)

i recommend wiping those two folders - you will have to download all faf related game files again which includes the ~1 GB of files required to play coop

[macpharlan]

ok, I did a clean install of FAForever client, deleted the C:\ProgramData\FAForever directory and some cache files that held my preferences.

I'll test jumping into a game when I get a chance, I did notice I am having issues in the vault, just sits there 'loading maps', not sure if that is a symptom of my issue or not. I used to be able to browse around with no issues.

log attached.


Update: I was able to do a match with me and a friend, went about 15 minutes no dsync as a test. Will try with my other friend thane and see if I get same results, this was the first game without him in it.

Note: Map loading issue in FAF is fixed if I hit 'back' on that screen, refresh sits and spins for a long time

Update2: Looks like all may be well, did a second game with friend thane and completed without desync (26 mins).

The only thing I can think of is I did not disable my windows key this time, any chance that could affect.


Final Update: Ok, played 3 different games this morning, no dsync, not sure what it was. I had everyone remove the FAF directory under the programdata folder but thought we did that last night also, today all is well. Thanks for the help, great support great client.

[Uveso]

Thank's for updating your report!

After looking into Downlord's client log, i found the error:

Code: Select all

: Could not populate maps
: Illegal char <:> at index 8: strayway:_hakatiido.v0001.png

Looks like we have a map upload in our vault with a bad file name.
Windows don't like filenames with ":" in it ^^

I guess the next client update will fix this. (Or vault update maybe.)