TextMesh Pro *** 3.2.0-pre.4 Release Now Available! ***

We've got a bug to report! Emoji in a TMP UGUI component that uses a text style which uses a different font often causes the following error:

Code (CSharp):

1. IndexOutOfRangeException: Index was outside the bounds of the array.
2. TMPro.TMP_Text.PopulateTextProcessingArray () (at Library/PackageCache/com.unity.textmeshpro@3.2.0-pre.4/Scripts/Runtime/TMP_Text.cs:2233)
3. TMPro.TMP_Text.ParseInputText () (at Library/PackageCache/com.unity.textmeshpro@3.2.0-pre.4/Scripts/Runtime/TMP_Text.cs:1999)
4. TMPro.TextMeshProUGUI.OnPreRenderCanvas () (at Library/PackageCache/com.unity.textmeshpro@3.2.0-pre.4/Scripts/Runtime/TMPro_UGUI_Private.cs:1713)
5. TMPro.TextMeshProUGUI.Rebuild (UnityEngine.UI.CanvasUpdate update) (at Library/PackageCache/com.unity.textmeshpro@3.2.0-pre.4/Scripts/Runtime/TextMeshProUGUI.cs:216)
6. UnityEngine.UI.CanvasUpdateRegistry.PerformUpdate () (at Library/PackageCache/com.unity.ugui@1.0.0/Runtime/UI/Core/CanvasUpdateRegistry.cs:215)
7. UnityEngine.Canvas:SendWillRenderCanvases() (at /Users/bokken/build/output/unity/unity/Modules/UI/ScriptBindings/UICanvas.bindings.cs:96)
8.  

It's not 100% consistent, but we find we can trigger it pretty reliably in a scene with a single TMP component by jumping in and out of play mode and changing the text style. Changing to a text style that uses the same font (or even font variants - using a font file with different weights) doesn't cause the error.
Based on the fact that it sometimes works, and that it only stops working when we jump in and out of play mode repeatedly we would guess there's some sort of weird caching error going on.

 

Oh! And while I'm at it; we've found that text styles that use a different font (again, font assets that are just variants for weight/italics etc seem fine) aren't reliable. Sometimes they render in a jumbled up way. We only see these issues when the font from the style is different from the one set in the Font Asset field.

 

%50 of the PC users is affected by this bug in our game. Version: 3.0.6
Also we are not sure to use 3.2.0 pre 4. AS it says it's not ready for production and do not use it in production
What should we do? We like the 3.0.6 version, the supported font etc. we do not want new emoji things etc. we want to stay at 3.0.6 version but can you provide the fixes to 3.0.6 version?

 

I am encountering an issue with the Kerning setting for Hebrew test.
For example "כריס שבוע טוב מה שלומך?" is displaying incorrectly when Kerning is enabled with characters overlapping. This seem to be an issue with all fonts from what I can see.
Note: This wasn't the case with Kerning enabled in the previous version so I assume this is related to the change to Font Features.

Kern Off

Kern On

 

Gotcha! Took the time to put together a minimal repro; would love for this one to get fixed before the official release!
Issue is IN-35240.

 

Hi @HugoBD-Unity

I'd really like to know when this iOS emoji problem will be fixed?
For Android I just look for the emoji font in the device and use that instead of adding the font file to the project - this is the best way to handle emoji because emoji fonts tend to be way way too big.

It works fine for Android but iOS on the other hand can't do this and makes the app size about 250mb bigger.
The game I'm developing is a very lightweight, teeny tiny 2D game so it should be under 50mb but because of this whole iOS emoji thing, it ends up being over 300mb which is ridiculous for such a small game.

• Dynamic OS FontAsset has limited support on some iOS devices. The Apple Color Emoji font file found on OSX and several iOS devices works fine. However, the Apple Color Emoji-160px found on newer iOS devices is not support as the emoji's are encoded in JPEG format which is not supported by FreeType.

I'd love to get rid of Apple Color Emoji so I can simply find the font, make use of that and keep the app size small.

 

We'd also like to hear about the plan for this! We're currently prototyping but when we enter full production we're going to need a solution if we continue.

 

The size is one issue but I struggle to see how using Unity solution is viable anyway when it doesn't even support most emojis in the first place.

 

i'll don't get it....
how long do we ask for true emoji support?
we have 23 now... and still nothing serious...
btw... those Atlas are also huge for TMP to use... over 10MB each... now...
Text and Scroll rect are the biggest issues when working with Unity

 

@HugoBD-Unity are you there?

 

@HugoBD-Unity ?????????

 

