TextMesh Pro Migrating from Legacy / Asset Store to Package Manager Releases

I'm parsing program source code that supports inline XML documentation, at the same time I add my own tags as markers for certain things. (like <1>, </1>, ...)

Using \u003C \u003E works only when I manually toggle "Parse Escape Characters" off and then back on. The text doesn't change though, but ingame it does. I'll record a gif to show what I mean because that might be a little confusing.

 

Actually it always does that whenever the text is refreshed.

All I'm doing in my code is setting the string using the SetText(string) method. I'll try toggling it off and on again in code.

 

Thanks Stephan, that's very kind (sure you've got a zillion other things to do!). I'm uploading now and will email the link when completed.

 

I still can't understand how to fix it if I have already installed Unity 2018.1. I followed steps you describes in answer but nothing helped.
I don't see any sense in Step1 - why that empty scene should be opened at all? Why not to close all Unity editors (I got multiple versions unity Unity HUB) and even if that MUST be opened, how can I do it reinstalling 2018.1... crazy

 

Can you explain the difference between .bounds and .textBounds and what they do exactly?

I want to figure out if the cursor intersects a text by myself (meaning without IsRaycastTarget!),
so what I'm doing is

Text.textBounds.Contains(Input.mousePosition)

but that doesn't work at all.

textBounds and bounds seem to be relative (to their parent?)

How do I get the correct bounds so I can test for intersection?
Is there some other property somewhere? Or can textBounds be converted somehow?

Edit:
Figured it out, it's obvious in hindsight.
Vertex coordinates are in local space and can be transformed with

transform.TransformPoint(...)

, just like with every other local / transform pair, nothing special about TMP (fortunately).

 

I did it 5 times already, nothing helped even with empty Unity 2018.1 project

I just tried remove 2018.1.0 and install latest 2018.1.3 using Unity Hub, followed all steps and NOTHING works - TMPro namespace is still not available. Wtf..

 

Sure I did and after used Windows > TextMesh pro > Import resources

 

Hi Stephan,

Sadly, I never got the GUID Remapping Tool to work, so ended up just re-implementing all the TextMeshPro objects by hand over a couple days :-( Unfortunately, I can't feasible get you a copy of my project files.

I do have one weird question for you, though:

The bottom right of my screen is suck like this (Editor Mode and then Play Mode)



It seems to be stuck this way permanently. I've never seen this before Unity 2018.

I've never baked light in my life. In fact, my project is just audio + GUI.

What I'm wondering is, is there any possibility this is some weird after-effect of the GUID Remapping Tool? I notice there are some visual similarities, so was just curious if you use that Unity bake GUI.

The GUID Remapping Tool doesn't show a scan in progress, but still, given that the tool just didn't work for me, thought I'd ask.

 

Didn't understand any word here... Why and how should I modify these files?
screenshot
Don't you think there too many things to complete just to start using a single package out of the box? I can't access Unity.TextMeshPro namespace, it just doesn't exists, same as TMPro and other similar namespaces

 

I'm assuming that means you are not a programmer (?) In that case I'll explain:

.asmdef files are used to split the code of a project into multiple assemblies. That has many advantages that I won't explain here (google it).

If you are using .asmdef files in your own code (google what they are and what they are used for),
then your code will not be able to access the Unity.TextMeshPro classes and methods until you add the reference to it. And you do that by modifying your .asmdef file. No need to mess around with a text editor. Just click your asmdef in unity and it shows an UI.

Here's an example of my project:


There's literally nothing else to do.
1) Install package 2) add tmp ref to assemblies that want to use it 3) there is no step 3 actually... haha

GUID remapping is only needed when you want to upgrade your project anyway, so that's not something you'd have to do either to get things running "out of the box". It's just something for people who want to switch to a newer unity version with a project that's already underway.

 

The thing is I do not use it. That's why I can't understand, why it's not possible to use package as it is just after import.

 

did you try it in a completely new project?
works without any problem here

 

Yes, sure I did. I have found an option to remove VS related files but that didn't work as well. After that I changed script editor from Visual Studio for Mac to Visual Studio Code and that worked just fine - TMPro namespace become available.

That's weird.. what could be wrong with editor

 

That sounds like the solution generator code in Unity for VS is broken maybe.
But it should still work if you'd use it, like with lots of red errors in vs, but then save anyway and switch to unity. That should make unity compile your scripts and then it should work, no? Can you try that, using VS and using it even if it is marked as not found, and see if unity can compile it anyway?

VS "knows" what you can use based on the solution and project files.
So maybe those are not generated correctly by Unity on mac?
It's the only explanation I can think of, I mean if another editor thing works... hmm

But doesn't VS Code also load the same kind of SLN and CSPROJ files?
If they were really broken then the same problems should be appearing in VS Code.
I never used Visual Studio Code, just the normal VS, so maybe it does things completely differently....

 

Yes it does

That compiled, and been signed with "red" color where been used that namespace.

I just reinstalled VS and seems now it works fine. Don't know what was that..

 

