WINDOWS STEAM BUILD FOR MAC OS SIERRA HOW TO
WINDOWS STEAM BUILD FOR MAC OS SIERRA MAC OS X

Unity needs to reach out to Microsoft and Apple so that this can be seamless. I don’t expect users to pay for a game and then modify it just to make it work, no matter how simple that modification may be. I understand that windows can’t natively set the permissions, but I don’t believe for a second that they couldn’t implement something, nor do I believe that Unity is incapable of implementing some sort of fix, and if absolutely nothing else Apple certainly would be able to do it, considering it’s running natively on their platform.Īs simple as it is to fix it’s absolutely absurd to make end users go through this process. I feel like with something as big as unity these companies would work together to find a way to seamlessly build for all supported build platforms.

WINDOWS STEAM BUILD FOR MAC OS SIERRA MAC OS X

But if you just want to try the Sierra MacOS, then the ideal solution is to use a Mac OS X virtual machine. In order to use it, you either need to buy a Mac or build a hackintosh. It seems absolutely insane to me that in 2021 this could still be an issue, it’s not like we’re talking about someone’s personal rpg maker game or something, we’re talking about an industry standard tool. MacOS Sierra is the latest version of Apple's operating system, which of course cannot be installed on just any computer. I really can’t believe that there isn’t some sort of fix, be it from Unity, Microsoft, or Apple. I hope this helps and I'm by no means a professional with this so but my friend and I can try to help in anyway possible. Once we approved permission, the app ran no problem. This unlocked the permissions on the application but when the app was opened, we had to allow permission through the Mac firewall to let it run on the computer. I honestly can't remember where I found this code and when I remember I'll be sure to credit them, but with terminal you need to navigate to the download folder (or wherever you put your app) and add the following: To fix this, you have to use Terminal to navigate your way into the file and unlock the permission settings that were changed due what we believe is from the compression. However, the following information did allow my Mac Build to run after the compression. This problem doesn't exist if you build from Mac or Linux editor.' To launch something, you need to mark the executable with execute permission.

All files taken from a Windows machine will have default permissions, which are read/write. The comments made it clear to me that 'this has nothing to do with compression or even corruption.

Once you follow the video's directions exactly for the Mac version, you can send the file to your Mac but when you do it will be labeled MacOS and then when you try to open it it will most likely fail and say missing application to open.įrom what I have learned from numerous threads (and I don't know how true this is, this is based off of other users), this is because the compression actually corrupts the executable file to open it on the Mac.

WINDOWS STEAM BUILD FOR MAC OS SIERRA HOW TO

I just figured out how to make the Mac build work with a friend and it was a bit of work.

Windows steam build for mac os sierra