I don't see how changing to Mobile Distance Field shader would help. I tried that and it just gives me less spectacular looking text, but still with shadows. As far as Material Presets, as I said I just copied this from one of your samples and made a few tweaks. It's using the Bangers SDF Logo material.

• Mac Viewer For Windows
• Picture Viewer Mac

Our software library provides a free download of PEVSoft Trainz Mesh Viewer 2.29.0.53. The size of the latest setup package available for download is 633 KB. The most popular versions of the PEVSoft Trainz Mesh Viewer 2.2 and 2.1.

I also don't see how this has anything to do with turning shadows on/off with the Mesh Renderer. When I turn them off, they work fine in the Scene view, but when switching to Play mode, the setting automatically gets turned back on and remains persistent even after stopping the game. This shouldn't happen. Click to expand.I am trying to make sure you use the correct shader for the job. The mobile Distance Field shader has been performance overall as it does not receive lighting from the scene nor is it capable of casting shadows. So unless you specifically want the scene lighting to affect the text and to cast shadows, you should be using either the Distance Field Shader or the Mobile Distance Field Shader. Note: There is a Distance Field Surface and Mobile Distance Field Surface shader both of which received scene lighting and can cast shadows.

In my previous post and comment above, I am suggesting you switch to the non-surface shader versions since you don't want shadows anyway so why not use the more efficient shaders. As far as the enabling or disabling Cast Shadow in the Mesh Renderer when using either of the surface shaders, I am looking into the state changing when entering or existing play mode and will get back to you shortly. I'll go back to the previous release to test this but be sure to get the latest release from the user forum since it includes the new support for Multi Font & Sprites along with Fallback font support and more. Update Make the following changes in the TMProPrivate.cs file.

The line number could be slightly off depending on the version of TextMesh Pro that you are using. Release 0.1.54 Beta 2 of TextMesh Pro with new TMP - UI - Input Field is now available on the user forum. This release includes a few new features and some minor bug fixes. See the release notes on the TextMesh Pro user forum for details. Note: The TMP - UI - Input Field is based on the Unity - UI - Input Field and mirrors its functionality. This is the first release (alpha) of this new component.

Rich Text and Multi Font & Sprites isn't support yet in the Input Field but I will adding such support in the new few releases. Click to expand.It does not support Dynamic Font Atlasing. It does however allow you to define what characters you wish to include in your Font Asset which is static and will work for any point size or resolution unlike the dynamic fonts which needs to at render the characters for each point size and style like bold or italic and add them into the font texture atlas at runtime resulting in performance overhead. For most languages which have fairly small character sets, adding all the needed characters into a font asset has always been pretty straightforward. It is also possible to combine multiple languages (most Latin based, Cyrillic and other) into a single Font Asset. Furthermore, since most projects / games rarely include more than 1000 - 1500 characters, it was easy with the 'Characters from File' option to create Font Assets that included all the known (in use) characters that were needed. Since most studios use Language files for localization (text files which contain the translated text), they already had all the information needed to determine what characters to include.

The primary justification for using Dynamic Fonts has always been languages like Chinese, Japanese and Korean which have much larger character sets. Sort of too large to include into a single font asset. Keep in mind that this was still manageable and possible with a single font asset since again even for those languages, most games don't include more than 1500 characters. However, where the issue became more significant was user input where it became harder to manage. Having said that, with release 0.1.54 which is available on the user forum, I introduced support for Multi Font & Sprites in TextMesh Pro along with support for Fallback Fonts. By using the Fallback font system, it is now possible to distribute the needed characters into multiple font assets thus making it possible to access as many characters as possible. See the following videos.

So in the case of the Chinese language, you can now easily create a primary font asset which includes all the known text in your title. Then for the unknown text, you can create additional font assets which include the rest of the characters that are likely to be used.

