QTPFS Path Repair #1550
Merged
QTPFS Path Repair #1550
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.
QTPFS Path Repair tracks damage to paths, not just whether a path was damaged, so that when it is time to repath, only the damaged portion needs to be be repathed. This repath is constrained in area to avoid creating bad paths such as forcing the reconnection if it is more appropriate to do a full repath. The pathing system will switch to using a full repath if it isn't appropriate to repair or it can't feasibly repair the path.
This change is intended to reduce the time needed to update paths in response to damage. Previously the whole remainign path had to be recalculated starting from where the owner had got to.