ClickDetectors within models fail to activate while the character or mouse is moving

Bug Reports Engine Bugs
#1

Reproduction Steps

1. Create a Model with multiple parts and a ClickDetector within
2. Have a script which connects to the MouseClick Event of the ClickDetector
3. Press your mouse down on any part within the model (keep the mouse pressed down)
4. Quickly move your mouse to a separate part within the model (or quickly move the character so the mouse is now hovering a different part)
5. Release the mouse

Expected Behavior

I expect the MouseClick event to be fired.

Actual Behavior

The MouseClick Event is never fired. The Click of the mouse must start and end on the same part of the model in order for the MouseClick event to be fired

This video shows an example of the problem:

Throughout the video I’m starting my click on one part and releasing it on another, the ClickActivated event is never fired.
I also show in the video that you can start the click and move the mouse as long as the click is released on the same part.

This is an issue with both Roblox Parts, and imported meshes.

Here is how the ClickDetector is being parented in the file explorer:

705×495 427 KB


Workaround

The only workaround is for my players to make sure they are not moving when building in my game. This leads to frustration and confusion(especially on mobile where it’s very common to be moving with the joystick and tapping a model to delete it).

Issue Area: Engine
Issue Type: Other
Impact: Moderate
Frequency: Constantly

3 Likes
#2

Thanks for the report. Do you still encounter this issue ?

2 Likes
#3

Yes, this is still an issue.

ClickDetectors will only fire if the initially clicked part is the same as the released part within a model.

#4

A bit of a necrobump, but this hasnt been fixed yet, as I ran into this recently. This gets a bit annoying especially for models with a lot of small parts, so a fix would be appreciated.

1 Like
#5

Thanks for reporting this! Please check this to see if using DragDetector could solve your issue? Since ClickDetector was set up in this way. Please let us know if that helps, or we can help to look into any issue you have. Thanks!