2018.2 text mesh pro. plugin Errors.

Archived Forums Questions & Answers
1

After updating from 2018.1.7 to 2018.2. I get these game braking errors from text mesh pro:

120579-errors.jpg
120579-errors.jpg1926×742 287 KB

two of them are about plugins with the same name. and the rest is:
AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.textmeshpro@1.2.4/Scripts/Runtime/TMPro_Private.cs(3709,45): error CS0121: The call is ambiguous between the following methods or properties: TMPro.TMPro_ExtensionMethods.Compare(this UnityEngine.Color32, UnityEngine.Color32)' and TMPro.TMPro_ExtensionMethods.Compare(this UnityEngine.Color32, UnityEngine.Color32)'.

I also checked the location where the multiple plugins should be. "AppData\Local\Unity\cache\packages\packages.unity.com\com.unity.textmeshpro@1.2.4\Plugins" But there is only one of each plugin. I dont know why i get these errors. Reverting the project back did not help either.

 –

The same error.

 –

9 Answers

9
3
  1. Delete the old version of TextMesh Pro in the Asset folder
  2. Reopen Project
  3. Window → TextMeshPro → Import TMP essentials
  4. Window → TextMeshPro → Project Files GUID Remapping Tool.
  5. Scan & Save.

This will update the project and fix all missing TMP scripts.

See more info on my blog: makaka.org

Is there a solution for those who don't want to remove our current TextMeshPro files because we have done changes on the classes? The only solution it cames to my mind would be to change the namespace of ALL the previous TextMeshPro scripts... Anybody know / think there is a cleaner solution?

 –

I am trying this now with my several hundred complex prefabs, it looks like it will take approx 6.5 hours.. wish me luck :O

 –

Many thanks.

 –

This didn't work for me( In my empty project (no legacy!) I get these errors even after @atorisa 's 5 steps. (Project Files GUID Remapping Tool never seems to finish scanning and gives no results which I can save, though) I tried to remove the original unity 2018.2 TMP in Explorer but it appears again on unity's upstart! I'm fed up with this bug. I need to use TMP in my scripts but VS doesn't even see the namespace Please, help!

 –

When I used this method it was fine except for Prefabs that contained TMP references, which didn't get updated, so I had to manually replace those.

 –
2

Jason the senior programmer I work with says that the error is because Text Mesh Pro is now included as part of the Unity 2018.2 package. So Just delete the downloaded version and the problem will go away.

How to remove this package. I guess you are talking about removing from package manager. Is that correct?

 –

Thank you. I was struggling to fix this issue and you were right, the latest version does seem to simply include it.

 –

Thanks a lot!!! It works for me very well

 –

Thank you!

 –

it's a freeze, sorry about the misinformation.

 –
4

Thank you. I was struggling to fix this issue and you were right, the latest version does seem to simply include it.

NP, glad I could help.

 –
5

I have downloaded Unity 2018.2 started a new project and im having the same issue i haven’t upgraded an existing project. I cant seem to find an answer on the forums

When you say you started a new project, are you loading any add-ins or other tools that you use to "start a new project". I blank file with no code at all in it theoretically wouldn't have the same issue. I am not trying to be difficult just better understand you issue.

 –

Yeah, i was just about to do that. Thanks a lot mate

 –
6

Ah, thanks. for clarifying. I didn’t follow the five steps, they just helped me to recognize the problem. In 2018.2 Text Mesh Pro is built in. If you follow the 5 steps it has you re-import it. But that means you are loading it again in to your blank file. Try building a new file and not loading text mesh pro at all. then try using it as if you did load it. in the new version, it is there. It is in a different location, but it is there and you don’t need to load it at all. If you have it loaded it causes the errors.

You also don’t need to run the GUID re-mapper. Again, the way I solved the issue in my project was to manually remove the stand alone version of text mesh pro. That was the only think I need to do. It took me a bit in a legacy project to make sure I did it right, but it did work. For new projects, should be simple, create a new project in 2018.2 and then just start working. no steps. Again, I hope this helps. I understand the frustration, I was very frustrated with this as well until I finally found this post and understood the problem. (didn’t use the steps, but the post helped me to understand it was simply included in the new version and the built in version will conflict with any loaded version because of hec03’s the comment)

7

In unity 2018 I delete the some dependencies over the manifest.json in Pachages folder.
Just I can continue working.

8

Since this is marked solved without an explanation, I’ll list my fix in case anyone else sees this. I went to Project Settings>Player>Other Settings>Configuration and changed Scripting Runtime Version to .NET 4.x Equivalent, then restarted Unity.

There are explanations in the older comments and the comment that's marked as correct. Your solution may also help anyways.

 –

Here is a quick and rather simple tutorial for following and shooting at a player: https://www.youtube.com/watch?v=db0KWYaWfeM. It may seem like I'm being a jerk but I've spent years in diagnostics and have learned that the more accustomed to finding information you become, the easier it will be for you in the end. Sometimes you may be stuck for hours/days waiting for someone else to answer a question or give you the information. Hope this helps and good luck in your adventures in programming =).

 –
9

This is the best answer for me in the end , updating the project to use the latest .NET. It’s in the project settings or preferences. Thanks for that Jon Brant

Deleting the TextMeshPro folder only worked up to the next reload of the project. The .NET fix made it permanently disappear

Thank You Very much Bro!!! @HellsHand

 –
10

I just re-imported all my assets and it built fine after the error.