Have you had this happen per chance?ĮDIT: I used an actual timer, and script compilation was exactly 15 seconds and entering Play Mode took 12 seconds. Selecting anything in the hierarchy or any asset fixes this. The only issue I've noticed is sometimes, when switching tabs or to the editor from another app, half of the letters in the entire editor disappear. Besides script compilation, the Unity editor isn't a very demanding program at all and personally seems to run perfectly fine under Rosetta so I don't think that was as big a priority as native M1 build support. Though I do think even the newest editors are running under Rosetta but with the ability to create builds with native M1 support. It probably does have to do with the version of Unity we're using, if it's a problem for you I would download a newer version of the Unity editor and attempt a conversion of the project and see how long the compilation times take. the settings I designed to be adjustable during runtime within the game) and through Unity's graphics settings while the Intel struggled to handle a low settings environment.

Running the game itself, however, the difference is night and day with the M1 easily handling max settings in-game (i.e. I definitely see an improvement entering Play Mode, but not a large one. Considering the Intel MacBook Air 2020 was pretty weak, that does sound pretty bad. With hundreds of scripts to compile, I see exactly zero difference in script compilation time between the two (around 15 seconds). I'm on the same exact same version of Unity, and upgraded from the Intel MacBook Air 2020 (base model) to the M1 MacBook Air.

Add ram to mac mini m1