Official Now Available - Native Apple Silicon Editor Preview Builds

Anyone using Apple Silicon should probably keep their expectations low for a few months. In around 2-3 hours of editor time I've ran into the input bug, had a couple freezes, an asset that crashes the editor every time I import or have it in my project. I have models that will not work with URP. The auto material conversion failed, extracting the included URP materials failed, the new URP upgrade tool failed - the first time I used it is consumed all my system memory (82.66 GB) and the second time, converting in batches, did nothing so I ended up going to SRP. This is a brand new project with a character controller and three Synty model packs so it's basic.

When the editor does work, it's quick and responsive. Imports, except for shaders, are fast. Entering play mode is fast. All those 'hold on' popups are gone. I don't know how much of that is Apple Silicon vs 2021.2.0f1, but when it works it's great and a really nice experience. Very impressive. For the first time in years, it doesn't feel like the editor is slowing me down.

 

How do you have 82GB of system memory on an Apple Silicon machine? Isn't the max 64GB? Or are you counting swap or something?

 

I only have 16 GB. I think any greater than 16 GB is virtual memory.

 

I will try. I've tried to submit the crash reports but those would never completely upload.

 

Looking forward to 2f1, but in the mean time.

Is anyone finding the scene view (windowed) much smoother in 1f1?
I have game and scene view showing side by side (plus ui of cause), and usually the scene view would be very choppy while navigating - unless I made it full screen. Now, it's just smooth sailing.

 

Anyone experiencing 30fps lock on game view?
I'm using M1 air and 2021.2.1f1 apple silicon.
create empty project and press play button game view is 30fps limit.
if I change game view to maximize window then limit has gone and it works 60fps.

It doesn't happen on b16 apple silicon version.

 

This specific version used to be significantly fast "2021.2.0b16" compared to all versions in terms of the renderer. I was really glad they improve it, but now it seems as laggy again as the Unity 2021.2.12 beta and below.

 

Do you see long segments of Gfx.WaitForPresentOnGfxThread? Im getting this and its awful when Game View isn't maximized. Perhaps it is this bug: https://issuetracker.unity3d.com/is...rsignal-uses-around-9-ms-on-almost-all-frames

 

I've installed 2021.2.0f1 on my MacBook Pro (Apple M1).

Any idea why it's showing "<Metal><Rosetta>" in the window title?
Everything remains very slow. (Slower in fact than before.)

I've also had a couple of bizarre bugs that I have reported (typing in inspector is one character behind the keyboard; lists within ScriptableObjects don't show up properly in the inspector).

 

This workaround has no effect for me. Although the Unity Editor still shows "<Metal>" in the titlebar, even though only OpenGLCore is listed under "Graphics APIs for Mac". Using 2021.2.1f1.

 

via Unity Hub 2.4.5 (the usual way I install).

How should I do the install instead?

 

Try upgrading the Hub to 3.0.0beta6. I use that version and it shows whether the build is Intel or Apple Silicon.

 

Hub v3 beta 6 is the first Hub that can install Apple silicon builds. You can also install them directly using these links, but I recommend the Hub:
2021.2.0
2021.2.1

 

I've noticed that importing packages is extremely slow on the Apple Silicon editor. Like, several minutes, when it should normally take 20 seconds. Specifically importing the Firebase SDK into a blank project on Unity 2021.2.1f1 Apple Silicon takes about 5 minutes on my M1 Max, and it maxes the CPU across all cores during most of this time — it seems like it spawns a dozen Intel mono processes (see pic), even though the editor itself shows as "Apple".

Any ideas? Is this expected? I frequently need to update about 8 of these SDK .unitypackages and it makes what should be about 5 mins together take upwards of an hour to slog through.

 

Sure, I've filed a bug. Case 1379951.


BTW, I was able to grab the list of open files from one of the Intel mono processes, just to confirm it really was being spawned from Unity (it was). Here's the full list if it's helpful.

Code (CSharp):