According to the Chinese government, 99.9% of text is found in the which is 8105 characters which are broken up in Frequently used characters and commonly used characters and the rest. With this information, you can then create a Fallback Font Asset which includes all the commonly used characters (minus those already included in your primary known text font asset) and then another with the frequently used character again filtering out those you already have in the other Font Asset and Fallback. I realize this is more work up front but like I said since most studios already have the localized text files, this is fairly simple to handle and offers the best performance since the Font Assets are static and work for all point size and resolution and guaranteed to look the same on all devices. Again, keep in mind this is mostly only relevant for CJK as other languages are much easier to deal with given they don't include that many characters.

Click to expand.A shorter answer: The only feature of 'dynamic font' not supported is using the native target platform font. Note: dynamic font is not required for localization or even chat box. Example: using a Chinese font (8230+ glyph, 2Meg), with zero CPU overhead. All of the Glyph data is store in GPU memory.

And you get sub pixel rendering at any scale. One good thing in not depending on a platform font (beside the better performance) is that you are guarantied that your text will look perfect and identical on all platform. From windows phone, mac, PC to a Ps3. At the moment I am using the Unity UI system too display some text. But the Text component renders my font incorrectly. So I was wondering if TextMesh pro has beter support for the features I need.

I have two problems with the Text component from the Unity UI: The fist one is that when fading a text with overlapping characters results in a bright spot in the overlapping area see: for further details The second problem comes in play when applying a outline and a shadow to the Text component and then fading the text to say 50% opacity. This result in a too gray text see this question for further details:. I am hoping that TextMesh pro is capable of those thing described above. Click to expand.In short.

In your example will render as you expect. Will render the same First problem results from having each letter rendered individually Second problem results from each layer of each character rendered individually TMPro will solve your second problem Since even if you have an outline, shadow, glow, etc. Its rendered in a single pass But each character are still rendered sequentially, so semi transparent character that overlap will look the same as your first example. To address that, you need to render the layer that you will fade into a render texture. Note: TMPro let you animate/control 5 transparency property individually: The outline, the face, a secondary layer, a glow and the overall character.

Click to expand.Here is a proof of 2 & 3 solved I cant help on how to manage render targets. So my only suggestion would be to look at Unity doc and ask for help if this is not covered. Here is another example. Bigger so you can take a closer look. The outline is white and about 50% transparent The face is red and fully opaque The shadow is black set to be about 30% soft And each character transparency is going to 100% to about 30% The outline, face, shadow blends as expected. All in one Draw call, 12 Triangles (2 per character). Click to expand.There are two resources folder in the package.

The first, the 'Examples' folder and included files and sub folders which includes a Resources folder can all be removed since they are examples. The remaining files in the 'TextMesh Pro/Resources' folder which includes the Default Arial SDF Font Asset, the Default Sprite Asset, the shaders and related files, the TMP Style sheet, the TMP Settings file and the language line breaking file are all essential (unless see below). If you have assigned an alternative default font asset in the TMP Settings file and an alternative Sprite Asset then both ARIAL SDF and the Default Sprite Asset can be removed. The other files are mostly data and much smaller. Depending on which shader you use, you could also exclude some and could using the project settings - graphics to choose which get includes. Click to expand.The latest release is available on the TextMesh Pro user forum, so I suggest you upgrade to this one first.

Next, make sure you read the release notes and upgrade notes. For instance, when upgrading to a new release, you have to remove the previously installed version of TextMesh Pro before importing the new one. This is required since Unity's Asset Importer isn't an installer and can only add new files. It has no ability to deal with files are no longer in use and should be removed. Hi there First of all, amazing tool.

I'm kicking myself for not picking this up years ago. Apologies if these have already been asked (I wish the unity forums had a 'search this thread only' option ) 1) Is there a way to choose default settings for text objects? If not it would be nice if there was a panel to setup some default options (eg.

