[MTT-14843] Refactor sending and receiving of N4E RPCs in UnifiedNetcodeTransport to not use entities#3943
Open
ShadauxCat wants to merge 1 commit intoexperimental/v3-x-x/unifiedfrom
Open
Conversation
…reserving send/receive order without having to encode an order value and reorder messages on the receive side.
EmandM
reviewed
Apr 17, 2026
|
|
||
| #if !UNIFIED_NETCODE | ||
| // Process outbound messages | ||
| MessageManager.ProcessSendQueues(); |
Member
There was a problem hiding this comment.
Hmmm, should we be also checking the transport here? Are we allowing users to still use UnityTransport as normal? Or are you forced into the UnifiedTransport?
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
2 participants
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.
Purpose of this PR
Refactors sending and receiving of N4E RPCs in the UnifiedNetcodeTransport to not use entities. This removes the need to include a ulong encoding message order and to do message reordering logic on the receiving side.
In addition, I also moved the location where we call NetworkMessageManager.ProcessSendQueue() to be right before N4E processes their send queue. In the place it was previously (PostLateUpdate), N4E wouldn't process anything we sent until the next frame.
Jira ticket
MTT-14843