1. cwd
2. /Users/aroman/Projects/SlowFirebaseImports
3. txt
4. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/MonoBleedingEdge/bin/mono
5. txt
6. /private/var/db/oah/279281325309952_279281325309952/f805ce9e4c3bcc7f15c8758bb1cb2e9946e38339e952c72d592ace8e15caac59/mono.aot
7. txt
8. /usr/libexec/rosetta/runtime
9. txt
10. /Library/Apple/usr/libexec/oah/libRosettaRuntime
11. txt
12. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/AssemblyUpdater.exe
13. txt
14. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/APIUpdater.Framework.dll
15. txt
16. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/CommandLine.dll
17. txt
18. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/MonoBleedingEdge/lib/mono/net_4_x-macos/mscorlib.dll
19. txt
20. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/Unity.Cecil.dll
21. txt
22. /Library/Preferences/Logging/.plist-cache.OFZTS87E
23. txt
24. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/MonoBleedingEdge/lib/mono/gac/System.Core/4.0.0.0__b77a5c561934e089/System.Core.dll
25. txt
26. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/MonoBleedingEdge/lib/mono/gac/System/4.0.0.0__b77a5c561934e089/System.dll
27. txt
28. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/MonoBleedingEdge/lib/libmono-native.dylib
29. txt
30. /private/var/db/oah/279281325309952_279281325309952/13b34fca35588fc687b32937637df4e889c5de48af2233e986a4c63ec34c89eb/libmono-native.dylib.aot
31. txt
32. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/Unity.Cecil.Pdb.dll
33. txt
34. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/Unity.Cecil.Mdb.dll
35. txt
36. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/MonoBleedingEdge/lib/mono/gac/Mono.Security/4.0.0.0__0738eb9f132ed756/Mono.Security.dll
37. txt
38. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/Tools/ScriptUpdater/Unity.Cecil.Rocks.dll
39. txt
40. /usr/lib/dyld
41. txt
42. /private/var/db/oah/279281325309952_279281325309952/c03495af1b5741a32c1778fdd4225e603d867984d0fa0cc1817729db6db253ad/dyld.aot
43. 0
44. ->0x8b779fd6a999b4a3
45. 1
46. ->0x9760f4e9c4a875a4
47. 2
48. ->0x591df1eabf0aea1f
49. 3
50. /Users/aroman/Projects/SlowFirebaseImports/Assets/Firebase/Plugins/Firebase.Crashlytics.dll.mdb

 

@Tautvydas-Zilys wow, actually, it's not just mono processes being spawned during import. it's also clang++ running while compiling for IL2CPP! Here's another screenshot showing that the Unity process itself shows as "Apple" (so I really am using the Apple Silicon editor), it's spawned a bunch of INTEL clang++ processes (!). Honestly this is sort of good news for me, because I have been fairly disappointed by the Apple Silicon build performance... seems like that's actually because it hasn't really been native the whole time —somehow— at least on my machine...

 

Android, with IL2CPP. Here's a list of open files from one of the clang++ processes. Seems the packaged clang++ that comes with the Android module is not Apple silicon native, but rather for x86_64?

Code (CSharp):

1. cwd
2. /Users/aroman/Projects/Flowerfare/Client
3. txt
4. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++
5. txt
6. /private/var/db/oah/279281325309952_279281325309952/52359749af7c6395d5ad7b4b4ab668c268dff1d250ee93819a1a1f281cb43045/clang++.aot
7. txt
8. /usr/libexec/rosetta/runtime
9. txt
10. /Library/Apple/usr/libexec/oah/libRosettaRuntime
11. txt
12. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/libil2cpp/il2cpp-config.h
13. txt
14. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__config
15. txt
16. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/lib64/clang/9.0.8/include/stdint.h
17. txt
18. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/libil2cpp/il2cpp-object-internals.h
19. txt
20. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/libil2cpp/il2cpp-class-internals.h
21. txt
22. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/libil2cpp/codegen/il2cpp-codegen-il2cpp.h
23. txt
24. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/cmath
25. txt
26. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/math.h
27. txt
28. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/type_traits
29. txt
30. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/pthread.h
31. txt
32. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/lib64/libc++.1.dylib
33. txt
34. /private/var/db/oah/279281325309952_279281325309952/a6848eb1e3169fa87981624b7defc0ee25c1374907b59bf4e7779da9031979fb/libc++.1.dylib.aot
35. txt
36. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/lib64/libc++abi.1.dylib
37. txt
38. /private/var/db/oah/279281325309952_279281325309952/cb5a450d7395b61917156e81f7cc96f4762256ae565be5e2170874f1a5efe9aa/libc++abi.1.dylib.aot
39. txt
40. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/artifacts/Android/il2cppOutput/cpp/Unity.Mathematics2.cpp
41. txt
42. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/limits
43. txt
44. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/external/baselib/Include/C/Baselib_Atomic_TypeSafe.h
45. txt
46. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/external/baselib/Include/C/Baselib_Atomic.h
47. txt
48. /Applications/Unity/Hub/Editor/2021.2.1f1/Unity.app/Contents/il2cpp/libil2cpp/os/ErrorCodes.h
49. txt
50. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/string
51. txt
52. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/string_view
53. txt
54. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__string
55. txt
56. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/algorithm
57. txt
58. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/utility
59. txt
60. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__tuple
61. txt
62. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/memory
63. txt
64. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/iterator
65. txt
66. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__functional_base
67. txt
68. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/tuple
69. txt
70. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/atomic
71. txt
72. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/functional
73. txt
74. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/vector
75. txt
76. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__bit_reference
77. txt
78. /Applications/Unity/Hub/Editor/2021.2.1f1/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/c++/v1/__split_buffer
79. txt
80. /usr/lib/dyld
81. txt
82. /private/var/db/oah/279281325309952_279281325309952/c03495af1b5741a32c1778fdd4225e603d867984d0fa0cc1817729db6db253ad/dyld.aot
83. 0
84. ->0xbc0ad7b229a98494
85. 1
86. ->0x80c071d2ee53b71c
87. 2
88. ->0x6a0ada2a25e69927
89. 3
90. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/Player8326491b.dag
91. 4
92. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/Player8326491b.dag_derived
93. 5
94. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/tundra.log.json
95. 6
96. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/TundraBuildState.state.map
97. 7
98. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/tundra.digestcache
99. 8
100. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/tundra.scancache
101. 9
102. 10
103. 11
104. 13
105. 14
106. 15
107. 16
108. ->0x1a1b20d572f0ac04
109. 17
110. 18
111. 19
112. /Users/aroman/Projects/Flowerfare/Client/Library/Bee/artifacts/Android/iz17e/51xl_thematics2-b8ed86c1.o.tmp
113. 20
114. ->0x8f20e3fb1c6ad0f0
115. 21
116. 22
117. 23
118. 25
119. 26
120. 27
121. 28
122. 29
123.  

 

