Maybe your router then?
ishmaelmoreno
Give a shot at the hotfix I just sent online: https://github.com/Psychokiller1888/air ... construct2
I wouldn't delete up to 126 for testing, just comment out lines 114, 115, 116. Give me 2 minutes, I'll push a test version on my git
Grab a free web hosting on the net to try out your creations. I do upload on my own servers, but there are lots of free hosting plans that can give you an idea of the hosted game
Develop games in your browser. Powerful, performant & highly capable.
Have you tried to upload somewhere else and test your game not using AirConsole?
For simple property messages
OnMessageFromAnyController
OnMessageFrom
OnMessage
I usually do OnMessageFromAnyController
Then use AirConsole.DeviceId and AirConsole.Message to see what what sent
You need to know if it is the controller not sending the touches input immediately, or your game not treating the onMessage immediately because too busy per exemple
I don't know why... Do you have high latency problems when playing any other games on airconsole.com?
This is correct at least. On what devices do you experience that high latency?
How do you capture and send the button events? !!Do not use onClick or onTouch!!
I don't know unfortunately, this does not happen to me. The game runs about the same on local as on AC preview, expect for the caching part one first load of course. What kind of lag are you talking about? The game itself? Or the controllers buttons reaction time?
The fact that he doesn't care is enough. They are hiding behind an easy excuse of the drivers being the problem because they can't repro. This bug has been reported since looong and always been denied. It is not my job to look around and bring informations in that sense. I can give infos if I have them and/or I'm being asked, but as you can see, no officials ever asked anything. Bug reporting here is terrificly bad. I can act nice you know, when I'm taken serious. This is by far not the case here as you can see based on the answers you got after all the huge work you made for them trying to rule out cases and demonstrate with A+B that it is not a driver bug.
Member since 1 Apr, 2016