TextMesh-Pro native Addressables support

[Grizmu]

Is the native support for Addressables planned for the TextMesh-Pro plugin?

TextMesh-Pro uses Resources for its font assets. Adding Addressables to a project and trying to mark those font assets as addressables causes them to be duplicated inside the memory.

Current workaround is to implement this support manually. This is something that always needs to be done for memory-intensive projects, especially if there are many font assets used, so it would be nice to have a built-in solution.

Related topics:

TextMeshPro & Addressables (Asset Bundles)

There was a discussion about this on Addressables forum, but since it’s been 2 years since last official response, I’d like to get some recent insights into the situation. Our project stumbled upon this issue because we made the decision to put almost all of the game assets into Addressables (and away from Resources/ BuildSettings) except for a small Boot scene. We have a lot of UI prefabs/scenes with TMP elements that reference materials and font assets. These same assets are meant to be in R…

[Bug 1.2.4] Duplicate TextMeshPro assets in bundles

Due to the nature of TextMeshPro it stores its font & material assets in a Resources folder. Under Addressables it is listed as Build-In Data. But when you have an asset group containing a UI prefab which contains a TextMeshProUGUI element, it will build the bundle with the TextMeshPro assets as dependency inside the bundle. So each separate UI bundle will be around 424KB but it is only a prefab (See the attached bundle with Asset Bundle Browser). One workaround fix is to drag drop the Resourc…

[uDamian]

Hey, we don’t plan to add support in TMP at this time. TMP is primarily getting fixes at this time. No major improvements are planned as we focus more and more on UI Toolkit’s text solution.