Here are a few tips and steps I take for building. I think it might be helpful for some.
I mention before but as I read on this thread might not apply to everybody due to disk space. I keep two copy of the branch because I wasted too much time trying to fix broker commit and at the end I learn my technical expertise isn’t at that level so for my own sanity I clone the repo ue5-main twice and always keep one update, if it break it’s fine because I still got one that is compiling.
Anyways here are the steps I used to compile and unless the commit is broken this steps work all the time for me.
Files I modified for editor and shader native Apple silicon M1 (normally I only do this once, git pull doesn’t override them):
Engine/Build/BatchFiles/Mac/XcodeBuild.sh Line 106: dotnet Engine/Binaries/DotNET/UnrealBuildTool/UnrealBuildTool.dll ShaderCompileWorker Mac Development -architecture=arm64
Engine/Source/Programs/UnrealBuildTool/Platform/Mac/MacExports.cs Line 48: return AppleArchitecture;
Engine/Build/BatchFiles/Mac/Build.sh Line 28: dotnet Engine/Binaries/DotNET/UnrealBuildTool/UnrealBuildTool.dll ShaderCompileWorker Mac Development -architecture=arm64
And this last step build the shader and Editor in one step: ./Engine/Build/BatchFiles/Mac/Build.sh UnrealEditor Mac Development -buildscw -architecture=arm64 -verbose
Not silly at all ”is it plugged in” is always a good starting point.
I did double check that and it was pointed to the correct one. So literally as I posted this message this morning after having built the projects via Xcode + cli but getting only intel binaries I hail married and hit build in Xcode for ue5 before work and I just checked and it worked!!! Not entirely sure which steps I performed to make it work but @Rspaulino s last post mostly covered it although there were a few other script files that I didn’t change that they did.
I got it all up and running with unreal editor showing up as apple, woo!!!. Now to figure out how the heck to work in unreal
@Rspaulino this is awesome, thank you!!! Based on your description the last step is what I think I was tripped up on with cli step, I didn’t see the architecture as an option in those docs and was thinking It somehow magically used the xcodebuild.sh with it which makes sense why I kept getting intel binaries.
Thanks again for your time and such concise steps!
I’ve noticed that both the 5.1 branch as well as the ue5-main branch (which is 5.2) have PointLights which don’t work unless I enable Distance Field Shadows. They show up as Preview textures (the words Preview are literally cast on the effected objects). SpotLights however do work.
Additionally enabling Quixel (and the web browser plugins) cause instant crash once I open the quixel browser from either the menu or by going Content Browser → right click → Add Quixel Content. (See screenshots)
I feel so dumb for asking here, but I’ve now tried to download the branch from github twice and I get the same result. I have tried to google to the best of my ability, but it has all been futile, so I figure I’ll ask here.
I downloaded the 5.1 branch from github, and followed the instructions underneath explaining how to build the project.
Once the github files are downloaded, I double click the “Setup.Command” and afterwards GenerateProjectFiles.command." I then try and open the project in xcode, but it is completely empty… I’ve attached a screenshot showing the error msg.
I really hope someone can help me out here, as running the native client installed through the game launcher leaves my CPU at 95c.
Where it says UE5 with the application icon, click it and select the ShaderCompiler. Hit CMD+B to build. Once that’s finished go back to ShaderCompiler and select UE5 again. Now hit CMD+B again to build the editor.
I would like to ask you some questions. UE5 doesn’t work properly for me on my M1 Max. I don’t know if I have to do some configurations.
Write me if you don’t mind, fankugast@gmail.com
Hi there, I’m new to the game development space. Sharing some updates / issues experienced when using the 5.1 Preview build from the Epic Games Launcher. I am using an M1 Max 32 core, 64GB RAM.
The shaders have completed compiling as the GPU status is now idling. I’m getting this weird rendering effect on the screen. I’ve changed the project settings to enable global illumination via project settings
Previously when running this sample project on 5.0.3, average framerates would be 18-20. Right now I see an average of ≈30fps so there are noticeable performance improvements.
If anybody has suggestions for me to fix this / it’s a common issue, please let me know. Thank you!
I haven’t been keeping up with UE5 for a while but I would suggest posting your question here in case somebody more knowledgeable than I can offer input as well about the issues you’re experiencing.
I have the same problem. Enabling dithered LOD transitions in the material editor seems to fix it but slightly increases the instruction count. Some of my static mesh LOD 0’s are also messed up. If anyone knows an actual fix, that would be great.
Great to see this thread
I’m going to assume Unreal will have an official fully working downloadable ARM release ready when Apple introduces their VR goggles somewhere end of this year or 2023. Unless Apple created a new 3D engine (or partnered with someone) that’s competing with Unreal, Unreal would make sense to be their main build tool for their VR native content. Apple will most likely release a new Mac to beat the current competition as well. Let’s see what happens.
”is it plugged in” is always a good starting point.
