Hello, today we are excited to share with you the last major addition to UI Toolkit 1.0, namely the integration of a text engine coming directly from Text Mesh Pro. The name of this engine is TextCore and is being directly integrated into Unity, with the long term goal of supporting the entire ecosystem (including migration of existing Text Mesh Pro users). About the new engine The TextCore engine has a set of characteristics that makes it much more appealing for UI Toolkit developers: Clear separation of text layout, mesh generation, and rendering operations of text objects Signed Distance Field capabilities, which bring performance improvements and less memory overhead for multiple text sizes Ability to embed static font data and limit dependencies on FreeType in the future Since the engine is a direct adaptation of Text Mesh Pro, so it allows us to actually support many equivalent features and continue our journey towards parity with UGUI & TMP. Getting started Please have a look at this getting started guide to learn more about what this new release gives you access to. Known issues Currently the only known bug for this feature is the following: The <sprite> rich text tag doesn't work unless you run the project at runtime first As much as possible we will keep this list updated for your information Next Steps You can expect a UI Builder update very soon in order to work with the new Font Asset support and other text options. In future releases, we have some plans for the following improvements: Support rich text strings for TextFields Improve the readability of Rich Text Tags in raw UXML Support for whitespace CSS properties Support for paginated text elements Support for <link> tags We’re eager to hear your feedback on these new features ! Please let us know if this is matching your needs and what you’d like to see prioritized. Thanks.