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. Dismiss Notice

Downgrading project from 2020.1 to 2019.1 causing UI issues

Discussion in 'Editor & General Support' started by skoteskote, Oct 23, 2019.

  1. skoteskote

    skoteskote

    Joined:
    Feb 15, 2017
    Posts:
    85
    Hi, I have a problem. I'm developing a get-to-know-each-other game for iOS and Android. The game is built in Unity 2020.1.0a8, and is entirely created around UI objects. My client want to add some nice VFX graphics in the background, and it looks awesome, but I can't get VFX graph to work for iOS in 2020.

    So, I have two options:
    1. Downgrading the project to 2019 to get VFX to work
    Issue: Since Unity has rebuilt the UI system in 2020 all my UI elements are missing their associated scripts when I downgrade/import the project to Unity 2019 (see attached screenshot.)
    Solution: I could rebuild the whole UI in 2019, but thats a few hours of work that I'd like to avoid... Is there a quick fix for this?

    2. Getting VFX graph to work for iOS in 2020
    Issue: Everything works in the editor, and no errors during build either in Unity or in Xcode. However when I play the app it doesn't display the VFX and I get a warning saying "UnityGfxDeviceWorker (32): signal SIGABRT". I have no real idea how to go forward with this.

    What are your suggestions?

    (I've tried reimporting assets and rebuilding the library after importing to Unity 2019, which did not resolve the issue.)

    Screenshot 2019-10-23 at 10.37.40.png
     
  2. Antypodish

    Antypodish

    Joined:
    Apr 29, 2014
    Posts:
    10,580
    Is quite irresponsible to use Unity alpha version in production. You are signed on your self that risk. Now probably need take a hit in a chin.

    If is just few hours of work, that is nothing in terms of game development time frame. Most of time, there are no tools, which allow to move to older version of Unity. Not to mention using alpha, or beta.

    So you better grab LTS Unity version, and make sure, you start project there. Is easier to migrate forward in future, than revert to previous Unity version, when something is not working as expected.
     
    skoteskote likes this.
  3. skoteskote

    skoteskote

    Joined:
    Feb 15, 2017
    Posts:
    85
    Learning the hard way, I guess. Anyhow, thanks for your comments. Rebuilding the thing manually now :)
     
  4. ArinFaraj

    ArinFaraj

    Joined:
    Jan 5, 2014
    Posts:
    13
    kinda had the same kind of issue here
    they should not make the beta version too shiny on there website
    i will never fall for it again xD
     
    AndreyAdrian and skoteskote like this.
  5. Petkopetko

    Petkopetko

    Joined:
    Feb 21, 2018
    Posts:
    2
    Hello!

    I had the same problem and I managed to solve it. The Entier problem was caused by some incompatible packages in my case Collab and TextMeshPro. You can identify your incompatibilities using unity console.

    This worked for me:
    1) Remove collab and tmp packages via Package Manager in unity.
    2) Quit the unity and remove the Library folder in your projects directory (i do not really know if this is necessary but it is recommended in situations like this one because it will force unity to "recreate" your project).
    3) Relaunch unity and wait until your project is rebuilt, then simply download removed packages back from Package Manager.
    4) (Maybe) Restart unity!

    After doing this it should be perfectly fine and working.
    I hope this was helpful for anyone with the same problems in the future!
     
    Last edited: Jun 5, 2021
    thexdd likes this.