I am facing a bug on the Quest 2 relating to TMP_InputField deselecting itself when shouldHideSoftKeyboard and/or shouldHideMobileInput are set to true. Digging into the TMP_InputField code, it really feels like this line of code in LateUpdate on line 1537 is the culprit.

Code (CSharp):

1.  
2.             if (InPlaceEditing() && isKeyboardUsingEvents() || !isFocused)
3.             {
4.                 return;
5.             }
6.  

On Android platforms:
InPlaceEditing() will return true if TouchScreenKeyboard.isSupported (always true on Android) and either shouldHideSoftKeyboard or shouldHideMobileInput is set to true.

Code (CSharp):

1.  
2.         private bool InPlaceEditing()
3.         {
4.             if (Application.platform == RuntimePlatform.WSAPlayerX86 || Application.platform == RuntimePlatform.WSAPlayerX64 || Application.platform == RuntimePlatform.WSAPlayerARM)
5.                 return !TouchScreenKeyboard.isSupported || m_TouchKeyboardAllowsInPlaceEditing;
6.  
7.             if (TouchScreenKeyboard.isSupported && shouldHideSoftKeyboard)
8.                 return true;
9.  
10.             if (TouchScreenKeyboard.isSupported && shouldHideSoftKeyboard == false && shouldHideMobileInput == false)
11.                 return false;
12.  
13.             return true;
14.         }
15.  

That's all good. If you want to handle the input yourself, set one of those two properties to true, but...

isKeyboardUsingEvents() will never return true on Android due to this:

Code (CSharp):

1.  
2.         private bool isKeyboardUsingEvents()
3.         {
4.             switch (Application.platform)
5.             {
6.                 case RuntimePlatform.Android:
7.                 case RuntimePlatform.IPhonePlayer:
8.                 case RuntimePlatform.tvOS:
9.                 #if UNITY_2020_2_OR_NEWER
10.                 case RuntimePlatform.PS4:
11.                     #if !(UNITY_2020_2_1 || UNITY_2020_2_2)
12.                     case RuntimePlatform.PS5:
13.                     #endif
14.                 #endif
15.                 case RuntimePlatform.Switch:
16.                     return false;
17.                 default:
18.                     return true;
19.             }
20.         }
21.  

What this means is that "InPlaceEditing() && isKeyboardUsingEvents()" will never be true on Android. The problem if statement will only ever be true if the input field is not focused.

I think the if statement should be changed to:

Code (CSharp):

1.  
2.             if (InPlaceEditing() || isKeyboardUsingEvents() || !isFocused)
3.             {
4.                 return;
5.             }
6.  

If someone has more info on this and has a good reason why it should be &&, I'd love to be enlightened, but my understanding of this bit of code is telling me it should be ||.

 

it's a joke... isn't it?
sry but we pay a lot for Unity and we are professionals and we have customers who are waiting....
damn i'll should had switched earlier to Unreal...

 

@HugoBD-Unity
I created a font asset with noto color emoji, but why is the sampling point size fixed at 109?

 

