Add bake state info and MultiNodeEdit support for NavigationRegion3D

[smix8]

Adds bake state info and MultiNodeEdit support for NavigationRegion3D.

Resolves #104116

Allows to select multiple nodes inside the editor and (re)bake or clear all selected navigation region nodes with one button click.

Adds a new bake dialog that shows how many unique navmeshes need to be baked and how many navigation regions are selected. Revives the old bake state info text that was disabled due to old editor process being broken with threads.

Can't add for NavigationRegion2D because the 2d version depends on the AbstractPolygon2DEditorPlugin. That editor has no support for multi node edit. It is also shared with many other 2d polygon editors so can't be easily modified.

[MJacred]

Tested with simple setups from my Navgiation Area tests. Worked like a charm.

If possible, show a dialog with a message such as "You're attempting to bake multiple NavigationRegion3D nodes. This can freeze the Editor temporarily." Continue | Cancel.
But only if Godot has such a function such as showing a checkbutton between the message and the dialog buttons stating "Don't show this warning again."

The best case would be a queue on a separate thread to prevent potential Editor freezing… Could this be easily achievable with WorkerThreadPool?

[smix8]

Added a new bake dialog. It now processed the regions in a queue with the threaded baking.

The warning and exklusive popup Window hopefully enough to keep users from messing up the editor in the meantime.

Sorry but we cant allow users editing the scene while the baking runs. Doing edits in the middle of the node parsing is an easy way to cause crashes or data corruption. Switching scenes alone is trouble as the editor does too much problematic stuff in the background with the nodes on a scene switch. We also cant do all the parsing at the begin because that is also an easy way to run into memory crashes later.

[smix8]

Now that we have a new Window dialog added back in the bake state for the steps of the navmesh baking process.

[MJacred]

Doing edits in the middle of the node parsing is an easy way to cause crashes or data corruption

Yeah… w/o reliable locking of said resources (+ the visual feedback), this is not advisable. And that would be cumbersome effort

---

bug: cannot bake (multiple) regions/navmeshes after cancelling once

reproduction steps

1. select multiple regions with different navmeshes
2. click "Bake NavigationMesh"
3. instead of baking, cancel the dialog
4. click "Bake NavigationMesh" again
5. Nothing happens. De-selecting and re-selecting does not fix the issue

[MJacred]

I tested with two planes of the size 1000x1000 with 100 subdivisions, in order to slow down the generation.

bugs

• Clicking "cancel" in the dialog only closes the dialog, it does not cancel the current baking The navmeshes still show up
• the bug I mentioned previously is still there: #104210 (review)

---

Just something I noticed…
As far as I can tell, NavMeshGeneratorTask3D::TaskStatus::BAKING_FAILED is never used. Anywhere in the engine.
e.g. NavMeshGenerator3D::generator_bake_from_source_geometry_data could return that value, which could be used in the calling func NavMeshGenerator3D::generator_thread_bake to update generator_task->status

[smix8]

cannot bake (multiple) regions/navmeshes after cancel

That the baking does no longer work after cancelling once at the very begin should be fixed now.

Clicking "cancel" in the dialog only closes the dialog, it does not cancel the current baking The navmeshes still show up

The cancel can only cancel queued navmeshes after the currently baked navmesh. There is currently to way to cancel a navmesh bake that has already started. There is no API for it on either node, server or thirdparty lib. That would be a lot of work not in scope of this PR.

[MJacred]

That the baking does no longer work after cancelling once at the very begin should be fixed now.

Fix is confirmed.

The cancel can only cancel queued navmeshes after the currently baked navmesh

You're right, I mixed that up with my tests on non-unique nav regions. Sorry for the confusion.

---

refinement suggestions:

• adding to the dialog the note: "Cancelling takes effect after the currently baking region is finished." (or sth. along the lines)
• change button text from "Cancel" to "Close" when there's only 1 unique navmesh, as actually cancelling is impossible in that context

[akien-mga]

YOLO approved.

[akien-mga]

Thanks!