feat: RPC Network Update Order and Network Update Loop Registration#442
Merged
NoelStephensUnity merged 31 commits intodevelopfrom Jan 15, 2021
Merged
feat: RPC Network Update Order and Network Update Loop Registration#442NoelStephensUnity merged 31 commits intodevelopfrom
NoelStephensUnity merged 31 commits intodevelopfrom
Conversation
This branch *is not for any prouction use*, but is for a quick holiday port of a Unity Lesson (Chapter 17: Zombie Toys) to a client server architecture. This currently only supports single player (server authoritative client) and the monster AI (server authoritative). This branch, however, does include some potential fixes to potential bugs in the current development branch.
Some interesting changes. Had to add a "destroy" parm to be able to use registered custom destroy callbacks.
Just some tweaks and a useful way to get notified the network session is shutting down.
minor update
…/networkupdate"" This reverts commit 9a09588.
Making adjustments from the merge of develop
The RPCQueueRevisited kind of threw this branch into chaos. These are some of the fixes for the merge issue.
Lost some of the batching changes, also wanted to keep the original RPC Send methods.
This just fixes some of the stutter associated with batching.
Added a more modular way to register with the network loop update system. This includes four possible paths: Add the INetworkUpdateLoopSystem to your class declaration and provide the appropriate methods. =or= Derive your class from: GenericUpdateLoopSystem for a slim non-monobehavior derived class. UpdateLoopBehaviour for a MonoBehaviour derived class. NetworkUpdateLoopBehaviour for a NetworkedBehaviour derived class. NetworkingManager now only is updated during the PREUPDATE and UPDATE stages. RpcQueueContainer now automatically registers for all update stages but also provides the ability for one to handle RPC queue processing externally (i.e.. at different stages).
The updated names and formating for Unity standards will be coming in the RPCQueueRevisited PR
This just applies the fix for bool reading and writing PR #438
Removed the code that extracted the host client id from the connected client list as the bug that invoked that change was finally found and not related to this temporary fix. Did some standards clean up.
Had to refactor some of the code based on current state of develop branch.
Contributor
|
Added HotFix for MessageBatching: using different writers for different SendStreams. |
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
reviewed
Jan 14, 2021
0xFA11
suggested changes
Jan 14, 2021
Contributor
0xFA11
left a comment
There was a problem hiding this comment.
I'll have another thorough look at this PR.
jeffreyrainy
approved these changes
Jan 14, 2021
The majority of these changes are syntax/standard oriented, but there are a few good catches like removing C# 8.0 standard "using", try an catches left in, and some const definitions for some of the RPC queue related boundary checking.
Removing the ifdef.
Moving the RPC queue related files to the Messaging directory since they are within the same namespace (and it is the proper location for them).
0xFA11
approved these changes
Jan 14, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MTT-174
This commit provides the ability to:
Actionwith a specific network update loop stage.Ancillary information:
Additional updates unrelated to MTT-174: