Multi touch no longer working correctly

[MrLambert]

Hi Everyone,

Hopefully someone can give me some insight here, I'm having a problem with multitouch registering when more than touch has been released at the same time.

The controls I am creating are similar to the moonlander style, tapping the left side of the screen rotates left, same for the right. Tapping both sides of the screen at the same time gives you forward movement, and this is where I have the problem. Not always, but most of the time only one of the two tracking objects is destroyed resulting in my character spinning out of control.

I could be wrong, but I don't recall having this issue before the update(Using the steam version. I also had 281.3beta of the android exporter installed BEFORE the steam update, I have no idea if the beta was overwritten or not during the update).

The code I lifted from examples on the forums:
Untitled-1.jpg


Thanks in advance!

[Fernando]

can you post a small mfa for me to test here?

[MrLambert]

Sure, see attached. I trimmed the file down to just the control system and a placeholder graphic, however the error still occurs.

This only happens while testing on an android device, not during a pc simulated-tap test. I'm testing on a samsung note i717.
I also found that it is only releasing at the same time which causes the error. Releasing multiple simultaneous touches one at a time still works.

Thanks for your help

dualTapTest.mfa

[DaveC]

Actually you'd need to do a for each loop for this, if you wanted to create two multi touch objects at the same time.

[MrLambert]

Creating the tracking objects works fine, destroying them is the problem. I did however go ahead and try to use for each loops in both the destruction and creation of the objects, but I got the same results. Maybe I'm just not using them correctly? I've only had fusion for a couple weeks and I'm still pretty green :p

I mentioned earlier that this did not happen during pc testing- I did eventually find that this does in fact happen during pc testing, but much less often and is more difficult to reproduce.

Anyway, I'm attaching the for-each version here as well in hopes that someone can help me figure out what I am doing wrong.
dualTapTest_forEach.mfa

thanks again

[Fernando]

I think the problem is that you are using fastloop for setting the physics, events 23, 24 and 25 for me here since you are changing animation you should use a value as flag and set 1, 2 or 3 and react


I don´t see any benefit to use fast loops in theses events

[MrLambert]

Does that file work ok for you FVivolo? Because I am still having the same error with your modified version.
I tried removing everything except for the tracking objects and multiple touch object; it is just a blank screen that tracks taps, but even this doesn't seem to work for me. It only wants to remove a single tracker. When I try tapping with 4 fingers, and then I release them, I would be left with 3 tracking objects still on screen. Doesn't seem to matter if the initial touches are simultaneous or not, only when they are released at the same time.

the boiled down version: tapsOnly.mfa

[Fernando]

please test this apk and tell me

http://dl.dropboxusercontent.com/u/4...ualTapTest.apk

------------------------

i will test tomorrow morning

[MrLambert]

No luck, still only removes a single tracking object.

[DaveC]

if you create unique objects (instead of duplicates of the same object) specifically for each specific touch (say touches 0,1 and 2) do you still get the same issue? (I strongly suspect you won't)

eg
on touch 0 create touch 0 object (a unique active)
on touch 1 create touch 1 object (a unique active)
on touch 2 create touch 2 object (a unique active)

on end touch 0 - destroy touch 0 object
on end touch 1 - destroy touch 1 object
on end touch 2 - destroy touch 2 object

always
set x pos of touch 0 object to x of touch 0, set y pos of touch 0 object to y of touch 0
set x pos of touch 1 object to x of touch 1, set y pos of touch 1 object to y of touch 1
set x pos of touch 2 object to x of touch 2, set y pos of touch 2 object to y of touch 2