Unity 5.3.0f4 Touch Bug

Unity Engine
,
1

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.

2

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

3

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

4

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.

1 Like
5

Following a (temporary?) solution found in this thread 5.3 Android SG6 Framerate Dropped Significantly - Unity Engine - Unity Discussions
I have disabled Opengl ES3 in the player settings. That at least solved the framerate issue.

6

Same problem with touch on IOS & android in 5.3

7

@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?

8

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

9

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.

10

@Trav3l3r what is the case number?

11

Case 753711

12

800×450 77.3 KB

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)

13

@bitter : any news regarding this case?

14

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

15

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.

16

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.

17

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

18

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 :frowning:
I understand there’re a lot of bug reports to go through, but a reply in some form would have been nice…

19

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

20

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.