You'd probably need two comparisons per direction:

system compare two values: touch.x < touchstartx

system compare two values: abs(touchstartx-touch.x)<abs(touchstarty-touch.y)

would mean swipe left.

Make variables for touchstartx and touchstarty and check them against touch.x an touch.y to see the general direction of the movement is.

Couldn't you use the debugger to check what is happening?

It can show exactly what is taking the most processor time.

AllanR,

I have only tested on desktop and Android, for I haven't got apple-products. It should work, though. I'll look into what the issue could be, probably something different with touch ID.

After reading part of the tutorial it became clear you use 8 direction behaviour to move your sprite. adding objects with the solid behaviour will be the solution.

What are you using for movement? Construct has many movement behaviours.

Depending on your setup untill now it could be the answer differs.

pixel perfick

I'm not planning to make a digital D pad, for it should be possible for anyone knowing the basics of Construct2 to create it themselves.

At least from what I understand it would just be sprites with on touched behaviour.

For the dual thumbstick option I have chosen to make an example with a tank of which the top can rotate freely..

Update (hopefully coming soon)

Just keep them coming..

Dual joystick-implementation could be fun..

I'm kind of dissapointed you haven't responded to my email.

Even if only to tell me you are not interested.

It shouldn't be too much trouble to be respectful to people, should it?

I would be willing to help, although I don't work with Adobe flash.

I do however work with photoshop, inkscape, scribus, blender3D and have a lot of experience with Construct2.

Something like this would probably work:

barprogress - set height : (layoutheight-scroller.y)*barback.height/layoutheight+barprogress.y