Revert spatial hashing default visRange to 30 - #4121
Merged
Conversation
Co-authored-by: miwarnec <16416509+miwarnec@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
miwarnec
August 5, 2026 06:49
View session
miwarnec
marked this pull request as ready for review
August 5, 2026 06:50
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.
Commit 025a763 (#4015) changed the spatial hashing
visRangedefault from 30 to 1200 alongside the grid refresh interval optimization. This reverts only the defaults and default-related comments, keeping the interval-based refresh behavior.Changes (in both
SpatialHashingInterestManagementandSpatialHashing3DInterestManagement)visRangedefault: 1200 → 30, tooltip restored to original textdistance = 1200 … 600 * 2→distance = 30 … 15 * 2,400+400=800→10+10=20The
RefreshGrid()/RebuildAll()interval logic and its explanatory notes from #4015 are unchanged; the "Updated Notes" comment mentioning 1200 as a real-world example was kept since it documents the interval behavior, not the default.