Orthographic enabled, default font type etc.). 2) That 'extra settings' panel is really hard to spot - I noticed it's tricked many others in this thread with it's small size at the bottom of the panel. Can I suggest that this is either open by default or just have the settings moved into the main panel? 3) I noticed that if I place a text mesh in my game that is not part of the canvas (so it's using a text container + TextMeshPro script, not TextMeshProGUI) it converts the Transform component to a RectTransform.

Is there a reason it doesn't leave it as a regular transform? 4) Is there a reason why Dilation only goes up to a max value of 1? I modified the shader to allow a larger value and in some cases it seems I can just keep increasing the size just fine, where as others it seems it caps itself at size 1 even if the shader allows more. I had some small text that I needed a slightly larger white outline than what 1 allowed. 5) When creating a new text mesh, using the 'Create' option in the hierarchy toolbar puts the new textmesh in a seemingly random place in the hierarchy. I had a look at the code and it seems to be trying to put it under the first parent canvas it finds, but in my case it seemed to be going up to the root folder, but then if I was 2 folders deep when I clicked create it places it inside the second folder at the root level. I eventually found out you can right click instead and it will always create it as a child of the current highlighted folder, which seems to make a lot more sense.

Not a big deal but it was confusing at first. 5) When creating a new text mesh, using the 'Create' option in the hierarchy toolbar puts the new textmesh in a seemingly random place in the hierarchy. I had a look at the code and it seems to be trying to put it under the first parent canvas it finds, but in my case it seemed to be going up to the root folder, but then if I was 2 folders deep when I clicked create it places it inside the second folder at the root level.

I eventually found out you can right click instead and it will always create it as a child of the current highlighted folder, which seems to make a lot more sense. Not a big deal but it was confusing at first. TextMeshPro 0.1.54 Beta 3 Release Notes (On the Asset Store) Please carefully review the release notes before upgrading and always backup your project beforehand. These notes reflect the changes between release 0.1.52 Beta 3.1 and this new release. For quick reference here are the release notes for. Upgrade Note - Since Unity's Asset Importer doesn't remove older files or can get confused at times, you have to remove the previous installation of TextMesh Pro by deleting the 'TextMesh Pro' folder.

This process works well as long as you didn't save any font assets, materials or any files inside the TextMesh Pro folder hierarchy. If that is the case, then be sure to backup those files first. Important Note I - This release still includes significant changes to both TextMeshPro components. This new release will also affect previously created objects that were using sprites so as usual and despite all the testing I have done with various scenes and projects, please make sure you backup your projects before upgrading to be on the safe side. Beta Release - This release is considered Beta (for real) as the changes brought about the support for Multi Fonts & Sprites are pretty significant but more importantly rather difficult to anticipate all the different ways that users might end up using these new features in projects and via scripting.

Besides finding potential bugs, the goal of this beta is to uncover potential workflow challenges, potentially missing API functionality, and help evolve best practices related to these new features including the Font Fallback system. New Features and Functionality. Added support for Multi Fonts & Sprites. I am currently working on an updated video for this feature.

In the meantime see the following which will still provide a good overview of this new feature. Added new tag. Note the name of the font and material are case sensitive.

switches to the previously used font. switches to the default font assigned to the text object. Revised tag implementation. Note The sprite assets must be located inside 'Resources/Sprites/.' . As per the previous release, the 'tint' and 'color' attribute can also be added to the sprite tag. Added support for Font Fallback which can be defined in the TMP Settings file.

See the following for further details. Improvements & Fixes. Fixed an issue where the reference to the CanvasRenderer could be lost. Fixed an issue where the text alignment could be wrong when using Overflow - Ellipsis or Truncate mode.

Fixed issue where anchor positions of the Text Container when loading a scene created with a previous version of TextMesh Pro. Fixed an issue with scaling where the text could be rendered as blocks. Improved how fading of the face, outline and underlay portions of the text is handled in the shader.

Updated the Font Asset Creator to improve handling of OTF fonts. Improved handling of ZTest when using the Canvas system.

Mac Viewer For Windows

Fixed a few minor issue related to the Text Container and newly added support for RectTransform. Fixed an issue related to text alignment when using sprites. Improved handling of Line Height and Line Spacing. Font Asset Creator now shows Hex value of missing glyphs as well as Decimal value. Improved handling of Undo / Redo related to Material Preset Drag-n-Drop functionality.

