Unity and macOS 10.13 (High Sierra)

I believe all the major issues are already fixed in latest 5.6.x, 2017.1.x, 2017.2.x patch releases (I'm using it everyday on my machine). If you encounter MonoDevelop issues, I recommend moving to Visual Studio for Mac, as it will be replacing MonoDevelop in future versions of Unity. I will update main post early next week.

 

Hello,
I've been following this thread; however, I still encounter freezing and restart of my laptop.
I have:
1. Unity 2017.2.03f (downloaded yesterday)
2. macOS High Sierra 10.13.1

Unity shows an Editor warning: Metal support disabled, skipping device initialization.
Before my computer suddenly freezes/restarts when I am using Unity, Unity itself is super slow. Just loading a default sphere onto the scene causes the software to freeze and the Game panel is not showing anything but a dark gray screen.
This did not happen until I upgraded to High Sierra. I also attempted to run it on a partitioned hard drive, but it is still slow (although I haven't experienced a sudden laptop restart yet).

Any help is much appreciated.
- D

 

Please try 2017.2.0patch4: https://unity3d.com/unity/qa/patch-releases?version=2017.2

 

Not sure if this is directly related but after updating to High Sierra and updating MonoDevelop all my internal methods in MonoBehaviour's are no longer accessible to scripts in the same assembly. Is this no longer supported?

 

As vital as the Unity Gear Store obviously is, maybe this thread should be listed in the little important topics bar at the top of the forum?

 

Visual Studio for Mac will replace MonoDevelop? Curious, what are the reasons for this?

 

Basically it's most up to date product of the same line: MonoDevelop -> Xamarin Studio -> Visual Studio for Mac

 

What build will we see the change happen in?

 

Updated leading post with most up to date information summary.

 

Did anyone test iOS player unit tests on Mac 10.13.1 + XCode 9 + Unity 2017.2? Not sure if it is related to the new Mac / Xcode but no iOS test runs even with a fresh empty Unity project. Unity is simply not pushing or not starting the tests on the ios device. I posted more here but so far without any results: https://forum.unity.com/threads/ios-testrunner-doesnt-run-the-app-on-test-device.506332/

 

Hello...

i have the "Blank Project Window" Issue on a Unity 5.5.0f3 Project using HighSierra 10.13.1

Is there a patch for this Unityversion available?

It´s a Google Cardboardproject using the CardboardSDK (Version 1.10 if i recall correctly) When i started this Project we had issues finding a working Unity/SDK/Assetstore-Assets combination which work together and had all our needed features Bug-free (things like spartial audio), so we ended up with Unity 5.5.0f3

So "simply" upgrading Unity to a newer version might not be the easy fix here

 

Hello

I cannot add Unity IAP when running Unity 2017.1p4 (p3, p2, f1) on High Sierra. Tried on several computers, nada. On El Capitan it works fine.
After adding the IAP the import hangs the Editor and that's it.

Any details on this?

P.s.
Addint Unity IAP on El Capitain computer, commiting to git, pulling on High Sierra and running the project again results in a hanging Unity Editor.

 

There will be blogpost on this soon.

 

Please submit a bugreport.

 

I hope that your blog post also contains an apology. Institutionally, Unity really left the Mac base in the cold on this for months and a lot of developers have suffered for it.

 

Visual Studio for Mac is probably the single worst IDE on Mac right now Are we going to be forced to use this in the future for some reason, or can we continue to use our own external editors such as Rider, VSCode, Xamarin, etc?

 

If it would be forced for some reason than that reason would be Microsoft wanting more market share of VS and unity getting a deal out of it.

can't see any other reason. So I guess it won't be forced, and we can still add the external editor in the preferences.

 

It's only about what is bundled by default with Unity, you still can use any IDE you actually prefer.
P.S. Microsoft bought Xamarin and Visual Studio for Mac is actually based on Xamarin Studio + a lot of improvements on top.

 

Yeah which is why Xamarin went downhill It used to be nice and lightweight, now it is getting as bloated as Visual Studio. So sad

 

I'm getting massive issues with High Sierra and network shares using smb, is this a known issue and are there are fixes for it?
Basically when I open a project from a server using smb the connection to the server is lost and the project fails to open 99% of the time.

 

Just an update from my side: XCode 9.2 not Mac OS 10.13 (likely 9 already) breaks iOS unit tests. Reinstalling xcode 8.8.3 in another folder + switch the used folder with
sudo xcode-select -s /Applications/Xcode8.3.3.app/
fixes the issue.

 

Trying out Acronis on our Windows server, that seems to fix the issue for me by implementing afp sharing protocols.

 

Somebody test the new Unity 2013.3 and the compatiblity with macOS High Sierra ?

 

No explosions yet.

 

Do you mean 2017.3 ?

 

Yes.. 2017.3 ! All works fine?

 

I haven't tried all the thousands of things, but so far I've only seen some strange warnings while upgrading projects.

 

2017.3.0 should be fine for High Sierra right? (I notice it is not listed...)

 

Brutally, wiped everything out. All projects in version control, and re-install software on a need basis to avoid starting with a lot of cruft.
I know this isn't the answer most may be looking for but version control, cloud files and removable media (for backing up important projects) are a stable, reliable solution that also works if Jabba the Hutt happen to step on your laptop.

 

Hello, any chance I can make Unity 5.2.2p4 to work somehow on HighSierra? Tried installing unity on HFS+ partition, didn't help, I'm constantly getting `Failed to load window layout` dialog, clicking any of the options doesn't help

 

From the OP:

There will be no Unity 5.4.x fixes for High Sierra, you have to either keep your machines on macOS 10.12 or upgrade your project to Unity 5.5.x and later. In general 5.4.x and older Unity versions might work with High Sierra on HFS+ disk, but it should be considered as last resort workaround if you have to use older Unity versions on new OS.
​

So: probably not.

 

FYI, for anyone holding out on upgrading to 10.13 - High Sierra. A recent security article on RPS suggests 10.13.2 or higher is a must to mitigate threats.

https://www.rockpapershotgun.com/2018/01/04/intel-amd-cpu-meltdown/

 

Any Updates on this?

 

I have the latest 10.13.2 and SMB connections basically hang the system and force a reboot. Unusable and broken. Some forums have suggested using an alternative to smb, cifs://server-name You could try that. Might be slower.

As a side note, I get other problems with High Sierra and Unity, for example 'mdworker' (Spotlight indexer) works like crazy whenever Unity is running, consuming CPU. I've tried resetting the index but that doesn't help. Only solution is to turn it off, which isn't acceptable. Been like this for weeks. New OS file system has a lot of kinks to be worked out.

 

Curious if you've done any builds to iOS since your upgrade.

My Unity 2017.3.0p1 + OSX 10.13 + XCODE 9.2 works just fine in Unity, but I cannot build to iOS. Just results in all sorts of crashes that never existed before.

 

Quick random question:

I have to upgrade to MacOS High Sierra at work today and we're running Unity 2014.1.1f1. If I patch Unity to 2014.1.2p4, will that block others who haven't patched Unity yet from opening the project?

Sorry, I've never patched Unity, just did full updates (I don't know how patches affect builds).

 

Patches are no different from full updates, in that they are both work the same way. They're merely labeled as patches since they haven't had the full QA. But otherwise they're just regular updates.

--Eric

 

Thanks @Eric5h5

Good to know. Going to IT to tell them we need wait (also since Adobe apps have issues with High Sierra). We're close to shipping so why update and change a bug.

 

What exactly is the expected impact on users with this? I'm having reports of some of my older titles, some of which are on Unity 4.x, having trouble with high sierra. I had one on 5.4x that was having an issue, which we then updated to 2017.1p4 and hopefully that is in a working range.

For my very latest stuff, I'm split between 2017.3 and 2017.1. I'm not developing on OSX, but I'm concerned about users. We're reading some files from disk using WWW in the case of all our projects, and it looks like that might have some issues?

 

We've had to resort to installing Acronis on our server to solve the problem, nothing else seemed to work.

 

Just wanted to chime in that I updated to High Sierra (and APFS) on a 2017 MacBook Pro and Unity 5.6.4 works well without any issues.

 

Any updates? I'm running 2017.3f3, dual monitors, APFS, & Rider. Unity still doesn't recognize script changes. I have to manually refresh to trigger a recompile.

 

What is your bugreport number?

 

I have constant freezes when doing editor stuffs in Unity3D 2017.3.0f3 (clean install) on High Sierra unfortunately

It's kinda unworkable at the moment for me in the editor

 

Were these freezes happening before upgrading to High Sierra?
Also could you please try latest 2017.3.1p1 patch release: https://unity3d.com/unity/qa/patch-releases?version=2017.3

 

I don't think it freezed as often as it does now. I'm using a multi-monitor setup (when switching to single monitor it seems to reduce the freezes). I updated to 2017.3.1p1 but the freezing is still happening

 

Please submit a bugreport with detailed explanation of your setup. Thanks!

 

Will do

 

Have you tried Unity 2017.3 (the latest patch) yet?

I am having the same issues as you. so many build errors that have practically made it impossible for me test anything for iOS devices. I have been using sample codes from Unity, and other online tutorials and no one in their forum have had such issues. ARkit remote doesn't work either. have submitted the bug report(s) as well, but received no response.

Running Unity 2017.3 on Mac Pro 2017 (maxed out specification) - High Sierra.

 

I'm not sure where to ask this, so I'll start here. I have 2017.3.1f1. on a MBP mid-2014. I can create and work on projects just fine. I can run the player just fine. If I export it to an App, it crashes. One test I did was run it on another account on the SAME Mac and on that account it ran fine.

I uninstalled (completely) the app and reinstalled. Any ideas on what could be causing this? I also looked at the logs and will be happy to provide any details. If I run from command line it gives a Trap 6 error. If I look in the player logs it says `No valid pixelFormats set'

I did this with a simple 3d project (no extras, just created a new 3d project, ran play mode - worked fine, exported to app and crashes).