Multi touch no longer working correctly

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:
Attachment 13774


Thanks in advance!

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

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

Attachment 13776

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.

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.
Attachment 13787

thanks again

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

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: Attachment 13795

please test this apk and tell me

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

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

i will test tomorrow morning

No luck, still only removes a single tracking object.

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

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.

Attachment 13799

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!

Attachment 13801

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

Quote:

---

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. ;)

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!

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

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

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

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).

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 ^_^

Good afternoon, everyone.

Quote:

---

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.

Attachment 13805

Your apk works perfectly on my device as well raxabit.

Raxabit, have you also tested building the .apk after you've updated your fusion/android runtimes? it no longer works after that?

i have check and compare the code for multitouch and is the same from 280.32, the same logic

also tested the raxabit example and yes it works ok here, but not the dualTapTest

Yeah, raxabit your .APK using the older Fusion Build works perfectly.. but of course when I build it from the newer Fusion builds the same file doesn't work... I think FVivolo is getting close to a fix though! ^_^

With Fusion 280.32, the problem shows up in 281.8 of the Android export module. 281.7 and earlier doesn't seem to be a problem.

fear not, Fvivolo seems to have fixed the issue now (in a unofficial beta) so it should be working again for the next beta!

This is excellent news. I can't wait! ;D I'll bet MrLambert is also pretty pumped for this.

Definitely glad to hear there is a fix in the works. I guess I'll just keep chugging along and test with a set of keyboard controls instead until the beta is available. Thanks everyone!

check here MrLambert - http://community.clickteam.com/threads/88048-Android-beta-281-2-20140716

hi, and thank you
is there another file on this page

because - cannot install this program, a required file is missing ,

about this update :
http://community.clickteam.com/threa...281-2-20140716
when I start to install it

it shows me a window, and in there
cannot install this program, a required file is missing

any help?

plz :-)

Thought I would follow up and confirm that the beta fix is indeed working for me. I still get the error when testing on pc, but it works perfectly on my android device now.

hassahn~ I didn't have any problems installing the beta on my end. My only suggestion would be to double check your install directory. I installed into the base fusion folder: C:\Program Files (x86)\Steam\steamapps\common\Clickteam Fusion 2.5

Thanks!

thank you mr. Lambert it work :-) thank you