Objects don't report touch/click release when moved out of touch/click region

I THINK this is a bug, sorry if I’m mistaken.

If you touch an objects collision boundaries, then move the object outside the touch region no release events are fired when the mouse is released or touch removed. Touch/mouse enter/leave don’t work either.

Being kind of hard to explain I provided a picture.


Hi ,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • What steps can I take to reproduce this error on my end?
  • Are you doing this in PIE, simulate, launch, or in a packaged project?

This happens with a launch in new window. The project is essentially empty. There are only a few sprites and two blueprints, nothing significant. I’ve experienced this on other projects though and I never really understood what was happening until recently. In all cases it’s been with Paper2D/sprites.

This also occurs if another sprite overlaps a sprite your’e holding. After the overlap occurs any release information is lost. I’ve seen this happen in compiled projects as well.

I can run more test if you like?

  • Easiest way to reproduce would be to add a sprite with collision(128 by 128px).
  • When sprite is touched Convert mouse to world space, move sprite vertically by 200px.
  • The sprite will then be slightly above where you touched and release events should be broken.

I attempted this on my end but everything seems to be acting as intended. Do you have a sample project where this is occurring I could take a look at? I’d be more than happy to see what may be going on.

I’ll reproduce the issue in a clean project and get that to you.

I realized I left a step out after reproducing the issue. When the sprite is held I enable tick, and per tick I move the sprite slightly above the mouse position. In this instance, when the sprite is moved out of the collision area(mouse click location) release events aren’t registered.

I uploaded an 80kb example here: https://drive.google.com/open?id=0B4iXWOPFnPIZT0tLakdteG91S2M

I was able to reproduce this on my end and have entered a bug report, UE-31030, to be assessed by the development staff.