Try resolving threading issues - #43
Merged
Merged
Conversation
This should be more efficient than setposing the client physobj constantly.
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.
Lots of primitives results in non-threaded primitives regenerating immediately. This lags when you're moving into PVS with those primitives; and at some point, the lag becomes so great from that PVS update that a full update will be triggered due to netchan timing out, resulting in pretty much an infinite loop of prim regen -> timing out netchan -> full update -> forever until the primitives are removed
This hopefully fixes that(?) I did test it and it seems to work perfectly fine