Dial to tweak how often statesynchronizer sends property snapshots.#405
Open
warsang wants to merge 1 commit intofoxssake:mainfrom
Open
Dial to tweak how often statesynchronizer sends property snapshots.#405warsang wants to merge 1 commit intofoxssake:mainfrom
warsang wants to merge 1 commit intofoxssake:mainfrom
Conversation
the client when using a statesynchronizer node
Contributor
|
Thanks for the PR @warsang! Have you tested this with TickInterpolator? How did it perform? |
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.
Pretty simple change, added a dial to tweak how often we want to update/send state back to the client when using a statesynchronizer node. This is similar to the Multiplayer's Replication Interval option. My use case for this was I had resource nodes spawned on a map and I didn't want to send updates every network tick since their properties shouldn't be updated that often.
The Replicate "onchange" with the normal MultiplayerSynchronizer doesn't really fit my use-case because if a peer disconnects/reconnects, they don't get the node's position unless the node is moved (which doesn't happen often). My options were either use a Netfox statesynchronizer but updates are sent pretty often or use Replicate "always" with the multiplayer synchronizer and tweak the replication Interval dial to save on bandwidth.