I have developed my game on Unreal Engine 5.03 on Windows, when I try to open the project on MAC to package it for MAC. I’ve got compile shaders error, could not locate target file. location intermediate/shaders/tpm/EF04 something like this.
How can I fix this?
Please help, I need a package on MAC for the educational game I created to teach students, since the school only has MACs.
I am very new on MAC. Never tounch it before and also a first time developer on Unreal Engine too.
Hey there @gr4j0m3r! Sounds like the shaders might benefit from being regenerated. So first things first, please back up your project before doing any of this as it can cause different issues than the one you’re having.
First, open your project and go to the console and enter in recompileshaders all and this will force a recompile of the shaders. Then try to build again.
If that fails, close the project, head to the project folder and delete the Saved and Intermediate folders. This will get rid of lots of caches and saved data that will all have to be regenerated. Then launch the project to regenerate them in their entirety. Then try to build again.
2 Likes
Thank you, I will try this.
It works, the project can be opened now. One question, do I have to wait for shader compiling to complete (in editor) before I can package the project (shipping). I borrowed an old MAC from a frind and take forever. Like I said the game already run good on Windows but since I deleted save and intermediate folders (recompileshaders all didn’t wortk) so I wonder if I have to wait for it again?
When building the shaders are prepared on their own, I don’t believe the preview shader build in editor is required for your packaged build to succeed. When attempting to package, does the error remain the same shader listed as missing?
1 Like
No, the shader missing did not occur when pakaging, not even in the first place. I have waited till compiling is done but now I am trying to package but got automation error instead. I’m kinda give up and opt to use Windows version instead since the automation error is not the only error I got when packaging, which is not occur at all when I package it
on Windows.
Ahhhh that’s unfortunate! Are the windows builds working appropriately however?
Windows version got no error at all.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.