Oh, I see. I had actually expected that this would be native as part of the Apple Silicon editor. It might be worth clarifying that in docs/release notes somewhere, as I suspect others may have also have had the same impression, and it's a significant part of my development workflow. (Our app targets iOS and Android, and typically it's easier to iterate via Android than iOS because you don't need to mess around with XCode in the middle.)

M1 Macs have M1-native clang++ (universal binary) in /usr/bin, presumably installed as part of xcode. I'm not sure why Unity needs to bundle it's own clang++, instead of the native system-wide one, or if it's possible to override that?

As for whether Google has ported the NDK, apparently they're tracking this here: https://github.com/android/ndk/issues/1299

From my understanding of the NDK release schedule, it seems the feature is tentatively targeted for the r23c release, which seems to be scheduled for around Q1 2022. I'm not sure what the process is for downstreaming that into Unity, but I guess when it's out I could install it myself, then go into Preferences > External Tools and point Unity to the install?

Regardless about the NDK being native or not — that doesn't explain why the mono processes being spawned during the package import (not building for a target) weren't native, right? Any clue on those?

 

I'm running 2021.2.2 (just updated), targeting WebGL and I also see some clang++ processes running as "Intel" while my editor runs as "Apple".

 

2021.2.2, On play = Obtained 0 stack frames

 

Just updated to Unity 2021.2.2f1 (Apple Silicon), I can confirm that the latency issue with the inspector has now been fixed. Thank you!

 

Ah feels good to be rid of that annoying lag.. I did power through using 2021.2.1f1 for a bit and in addition to the lag I experienced some hangs and some crashes here and there. Let's see if those are still there now.

 

Hmm yes, seems it is specifically with the project. The issue seems to occur when I'm loading new scenes which I do async in a coroutine, but I haven't quite found the cause yet. This wasn't an issue in 1f1 or versions prior.

Part of the Editor.log states:

=================================================================
Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0x1031399d4):0x1031399c4 fd 03 01 91 f3 03 02 aa f5 03 01 aa f4 03 00 aa ................
0x1031399d4 01 14 40 f9 e0 03 02 aa 29 00 00 94 e0 03 00 91 ..@.....).......
0x1031399e4 e1 03 15 aa 9a 26 00 94 e0 03 00 91 a8 26 00 94 .....&.......&..
0x1031399f4 e8 03 20 2a 1f 3d 00 72 80 03 00 54 f5 ff 9f 52 .. *.=.r...T...R

=================================================================
Managed Stacktrace:
=================================================================
at <unknown> <0xffffffff>
at UnityEngine.ShaderVariantCollection:WarmUp <0x00007>
at <IESceneLoader>d__25:MoveNext <0x003d3>
at UnityEngine.SetupCoroutine:InvokeMoveNext <0x0005b>
at <Module>:runtime_invoke_void_object_intptr <0x00077>
=================================================================
Obtained 0 stack frames.
Launching bug reporter
Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QObject(0x600000b70500), parent's thread is QThread(0x600001c30330), current thread is Thread(0x60000106f390)

 