Updated how the SDF Scale is updated when only the scale or lossyScale of a text object is changed. Fixed an issue where using the color or tint attribute with the sprite tag would affect all sprites. Fixed null reference issue which could occur when getting preferred values on disabled objects. Added ClipRect property to the material debug panel. This is used for debug purposes.

Improved upgrade compatibility with pre Unity 4.6 releases. Added tintAllSprites to TMP Settings.

Kerning is now disabled by default in the TMP Settings file since most users don't import kerning pairs in the first place. Fixed a minor issue related to word counting when using quotes at the start of the text input. Fixed a minor issue with the tags not working with East Asian languages. Updated the list of leading and following line breaking characters for East Asian Languages. Added support for Zero Width Space. Added the beta RTL support to the TMP UGUI component. Fixed an issue where re-parenting a text object to another canvas result in some events being ignored.

Added new overload for SetText to use StringBuilder. SDF scale encoding is now using the lossyscale.y due to Unity's CanvasScaler change in 5.4.0b5.

Repacked the sprites used in the Default Sprite Asset into a smaller 512 X 512 texture. Text objects now properly get refreshed when new Fallback Fonts are added to the list.

Beta 1b. Sub Text objects are now created using the same Layer as parent.

Beta 1b. Sub Text objects using the Mesh Renderer are now created with the same Sorting Layer and Sorting Order as their parent. Beta 1b. Fixed an issue where material references would be lost on object using a material preset and UI.Mask when updating from a previous release.

Beta 1b. Made a minor change to the UpdateSDFScale to avoid updating it when the text is either empty or null. Beta 1b. Fixed an issue with the shaders which resulted in text objects not being visible in Unity 5.2. Beta 1b.

Added the ability to assign a new Material Preset to multiple text objects via Drag-n-Drop. This works as long as the text objects share the same Font Asset and Material. Beta 1b.

Fixed an issue related to UI.Mask and material references eventually getting lost as object are enabled and disabled.Beta 1b. Fixed an issue where bold text was no longer bold when scaling.Beta 1b. The sprites used by text objects in the scene will now update right away when changing the Default Sprite Asset assigned in the TMP Settings file.

Beta 1b Beta 1c. Fixed an issue when using the sprite name tag attribute that was resulting in allocations. Improved how missing glyphs are handled. The assigned Font Asset will be searched first.

Next the Font Fallback list will be searched. If the glyph is not located, TMP will then look for the missing glyph character (9633) in first the currently assigned Font Asset. Next the Font Fallback list followed by the Default Font Asset assigned in the TMP Settings file and lastly try to locate the ARIAL SDF font asset. In the event neither of these glyphs can be located, the character will be skipped. Added the ability to define Fallback Font Assets for individual Font Assets in the Font Asset Editor Panel. See the for details.

Picture Viewer Mac

Fixed an issue where the font atlas texture reference could be lost in Material Presets when updating a Font Asset and saving over it. Added a new context menu option in the texture editor to allow copying the Font Atlas Texture from the Font Asset. See the following and video for details. Updated GetStencilID to avoid allocations. Fixed an issue resulting in the xAdvance value of characters in CharacterInfo not being accurate. Fixed an issue related to linefeed where a long word on the subsequent line would not render correctly. Added validation on sprite tag index and name.

Fixed a minor issue that would cause the wrong atlas to be used when a new font or material is assigned via scripting. Improved how TMP Settings are loaded and accessed. Fixed an issue where the underline thickness was incorrect due to the scale of sprites. Fixed an issue where the vertex color gradient was affecting the sprite color regardless of the tint attribute value. Added check to filter out duplicate kerning pairs from font files.

