Guard against tracking glitches that effect painting #808
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
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.
This is not a pretty fix - it basically ignores calls to PositionPointer that are exactly at the origin. This should never happen in normal uses and only affects the FreePaintTool. Scripts and other proc-gen uses bypass PositionPointer so should not be affected.
But it's still an ugly fix. Is there something we could do lower down the stack?
@mikeskydev - You're more familiar with input system and controller tracking. I think this is related to high-CPU or some other system overload scenario but I can't pin it down precisely.