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

Patch navigation map async synchronization #100823

Merged
merged 1 commit into from
Dec 26, 2024

Conversation

smix8
Copy link
Contributor

@smix8 smix8 commented Dec 26, 2024

Patches navigation map async synchronization.

Fixes regression from the two mega PRs #100497 and #100129.
Fixes #100769
Also fixes old bugs encountered in the search process unrelated to the PRs.

Between slicing my own mega branch into 2+ PRs and all the branch rebase and applying foreign changes new bugs and typos slipped in. In the end it was just too much chaos that made isolating the bug sources near impossible. I had to start basically from branch zero applying everything from those 2 PRs again step by step. That is why this PR changes some smaller parts back to the old code style and removes some minor internal things that we agreed in the review but actually caused new and unforeseen bugs.

I tested this PR for days to confirm that all known bugs and regressions are fixed caused by those 2 mega PRs while keeping all the actual changes and improvements. So calm your reviews because I don't want to risk changing anything again before this is merged. As such prefer to merge this as is asap. If we want to change something we should do it after this PR has been merged.

Patches navigation map async synchronization.
@smix8 smix8 force-pushed the patch_async_mapsync branch from 3caac92 to c694081 Compare December 26, 2024 12:04
@akien-mga akien-mga merged commit 99a8ab7 into godotengine:master Dec 26, 2024
20 checks passed
@akien-mga
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bidirectional flag in NavigationLink3D is no longer taken into account by NavigationAgent3D
3 participants