!B (HNT-26703) Addendum: function 'AreMessagesToWrite' should be consistent in accord... 5.5.0_preview4
| commit | e51963c23db58835e8e27417ba131ab1bbe0bf5a | |
| author | Pedro Engana <pedroe@crytek.com> | |
| Fri, 1 Jun 2018 15:46:08 +0000 (1 17:46 +0200) | ||
| committer | Pedro Engana <pedroe@crytek.com> | |
| Fri, 1 Jun 2018 15:46:08 +0000 (1 17:46 +0200) | ||
| tree | e72c44be252b9368754567566ecded086bf6e0b7 | treesnapshot (tar.gz zip) |
| parent | 073de1328690aa84428b13028b38e1624ec9a660 | commitdiff |
!B (HNT-26703) Addendum: function 'AreMessagesToWrite' should be consistent in accordance to previous change in CL 1695214 !B (HNT-26703) Fix issue with message queue, where if a message with a dependency is in the queue, it would block the entire entity from sending any other message, until the dependency enters the queue.
With this solution, we skip over the message with unfulfilled dependencies, and we write any other pending message to socket.
This was causing issues in Hunt, where we were observing that even in zero packet loss conditions, messages were being mysteriously lost and delayed.
Copied from Perforce
Change: 1702274
With this solution, we skip over the message with unfulfilled dependencies, and we write any other pending message to socket.
This was causing issues in Hunt, where we were observing that even in zero packet loss conditions, messages were being mysteriously lost and delayed.
Copied from Perforce
Change: 1702274
| Code/CryEngine/CryNetwork/Protocol/NewMessageQueue.cpp | diffblobblamehistory |