Repository navigation
physics tweaks - #1826
Open
Azaezel wants to merge 2 commits into
Open
physics tweaks#1826Azaezel wants to merge 2 commits into
Azaezel wants to merge 2 commits into
Conversation
add preIntegrateForces - hat tip atomic walrus: https://torque3d.org/forums/topic/10685-rigid-physics-general-discussion/#findComment-34584 pad integration based on velocity to mitigate punchthrough, and default it to 4 since that seems the most general stable/perf accroding to most folks actual useages ditch overagressive network filtering based on atrest. it was leading to client desync
This branch has not been deployed
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.
add preIntegrateForces - hat tip atomic walrus: https://torque3d.org/forums/topic/10685-rigid-physics-general-discussion/#findComment-34584
pad integration based on velocity to mitigate punchthrough, and default it to 4 since that seems the most general stable/perf accroding to most folks actual useages
ditch overagressive network filtering based on atrest. it was leading to client desync