You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has been some work on this earlier in the year. There still can be a problem in some situations that can cause out of order delivery, so we recommend adding some ordering bits to your message so you can sort them accordingly.
We are seeing messages arriving out of order when using the SendReliableMessage API.
Device A (Server) is sending messages with the following identifiers: 21, 22, 16, 17, 17.
Device B (Client) is receiving messages with the following identifiers: 21, 16, 17, 22, 17.
These are the logs from device A:
These are the logs from Device B
Another user has reported this problem: http://stackoverflow.com/questions/27199974/sendreliable-message-sometimes-not-received-by-opposite-peer
Iit seems like the SendReliable pathway does not meet the in-order gaurentee outlined here: https://developers.google.com/games/services/common/concepts/realtimeMultiplayer#sending_game_data
Any information or confirmation on this bug is greatly appreciated.
EDIT:
I've modified the ButtonClicker sample on a fork of this project to demonstrate that the reliable messaging system delivers messages out of order:
https://github.com/jknight-nc/cpp-android-basic-samples/tree/outoforder
The commit is located here: jknight-nc@b3c62c8
The text was updated successfully, but these errors were encountered: