Simultaneous tapping Virtual gamepad example (SOLVED)

britzl · July 30, 2019, 7:50pm

Hmm, I thought I had updated it to support multi touch. Can you share a link to the example?

Pkeod · July 30, 2019, 8:09pm

Please confirm that something like this works on your device with multitouch https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester&hl=en_US

shadowmaikda · July 30, 2019, 9:19pm

I downloaded here

I watched this source (it uses the same virtual gamepad example)

and in the source of the same bug

shadowmaikda · July 30, 2019, 9:20pm

I have no problems with multitouch

Dragosha · July 31, 2019, 4:10am

Multitouch works on Android/iOS build, but does not work in html5. Where are you testing?

britzl · July 31, 2019, 4:18am

I believe @AGulev looked into this. Alexey, did you do any work on multitouch for HTML5?

shadowmaikda · July 31, 2019, 5:28am

maybe I do not explain correctly

multitouch works, but if i tap two points on the screen at the same time then there is a bug
https://forum.defold.com/uploads/default/original/3X/0/f/0fe36b953ddd1b66c62e5c8ed8bf386d89c67f20.mp4 https://forum.defold.com/uploads/default/original/3X/3/6/36590ba8508f84247b1a0b68c31284033b9a5fb7.mp4 look at the touch points

shadowmaikda · July 31, 2019, 5:49am

I tried to check if the stick was released and when I saw the bug, then only one touch point was released (one message is released)
This only happens when the tap was at the same time. But I want to use it in my project.

AGulev · July 31, 2019, 6:06am

Not really. I have it in my backlog for exploration day (not sure that it is possible to finish in exploration day. @sven knows input system better and could estimate this issue more accurate, I think).

As I understand, you are testing it in native (not html5) bundle?

shadowmaikda · July 31, 2019, 6:14am

I use apk on my android device

britzl · August 2, 2019, 6:27am

I found a problem in my example. I’ve pushed an update. @shadowmaikda, please try it again.

britzl · August 2, 2019, 7:34am

I also “productified” the on-screen controls into a reusable module:

github.com

britzl/defold-input/blob/master/in/onscreen.lua

local M = {}


M.BUTTON_PRESSED = hash("button_pressed")
M.BUTTON_RELEASED = hash("button_released")
M.ANALOG_PRESSED = hash("analog_pressed")
M.ANALOG_RELEASED = hash("analog_released")
M.ANALOG_MOVED = hash("analog_moved")

-- Create an instance of onscreen controls
-- @param config Optional table with configuration values. Accepted values are:
--		* touch (hash) Action id for the binding to single touch
-- @return instance
function M.create(config)
	config = config or {}
	config.touch = config.touch or hash("touch")

	local instance = {}

	local controls = {}

This file has been truncated. show original

With example:

github.com

britzl/defold-input/blob/master/examples/onscreen/onscreen.gui_script

local onscreen = require "in.onscreen"

local post_to_listener

local function on_analog(action, control, touch)
	if action == onscreen.ANALOG_PRESSED then
		print("analog pressed")
		post_to_listener("analog", { x = 0, y = 0, pressed = true })
	elseif action == onscreen.ANALOG_RELEASED then
		print("analog released")
		post_to_listener("analog", { x = 0, y = 0, released = true })
	elseif action == onscreen.ANALOG_MOVED then
		print("analog moved")
		post_to_listener("analog", { x = touch.x, y = touch.y })
	end
end

local function on_control_a(action, control, touch)
	if action == onscreen.BUTTON_PRESSED then
		post_to_listener("button_a", { pressed = true })

This file has been truncated. show original

AGulev · November 26, 2019, 8:34pm

Solved in 1.2.164

kakerlaka · March 22, 2020, 5:38pm

hello everyone,

i am still running into the same problem, multiple taps make the analog or buttons hang or “get stuck” … am using defold 1.2.166 (got version from “help” menu -> about), onscreen.lua module from the current defold-input master, and the example scripts.

also, sometimes the buttons or analog stick react for about 2 to 3 seconds and then trigger a released although i am still holding the button and or stick … happens on laptop, tablet and phone.

are there any posts or updates i missed ?

britzl · March 22, 2020, 6:01pm

Hmm, how many fingers are touching on screen at the same time?

Haven’t heard of this before. Can you try to narrow down some solid steps to reproduce this issue?

kakerlaka · March 22, 2020, 6:14pm

2 fingers … its 1 analog and 2 buttons, simple shooter, analog to turn ship and a button each for thrust and shooting

this happens randomly when app starts up on phone … i start the app, hit and hold the fire button but the shots for example stop after a few seconds … then when i release the button and press it again,ship shoots for a few seconds and stops again. same with the analog button. i close the app on the phone, restart it and all works exept the hanging thingy

thanks for the fast reply and the effort to help

britzl · March 22, 2020, 7:48pm

So I can get this to happen using the example project on a phone?

Does it happen on a laptop as well? Windows, macOS or Linux?

kakerlaka · March 22, 2020, 9:40pm

yes. i downloaded defold-input from here, https://github.com/britzl/defold-input , opened it in the editor,bundled it for android and on both, tablet (android version 4.4.2 i know!) and on phone (android version 8.1.0) it can be reproduced by: open app, tap onscreen button, tap and don’t release the fire button, now move analog up, keep up and release fire button … now release analog and it is stuck.

no touch on laptop, i can’t reproduce the stuck issue, and so far the buttons or the stick don’t do that thing where they release after a few seconds although they are pressed …
laptop is running linux

britzl · March 24, 2020, 11:18pm

Thank you for the bug report. I found the problem and have released a new version:

kakerlaka · March 25, 2020, 12:34pm

very welcome and thank you for fixing it. i am going to check it out right now

edit:
i tried and tried to get it stuck but i couldn’t … works like a charm.
one thing i noticed though is that the analog follows the mouse on the smallest movement on the laptop but on android you tap and then have to move your finger over the analog image boundaries for it to actually start reacting. it “jumps” from resting position to where your finger is and then starts following correctly.

edit2:
the issue where the buttons and analog release (stop working, ie. buttons depress and analog goes to resting position) after a second or so is still happening on android. it’s always the same duration.