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

Lets face it - Unity is an absolute mess

Discussion in 'macOS' started by johannig, Sep 15, 2020.

  1. johannig

    johannig

    Joined:
    Apr 22, 2015
    Posts:
    27
    Recently, Unity has become an absolute mess. I don't know if this is only on Macs, but it's come to the point that it's unusable. I've changed Macs, reinstalled Unity, Xcode and pretty much anything you can think of.

    First, I encountered terrible performance with Unity Sprite Shape. I've been trying to figure out a solution with them for 3-4 months now. Although they've been able to reproduce it, all their suggestions for improvement have failed to work.

    Second, is the game breaking OpenGL bug. One of their solution suggestions was to change from Metal to OpenGL. The problem is that once I hit "Play" within the Editor with OpenGL the whole computer shuts down. Not just Unity, the whole freaking system! They told me they were aware of this bug (yet, suggested it as a solution).

    Third, I was unable to build for the longest time. Finally after updating I was able to fix this - but I received no help or suggestions from Unity. Every try ended with "Build failed".

    Lastly, I've encountered their freshest bug where I can't launch Unity. Every time I try, I'm welcomed with a "Failed to load window layout" message. It offers three choices and none of them works. I've tried reinstalling and updating and nothing works.

    TL:DR - My experience with Unity on Mac the past few months are that I had terrible performance issues, couldn't build, the program shuts down my whole system when I try to play with OpenGL and now I can't even open the program.

    Unity is unusable on Mac.
     
    JoeStrout likes this.
  2. DaftPuzzler

    DaftPuzzler

    Joined:
    Dec 1, 2018
    Posts:
    12
    Are you still having issues? I'm on a 2012 iMac running the newest editors and plugins just fine.

    What is your machine?
     
  3. enhawk

    enhawk

    Joined:
    Aug 22, 2013
    Posts:
    832
    any mac released before 2014 needs to use opengl, as metal is unsupported.

    recent versions of Unity are not tested on older machines, perhaps use an old version of unity that was good with non-metal machines, like Unity 2017 LTS
     
  4. DaftPuzzler

    DaftPuzzler

    Joined:
    Dec 1, 2018
    Posts:
    12
    My Late 2012 iMac supports metal. I think I'm right at the cutoff.
     
  5. johannig

    johannig

    Joined:
    Apr 22, 2015
    Posts:
    27
    I'm on a Mac mini 2020, i5 & 64gb RAM. So the OpenGL bug is clearly affecting later versions, too. I've been able to build lately and was able to fix the "failed window layout" bug with some weird workaround. Performance issues are still a very real thing, though. Still can't use OpenGL without crashing the whole system.
     
  6. JoeStrout

    JoeStrout

    Joined:
    Jan 14, 2011
    Posts:
    9,841
    Just to be sure: you do have "Metal Editor" turned off in the project settings, right?

    That's the first thing I always have to do upon starting a new project, as the metal editor for me is unstable and causes all sorts of problems. But once that's off, Unity works fine.
     
  7. johannig

    johannig

    Joined:
    Apr 22, 2015
    Posts:
    27
    I have to use Metal because of that fatal bug when I run OpenGL. I was emailing back and forth with Unity support and they basically said: "Oh yeah, we are aware of that bug". Which is crazy to me. How haven't they fixed that ASAP?
     
  8. JoeStrout

    JoeStrout

    Joined:
    Jan 14, 2011
    Posts:
    9,841
    Yeah, I don't know, I've never seen that one.
     
  9. AcidArrow

    AcidArrow

    Joined:
    May 20, 2010
    Posts:
    11,001
    That’s not true.
     
  10. enhawk

    enhawk

    Joined:
    Aug 22, 2013
    Posts:
    832
    2012?
     
    AcidArrow likes this.
  11. Mauri

    Mauri

    Joined:
    Dec 9, 2010
    Posts:
    2,657
  12. rebecca_ad

    rebecca_ad

    Unity Technologies

    Joined:
    Jul 9, 2018
    Posts:
    5
    @johannig have you resolved this issue? If not, have you tried deleting your Library folder and then launching?

     
  13. johannig

    johannig

    Joined:
    Apr 22, 2015
    Posts:
    27
    No that one did not work. I had to change some script that came up. Found the solution online somewhere, but can't find it right now. My latest problem is that my trigger2D colliders are working fine, until I try them in my build. Obviously there is nothing wrong with my code - I've been using it for AGES - and it still works in Play in the editor. Are you guys aware of this?
     
  14. rebecca_ad

    rebecca_ad

    Unity Technologies

    Joined:
    Jul 9, 2018
    Posts:
    5
    @johannig I'm not aware of the issue nor could I find an open bug describing any issue with trigger2D colliders not working in built players. Could you file a bug and include the project and scripts where the error occurs?
     
  15. johannig

    johannig

    Joined:
    Apr 22, 2015
    Posts:
    27
    At some time before I had deleted layers & tags that I wasn't using. After that, this happened. It started working again after I added a bunch of random layers & tags that I won't use - the the exact same number of tags I had before. Weird bug - as the "Player" tag I was using was never moved around. Only tags that came after it was deleted, so both the name - which I call in script - and the number stayed the same.