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. Join us on Thursday, June 8, for a Q&A with Unity's Content Pipeline group here on the forum, and on the Unity Discord, and discuss topics around Content Build, Import Workflows, Asset Database, and Addressables!
    Dismiss Notice
New Forum User Notice Content Pipeline Dev Blitz Day

TextMesh Pro TextMesh Pro package version 2.0.0 for Unity 2019.1 requires .Net 4.x Scripting Runtime

Discussion in 'UGUI & TextMesh Pro' started by Stephan_B, Apr 16, 2019.

  1. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    Since the old .Net 3.5 Scripting Runtime was deprecated in Unity 2018.3, it will be necessary to upgrade the Scripting Runtime of your project to use .Net 4.x when upgrading to Unity 2019.1 and to the version 2.0.0 of the TextMesh Pro package.

    To switch the project to .Net 4.x, go to the menu "Edit - Project Settings" and switch the Scripting Runtime version to .Net 4.x as seen below.

    upload_2019-4-16_14-24-59.png
     
    Last edited: Apr 16, 2019
    Stephan_B, Apr 16, 2019
    #1
    Gusts92, nkcowmaster, michael554466OG and 1 other person like this.

  2. nkcowmaster

    nkcowmaster

    Joined:
    Jun 28, 2013
    Posts:
    4
    Exactly what I needed. Thanks!
     
    nkcowmaster, Apr 30, 2019
    #2

  3. jayatubi

    jayatubi

    Joined:
    Dec 9, 2013
    Posts:
    143
    Any new features compare to the 1.4.1?
     
    jayatubi, May 9, 2019
    #3

  4. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    1.4.1 and 2.0.1 are the same with the exception of 2.0.1 having a dependency on UGUI and using .Net 4.x (mostly the syntactic sugar part of it for the time being).

    UGUI was supposed to be a package for 2019.1 but didn't make it in time. A wrapper was added to allow TMP to treat the still internal UGUI as a package so that when UGUI become a package, version 2.x of TMP will simply work.
     
    Stephan_B, May 9, 2019
    #4

  5. MrPhilipJWilliams

    MrPhilipJWilliams

    Joined:
    Nov 4, 2018
    Posts:
    3
    This fixed it. THANKS :)
     
    MrPhilipJWilliams, Jun 18, 2019
    #5

  6. WhitethornDigital

    WhitethornDigital

    Joined:
    Aug 12, 2018
    Posts:
    46
    Weird question, but we're working on porting a game using the 2017 LTS that is written in .NET 4.6. Is it possible to get the .NET 4.x version of TextMesh Pro on this version of Unity? The Asset Store version is 1.2.2 and 2017 doesn't have the package manager window (that we can find). We've run into a bug that we are 99% sure is related to the mismatch of our scripting backend and the targeted platform for managed plugins that we're using. Thanks!
     
    WhitethornDigital, Jun 18, 2019
    #6

  7. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    The Unity 2018.3 or newer versions of the TMP package require the new FontEngine which was introduced / included with Unity 2018.3. As such, it is not possible to use these newer versions of the package with previous versions of Unity.
     
    Stephan_B, Jun 18, 2019
    #7

  8. WhitethornDigital

    WhitethornDigital

    Joined:
    Aug 12, 2018
    Posts:
    46
    That makes sense! Thanks for the quick response, we appreciate it
     
    WhitethornDigital, Jun 19, 2019
    #8

  9. ProducedByTiG

    ProducedByTiG

    Joined:
    Sep 30, 2018
    Posts:
    1
    Thank you ! after upgrading unity, I was getting the error:

    "Feature `out variable declaration' cannot be used because it is not part of the C# 4.0 language specification"

    and this fixed it !
     
    ProducedByTiG, Jul 26, 2019
    #9

  10. itmahahm73

    itmahahm73

    Joined:
    May 18, 2019
    Posts:
    1
    Thank that is i want,very thanks.......
     
    itmahahm73, Aug 17, 2019
    #10

  11. StacticKoud

    StacticKoud

    Joined:
    Nov 29, 2018
    Posts:
    8
    StacticKoud, Sep 9, 2019
    #11

  12. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    Stephan_B, Sep 9, 2019
    #12
    StacticKoud and michael_looply like this.

  13. StacticKoud

    StacticKoud

    Joined:
    Nov 29, 2018
    Posts:
    8
    Any news about the release?
     
    StacticKoud, Sep 23, 2019
    #13

  14. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    Currently going through the release process. Ran into a minor issue with package release automation which should be resolved tomorrow. So unless I run into some unforeseen issue, new release should be available within a few days.
     
    Stephan_B, Sep 23, 2019
    #14

  15. StacticKoud

    StacticKoud

    Joined:
    Nov 29, 2018
    Posts:
    8
    Great! Hope that the new version resolves all our issues.
     
    StacticKoud, Sep 23, 2019
    #15

  16. AlexWijnbeek

    AlexWijnbeek

    Joined:
    Sep 7, 2018
    Posts:
    1
    Could you give an indication of the status of the new TMP package? I'm really looking forward to all the fixes in this release!
     
    AlexWijnbeek, Sep 30, 2019
    #16

  17. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    Late(r) today.
     
    Stephan_B, Sep 30, 2019
    #17

  18. MrLucid72

    MrLucid72

    Joined:
    Jan 12, 2016
    Posts:
    892
    For anyone using GameSparks, note that TMPro will throw errors when you build in 2018! Amazon has no plans to support 4.x. Seems to work in 2018.

    Sadly, 2018 is the end of the line for GameSparks users. I'll poke them to open source the code if no fix is planned :p
     
    MrLucid72, Oct 4, 2019
    #18

  19. Stephan_B

    Stephan_B

    Unity Technologies

    Joined:
    Feb 26, 2017
    Posts:
    6,588
    BTW: I reverted the .Net 4.x changes to the TMP package in 2.1.0. This is temporary in the sense the Unity itself will eventually deprecate .Net 3.5 but until then, TMP is back to no longer requiring .Net 4.x
     
    Stephan_B, Oct 4, 2019
    #19
    MrLucid72 likes this.

  20. MrLucid72

    MrLucid72

    Joined:
    Jan 12, 2016
    Posts:
    892
    Woot! No worries, the longer this can be temporarily "delayed", the better. Reports say it's really only TMP that has the errors (for now). Understandable when you can't do this anymore. For now, it allows us to get another year of updates because of this.
     
    MrLucid72, Oct 4, 2019
    #20