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

Error: _queue_monitor_update: Parameter "get_space()" is null. when deleting an Area3D affecting a SoftBody3D #97116

Closed
LucidTaZ opened this issue Sep 17, 2024 · 2 comments · Fixed by #97130

Comments

@LucidTaZ
Copy link

Tested versions

Reproducible in 4.3-stable

Not reproducible in 4.2.2-stable

System information

Godot v4.3.stable - macOS 14.6.1 - Vulkan (Forward+) - integrated Apple M2 Max - Apple M2 Max (12 Threads)

Issue description

When deleting an Area3D that blows wind on a SoftBody3D, the below error is printed:

E 0:00:01:0112   _queue_monitor_update: Parameter "get_space()" is null.
  <C++ Source>   servers/physics_3d/godot_area_3d.cpp:214 @ _queue_monitor_update()

The Area3D is deleted through a queue_free() call.

Steps to reproduce

Scene contains:

  • SoftBody3D with a mesh (QuadMesh works)
  • Area3D with a CollisionShape3D
  • Both can be at default settings (layer, mask, etc.) as long as the SoftBody3D is inside the Area
  • I found this issue in my Area3D's that cause wind to blow on the SoftBody3D, although it also happens when the wind parameters are left on the defaults

Minimal reproduction project (MRP)

softbody3d-wind-issue-reproduction.zip

@matheusmdx
Copy link
Contributor

Bisecting points to #81809 as the culprit, @Rindbee

image

@AThousandShips AThousandShips added this to the 4.4 milestone Sep 17, 2024
@Rindbee
Copy link
Contributor

Rindbee commented Sep 17, 2024

It seems that the soft_body was forgotten when adding the get_space() check code in GodotArea3D::remove_*_from_query().

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

Successfully merging a pull request may close this issue.

4 participants