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 does not report input events if it is not in a collision layer #11159

Open
Tracked by #45334
alejandrocoria opened this issue Sep 10, 2017 · 7 comments · Fixed by #40193
Open
Tracked by #45334

Area2D does not report input events if it is not in a collision layer #11159

alejandrocoria opened this issue Sep 10, 2017 · 7 comments · Fixed by #40193

Comments

@alejandrocoria
Copy link

alejandrocoria commented Sep 10, 2017

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Windows 7 - 64bits
Godot 2.2

Issue description:
Area2D does not report input events if it is not in a collision layer.
I think the collision layers have nothing to do with the detection of input events so it should always detect them (when it is pickable, obviously).

Link to minimal example project:
Area2D Input Bug.zip (Run with Visible Collision Shapes)

@vnen
Copy link
Member

vnen commented Sep 17, 2017

Can you reproduce this with Godot 3?

@alejandrocoria
Copy link
Author

Yes

@girng
Copy link

girng commented Jan 23, 2019

just ran into this issue good thing i searched before making a new one xD. i checked layer 1 and boom, input detection is working. =]. i had pickable enabled so i was like wtf lol
edit: this happens with KinematicBody2D as well

@lopho
Copy link
Contributor

lopho commented May 1, 2019

Can reproduce on 3.1.1.

If this is not fixable due to how mouse picking is implemented, a hint in the documentation and editor would be good to have to avoid confusion.

@KoBeWi
Copy link
Member

KoBeWi commented May 23, 2019

Likely fixed in #28608
Unless the correct solution would be to somehow change how picking works.

@akien-mga
Copy link
Member

I think it can still be considered a bug that picking doesn't work if not in a collision layer. Picking is likely done by a RayCast and thus uses collision layers behind the scene, but in the case of processing input events as a user I wouldn't expect it to matter.

@akien-mga
Copy link
Member

Reopening as #40193 was reverted due to #40705.

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.

8 participants