Unity 5.3.0f4 Touch Bug

Hi,

Since I upgraded to v5.3.0f4 from v5.2.3p2 I'm having problems with touch recognition on UI controls on Android (I haven't tested it on iOS, yet).

Basically, when you touch one control the event goes on as "down" until you touch other control on the screen. This worked perfectly well on previous versions of Unity so I don't know what changed.

As I'm also experiencing some visual glitches, I'd like to manually switch to the OpenGL 2.1 backend to see whether it has to do with the switch to the OpenGL 4.x core.

So, how can I switch back to OpenGL 2.1 backend? Thanks.

 

Anyone? How can I manually switch back to OpenGL 2.1 backend on Unity 5.3.0f4?

 

C'mon guys it's a simple question. Any mods?

 

I upgraded my project to 5.3 (from 5.23) earlier today and experienced similar issues as you describe here.
Framerate on my s6 went from a stable 60fps to fluctuating between 40~50fps. And even worse, touch controls don't seem to function properly anymore. It's almost as if they become stuck in onDown state or until the onExit has occurred.

I read in another thread that for the Eventsystem component you nolonger need the Touch Input Module, but while it didn't seem to break anything when removed, it also did not fix the problem.

Anwways, any help would be appreciated.

 

Following a (temporary?) solution found in this thread http://forum.unity3d.com/threads/5-3-android-sg6-framerate-dropped-significantly.372714/
I have disabled Opengl ES3 in the player settings. That at least solved the framerate issue.

 

Same problem with touch on IOS & android in 5.3

 

@Trav3l3r: I'm targeting OpenGLES2 only, to avoid such drops in perf.

Have tested in more devices and all are having the same Touch issue with 5.3.0f4.

I guess the QA team is aware of this, right?

 

I have made a sample project for my issues with input on mobile and send it to Unity to investigate

 

Thanks for this. Let's hope they'll have a fix soon or else it will force to roll back to previous versions.

It would be nice that someone on the Unity Team confirms they are aware of this bug, though.

 

Case 753711

 

This is a screen shot from the project I added with the case. The outlined box shows a log from a single press and release on the left button. Somehow events are now mixed, whereas this was not the case prior to 5.3
(Notice that the onEnter/onDown & onExit/onUp events on this button are linked and logged simultaneously)

 

@bitter: any news regarding this case?

 

I was kinda hoping for some feedback as well. QA got back to me with a question, and I followed up with three more replies, but it's been quiet ever since

 

By searching in the forums I found that v5.3.1 is to be released today or tomorrow. So, can someone on the QA Team confirm whether this upcoming version fixes this issue? Thanks.

 

v5.3.1 is out now but I don't see in the readme a mention to this bug. I will download it later today, so can anyone confirm whether the issue has been fixed or not on this release? Thanks.

 

I have downloaded and installed v5.3.1. The issue is still there. So case 753711 is still open.

 

Same here. No fix, no follow-up on my case report, no more answers.
Somewhat disappointing considering the time in put into reporting and setting up scenes for QA
I understand there're a lot of bug reports to go through, but a reply in some form would have been nice...

 

Not to mention that for games that rely on UGUI elements as Touch controls this is a huge drawback.

 

I have the same problem.
The first person view keeps spinning since it never registers the touch as ended.
Worked properly on 5.2.4 and 5.2.3 but in 5.3.0 and 5.3.1 this is broken.
In editor (5.3.x) the touch controls work properly.

 

Such huge bug affecting Android & IOS. UNITY please look into this...

 

Can anyone on the Unity Team confirm whether this issue has been addressed? And ETA for a fix?

 

Something may be deeply wrong with v5.3.x on this regard given that after two more versions (5.3.1 and 5.3.1p1) the bus is still there and nobody has indicated whether the issue is being addressed and or ETA for a fix.

 

I have seen more threads appear with this issue and replied there with a nod to this thread, so hopefully it will get picked up

 

Same problem here. Touch often not recognized on iOS (5.3.1p1).
This problem did not occur even once less than 5.2.x.

 

Can anyone respond with an ETA for fix, please? This is a very serious bug.

 

Good news. I received an update from QA today, stating that they've been able to reproduce the issue and that it's been forwarded to the developers.

 

Good news, indeed!

 

Good news!

 

I solved this issue enabling "Touch Input Module" and "Force Module Active" options in the EventSystem

I'm using Unity 5.3.1f1 and a MotoG 2014 and a very small project.

Try it and report please.

 

That was in fact mentioned in a different thread as well and I have found it to work. However, the 5.3 release notes say that TouchInput module is no longer needed. So while seemingly effective, I'm not sure if it should be used as a final solution.

 

No need to force the Touch Input Module, just disable the Standalone Input Module.

That was the problem for me. In previous versions of Unity I had it disabled, but when upgrading to 5.3, it was automatically re-enabled during the conversion process.

Disabling the Standard Input Module, fixed it for me.

 

Hi Yury, thanks for posting! I have replied to your email. We're not out of the woods just yet

 

Hi, I recently released an update for my Android game on 5.3.1f1 (same version as the previous) which seemingly worked fine but I was then barraged by emails and people telling me that that the touch controls are no longer responsive and sometimes take 10-20 clicks to even register! Many people couldn't even get past the main menu. The only solution for me was to roll back the update because I had no idea what suddenly caused input to stop being registered. The event system and input module was never touched.

Is this problem the one being experienced in this thread? It's extremely frustrating knowing that your game could be rendered unplayable from a bug you can't reproduce.

 

No, I've seen this issue come up in several other forum threads, (in UI section for example).
Unfortunately there doesn't seem to be a whole lot of support on this matter.
Yury replied on my submitted case suggesting a script change (as he wrote here as well). He wrote that (for him) with the change everything worked as expected on a Nexus 6.
I replied that same evening that his suggested change didn't help. At least not on my test devices (Samsung s6, HTC desire). There's been no reply in any form since then...

Some have suggested that it helps to enable the Force Module Active setting on the Touch Input Module (despite it nolonger being a required module according to the release notes). Use with care though as a user in this thread says it didn't help for him.

I assume Unity QA is quite busy with other issues, but it is somewhat disappointing to receive so little feedback on this matter.

 

As said in that post -as well as in this thread a few posts before- the workaround that works for me is to deactivate the Standalone Input Module and to activate the Touch Input module (no need to force it).

 

Since this bug is still active (and I personally just discovered this bug/thread myself), people should go to the issue tracker and upvote 753711

 

Agree, this is major, major bug
Please up vote 753711
I hope it will get fixed when 5.4 comes out

 

@iomac, have you received any feedback from Unity on your case?

 

I just encountered this bug myself on version 5.3.2f1. I upvoted the issue, hopefully it will get fixed soon.

 

Workaround with touch input module didn't help me. On issue tracker status of bug in Fixed in Unity 5.4.0. But when will it released?

 

Bump