- Home /
Black screen while launching editor on Mac (high sierra)
Hello All,
This is an issue with too little or almost no useful posts I found online, specially for mac.
First I installed uniy 5.6.2 , faced this issue, unistalled and then installed Unity 5.5.1 and still the same.
MacOS is High Sierra version 10.13.1 but I think its irrelevant of the version.
Can't give more details since on double clicking the Unity Icon , a black screen is shown and stuck here!
Anyone faced such an issue?
The closest link to this was this , but guys talking about Windows 7 there and couldn't reach to a solution still.
Yash987654321 is suggesting to:
SOLVED! I managed to solve the whole issue!!!! To do this first go to C:\Users\ad$$anonymous$$\AppData\Roa$$anonymous$$g\Unity\Packages\node_modules\unity-editor-home and then create a new folder named "dist" (without inverted commas) then copy everything you have in C:\Users\ad$$anonymous$$\AppData\Roa$$anonymous$$g\Unity\Packages\node_modules\unity-editor-home to the new made "dist" folder and you are ready to use 5.3!!!!!
in the upper post, but how to in case of a mac ?
found this post
If you use the console app and watch the Editor.log under ~/Library/Logs/Unity it was attempting to open the index.html file (which didn't exist) that contained your most recent projects. (~/Library/Unity/Packages/node_modules/unity-editor-home/dist/Index.html) I renamed the ~/Library/Unity/ to ~/Library/Unity-old/ fired up Unity and got it all working again.
But :( still the same
Answer by C4nDiM4n · Mar 07, 2018 at 12:49 PM
As @moghes has written you need to edit your ~/Library/Unity/Packages/ folder. What you can do that should solve the issue is to get the Package folder from someone that has a working Unity and just take that one.
* So replace your Package folder with a Package folder that you know works.
It even works from PC to Mac since that is what we did.
Answer by RyanAtEvno · Mar 07, 2018 at 04:01 PM
When I had this issue in the past, it was an asset package I had downloaded that became obsolete and was causing editor render issues. ProBuilder was the culprit for me. Just had to update delete the package in /Library/Unity/Packages/ folder then reinstalled after.