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. Let us know your feedback about the Global Illumination changes in the 2023.2 beta.
    Dismiss Notice
  3. Dismiss Notice

Unity 5 beta 16 will not open my project

Discussion in 'Unity 5 Pre-order Beta' started by Todd-Wasson, Dec 8, 2014.

  1. Todd-Wasson

    Todd-Wasson

    Joined:
    Aug 7, 2014
    Posts:
    1,077
    Not sure what info to post here to help, but beta 16 will not open my project at all. The start up window opens, I choose a project, and it just closes with no error messages or anything.

    Upon startup, I can create a new project and the editor opens fine, but as soon as I load the project I've been working on in beta 14 it just closes.
     
  2. Archania

    Archania

    Joined:
    Aug 27, 2010
    Posts:
    1,662
    I would create a new project and start bringing things into it. Something might be bugged causing it to crash. Just an idea
     
  3. Tomza

    Tomza

    Joined:
    Aug 27, 2013
    Posts:
    596
    I have the same problem. When I try to open a project that exists, Unity Beta 16 disappears from Task Manager. So I starts it again and it goes to the previous opened project. From Menu in the opened Unity, I choose to open a project I want and it opens. In other words, I try to open the same project two times - first time, Unity crashes, so I try again and the project is opened.

    Yes, there's something wrong with Unity Beta 16. Try to open the project more than one time.
     
  4. shkar-noori

    shkar-noori

    Joined:
    Jun 10, 2013
    Posts:
    833
    I don't think it's a bug, you just have to re-compile your plugins. the name of an attribute has changed and it's causing Unity to crash if you have plugins using that attribute, re-compiling your project for the b16 UnityEngine.dll & UnityEditor.dll fixed the problem for me.
     
  5. Tomza

    Tomza

    Joined:
    Aug 27, 2013
    Posts:
    596
    I have no plugins. The project was recompiled, because before recompiling I coudn't even start Unity.
     
  6. Todd-Wasson

    Todd-Wasson

    Joined:
    Aug 7, 2014
    Posts:
    1,077
    As I much as I appreciate the suggestions, I don't understand how I can follow any of them if the project won't open in 16.

    About all I can do is just stick with 14 and hope Unity will fix it in 17 or 18.
     
  7. fermmmm

    fermmmm

    Joined:
    Oct 18, 2013
    Posts:
    129
    I had the same problem with beta 17 and fixed it by deleting the following folders:

    [Project root] / Library / ScriptAssemblies

    and

    [Project root] / Library / UnityAssemblies

    Then the project openeded and the folders were generated again.
     
  8. seattlebluesky

    seattlebluesky

    Joined:
    Sep 2, 2014
    Posts:
    170
    Between each beta I nuke the Library sub-folder completely as well as emptying the GICache. Sure this means that content will need to be re-imported into the new version of Unity, but given the expected churn between beta releases it seems like the most prudent approach.
     
  9. Todd-Wasson

    Todd-Wasson

    Joined:
    Aug 7, 2014
    Posts:
    1,077
    Thanks. I'll give that a try when I get time.
     
  10. seattlebluesky

    seattlebluesky

    Joined:
    Sep 2, 2014
    Posts:
    170
    You should make a backup of Library first of course just in case, but to the best of my knowledge it contains recreatable content.
     
  11. Todd-Wasson

    Todd-Wasson

    Joined:
    Aug 7, 2014
    Posts:
    1,077
    Thanks a ton, guys. That fixed it. :)