Use a simulation rate of 30 steps per second instead of 10 #355
Conversation
This file contains 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
Ralith
approved these changes
Feb 19, 2024
patowen
force-pushed
the
faster-tick-rate
branch
from
c2b8d23 to
8547f2d
Compare
patowen
changed the title
patowen
force-pushed
the
faster-tick-rate
branch
from
8547f2d to
c6f7179
Compare
|
Sounds good to me. I bumped it up to 30. Going up to 60 might be nice, but it does increase required bandwidth etc. so I'll only bump it up further if you suggest such a change explicitly. |
|
I don't foresee bandwidth being a problem, but this seems like a happy medium. |
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.
A faster tick rate reduces the lag between mouse clicks and the modification of terrain, which would be a good quality of life improvement, especially while prediction is not implemented for terrain modification.