Fixed an issue in the Font Asset Creator that was causing the default material to not have a valid reference to the font atlas texture. This only occurred on first use. Fixed a minor issue with Match Aspect Texture mapping option. Sprites are no longer affected by bold or italic styles. Added new Context Menu to the Sprite Asset Editor to Add Default Material to the selected Sprite Asset. Fixed an issue where the GetLinkID function would not return the correct value when the link was part of a style tag. Fixed a minor issue with the and tags.

Beta 2. Fixed an issue to make sure lineInfo.lineExtents data is correct.

Added property bool isRightToLeftText to enable or disable RTL support. Fixed an issue where the Cast Shadow property on the Mesh Renderer would always get set to On when using one of the surface shaders. Added drawing of LineExtents in the TextInfoDebugTool.cs. LineExtents are drawn as grey lines. Added the ability to select a Material Preset from the TMP Inspector panel.

See. Added CrossFadeColor and CrossFadeAlpha functions to the TMPText class. These functions mirror the functionality of the Graphic.CrossFadeColor and Graphic.CrossFadeAlpha functions. Improved handling of text input when using the.text property. The source string will no longer be parsed. Added control over Escape Characters parsing in the Inspector Text Input Box.

Added this new property to the TMP Settings file as well as in the Extra Settings Panel. Made a minor change to further improve the handling of SDF Scale. Added the ability to drag-n-drop any Material Preset on the Material Inspector and have the Font Asset and Material automatically switch to the matching Font Asset and Material. (see video). Added new UI - TextMesh Pro - Input Field.

(Alpha). Fixed a minor issue with word tracking where quotes (single) we included as part of the word. Beta 3. Made a minor change to the handling of missing glyphs where a space will be used when no other possible glyph has been found in the font asset, fallbacks or default font asset.

Fixed a minor issue with the tag where text alignment would be incorrect. Fixed a minor issue with word tracking related to single and double left and right quotes. Added a few more Punctuation characters to the Extended ASCII set in the Font Asset Creator. Fixed an issue where the Material Preset list in the Inspector would not update correctly when no font asset is selected. Legacy InlineGraphicManager will now automatically be removed as well as any child inlineGraphic objects.

The TMPCharacterInfo.vertexIndex has been changed to an int instead of short. Added new property bool useMaxVisibleDescender to control whether the text's vertical alignment will be adjusted when using MaxVisibleCharacters. Fixed an issue with line breaking for CJK where certain characters were not breaking correctly. Font Asset embedded Default Material and Font Atlas Texture are now accessible in the project window. Improved the ability to assign a new material and font asset to a text object via Drag-n-Drop.

See. Missing glyph character can now be defined in the TMP Settings file. Added new overload to ForceMeshUpdate(bool ignoreActiveState) to make it possible to regenerate the text object even if disabled. Added the ability to retrieve the characters from an existing font asset when using the Custom Options in the Font Asset Creator.

See. Line breaking Leading and Following character lists are now defined in the TMP Settings and a shared resource for all font assets. Added support for Bold and Italic typeface which can now be assigned per font asset in the Font Asset Editor inspector. Fixed the text not disappearing when disabling the text component instead of the gameobject.

Added the KeywordOutline to the ShaderUtilities class to make it easier to enable the outline shader keyword used by the shaders. Made some improvements to the handling of Material Presets when using alternative typefaces (font-weights) and fallback fonts. Fixed an issue causing an error related to font-weights when older font assets are used. Added support for Hyphens in the handling of Line Breaking. Fixed an issue with Justified text alignment where using characters like No-width space would result in incorrect alignment.

Note (1) - Unity 5.0 / 5.1 Release of TextMesh Pro is available on the TMP User Forum. Note (2) - In Unity 5.4, you will get some warnings about line ending. This is resulting from Unity modifying the shader files on import to add the following comment ' // Upgrade NOTE: replaced 'Object2World' with 'unityObjectToWorld' and changing the shader source code to address the shader define change they have made in 5.4. Note (3) - When using the tag, the InlineGraphicManager component is no longer needed and can be safely removed. The sub objects that were using the InlineGraphic component can also be removed as they will be replaced by the new TMP Sub object of the appropriate type. Note (3.1) - As a result of changes that Unity made related to the 2D RectMask, Sprite Assets now have their own default material which uses the TMPro/Sprite shader.