About ligatures. I was testing a cursive font in TMP, and to no surprise it didn't work very well, as the letters don't connect. I tried updating to this new version with ligature support, and while (at least) one instance is working, most of them are not. The font is Belle Allure (https://www.jeanboyault.fr/belle-allure/).

First picture is from OpenOffice, this is how it should look. Second picture is from Unity using TMP-version 3.2.0-pre.4. As you can see, the "el" - pair is working, others are not. I'm using dynamic font asset and can see the "el" ligature in the font atlas, but for some reason nothing more is utilized. I'd expect all of them font since one does? Any ideas?

in OpenOffice:

in Unity:

 

Okay, thanks for clarifying. Is contextual substitution something that will be supported in TMP at some point, or..?

 

Input Fields with Validators work fine in Editor, but are broken on devices (iOS, Android). I am not able to input any text.
Was working fine on a previous version

 

Submitted! CASE IN-40706
A bit offtopic, but wouldn't it make sense to ignore the Library folder when sending a bug report from within Unity? I just sent 1.5GB of data for a project that is less than 3MB

 

Is there an ETA on fixes for this version? We're having to perform a lot of awkward workarounds, but if fixes are coming soon we'll hold off.

 

For anyone having issues with weird lines or character shapes - for me this turned out to be caused by outdated TMPro shaders. Updating the package in an existing project does not re-import these assets. To fix reimport the Essential Resources via Window/TextMeshPro/Import TMP Essential Resources.

 

Thanks for that

 

I submitted a report for IN-35240, I've also reported a few other bugs on this post too. Generally curious to know which of all the bugs that have been reported on this post are getting addressed in the next version!

 

@HugoBD-Unity What about the issue with mobile input on webGL when the input field's context type is different from normal, example: decimal number?

Error:

Invoking error handler due to
InvalidStateError: Failed to execute 'setSelectionRange' on 'HTMLInputElement': The input element's type ('number') does not support selection.
Error: Failed to execute 'setSelectionRange' on 'HTMLInputElement': The input element's type ('number') does not support selection.
at _JS_MobileKeyboard_SetTextSelection (...i hided this part for privacy
/Build/farming_build.framework.js:10:234148
at Object.touchEventHandlerFunc [as handlerFunc] (...i hided this part for privacy)
at HTMLCanvasElement.jsEventHandler (...i hided this part for privacy)

 

Done, thank you: IN-43034

 

can I install com.unity.textmeshpro@4.0 in unity 2020.3?
Please help

 

Anything we can do to bump it? You can google the error text and find quite a few references to it (or something much like it) - heck it's even been reported again on this thread! (*** 3.2.0-pre.4 Release Now Available! ***)
I appreciate that you've got a system but it doesn't prioritise bugs that are hard to describe and only occur when using lesser used features - but we'd really like to see it fixed, given that it's makes one of TMPs most handy features basically unreliable.

 

I have a questions about TextMeshPro 3.2.0-pre.4:
Will it be updated to the release version ?
Could we use it in our project without any problem or is it better to wait release?

Thanks in advance !

 

There seem to be a few reported issues, which might or might not affect you, so I would advise you to wait.

 

@HugoBD-Unity Am I right in thinking that using this preview package is the only way to fix the custom validator issues with soft keyboards on Android (using 2022 LTS)? Other than waiting for 2023 LTS due to the UGUI merge.

 

Hi guys
I have a little problem with the emoji in Text Mesh Pro 3.2.0-pre.5


as you can see here, when I tried to paste an emoji into the text, it got completely while out (no color). Althrough I can modify the color I want in TextAsset Material (Face>Color). I tried to pull the alpha to zero like the pic below:

and the emojis then gone



Then I tried to drag the texture atlas into TextAsset Material (Face>Texture). I then drag that material into "Plane" 3D object I created. It perfectly fit in the material.


But when I goes back to TMP_Text one, it unfortunately didn't work...


Can anyone here help me through this part? Much appreciated

 

Hello Everyone here,
I am trying to Use the emoji in my project now over the Month I tried the TextmeshPro 3.2.0-pre.4.
I made the Font Asset From the Noto Color Emoji Font.
I drop it in the Fallback emoji text but when I try to paste the Smiley Emoji I Didn't Work.
Any Type of Help will be Appreciated guy's.

 

hey Hugo,
Moreover, if I tried to Paste the Unicode of Emoji in the text field this is Showing.

 

I think I found an API that supports emoji in this thread here:
TextMesh Pro - Full Emoji Support Api (emoji Sequen - Unity Forum
I wasn't test that though but maybe it'll help in your case.

 

Hey Unity, is there any ETA available on next update? Thanks!

 

A warning for those looking to upgrade to pre.5/6, which have been silently released - they're terribly buggy. We couldn't get it to compile at all on one Unity version, and once we fixed that our text seemed to have been scaled drastically. pre.4 has issues but appears to be the best version of TMP for now.
Hope this saves someone some time!

 

any idea when all these pres will converge to a complete new release? thanks

 

Our Unity rep said a couple weeks back that this package has been shelved, and isn't due any new releases. So that's it!

I'd stick with pre4, and I guess we're supposed to move over to UI Toolkit sometime in the future - some indie friends of mine warned me to wait a little longer on that though, it's not really feature complete yet.

I'd also heard that one of the devs would post about this officially last week, so perhaps there'll be something official soon.

 

pre4 has a lot of bugs though. So we won't have a proper TMPro update unless we update to 2023 LTS with runtime fees?

 

My understanding is that its simply been abandoned, and won't be updated in any future versions. So you'll just have to live with the bugs in pre4. Bit of a classic case of Unity development, unfortunately. I imagine they think the future is the new UI system. I never did see a public post from the devs, which is a shame since they told me they would.

 

this is horrible if true. do you have any new info that can confirm this? UI toolkit is garbage for complex scenarios, and in any case leaving uGUI to rot would be a stupid path for them to follow, as it's an already working, fully-featured solution. the fact that they're not overlapping them more, keeping them as completely independent instead, is just poor planning. yes, they should be independent, but you should be able to embed uGUI stuff into UI Toolkit with some custom nodes. uGUI is just too complete, I can create anything in it in a couple of hours: banking app, main menu, a tinder app, a chat app, anything -- and it works on all platforms. it's just too complete