Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve Check Tracker filter performance issues #4111

Merged

Conversation

Malkierian
Copy link
Contributor

@Malkierian Malkierian commented May 4, 2024

When the check filter got added, there were quite a few problems with redundant checks, unnecessary checking, etc, causing massive lag with the check tracker open. The worst of these was passing checksByArea to shouldHideArea() for every area every frame, probably creating a copy every time. Since checksByArea is a global variable in the CheckTracker namespace, this passing was unnecessary anyway. Passing checkSearch was also unnecessary for the same reason.

Also properly capitalized the function names for it, and put IsVisibleInCheckTracker() into the newly renamed ShouldShowCheck() that also checks for filter matching, if applicable.

Build Artifacts

Stop passing checksByArea to functions in the same namespace.
Only get value of `HideFilteredAreas` once per frame.
Gate area and check evaluations behind checks being visible and search filter size greater than 0.
Proper function capitalization.
@Malkierian
Copy link
Contributor Author

Malkierian commented May 4, 2024

@garrettjoecox
Copy link
Contributor

Not really sure what change this is conflicting with, but once you fix I'll merge

@garrettjoecox garrettjoecox merged commit 8d3902a into HarbourMasters:develop May 7, 2024
6 checks passed
@Malkierian Malkierian deleted the check-filter-optimize branch May 7, 2024 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants