Fixed grass jumping too abruptly after long play#13
Open
Mawrak wants to merge 5 commits into
Open
Conversation
Fixed intro texture alignment, relative to ui_load
Contributor
Author
|
After more tests I realize the effect can still occur at times, so this isn't a full fix, though it seems to lessen it very significantly, I will keep experimenting to see what I got wrong, but I suppose this is still better than nothing |
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.
There is a common issue where after playing for some time grass starts to behave weirdly, wind waves change grass position too rapidly and abruptly. You can see it happening quickly using "time_factor 1000" command, then returning "time_factor" to 1. Grass will be broken. But it can happen in normal gameplay too as far as I have seen. It's an ugly graphics glitch which ruins an otherwise very pretty game.
It appears to be related to floating point error, and this fix appears to completely remove the issue.