Shaders wont compile, tested 4 projects, if I press ok on the popup uefn closes.. Logs were sent
Unreal Editor for Fortnite
Other
Not sure
Shader loads
Shader error
PC
6570-5231-1418
hi ,
Metal shader fail for iOS Apple iPhone when trying to create Cinematic stream
Works on Android, Preparing Shaders successfully . Works on NS1 and PC
Metal Shaders are Apple IP for iPhone and therefore fails in Mobile Emulator for any Apple device
Metal Shader Format is Apple IP
possibly look at Launching the project on a real iPhone so that the phones packaged shaders are loaded back to UEFN.
See
Quote from above link
They’re compiled into a proprietary format (LLVM-based, device-agnostic intermediate language) that is not publicly documented. This happens as part of the build process, by default; the Xcode toolchain has a build rule to take Metal source files, compile them, and shove the output .metallib into your application’s bundle someplace. Apple’s documentation covers this in more detail.
Lets hope that will help Epic Support.
There is another problem that Apple has different licences of Europe and the USA, which may again be a problem.
FORT-1083250 has been ‘Closed’. We’re unable to reproduce this issue.
This is a consistent and frequent issue, since v40.30 I can confirm I am also getting these same problems…
It seems to be related to Windows Defender flagging many files at fortnite install folder as untrusted, and blocking uefn to run (or sometimes crashing during execution).
Two alternatives that I’ve found to fix/workaround this issue:
Here are some attached screenshots that is related to the problem:
And this is my current windows defender protection exclusion list to avoid the issue (there is more, does not fit on a single image… Every time it flags a new file/folder I add here):
After some digging, seems like the related files are unsigned, this being the reason why the defender is blocking it, here are some examples:
Reinstalling the game does not fix it (downloaded files from game install process are still unsigned)
For comparison, a properly signed file (so Windows Defender can verify its authenticity and does not flag it as untrusted) looks like this:
@Flak Please reopen this thread with these additional details, I hope it helps reproducing the issue and providing a fix. I know more people facing this same issue, so is not an isolated case…
(I have not tested if behaviors difer from Home/Pro/Entrerprise versions of windows, but also may be a good thing to check if is not only on consumer-facing environments)
I am using
