Multi touch no longer working correctly

[raxabit]

Hello!

MrLambert, you're not alone on this.

DaveC, I have tried your method, but the problem persists. Frame 1 of the attached MFA demonstrates this. I think this is a problem with the Multiple Touch extension not being able to to end multiple touches at the same time.

Frame 2 is a work in progress, but a real mess! If both touches are released at the same time, it will not leave one behind (which is good). Tested this on PC and Android.

On Android, if you start a new touch after this, it will act as if you started two (which is bad). Finger 2 will show up at the last X and Y of Touch 1. It will stay there until you touch and release it (but not simultaneously with another release) OR if you move Touch 1 around while Touch 0 is engaged.

Destroying and recreating Multiple Touch Object 1 does not reset the touch state. Maybe there's another approach to this.


I hope this serves as a good hint for anyone looking into this.

RaxaTouch.mfa

[DaveC]

I can't look at this until I get home.. but you could do a slightly different test.

touch 0 is active (move x/y position of detector to X/Y of touch 0)
touch 0 is active (negate) (set x/y to -50,-50)

it could possibly be a new issue in one of the new builds, we'll see!

[raxabit]

TOUCHTOUCH.png

Unfortunately, this doesn't make a difference with the simultaneous release issue.

it could possibly be a new issue in one of the new builds, we'll see!

This wouldn't surprise me. I tried using earlier versions of the Multiple Touch extension, but that didn't make a difference.

I'll continue working on that sloppy Bugsauce Frame 2 from my last MFA later in the morning. If I'm lucky, someone else will figure it out before then.

[DaveC]

I'm 100% certain this was not an issue at least a few months ago.. but it does seem to be broken now, even on my own games that I had thoroughly (100%) tested the multi touch on. It's definitely a serious problem that must be fixed!

[Fernando]

Please post a bug report for this in order to check,

i tested here and the first version did let the red point always on, but my example do work correctly here, tested in G tablet (only 2 multitouch) later i will test in Nexus (10 points)

but please test the apk modify and the mfa to see if work correctly, thanks

[MrLambert]

Thanks for chiming in raxabit and for the confirmation DaveC, I was starting to get worried that I was the only person seeing this!

FVivolo- I won't be able to get into fusion until later today, however I don't believe this is a device specific problem. I get the error on pc when using simulated taps, you have to release ctrl and mouseclick at nearly the exact same time for it to occur. I didn't notice the error on pc at first, but now that I know how it occurs, I can reproduce the bug easily.

thanks again for your help everyone

[DaveC]

I can re-create the bug easily on that .APK you posted FVivolo. If you keep tapping and releasing at the same time (2 fingers) in different places, eventually you'll see one or two of the objects gets left behind. This is a big problem for me where I have my virtual touch buttons, when the player is touching left/right/jump etc. sometimes the buttons will remain held down because the released touch is not being recognised. I can also recreate the problem on the PC runtime.

EDIT: I posted to the bug tracker, other people might like to chime in there with a better example if you have one.

http://bugbox.clickteam.com/issues/2073

[Fernando]

please post in the bug report i will check

nothing have change in the multitouch only me that i have new changes (not posted) which are under testing (mostly to update to newer API).

[DaveC]

one more thing to note, I have several .APK's of my game that I saved only a couple of weeks ago where the problem does not exist, I've changed no code in my game, but all the new .APK's that I create have this problem.. so it must have been a change to something recently that has caused the issue. Good luck finding it ^_^

[raxabit]

Good afternoon, everyone.

one more thing to note, I have several .APK's of my game that I saved only a couple of weeks ago where the problem does not exist, I've changed no code in my game, but all the new .APK's that I create have this problem.. so it must have been a change to something recently that has caused the issue. Good luck finding it ^_^

I just did a fresh install from CD of Fusion (280.32) and the Android exporter, didn't update it. The problem persists on PC, but is seemingly gone in Android builds.

Here's an APK built from DaveC's example in the Bug Box. It works fine for me, but what about everyone else?

Hope this helps.

MtouchEx.apk