When creating new Sprite Assets, a default material will be automatically assigned to the Sprite Asset. However, Sprite Assets created prior to this release will be missing this default material causing them not to render. In order to address this, you will need to regenerate the Sprite Asset by selecting the sprite from which the sprite asset was created, and right-click 'Create Sprite Asset', which will set the default material correctly. Note (4) - Due to a changes related to the handling of Masking (2D Rect Mask), when using the normal TMP objects with previously created materials, you most likely will have to reset the ClipRect property in the Material Inspector to a value of (-10000, -10000, 10000, 10000). See Note (5) - In Unity 5.4, you might be getting warnings about inconsistent line endings in some of the shader files. This is a result of Unity modifying those files on import due to them renaming a shader variable between Unity 5.3 and 5.4.

They also add the following note to the shaders '// Upgrade NOTE: replaced 'Object2World' with 'unityObjectToWorld' Note (6) - Handling of Material Preset with Typefaces (font-weights) and Fallback has been improved. However, I still need to resolve an issue when presets are manually assigned to child Submeshes. Let me suggest an interesting feature: it'd be cool to be able to add sprites in the text without having to reference an atlas. The typical use is when you have sprites which you create in code with a texture downloaded from the net. I know asset bundles may let you download an atlas, but sometimes it can't be done (think for example when you have a 3D application which lets you browse thousands of pictures and you want to display them together with text). You could have a method to add a key, Sprite reference pair to your text, letting you use the key in the text to display it, the same way you do it with sprites in an atlas. Let me suggest an interesting feature: it'd be cool to be able to add sprites in the text without having to reference an atlas.

The typical use is when you have sprites which you create in code with a texture downloaded from the net. I know asset bundles may let you download an atlas, but sometimes it can't be done (think for example when you have a 3D application which lets you browse thousands of pictures and you want to display them together with text). You could have a method to add a key, Sprite reference pair to your text, letting you use the key in the text to display it, the same way you do it with sprites in an atlas. Click to expand.The functionality that you describe is already possible. Sprite Assets simply reference a texture and the location of sprites (coordinates) inside that texture.

So assuming your texture / sprites were setup using a grid, you could write into this texture and replace its content with new images coming from anywhere. As long as the location of each sprite (coordinates) described in the Sprite Asset doesn't change, the content of what is actually there doesn't matter. Basically, you would pre-create a Sprite Asset that references a bunch of sprites setup using a grid and then at runtime, fill in this texture by writing new images into it respecting that grid. Hello, i also have the problem with the dlls, 'Failed to load 'Assets/TextMesh Pro/Plugins/64 Bit Plugins/TMProPlugin.dll' with error 'The operation completed successfully. ', GetDllDirectory returned '.

If GetDllDirectory returned non empty path, check that you're using SetDirectoryDll correctly.' 'DllNotFoundException: Assets/TextMesh Pro/Plugins/64 Bit Plugins/TMProPlugin.dll' The dlls exist. I use Unity 5.2.1.p.3 and Visual Studio 2015.

I couldn't find a solution here and i have just registered at the forums. Hello, i also have the problem with the dlls, 'Failed to load 'Assets/TextMesh Pro/Plugins/64 Bit Plugins/TMProPlugin.dll' with error 'The operation completed successfully. ', GetDllDirectory returned '. If GetDllDirectory returned non empty path, check that you're using SetDirectoryDll correctly.' 'DllNotFoundException: Assets/TextMesh Pro/Plugins/64 Bit Plugins/TMProPlugin.dll' The dlls exist.

I use Unity 5.2.1.p.3 and Visual Studio 2015. I couldn't find a solution here and i have just registered at the forums. Click to expand.Just a minor correction after I looked at the About popup, I'm actually using Unity 5.3.4p5. I checked the scale components in the hierarchy and all of them are uniformly set to 1, 1, 1 after the animation finishes (it's scaling from 0 to 1 on all axes). I'm setting up a new project to see if I can replicate it in the simplest way to send to you. I just tried replicating the issue in a new project and couldn't do it. Then I thought about the numerous errors being thrown with shader keywords (exceeding Unity's built-in limit) in my larger project and decided to package up the new project assets and import them into my actual game.

The exact same scene is now having the same issues whereas in the fresh project it's fine. This whole keyword issue is a deal-breaking plague for projects with complex assets. Anyways, thanks for the quick response. Seems like it's not your fault since several other assets (like UBER) are also failing all over because of this, but if there's anything you can do, please let me know!

On a side note, I'd also like to cast in a vote for RTL languages. I started a project several months ago involving a lot of Arabic that I think would be great with TMPro. That's when I originally started using this asset, but I also ran into an issue where I kept getting that character missing red 'X' for transliterated Arabic text. The same text worked with Unity's built-in UGUI component, but I couldn't get it to render with TMPro. Not sure if it's because the Unity UGUI component was substituting the characters to make it work or something, so this is something I might have to try again much later. And great work on this asset! When Unity isn't screwing it up, it looks great for a lot of things.

Just a minor correction after I looked at the About popup, I'm actually using Unity 5.3.4p5. I checked the scale components in the hierarchy and all of them are uniformly set to 1, 1, 1 after the animation finishes (it's scaling from 0 to 1 on all axes). I'm setting up a new project to see if I can replicate it in the simplest way to send to you. I just tried replicating the issue in a new project and couldn't do it.

Then I thought about the numerous errors being thrown with shader keywords (exceeding Unity's built-in limit) in my larger project and decided to package up the new project assets and import them into my actual game. The exact same scene is now having the same issues whereas in the fresh project it's fine. This whole keyword issue is a deal-breaking plague for projects with complex assets. Anyways, thanks for the quick response. Seems like it's not your fault since several other assets (like UBER) are also failing all over because of this, but if there's anything you can do, please let me know! Click to expand.Unity 5.0 has a limit of 128 shader keywords and TextMesh Pro uses about 9 keywords. Unity also uses some (not sure how many) but you have other addons that appear to be using a lot of them.

One possible way to reduce the keyword count on the TMP side is to remove the shaders that you are not using from the project. By editing the Shaders, you can also see how many each of the shaders are using. /quoteOn a side note, I'd also like to cast in a vote for RTL languages. I started a project several months ago involving a lot of Arabic that I think would be great with TMPro.

That's when I originally started using this asset, but I also ran into an issue where I kept getting that character missing red 'X' for transliterated Arabic text. The same text worked with Unity's built-in UGUI component, but I couldn't get it to render with TMPro. Not sure if it's because the Unity UGUI component was substituting the characters to make it work or something, so this is something I might have to try again much later./quote The is already support for RTL in the latest release of TMP. See the following thread which contains information about this In terms of the Red X, this indicates the character you are trying to render is not present in your font asset.

So you simply need to create a font asset and include this character. See the following video which covers the Font Asset Creation process as well as how to add characters for multiple languages. Click to expand.As the Font Asset Creator reports, that character is not available in this Gothic font file. Most font viewers use character substitution which misleads people into thinking a character / glyph is available in the font file when in reality it is not. As you can see from this image where I am using BMFont to look at this Century Gothic font file, it actually doesn't appear to contain any of the Arabic characters. When you are using UI.Text, unity is using another font since this Century Gothic does not contain those characters.

It begins with an almost excessive amount of dialogue, its story an exercise in cliche: Arianna is a princess of a distant kingdom who has journeyed to the city of High Lagaard. Etrian odyssey 2 untold the golden shadow.

Perhaps you are using another font file and if you provide me a link to it, I can double check. However, the report from the TMP Font Asset Creator on missing glyphs is accurate. If you had some Fallback fonts setup, TMP would also switch to a fallback font to render those missing characters.