So a bunch more testing here. I’ve been looking at the camera controls since yesterday. I’m not entirely sure what is causing the behaviour. Following the execution on this, everything seems to be plugged in correctly, and I can’t reliably reproduce the behaviour. It seems to happen most if I’m trying to scroll across a larger map quickly, but it also happens when I’m swiping slowly. Basically, you could describe it as rubber banding:
I touch in some direction to pan the camera, swipe across the screen, the camera moves, but when I let go, the camera jumps back to its starting location.
I thought this was a fast swiping issue, so I changed the pan speed to give more movement on swipe to make it less necessary to swipe rapidly to move a short distance, but even when I take a noticeable pause in between swipes, it will still jump like this. My best guess is that it is somehow misinterpreting some kind of swipe as a press or something.
It’s hard to debug this kind of stuff on the device itself. Especially when it can’t be reproduced accurately. Just a little testing that might help. I’m moving on to ability clicking and see if I can’t get anymore insight in to that.
Further testing of these three things:
1 - disconnecting tick as there is a comment saying it should be for tick
2 - checking the touch bool on click attempt
3 - hooking up the node on ability base
After experimenting with some combination of these three things, leaving tick and the ability base node connected and the bool checked gave the best results for controls in game.