Tuesday, September 20th, i.e. tomorrow, is the official release date for Apple’s next major revision of macOS (formerly known as Mac OS X). While I usually wait for a couple of patches this time I am in a situation where I am re-installing my system tomorrow anyway, so I wondered if I should go straight for Sierra.
Is there any official word if Unity is save to use on this system and if so, which versions of Unity?
Here somebody seems to have had a negative experience. A while ago Unity had a harsh time on Mavericks during it’s early release window … so how about it?
I think Bradamante is talking about the editor rather than OSX development.
If so, I’d love to know too. I think I’m just going to do it and see what breaks
I know but all Mac OS related should be there or at least in general editor support thread when you look what the description of this forum section says
Unity 5.1.1 and 5.4.0 install and run fine as well.
EDIT: in Unity 5.1.1, Editor no longer recognizes MacOS platform and under Build Settings, unselecting “Automatic Graphics API” only shows Windows graphics API. In addition to this, command buffers seems to stop working properly with “Invalid pass number” errors.
Well this forum is for the developers, and if you are one that uses WebPlayer then you pretty much need to move over to WebGL if you want to keep your game relevant
The point being if you develop for an audience that rely on the web player then to stay relevant you need to use it still.
Not everyone in the world has the luxury of being able to upgrade to Chrome. We work with many companies that are locked down to IE.
Then you have to hope that any bugs and compatibility issues that arise are considered bugs on their own end by the browser developer or os maker, and they fix things, because I dont think Unity are going to pay any more attention to WebPlayer issues.
I know that what happened with plugin support in some key browsers has left a big hole for people in certain scenarios, and for those who cannot switch it’s only going to get worse as time goes on. I’ve got much sympathy for this plight and I’ve seen an easier to get around version of it happening at work with some tedious business apps and java, most recently when I had to put some machines on a specific version of firefox in order to retain java capabilities. I dont think there is too much that will be done to ease the pain, and the main solace is in scanning the horizon for an eventual exit strategy from WebPlayer. Like the curse of IE6 for web developers for so many years, it can seem like the end will never come but eventually this stuff will be obsolete for almost all cases.
Well if you need to continue using a dicontinued product for any reason, you will have to make do with what it is and can’t really expect it to be fixed or supported. Sucks? maybe, but it’s just what you have to live with.
i think the dropping of web-player has more to do with Google and the makers of browsers than it does with UnityTech. They dropped WebPlayer because Chrome stopped supporting plugins like WebPlayer and the other browsers were going to follow suit and drop the nsapi as well. So i would assume if you still use webplayer you are catering to a audience that uses legacy web browsers so whats wrong with using a legacy version of Unity?
This is what we do but it now means that we have to develop in a legacy version and the latest one.
The only reason I bought it up was because the original thread was about compatibility with the latest Sierra. If you weren’t aware that version broke even the legacy version of Unity you need to know you have to move to WebGL for that platform.
