Unity 5.3 UI Bugs

Unity Engine
1

I do not like to update the version of the large number of bugs that make Unity. But I need to do and build UWP no choice. After upgrading from 5.1 to 5.3 I have received a lot of mistakes Unity.

ArgumentOutOfRangeException: Index and count must refer to a location withing string.
Parameter name: count
at System.String.Remove(Int32 startIndex, Int32 count)
at UnityEngine.UI.InputField.Backspace()
at UnityEngine.UI.InputField.KeyPressed(Event evt)
at UnityEngine.UI.InputField.OnUpdateSelected(BaseEventData eventData)
at UnityEngine.EventSystems.ExecuteEvents.Execute(IUpdateSelectedHandler handler, BaseEventData eventData)
at UnityEngine.EventSystems.ExecuteEvents.Execute[T](GameObject target, BaseEventData eventData, EventFunction`1 functor )

ArgumentException: Mesh can not have more than 65000 vertices
at UnityEngine.UI.VertexHelper.FillMesh(Mesh mesh)
at UnityEngine.UI.Graphic.DoMeshGeneration()
at UnityEngine.UI.Graphic.UpdateGeometry()
at UnityEngine.UI.Graphic.Rebuild(CanvasUpdate update)
at UnityEngine.UI.CanvasUpdateRegistry.PerformUpdate()

Common UI Flickering…

1 Like
2
  1. Can you file a bug report with an example?
  2. Do you have a lot of UI components or are you using a tiled sprite? The vert count can shoot up quickly with tiled sprites, you can use a custom material and the tiled parameter to do this without a vert increase.
  3. Need a bug report or more information.
3

My project is too large to upload, all errors are written off with the Developer Console on my device. Error 2) also appears in the editor 5.3, but not in the previous versions Unity

Yes, I’m quite intensively use UI, but it was not a problem in Unity 5.0-5.2 on this project

4

This is pretty much preventing us from shipping. :frowning:

5

Can you submit a bug with an example?

6

It’s a big project, I wouldn’t feel comfortable sending the whole thing. I’m finding it difficult to localize, it doesn’t happen in the editor, only in the player (OS X Standalone).

7

Try cutting the project down, its often a good way to identify if the bug is in Unity or your own stuff.
This may help http://answers.unity3d.com/questions/759081/how-can-i-create-a-minimal-reproducible.html
If you can create a repro that you are happy to send then pop the bug id in here.

8

It looks like in 5.3 the placeholder text on an empty input field disappears if you click on the field. The placeholder game object is active, but the text component of the InputField.placholder is being disabled.

Is there a work-around for this?

This worked fine in 5.2, so I had to roll back to 5.2 until this is fixed.

Thanks.

9

That doesn’t sound like a bug. Why would you want the place holder text displayed if you are typing in the field?

10

Yea thats the way the input field has alwasy worked so unless you’re seeing something different then what you’ve described i’d expect it to be the same in 5.2

11

It’s not when you are typing in the field. It’s when you select the field. For example, if you select on an empty field or backspace on a field until it is empty.

I should note, I’m seeing this behavior on iOS. Not sure if it’s on all platforms now that I rolled back to 5.2

12

Ok I see what you mean. Yes that is a bug. I’ll take a look.

13

Thank you Karl!

I have an event handler when selecting the input field, so any suggested work-around to allow us to enable the Placeholder text component is welcome.

Best,
-Mike

14

Is there a bug number for this? Was it fixed in 5.3.1?

Thanks,
-Mike

15

I don’t believe its been fixed yet. The holiday period has delayed things. Its on my todo list this week.

16

Hope you’ll fix this, too:

It’s been two months already and still no news.
I had to review and redo my inventory UI due to this bug. And still haven’t found workarounds. The only option is to remove size fitter and calculate size in the script, and that (in case of collections and multiple screen size support) is a pain you know where…

17

Both these bugs have already been fixed. I have put backport requests in for both and they should be in an upcoming patch. They probably wont be in the same patch as the content size fitter bug is still being reviewed whereas the placeholder fix is already in 5.4.

18

Thanks Karl. Happy New Year!

19

It’s 5.3.1p3 already and still there’s no fix. The issue is closed and marked as fixed. What’s going on?

2 Likes
20

The issue is fixed but its still on the way to a release. It got held up during code review as its batched in with lots of UI fixes. As soon as it lands it will go straight to a patch release.

1 Like