I hope Unity will keep working hard on Apple Silicon native builds. It's really game changer. Some tests on a relatively heavy project on 2021.2.2f1 shows that a classic M1 does (a lot) better than my Ryzen 3900X with a RTX 2080 Super. That's insane.

 

Issue occurs when pre-warming the shader collection. If I run .Warmup() on my collection it crashes. Tried clearing and making a new (save to asset) while having my main scene loaded (tracking 36 shaders and 80 variants) - still crashes. Created one while only viewing main menu UI (tracking 19 shaders and 19 variants), that did not crash the editor.

Unsure which shader its mad at, wasn't an issue before though.

Edit: Seems to work fine in a fresh URP Sample project.

 

I tried on a complex project with SRP, VideoPlayer and custom shaders...
And it crashes on project opening.

Editor log points towards video transcoding.

I'm eager to get a native build working someday, keep up the good work!

 

I don’t know if it’s just me. I have a huge problem. I uploaded it as a video. In the first half of the video, I am creating a new project, just to prove that the steps to create the project are okay. After entering the project, I selected the main camera and tried to select the tool, but the selected tool did not appear in the scene window. I tried to create a new image and found that the UI interface was completely messed up. Only when I turned off the Gizmos button in the Scene window did it return to normal. This is completely illogical, because I turned off the Gizmos button and I couldn't use the editor normally. For details, please watch the latter part of the video in detail. I was really frustrated. After fixing the input delay problem, such a serious problem occurred again. Although it is very difficult to adapt to a new architecture, it is very disappointing to have such problems in the official version.

 

Regarding the supplement to the above question, I am using a mac mini with an m1 chip, the operating system is Macos 12.0.1, and the Unity 2021.2.2f1 version based on Apple silicon is installed. I just tested and opened the previous project and found that the same problem occurred. The problem seems to be that Gizmos is acting in a different place. I uploaded a picture, and you can see that Image's position tool Gizmoz is applied to another position of the scene window. I will install and test it on my macbook air with m1 chip later. But I think there is a high probability that this problem will still occur. Hope we can solve it sooner. thank you very much.

 

This is solved here: https://issuetracker.unity3d.com/is...-scene-view-when-certain-objects-are-selected and they say it will be in the next release in theory.

 

Thank you very much for your answer. Will the next version be 2021.3? I hope so. Since every official release so far has had serious problems, I can only go back to 2021.2.0B12, although it still has some bugs, but it is the most stable version so far.

 

Unfortunately, the bug happen with 2021.2.2f1 (installed today with hub).
I can open the project if I remove the video files.

The crashing video is:
4MB - 00:03
1920x1080
AAC H264
HD (1-1-1)

 

So,... What's the status of the engine for silicon? I want to start learning Unity with a new Apple Silicon, but I don't know if that's a good idea. Any help, please?

 

I think it's getting there. As you can see it's already here, but some bugs to iron out here and there, it's fairly recent. Fixes are fast though. Just make sure, if you're using 2021.2, you're always on the most recent version as there tends to be fixes in each patch as of now.

2021.2.3 is coming soon I think, for now you can use 2021.2.2.

 

Each time i try to open my projects with any Apple Silicon release it crashes during the project import when it reaches any .mp4 files with the error message:

Start importing Assets/Resources/video.mp4 using Guid(a501d165fbf5a4f63ba8b3aa8a9dc8e5) Importer(-1,00000000000000000000000000000000) Obtained 0 stack frames.

Is anyone else seeing this issue?

 

Try to remove all .mp4 files from the project and import the project. After importing, check the files back in, Unity should import the files correctly. The same problem was with images due to compression.

 

removing them allows the project to launch, but as soon as i reimport them it crashes again

 

2021.3.21f1 is LTS required for Plastic and... works fine native apple silicon version?
Im waiting 1 year for swith to any M1 device but everytime i get some mac mini i have to return for any different reason or bug with unity

 

1 year?. How many computers have you returned?.
Anyway, I think a Mini is not the best option for gaming development, but I'm a newcomer, not an expert though

 

I just went back from a Macbook Air M1 to my old MB Pro 13" 2019 base model with an RX5600xt eGPU and it's amazing how nice and stable the LTS version works with Intel, I can't wait for the Silicon version to catch up to deliver that stability, I can imagine it will be amazing, but for now if you're planning to get an M1/ M1 Pro to work with Unity and you already have an Intel Mac, my advise is to stick with Intel for now, maybe with M2/ M2 Pro Unity will be stable enough to consider moving.