Area2D mouse_entered emitted weird

lastbender · July 13, 2025, 10:42am

I just checked and seen similar bug reports.
Exact same:

Strange Area2D `mouse_enter` behavior with controls

opened 01:01PM - 28 Mar 25 UTC

bug topic:physics topic:input topic:gui topic:2d

### Tested versions v4.4.0 and betas v4.4.1.stable.official [49a5bc7b6] ### Sy…stem information Godot v4.4.1.stable - Windows 11 (build 26100) - Multi-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4060 Ti (NVIDIA; 32.0.15.7283) - 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz (12 threads) ### Issue description There is strange behavior when the mouse is moving between Area2Ds and mouse blocking Control nodes (ColorRect used for visualization). Keep in mind in these examples, only the Area2D is emitting the signals and printing to the console. https://github.com/user-attachments/assets/6127dfb2-c0d7-4e19-a551-d420d308819f When moving your mouse over a Control that's overlapping an Area2D, the area will emit it's `mouse_entered`signal. _Sometimes_ it emits (couldn't get it on the video, I think it happens more often if you move your mouse slowly) when going from the Control to the Area, which to me is the expected behavior. https://github.com/user-attachments/assets/9df0bb92-43dd-4ad0-a0ed-3d576aadacb8 Now here is the strange one, that made me go deeper into this and make this report. If you move your mouse cursor fast enough from Area2D to a **completely disconnected** Control... the Area will emit it's `mouse_entered` signal. ### Steps to reproduce Get the MRP and move your mouse between the Area and ColorRect, the same way I was doing in the videos. Make sure to enable visible collision shapes to make it easier. ### Minimal reproduction project (MRP) [area2d_bug.zip](https://github.com/user-attachments/files/19506086/area2d_bug.zip)

Similar:

github.com/godotengine/godot

After a mouse exits a Control node and the containing window at the same time, `mouse_entered` signal is sometimes wrongly emitted immediately after `mouse_exited`

opened 03:46PM - 03 Jul 25 UTC

rxlecky

bug needs testing topic:input regression topic:gui

### Tested versions - Reproducible in: v4.4.1.stable, v4.3.stable, v4.3.dev6.of…ficial [89850d553] - Not reproducible in: v4.0.stable, v4.2.2.stable, v4.3.dev3.official [36e943b6b], v4.3.dev4.official [df78c0636], v4.3.dev5.official [89f70e98d] ### System information Godot v4.4.1.stable - Windows 11 (build 26100) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Laptop GPU (NVIDIA; 32.0.15.6636) - 13th Gen Intel(R) Core(TM) i9-13900HX (32 threads) ### Issue description After a mouse exits a Control node, `mouse_entered` signal is sometimes wrongly emitted immediately after `mouse_exited`. This leaves the client code mistakenly thinking that the node still has mouse hovering it. Here's the script used in the MRP, attached to a screen-wide button: ```gdscript extends Button func _input(event: InputEvent) -> void: if event is InputEventMouseMotion: var mouse_pos: Vector2i = DisplayServer.mouse_get_position() var window_rect: Rect2i = Rect2i(get_tree().root.position, get_tree().root.size) print(Engine.get_physics_frames(), ": mouse_pos %s, window_rect %s(has_mouse:%s)" % [mouse_pos, window_rect, window_rect.has_point(mouse_pos)]) func _on_mouse_entered() -> void: text = "entered" print(Engine.get_physics_frames(), ': entered') func _on_mouse_exited() -> void: text = "exited" print(Engine.get_physics_frames(), ': exited') ``` ... here's an example of the output log from a reproduction case: ``` 227: entered 227: mouse_pos (2072, 1279), window_rect [P: (1344, 726), S: (1152, 648)](has_mouse:true) 228: mouse_pos (2080, 1109), window_rect [P: (1344, 726), S: (1152, 648)](has_mouse:true) 229: mouse_pos (2086, 831), window_rect [P: (1344, 726), S: (1152, 648)](has_mouse:true) 230: mouse_pos (2086, 723), window_rect [P: (1344, 726), S: (1152, 648)](has_mouse:false) 230: exited 230: entered 230: mouse_pos (2086, 631), window_rect [P: (1344, 726), S: (1152, 648)](has_mouse:false) ``` ... and here is a video capture: https://github.com/user-attachments/assets/0305babd-d120-411c-8dda-31653b71c02f ### Steps to reproduce 1. Open the MRP and run the main scene 2. Move the cursor across the game window, entering and exiting it 3. Observe that the window will occasionally get stuck on 'entered' state even after the cursor exits the window 4. Read the debug log to see that `mouse_exited` was actually emitted but `mouse_entered` was emitted immediately afterwards ### Minimal reproduction project (MRP) [mouse-exited-bug-mrp.zip](https://github.com/user-attachments/files/21040841/mouse-exited-bug-mrp.zip)

The computer with the issue:

The computer without the issue:

Yes, I tried it exactly as on the notes. It didn’t work.

mrdicerack · July 13, 2025, 10:43am

What if this is an issue with AMD processors? I use an Intel too and it worked fine. @pauldrewett do you use Intel too?

pauldrewett · July 13, 2025, 11:28am

Yep. And it is working fine here too.