Text Mesh Pro Dozens of errors with Unity 2019.1

[MikeUpchat]

Just testing my project in 2019.1 but I am getting dozens of errors with Text Mesh pro, I checked the Package Manager and it says Text Mesh is up to date and works with 2019.1 so why am I getting pages of errors in the console? And how do I fix it?

[MikeUpchat]

This also happens with an empty project, get loads of Text mesh Pro errors and also ‘Failed to load extension manager’ what ever that means.

[Checko]

I am getting the same issue. The TMPro namespace isnt even recognized in my project now. No text mesh pro window available in the editor either.

[Stephan_B]

Since UGUI is moving to a package, TMP now has a dependency on this package. Now for some reason, this dependency is not getting resolved correctly.

I am installing 2019.1 right now to look into this. Will post as soon as I have additional information.

[MrSkiz]

Thanks Stephan. Good luck.

[Stephan_B]

I am not able to reproduce the reported behavior.

I created a new project in 2018.3 using TMP 1.4.0 and imported the TMP Essential Resources. Then opened this project in 2019.1.0f2 and didn’t get any errors.

Please close Unity and delete the package cache to see if these errors will persist. Maybe something went wrong when the package for version 2.0.0 was initially downloaded. The package cache is located at “AppData\Local\Unity Cache\cache”.

Edit
Packages are now also cached in the local project in the Library folder in “Library/PackageCache/…” Please delete the versions of TMP in there as well.

[MikeUpchat]

Deleted cache files, and no change. If I create a new empty project I get the same errors, loads of TMPro errors and I get the failed to load extension manager spamming the console.

[Stephan_B]

@MikeUpchat

Deleted cache files, and no change. If I create a new empty project I get the same errors, loads of TMPro errors and I get the failed to load extension manager spamming the console.

Can you submit a bug report with that new project that is giving you all these errors?

Please provide me the case # once you have it.

[afonseca]

I’m having the same issue loading a project created in 2018.3.10 where TMP throws the same errors in the console. Removing the package resolves it as I’m not actually using it. However, even after clearing the package cache if I try to bring TMP back in via the package manager, it will throw the same errors.

[Stephan_B]

@afonseca

I’m having the same issue loading a project created in 2018.3.10 where TMP throws the same errors in the console. Removing the package resolves it as I’m not actually using it. However, even after clearing the package cache if I try to bring TMP back in via the package manager, it will throw the same errors.

Did you also delete the TMP package from the local project cache in the Library folder?

[afonseca]

@Stephan_B

Did you also delete the TMP package from the local project cache in the Library folder?

Yes, after deleting package cache from both locations and reloading the project, errors appear while TMP package is installed.

[MikeUpchat]

Sounds like there is an issue with this, we shouldn’t have be deleting files from numerous cache folders to get Unity to work? That’s five people who have posted the same issue here and I know two more who haven’t, that’s quite a lot.

[TabuuForteAkugun]

I’m getting 66 of those errors in my project. So you aren’t alone

[Stephan_B]

@MikeUpchat

Sounds like there is an issue with this, we shouldn’t have be deleting files from numerous cache folders to get Unity to work? That’s five people who have posted the same issue here and I know two more who haven’t, that’s quite a lot.

It is clear there is an issue but I need to be able to reproduce it in order to figure out why it is happening.

I need someone to submit a bug report along with the project or provide me with a repro project to allow me to reproduce this.

Another potential reason for the issue might be related to the TMP package now using .Net 4.x so maybe if the project is still using .Net 3.5, it confuses the compilation of assemblies.

[Checko]

I too have tried deleting the package cache from both locations but am still getting compiler errors.

this is a sample
…/Library/PackageCache/com.unity.textmeshpro@2.0.0/Scripts/Runtime/FastAction.cs(24,45): error CS1644: Feature `out variable declaration’ cannot be used because it is not part of the C# 4.0 language specification

I am also getting a similar error with the render pipeline package. Not sure of the correlation, if any. seems to be a prob with the package manager maybe?! Not sure. This is out of my wheelhouse.

RESOLVED - I changed the Scripting Runtime Version to use .NET 4.x (it was using 3.5).
Edit > Project Settings > Player > Other Settings > Scripting Runtime Version dropdown

[Stephan_B]

@Checko

Feature `out variable declaration’ cannot be used because it is not part of the C# 4.0 language specification

This is due to the new version of TextMesh Pro using .Net 4.x since .Net 3.5 was deprecated in 2018.3.

I am backing out the .Net 4.x requirements for version 1.4.x of TMP but keeping those moving forward for Unity 2019.1.

[TabuuForteAkugun]

Thanks for the “delete Package Cache” suggestion. It worked for me

[Stephan_B]

@TabuuForteAkugun

I’m getting 66 of those errors in my project. So you aren’t alone

The 66 errors are related to the need to switch the project to use .Net 4.x as per my previous post as .Net 3.5 was deprecated in Unity 2018.3.

[afonseca]

@Stephan_B

Another potential reason for the issue might be related to the TMP package now using .Net 4.x so maybe if the project is still using .Net 3.5, it confuses the compilation of assemblies.

I think you’ve got it, the project I brought along from prior versions of Unity was still set to .NET 3.5. Changing it to 4.0 gets rid of the errors.

[afonseca]

@Stephan_B Might I suggest adding some console warnings if the project is set to .NET 3.5? This might give people a clue to go look at their project settings as it’s likely to cause issues going forward.