You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I press "up" on the virtual dpad, then slide my finger toward the top of the screen, the "up" button gets stuck in an "always on" state. The only way to release it is by reloading the game.
Discovered the reason for this just tonight; The virtual gamepad listens for pointer events on only a small part of the viewport. The initial touchstart/PointerDown event will be fired when my finger first touches the button. Then as I slide my finger, a series of touchmove/PointerMove events will fire. Eventually, my finger will leave the rectangle that the virtual gamepad is registered to. The following events will not be dispatched to the virtual gamepad, because they are outside of the listening rect.
And if the touchend/PointerUp event is fired while outside of that rect, this missed event means the virtual gamepad button will never be released!
The text was updated successfully, but these errors were encountered:
When I press "up" on the virtual dpad, then slide my finger toward the top of the screen, the "up" button gets stuck in an "always on" state. The only way to release it is by reloading the game.
Discovered the reason for this just tonight; The virtual gamepad listens for pointer events on only a small part of the viewport. The initial
touchstart
/PointerDown
event will be fired when my finger first touches the button. Then as I slide my finger, a series oftouchmove
/PointerMove
events will fire. Eventually, my finger will leave the rectangle that the virtual gamepad is registered to. The following events will not be dispatched to the virtual gamepad, because they are outside of the listening rect.And if the
touchend
/PointerUp
event is fired while outside of that rect, this missed event means the virtual gamepad button will never be released!The text was updated successfully, but these errors were encountered: