Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Font Asset Creator stuck at "Packing glyphs - Pass 8"

Discussion in 'UGUI & TextMesh Pro' started by raidshasd, Jan 18, 2020.

  1. raidshasd

    raidshasd

    Joined:
    Jan 12, 2020
    Posts:
    10
    To grant some context into perspective, I'm just done with massive s---storm of bugs, I wanted to resolve some bugs, deleted wrong things, tried to upgrade it to newer version of Unity, that created its own bugs, finally solved it, to find my entire project was thrashed by forces yet unknown.

    My first target to solve is TextMeshProUGUI disappearing, after some investigation I found out, it's because the SDF file was either empty or couldn't be loaded. I decided to delete all of the rendered SDFs (about eight of them) and decided to render them anew. I took typical steps, 
    Window > Text Mesh Pro > Font Asset Creator
    , I put a font in it, pressed the "Generate Font Atlas" button and it gets stuck at this screen:
    fac.png

    I did check whether the fonts were uncorrupted, and Windows opened them without any issue. I tried both OTF and TTF fonts, the "Save" and "Save As..." buttons are disabled and clicking them does nothing. I even tried making SDF from Arial font, that gets stuck as well.

    Unity version: 2019.3.0f5.
    TextMeshPro version: 2.0.1 [2019.3 verified]

    Edit: The included font "Liberation Sans SDF" does render a text, so the package can use SDFs and render them in scene, just not create them.
     
    Last edited: Jan 18, 2020
    raidshasd, Jan 18, 2020
    #1

  2. segant

    segant

    Joined:
    May 3, 2017
    Posts:
    196
    I think i have same problem. Some text are flickering.
     
    segant, Jan 19, 2020
    #2
    UJ-unity87 likes this.

  3. raidshasd

    raidshasd

    Joined:
    Jan 12, 2020
    Posts:
    10
    It turns out you can just uninstall the package, and download TextMeshPro as asset from Unity store. It works then.
     
    raidshasd, Jan 20, 2020
    #3

  4. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    The version of TextMesh Pro available on the Asset Store is a Legacy version that is very old and should not longer be used with Unity 2018.3 or newer. The package manager version of TextMesh Pro should be used.

    Can you provide a link to the font file that is exhibiting this behavior?

    Can you share a screenshot of the settings used in the Font Asset Creator that results in this behavior?
     
    Stephan_B, Jan 21, 2020
    #4

  5. raidshasd

    raidshasd

    Joined:
    Jan 12, 2020
    Posts:
    10
    ???

    I literally included screenshot displaying the entire Font Asset Creator window and told you that OTF/TTF fonts, including Arial (url: 
    C:\Windows\Fonts\arial.ttf
    ) won't render. Everything you asked for is in the first post.
     
    raidshasd, Jan 22, 2020
    #5

  6. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    Just tested creating a font asset using the Font Asset Creator using Arial.ttf as well as other fonts and this is working as expected on my end. The challenge now is figuring out why you are getting a different behavior on your end.

    upload_2020-1-22_12-59-43.png

    Can you check the import settings on this Arial.ttf font in the Editor?

    When I import this font in Unity this is what I get ...

    upload_2020-1-22_13-1-31.png

    If your settings match, can you see if you get the same behavior in a new / empty project using the latest package release of TMP for Unity 2019.x which is version 2.1.0-preview.3?
     
    Stephan_B, Jan 22, 2020
    #6

  7. BooTheJudge

    BooTheJudge

    Joined:
    Jan 30, 2014
    Posts:
    2
    I had the same issue recently. As I found out, in my case the problem was caused by the script trying to call Debug.Log method from a worker thread (in script TMPro_FontAssetCreatorWindow). After I commented this line, the atlas was generated successfully.
     
    BooTheJudge, May 12, 2020
    #7

  8. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    Interesting and certainly makes sense.

    Interestingly, I have probably generated 1000's of font assets without ever running into this.

    I just made the change to remove these Debug.Log from there current location to a more appropriate spot. This change will be in the next release of the TMP package.
     
    Last edited: May 12, 2020
    Stephan_B, May 12, 2020
    #8

  9. eclipse130300

    eclipse130300

    Joined:
    Dec 6, 2019
    Posts:
    32
    Stephan, I had the same issue recently. Bump!
     
    eclipse130300, Apr 19, 2022
    #9