Navigational mesh - analyze cells to check for computational shortcuts #5031
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.
We now collect information while we pre-analyze a cell. This allows us to make better decisions to just flatten a cell. As an example: there is no need to analyze a cell for land capabilities when it entirely consists of water. This saves roughly 5% to 10% on the computation time. It has less of an impact on larger maps as the dominant factor on larger maps is the raw quantity of heightmap samples.
Old situation:
New situation: