TextMesh Pro TextMeshPro text doesn't show up in built game

My TextMeshPro text shows up both in the Scene and Game tabs in the Unity Editor, but not once I've built the game. I've tried building for both Windows and Mac with the same result.


(in game)


(in editor)

No build errors appear in the Unity console.

Thanks,

HewwoCraziness

 

Thanks for the prompt reply!
Here's one of my broken text components in the Inspector view (all TextMeshPro components, both UGUI and InputField are blank once the app is built, but they're visible in both Scene and Game views):


Here's its parent button:


And here's the button's parent canvas:


Thanks,

HewwoCraziness

 

All components using TextMeshPro are using the Text Mesh Pro UGUI script. Would you like me to upload my scene file?

 

Sorry for the late response.

Here's the MEGA link (252 MB): https://mega.nz/#!5cEAXAAZ!aGc28ueTqHC16T-hoOztfZXPnHXIT1FbUgVNM1ECuUI
(Not sure if cloud service links are allowed, but there wasn't another obvious way to upload a large file.)

The zipped version inside the archive (NetSet_Win.zip) is an outdated build where text still works.
The folder version (NetSet_Win) is a very recent build where text is broken.

Thanks so much!

HewwoCraziness

 

@Stephan_B Thanks. This fixed my problem upgrading from 1.2.1 to 1.2.4. The text TextMesh Pro text shows up now in the build. Edit: I should mention I'm using Unity 2018.2.0b11 build. I'm a big fan of Textmesh and have been using it before it got integrated into Unity 2018.

 

I am also having problems with TextMeshProUGUI text disappearing when playing the game on a device (iOS). Everything looks fine in the editor, but not on the device.

I am using Unity 2017.3.1f1. Is there a way to get 1.2.3 or newer for 2017.3 builds?

 

Worked great, thanks! (Didn't realize I had missing variable definitions; thanks for the notice.)

 

I'm having this same issue with 2018.2.0f2 and TMP 1.2.4, from package mananger. TextMeshPro objects show as normal, TextMeshProUGUI in other hand are empty in all my builds.

Edit:
I'm building for Android;
1.2.3 does not work;
1.3.0-preview also does not work;

Using canvas in Screen Space - Camera is the only way to make the text show up.
Screen Space - Overlay does not work for any of the latest packages.

 

The scene 17 is working fine, but my scene is not working. I'm not sure what i'm doing wrong, at glance both the text componenets and canvas have the same setup apart from the font and aligment, I'm using the default LiberationSans SDF, center-middle

 

I'm having the same problem. TextMeshPro v1.2.4, installed via package manager in Unity 2018.2.2.f1. Running Unity on a Mac running High Sierra 10.13.4.

Everything looks fine in the editor, builds and shows all expected GUI elements minus text. I haven't mixed text mesh components (all UGUI).

Building for Windows works fine, though that build was built on windows using the prior version of 2018.2 (i think it was the 2018.2.1f1??) I'm working on the same project on my mac via Collab and updated it to the newest version of 2018.2.

Any assistance would be great.

Edit:

Tried setting my UI to Screen Space - Camera to no avail. I tried changing Text Mesh Pro materials from mobile to standard. This also did not resolve the issue.

 

Yep, can confirm I'm having the same issue in the Single Line TextMesh Pro scene and the Old Computer Terminal test scene.

 

No, the build with the issue is on Mac High Sierra on a 2016 Mac Book Pro. The Windows builds work fine for me too.

I'm using the standard/legacy rendering pipeline with all default settings. Gamma color space with "automatic graphics API" selected for Mac. Resolution is variable; I've jumped between windowed and full screen. There appears to be a split second of dots on the screen before the scene view pops in completely, but it's so quick that I can't tell if it's artifact of text mesh pro or just the first rendered frame popping on screen.

As for scripting back-end, it's Mono and the API compatibility level is .Net 4.x equivalent.

I'm getting no errors whatsoever.

 

I am having the very same problem using Unity 2019.1.0f2 with TextMeshPro 2.0.0. Building on Android it works fine. Building for iOS using Unity Cloud Build results in not showing all TextMeshPro texts. Furthermore, TMP_InputField also doesn't work.

I think I'll have to use Unity built-in UI components only, otherwise I'm stuck not being able make a proper build on iOS.

 

When I build to Android, none of my text are being displayed.
Neither the TMProUGUI for canvas or TMPro attached to an object at world space.

Works fine in Unity Editor.
2019.1.2 and TMPro 2.0.1

 

Are you using different assets + materials for the ugui and world space objects as suggested above? This has cleared up the issue for me. Along these lines, @Stephan_B any chance we could get this idiot proofed in a future release? At the very least, the behavior of the editor and builds should be consistent, but ideally it all 'just works' in some fashion.

 

Actually, I take back what I said. I also have this issue with TMPro and cloud build for iOS. @Stephan_B is this something you've been able to reproduce yet? My setup is quite simple, latest Unity, TMPro 2.0.1. I'm only testing world space elements, and have already assigned them a unique material (though I'm not using any UGUI components anywhere anyway).

 

@Stephan_B cheers, case 1168577, thanks!

 

We are having the same issue.

There is no mix and match of materials with UI/non UI elements. The scene is only using Unity Text and TMPROUGUI elements.

This does not happen to all our users, only some users experience this while it is fine for others.
How to debug what the cause is?

 

Hi, we are building with Unity Cloud Build and some texts are rendered in the center of the screen on Android, no matter what we do to place them correctly. We are using the "hack" with different materials mentioned above.

2019.1.10, TMPro 2.0.1.

 

One important finding here is that the texts are rendered at the correct spot if we use Vulkan rendering. With OpenGLES they end up in the center.

We're using the TextMeshPro/Mobile/Distance Field shader, and the issue is with the 3d tmpro text component.

Also running with LWRP, version 5.16.1.

 

We did not have the time to do this, fixed the issue by changing to the regular text component instead of the 3d. But the bug is easy enough to replicate - place a tmpro 3d text component in a canvas off-center. Build with Vulkan for Android - text correctly placed. Build with OpenGLES3 for Android - text incorrectly placed.

Sorry for not creating a sample project for you, we're dealing with too many Unity bugs in 2019 and simply can't spend more time on issues where we are able to find workarounds. Unity 2019.1 has been a disaster for us, costing us thousands and thousands of dollars in lost time due to serious bugs, but it is unfortunately a requirement when we need LWRP.

 

I have had the same issue.. the 3d Textmeshpro object render fine on Opengles2 and 3, but fails when I build to Vulcan. pretty sure this has something to do with it:

Flip Space Coordinates
Clip space coordinates differ by API. These are the coordinates that are output by your vertex shader and are consumed by the rasterizer. Each API's conventions are as follows:

Format: [MinX,MaxX][MinY,MaxY][MinZ,MaxZ]

• Direct3D11 and Metal: [-1,1][-1,1][0,1]
• Vulkan: [-1,1][-1,1][0,1] NOTE: Vulkan's clip space Y axis is inverted compared to other API's.
• OpenGL (ES): [-1,1][-1,1][-1,1]

 

does anyone have any news on this? we tried updating to 2018.4.7 but most of the textmeshproUGUI objects in the UI are dissapearing or switching the letters to weird things (as if the clip ranges of the material texture are all over the place). this happens when you do a build to webGL and you go fullscreen.

This thing happened to me in the editor sometimes in the past and it simple fixed itself by just hitting play in the editor, never was a problem in builds or webGL but now it seems to be.

 

Here's what I discovered today which cost me HOURS of development time.
If you change the text on a TMP UGUI component in runtime and then try to obtain the text data back from it, you get the string which was set in the inspector before you ran your game. I was hoping to have a typewriter effect for my character's dialogue but I don't think it'll be possible without using a separate string to hold the actual data it is displaying and avoid trying to pull it from the component itself.

I am running standalone Windows 32 bit and I have seen this happen in two different places using the same type of component. (Standard 2D text). Very easy to reproduce. I filed a bug report too!

What makes this particularly cumbersome is it doesn't happen in the editor player, only when you build your game.

 

this happens in a medium sized project, I'll try to reduce it to the minimum possible to give you a repro project, but in the meantime as a workaround I was thinking to have a running script somewhere that detects when the webGL player goes fullscreen and gets all the TextMeshProUGUI objects in the scene and re-renders them, how could I do this part? I know there is a method called SetAllDirty() but it's not documented so I'm not sure if it is the correct way, theres another called Rebuild() too.

 

I have found that TextMeshPro dont render on small z coordinate scale.
While it is pointless because we use 2D FullScreen Overlay Canvas, scaling canvas in Z coordinate fixed my issue.

I think this is some float precision hell because disappearing happens on different Z scale for PC and mobile

 

I dont remember exactly.
Uniform just dont work (Dont render)

Default Canvas makes scale something like 0.001 + add it as WorldCamera and set camera VOF to something small

Now it makes rectangular instead of disappear


Additionally in scene from far distance it looks wierd


Attached test scene setup

All UI works normal only TextMesh Pro get ugly

 

It is editor only and it hapend once and now all UIText in editor looks like this and it persists on entire working loop including editor version update.

Unfortunately it can t be done just because we use 3d ui on GUN that drawn in from of player hands. And UI that drawn in Gun Scope scale of up to 45 which means FOV around 2.

So for now TexMeshPro just not usable as text rendering solution for World UI for FPS Games with HUD UI and Scope scale