Search Unity

TextMesh Pro TMPro update to 2.1.5 causes 'RuntimePlatform' does not contain a definition for 'PS5'

Discussion in 'UGUI & TextMesh Pro' started by Peter77, Apr 17, 2021.

  1. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,609
    I use Unity 2019.4.20f1 and updated TMPro from 2.1.4 to 2.1.5 through the Package Manager.

    After the update was complete, Unity printed the following errors to the Console window:
    Code (CSharp):
    1. Library\PackageCache\com.unity.textmeshpro@2.1.5\Scripts\Runtime\TMP_InputField.cs(431,42): error CS0117: 'RuntimePlatform' does not contain a definition for 'PS5'
    2. Library\PackageCache\com.unity.textmeshpro@2.1.5\Scripts\Runtime\TMP_InputField.cs(455,42): error CS0117: 'RuntimePlatform' does not contain a definition for 'PS5'
    3. Library\PackageCache\com.unity.textmeshpro@2.1.5\Scripts\Runtime\TMP_InputField.cs(482,38): error CS0117: 'RuntimePlatform' does not contain a definition for 'PS5'
    This error caused Unity to reimport all assets in the project when I restarted the editor to check if a restart "fixes" the errors (as with so many other Unity errors). However, I terminated the Unity process when I saw Unity is going to reimport everything and changed back to 2.1.4 in packages.json instead, to avoid the reimport.

    I assume the "'RuntimePlatform' does not contain a definition for 'PS5'" isn't just going away with an editor restart.

    How can I upgrade from 2.1.4 to 2.1.5 using Unity 2019.4.20f1?
     
  2. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,609
  3. Stephan_B

    Stephan_B

    Joined:
    Feb 26, 2017
    Posts:
    6,595
  4. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,609
    Because it requires everybody on the team to update Unity too. It costs time and effort that we need to spend on the project instead. We don't take Unity updates that lightly when it affects a group of people.
     
    Neto_Kokku and RobbGraySBL like this.
  5. Stephan_B

    Stephan_B

    Joined:
    Feb 26, 2017
    Posts:
    6,595
    I can certainly understand that. I wasn't sure if there was a technical reason or something like that.
     
  6. RobbGraySBL

    RobbGraySBL

    Joined:
    Feb 4, 2014
    Posts:
    40
    You've written this question in other threads about updating. I just want to confirm that on a large team it's a huge amount of effort coordinating with lots of different people and even after weeks of prep and emails we still gets lots of tickets (mostly artists) blocked because they didn't update or can't figure out how to. On top of remote build machines, managing different branches with different versions, updating documentation, onboard installers etc. There's just a lot of little things that cost and grow as the team gets bigger.
     
    Last edited: Apr 19, 2021
  7. Stephan_B

    Stephan_B

    Joined:
    Feb 26, 2017
    Posts:
    6,595
    I will be releasing an update this week to specifically address this issue.
     
  8. mertzorlular95

    mertzorlular95

    Joined:
    Sep 11, 2019
    Posts:
    3
    This issue still exists in 2020.2.0f1 LTS.
     
  9. Stephan_B

    Stephan_B

    Joined:
    Feb 26, 2017
    Posts:
    6,595
    Make sure that you update to version 3.0.6 of the TMP package via the Package Manager.
     
  10. IsobelShasha

    IsobelShasha

    Joined:
    Sep 19, 2018
    Posts:
    11
    I'm still getting this issue with 3.0.6 (unity 2020.2.0f1)
     
  11. Stephan_B

    Stephan_B

    Joined:
    Feb 26, 2017
    Posts:
    6,595
    Looks like PS5 support was added in a subsequent release of 2020.2.

    Any reason you are not using the LTS 2020.3?
     
  12. EmmetOT

    EmmetOT

    Joined:
    Apr 25, 2016
    Posts:
    44
    To revive this, I'm currently on 2020.2.0f1 and I'm getting this. I also can't change the Unity version as it's not my project to change.

    Please address this as it's a major blocker - I need fixes in the update, but can't update because of this.
     
  13. EmmetOT

    EmmetOT

    Joined:
    Apr 25, 2016
    Posts:
    44
    Update for any googlers: this seems fixed in 2020.2.1f1.
     
  14. KevinCastejon

    KevinCastejon

    Joined:
    Aug 10, 2021
    Posts:
    98
    I just updated to TextMeshPro 3.0.7 and I got this error now..
     
  15. clownbaby

    clownbaby

    Joined:
    Sep 4, 2013
    Posts:
    3
    Also seeing this in 3.0.7, running Unity 2023.1.20f1:

    Library\PackageCache\com.unity.textmeshpro@3.0.7\Scripts\Runtime\TMP_InputField.cs(424,42): error CS0117: 'RuntimePlatform' does not contain a definition for 'VisionOS'
     
  16. KevinCastejon

    KevinCastejon

    Joined:
    Aug 10, 2021
    Posts:
    98
    I wiped the package then restarted unity and reinstalled it, now it works ‍♂️
     
  17. HapiFox

    HapiFox

    Joined:
    May 2, 2018
    Posts:
    4
    i'm using unity 2023.1.11 and upgraded textmeshpro to 3.0.7
    and this error occured

    Library\PackageCache\com.unity.textmeshpro@3.0.7\Scripts\Runtime\TMP_InputField.cs(487,38): error CS0117: 'RuntimePlatform' does not contain a definition for 'VisionOS'
     
  18. HapiFox

    HapiFox

    Joined:
    May 2, 2018
    Posts:
    4
    i've created a new project in unity 2023.1.11 and the TMP version is 3.0.6 with no errors.
    but the errors show up after i've updated TMP to 3.0.7
     
    lorogast and hualongdev2022 like this.
  19. shaandali

    shaandali

    Joined:
    Feb 13, 2020
    Posts:
    1
    recently I Updated the TMPro and I got this error:
    error CS0117: 'RuntimePlatform' does not contain a definition for 'VisionOS'

    any idea???
     
  20. chrpetry

    chrpetry

    Joined:
    Mar 7, 2018
    Posts:
    65
    Downgrad to 3.0.6
    I needed to adjust the manifest.json manually.