5.3.2p4 and now 5.3.3f1 are unusable

The GUI layers glitch so bad I can’t use these updates. This mess is suppose to the a TEXT object in a Canvas. It glitches almost animated and then will pop back on its own. Playing the scene will snap it back, but then will go right back to glitches. Im back on 5.3.2p3

Have you filed a bug report? Is this only affecting text or all UI components?

1 Like

No bug report yet but I can also confirm that 5.3.3f1 (like the rest of the 5.3.x series) has flickering UI textures (both fonts and other graphics) and flickering line renderers on OSX, along with other more general performance decreases. The last stable release for us is 5.2.4f1.

5.3.2p1 was fine for me. 5.3.3f1 has glitching UI + other visual glitches later in our game.

Is it related to this fix in p3?

  • (none) - Graphics: Reduced framerate spikes where culling system could sometimes stall for several ms while waiting for jobs.

On OSX 10.11.3, iOS mode in editor.

Yes I have a Case # -
Case 773377
It happens to ALL GUI objects, with TEXT, they glitch out, with IMAGES, they randomly pick another image and also glitch out, also when they are animated, which mine are, they wildly flicker all over the screen. This is in both the EDITOR and the GAME WINDOW. Also different objects will glitch at different time, but when animating, the whole screen goes crazy. I just tried re-importing my project and let it rebuild everything. No Go. Its not usable. For me the last stable version for my project is 5.3.2p3

Sorry, yes it does, I added my reply to the bottom. Case 773377

1 Like

Having exactly the same problem with 5.3.2p4, upgraded from 5.3.2p2 btw

Can someone share a project that has the issue in 5.3.2p4? I have not been able to recreate it. Submit a bug report with the project and post the number here and I will take a look.

Case number #773684. It’s a project has the issue created with 5.3.3f1. 5.3.2p4 should has the same effect.

1 Like

Thanks. It does not seem to recreate on Windows. I have asked QA to look at it, could be something specific to Mac.

1 Like

Happening to me on OS X as well. Flickering UI is driving me insane.

Yeah, I’m having this problem as well, it’s pretty headache inducing.

Edit:

Forgot to mention, I’m on OS X v10.11.3, Unity 5.3.3f1. My Graphics are NVIDIA GeForce GT 750M 2048 MB. Let me know if you need any other information.

The issue has been confirmed as an OSX issue. The UI team are now aware and looking into it.

3 Likes

Karl, probably unrelated to the Unity UI issue but the standard line renderer has been flickering for us on OS X for the whole 5.3.x series as well. We have not filed a bug+repo but can do if one has not been submitted already.

Without starting another 5.3 quality and QA thread, I’ll just quietly say that it has been a bit frustrating how an issue like the UI texture flickering has existed for pretty much the whole 5.3.x release series so far. There have been several bug reports that I’ve seen that mention the issue, it was ‘fixed’ and noted in release notes in some 5.3.x patch and main releases, but the flickering UI issue remains on OS X. If there’s a magic tickbox somewhere for ‘please test OS X stuff a bit more’ then please +1 it from me :slight_smile:

2 Likes

I’m not aware of any issues with the line renderer flickering. Could you file a bug report please.

There must be some other contributing factor to the flickering issue or certain combination of elements that causes it. I (and most of my team) use 5.3 on OS X / iOS and haven’t encountered this issue. But I am very curious what is causing it. Should we encounter it, it’ll be nice to have a solution.

1 Like

hi Karl - yep, sure. I’ll file one later and quote the case here.
Update: Bug Report + repo: Case #774093 Trail Renderer flickering in all Unity 5.3.x releases.

3 Likes

Same issue with line rendering, here is some insight

Seems we already know about the issue Unity Issue Tracker - TrailRenderer flickers and does not render at all times

Around since 5.3.0betas - hope my repo helps. Thanks for the followup, Karl :slight_smile: