Disable thread-unsafe EditorProgress for navmesh baking
Disables navmesh baking EditorProgress for now until fixed as EditorProgress is not thread-safe and uses hacks and Main::iteration() for steps which can result in random crashes when baking navmesh.
(cherry picked from commit 24bb0af4a9
)
This commit is contained in:
parent
fcff804844
commit
7bcb9fddc9
1 changed files with 8 additions and 1 deletions
|
@ -613,7 +613,14 @@ void NavigationMeshGenerator::bake(Ref<NavigationMesh> p_nav_mesh, Node *p_node)
|
|||
ERR_FAIL_COND_MSG(!p_nav_mesh.is_valid(), "Invalid Navigation Mesh");
|
||||
|
||||
#ifdef TOOLS_ENABLED
|
||||
EditorProgress *ep(NULL);
|
||||
EditorProgress *ep(nullptr);
|
||||
// FIXME
|
||||
#endif
|
||||
#if 0
|
||||
// After discussion on devchat disabled EditorProgress for now as it is not thread-safe and uses hacks and Main::iteration() for steps.
|
||||
// EditorProgress randomly crashes the Engine when the bake function is used with a thread e.g. inside Editor with a tool script and procedural navigation
|
||||
// This was not a problem in older versions as previously Godot was unable to (re)bake NavigationMesh at runtime.
|
||||
// If EditorProgress is fixed and made thread-safe this should be enabled again.
|
||||
if (Engine::get_singleton()->is_editor_hint()) {
|
||||
ep = memnew(EditorProgress("bake", TTR("Navigation Mesh Generator Setup:"), 11));
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue