Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Multiplayer always Desync in master [2+2=5] #4807

Closed
wzdev-ci opened this issue Jun 28, 2018 · 11 comments
Closed

Multiplayer always Desync in master [2+2=5] #4807

wzdev-ci opened this issue Jun 28, 2018 · 11 comments
Labels
closed component: Engine: Networking normal
Milestone
unspecified

Comments

@wzdev-ci
Copy link
Contributor

resolution_fixed type_bug | by Prot

How to reproduce in 1 PC:

  1. Compile or Download from build bot lastest master
  2. Download any side map, for example: http://addons.wz2100.net/279
  3. make two clean game root dir: mkdir -p wz1/maps wz2
  4. add new map to one of those dirs (or both whatever)
  5. run two game clients:
    warzone2100 --configdir=wz1 &
    warzone2100 --configdir=wz2 &
  6. Create a game with a non-built-in map
  7. connect each other
    Or simple use two different PC's
    Or watch video: https://www.youtube.com/watch?v=Y683YpuZDu4

This appers only after b0ea637fee35246eeba5106fb986cb5873e69641 patch.
The problem concerns only third-party maps.
Overall - multiplayer now unplayable.

Issue migrated from trac:4807 at 2022-04-16 13:07:31 -0700
@wzdev-ci
Copy link
Contributor Author

pastdue changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

pastdue changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

pastdue changed _comment0 which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

pastdue commented

Excellent catch. Will dig into why it's happening.

Just to confirm:

  1. Does this also reproduces on Windows with the latest builds from here: https://github.com/Warzone2100/warzone2100/blob/master/README.md#latest-development-builds ?
  2. This affects any third-party map?
  3. None of the built-in maps are affected?
  4. If you follow the same steps with a build of 4fddf373e321dbabd31a8ea9e89ed7c301e14514 , there's no error?

@wzdev-ci
Copy link
Contributor Author

pastdue commented

@prot: Could you please try the latest master, and then apply this patch:
[6]de0926f2aa272f178134c7c39734b0fa35dbf58.patch

And let me know whether it fixes this for you?

(If it doesn't, fresh desync logs from both players would be appreciated.)

@wzdev-ci
Copy link
Contributor Author

Prot commented

Yeah, first i try 4fddf373e321dbabd31a8ea9e89ed7c301e14514 - there is no problem, then b0ea637fee35246eeba5106fb986cb5873e69641 and problem appears.

Now test lastest 013daaf4a789c006bf249581aa0c247810955109 has problem
And apply patch 6de0926f2aa272f178134c7c39734b0fa35dbf58 problem still here.

@wzdev-ci
Copy link
Contributor Author

pastdue commented

Please try again with latest master + this revised patch:
[0522]ad59ee2987f61876554c1bfe58e3d2c74553.patch

@wzdev-ci
Copy link
Contributor Author

Prot commented

Thanks. Seems to be fixed.

@wzdev-ci
Copy link
Contributor Author

pastdue changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

pastdue changed resolution from `` to fixed

@wzdev-ci
Copy link
Contributor Author

pastdue commented

Fixed by: cc7c912ee1755bf3a28bffc690d8992b511af242

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
closed component: Engine: Networking normal
Projects
None yet
Milestone
unspecified
Development

No branches or pull requests
1 participant
@wzdev-ci