A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
New Unity Live Help updates. Check them out here!
Discussion in 'UGUI & TextMesh Pro' started by GilCat, Dec 12, 2017.
2018.1.0b4 still has this problem.
Bug is bad but has workaround, disable CanvasScaler and enable it in Awake by script during runtime
It sounds like this issue which should be fixed in the next 2017.3 patch.
Then we can expect it will be available?
Its due next week. This week is the release of 2017.3.1f1, next week is patch 2017.3.1p1.
it's sounds good
As a rule of thumb for production environments NEVER UPDATE YOUR UNITY UNTIL THERE IS DOT ONE release ( after first patch round )
Although, it looks like in this case waiting for 2017.3.1 wouldn't have helped. ¯\_(ツ)_/¯
Today is next week, almost end of it. I assume the patch will not be out today... next week, then?
I don't know the current status. I'm waiting to hear back from the team at the moment.
I'm told that they had to do a rebuild (last minute fixes). It should be ready for Monday.
look like it's work. thanks
a great comment from c0ffeeartc is working for me. I disable to canvas scaler, apply pre-fabs, then reapply the canvas scaler. Works to get the job done. Annoying work around but a working work around for now.
NM, doesn't work... broke soon after guess because it's a prefab...
The patch is out now...
Really. 2018.1b8 still the same issue. This is getting a bit too long. Nested prefabs almost decade and this bug are like nightmares.
With all due respect, this has nothing to do with nested prefabs.
Workaround that works for me is to place an invisible; but activated and enabled TMP somewhere above my real TMP's inside my prefab. I've had no issues since. Clearly might not be viable for everyone; but hopefully that will help somebody else out - I was scratching my head trying _everything under the sun_ for a few hours, so I totally understand the frustration.
Good luck folks.
Still happens for me in 2017.3.0f3...
This issue was introduced in 2017.3.0f3. You have to get the latest 2017.3 patch.
Still having this issue in Unity 2017.3.1f1
.: EDIT :.
Disregard above as I had the issue of the Unity Store downloading an incorrect version of TMP.
Followed instructions here.
When doing so, create a New Blank scene.
Delete your previous TMP asset folder then reimport.
Once imported, restart unity.
Hopefully, unlike me... It doesn't RESET your entire projects TMP Text elements, making you type out hundreds of lines over again and adjusting their Rect Transform.
.: EDIT 2 :.
Nope... Definitely still having the issue :|
TMP Version: TextMesh Pro - Release 18.104.22.1687.3.0b3 (dll only).unitypackage
.: EDIT 3 :.
Failed to notice 'Patch' section in Unity Download area of their site.
Unity Patch Releases
I believe this was fixed in 2017.3.1.p2 or 2017.3.1.p3.
I installed 2017.3.1p1 and it SEEMS resolved but now I'm worried that I should install the latest patch before I redo all the inactive elements in my UI so i don't have to do this again.
My philosophy is to only install the bare minimum patches that cover issues you are experiencing so it would be nice to know FOR SURE which patch resolves this problem.
This is probably the worst Unity bug I've experienced since my game is kinda UI heavy and uses TMPro. Regretting that decision to try 2017.3 right about now....
Running 2017.3.0f3 and still have this problem.
As per my last post above, this issue was introduced in 2017.3.0f3. As such you will need to get the latest patch for 2017.3 which is 2017.3.1p4.
Similar issue while inheriting from UnityEngine.UI.Slider, then applying prefab moves Fill RectTransform to the side for unknown reasons.
2017.3.1p1 or later. f1 does not have the fix.
I can confirm that this bug is fixed neither in 2017.3.1p1, 2017.3.1p3, 2017.3.1p4, nor 2018.1.0b12.
It does not even need a TextMesh component, simple UI components are sufficient.
I'm about to file a bug report, will post the case number when done.
case 1019992. they answered:
We have already fixed this and problem will not appear in the newest version, at some time in the future
Still happening on 2017.3.1f1
Has there been any word on a fix?
I found this thread looking for a solution to this same bug in my own project (a UI prefab using TMP labels). I found a workaround that seems to be working for me. I had several objects in my prefab hierarchy that are disabled by default, and I would find them in code and use them as templates to create button lists etc.
When the objects were disabled, I was seeing this issue occur (it occurs even on other enabled objects in the hierarchy). The workaround I did was leave ALL objects in my prefab's hierarchy ENABLED and then via my script I would disable the templates at the start when I load the prefab in. It seems to at least temporarily have fixed the issue I'm seeing.
Good luck! Hope this helps someone.
@karl_jones this only applies for the TextMeshPro problem, right? Would you know what happened to case 1019992? I hate to say it, but "will not appear in the newest version" is not helpful, there's too many. How do I find the version this has been or will be addressed?
Looks like that case is marked as resolved.
My recommendation would be to get the latest patch for 2017.3 or 2017.4. Make sure you backup your project before updating and then see if you still run into those issues. Again as far as I know these RectTransform issues have been addressed in those most recent patches.
I had the same problem, I fixed it by keeping the TextMeshPro UGUI object under an empty game object,
I still have this problem in 2017.4.1f1 and it's pretty annoying.
2018.1.0f2 and the problem is still here.
Are you referring to this https://issuetracker.unity3d.com/is...ther-ui-elements-when-canvasscaler-is-enabled ?
That was fixed during beta in 2018.1.0b5, If you are still having problems then please file a new bug report.
I can confirm the bug is back and also mouse clicks are detected on different places on screen than the button resides. 2018.2b6
Could you please file a bug report.