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

Area2d's wrong work about monitorable,monnitoring and area_enter #100346

Open
wQAQw1 opened this issue Dec 13, 2024 · 0 comments
Open

Area2d's wrong work about monitorable,monnitoring and area_enter #100346

wQAQw1 opened this issue Dec 13, 2024 · 0 comments

Comments

@wQAQw1
Copy link

wQAQw1 commented Dec 13, 2024

Tested versions

v4.3.stable.official [77dcf97]

System information

Godot v4.3.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU (NVIDIA; 31.0.15.2887) - 13th Gen Intel(R) Core(TM) i7-13700H (20 Threads)

Issue description

There are two area2d,we call them A and B, make A can check B. make A's area_enter connect to a function to observe.

When they are overlaping, turn A' monitoring(true -> false -> true), A' area_enter will emit. (It is right)

However, turn B' monitorable(true -> false -> true), A' area_enter wouldn't emit. ( I think it should emit)

Additionally, every change on B's monitoring (true -> false or false -> true) will makes A' area_enter emit. ( I think it shouldn't emit according to the principle)

I hope that a appropriate change will happen on there and make them liked described.

Steps to reproduce

  1. open the function "display collision area"
  2. press "D" until the small area overlap with the big .
  3. change B'monitoring and monitorable,then oberve

Minimal reproduction project (MRP)

test.zip

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

No branches or pull requests

2 participants