The remapping tool scan is very very slow.

 

I have around 28.000 files to scan. The first 1300 files are fast, 5 seconds, but then it takes ages. I reached 2.000 in an hour but I stopped it.

Also I'm surprised that if I delete the text mesh pro package (the new one from unity) and keep my old free version the inspector of any text mesh pro editor breaks. I'm using 2018.2 b8

 

I managed to delete a lot of files that i know for sure they don't have any dependency to textmesh, run the remapping and then recover the deleted files. However, there are some gameobjects that the text mesh ugui component is missing, some are fine, even in the same prefab.

 

Please make the Font Asset Creator window resizable. It doesn't fit in my screen resolution (1366x768). I don't understand why it should be so big and unresizable?

 

No I don't remember doing that. Is there any way of fixing it without having to redo them again? I mean, I saw lots of ame objects with the script missing in the same prefab.

Also it wold be nice that the remapping tool would let you choose specific folders to scan, the project can be huge and no need to scan fbx's or other files like that.

 

Yes it worked!

Although now Rotorz ReordableList is not compatible with 2018.2, oh dear...I'm gonna stick with 2018.1 in a while...

 

The 1.3 package just throws all sorts of errors for me due to references in Examples & Extras

Code (CSharp):

1. (Filename: C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\VertexColorCycler.cs Line: 11)
2.  
3. C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\TeleType.cs(19,17): error CS0246: The type or namespace name 'TMP_Text' could not be found (are you missing a using directive or an assembly reference?)
4. (Filename: C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\TeleType.cs Line: 19)
5.  
6. C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\Benchmark01_UGUI.cs(15,16): error CS0246: The type or namespace name 'TMP_FontAsset' could not be found (are you missing a using directive or an assembly reference?)
7. (Filename: C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\Benchmark01_UGUI.cs Line: 15)
8.  
9. C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\SimpleScript.cs(11,17): error CS0246: The type or namespace name 'TextMeshPro' could not be found (are you missing a using directive or an assembly reference?)
10. (Filename: C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\SimpleScript.cs Line: 11)
11.  
12. C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\TMP_TextEventHandler.cs(89,17): error CS0246: The type or namespace name 'TMP_Text' could not be found (are you missing a using directive or an assembly reference?)
13. (Filename: C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\TMP_TextEventHandler.cs Line: 89)
14.  
15. C:\Users\tim\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.textmeshpro@1.3.0\Examples & Extras\Scripts\VertexShakeA.cs(16,17): error CS0246: The type or namespace name 'TMP_Text' could not be found (are you missing a using directive or an assembly reference?)
16.  

+ about 20 more

This is in 18.b8

-edit-

downgraded? to the 1.3.0 preview version and it seems to work fine

like the new look UI is nice

 

The new look ui? Are you referring to the dpi feature they did on 2018.2?

 

Hey All. Does anyone know if TMP supports Stylistic alts (salt) of a font? If so how do you access them? or is it possible to remap a character to its salt?

 

Is there anyone have a problem with using TextMeshPro along with AssetBundles?

I loaded a scene with TextMeshProUGUI, and all the text become "pink color"

 

I have another BIG Problem.

I checked the remapper source Code to find out why my main Scene file is never showing in the file list. ​

The Remapper Tool can't open my main scene file ( ~ 600 MB ), so there is absolut no conversion on this Scene file.
This is the line from the remapper script:
assetDataFile = File.ReadAllText(projectPath + "/" + assetFilePath);
My main Scene was not open at this time.

EDIT: I found out it's a outofmemory exception

Any Ideas ?? :/

 

Is there a scripting symbol for TextMeshPro I can use to integrate it with my plugin?

 

Keep getting a console error when using the Package Manager version of TMP.

This is in a new project using 2018.1, whilst everything still works this error keeps getting in the way. I can get it to go away by adding that font/ folder structure to the project - but we don't want it in the project.

 

Hey Stéphane,

I've just upgraded TMPro to the Package Manager version within 2018.1. The whole thing went completely smoothly. I wanted to say thanks for providing such a nice upgrade mechanism and instructions.

Alain-Daniel

 

I've followed the steps and I don't have any errors. However, my scripts no longer like my "using TMPro;" directive. Is there a new namespace that I need to use? If not, how do I now access the TextMeshProUGUI ui text components via script? Thanks in advance for any help.

 

So far I've tried this process for 2018.2 because I was using the Text Mesh Pro plugin for 2018.1 and never ran into any errors or problems. With 2018.2 I have the problem of errors based on there being 2 Text Mesh Pros (Plugin and Unity Package). Following the process listed above I get through Project Files GUID Remapping (after it informs me I need to change Asset Serialization from Mixed to Force Text before it can do the scan) but the areas where I was using Text Mesh Pro from the Plugin are left as "Missing" at the end of the process. Is there possibly something I am doing incorrectly within the described process? I don't want to end up having to manually replace every Text Mesh Pro in my Unity Project.