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!

Kerning issues with Bold Fonts from 2.0.x to 2.1.x

Discussion in 'UGUI & TextMesh Pro' started by PIBOCO-Developer, Nov 25, 2020.

  1. PIBOCO-Developer

    PIBOCO-Developer

    Joined:
    Feb 10, 2020
    Posts:
    11
    I am having an issue with kerning of bold fonts a project which was previously on TextMeshPro 2.0.1 which has been upgraded to 2.1.0.

    I have attached a picture of photos of the app from 2.0.x (upper) and 2.1.x (lower). It is obvious that the kerning is less lenient in the second version, especially in the lower line ("à documenter mon expédition").

    We are using a non-bold font with bold enabled in the inspector for the component. All platforms (PC/Mac Editor, iOS, Android) are affected equally.

    Any help would really be appreciated.


     
    PIBOCO-Developer, Nov 25, 2020
    #1

  2. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    From my previous reply in the following thread.

    As per the release notes for 2.1.0-Preview.12.

    - Fixed Font Asset Bold Spacing adjustment scaling based on the text object point size instead of current point size. Case #1241132

    The bold spacing is defined per font asset where the default value is 7 where the values are expressed as 1/100 em. For instance, if the sampling point size is 90 and the text point size is 90 or 1:1 then a value of 1 for bold spacing would equal 1 pixel.

    In past, the scaling of the bold spacing was inconsistent relative to sampling point and point size of the text.

    The solution is to adjust the bold spacing in the font asset to a value that mirror the previous spacing. Once adjusted, you should be fine.
     
    Stephan_B, Nov 25, 2020
    #2
    PIBOCO-Developer likes this.

  3. PIBOCO-Developer

    PIBOCO-Developer

    Joined:
    Feb 10, 2020
    Posts:
    11
    Thank you very much Stephan! We must've missed it, CTRL+F'ing for kerning didn't return anything but I guess we just had to RTFM at little closer. Either way, it's resolved, and good to know that there was a good reason for changing this behavior.
     
    PIBOCO-Developer, Nov 26, 2020
    #3
    Stephan_B likes this.