Issues with cooking for Mac on Windows with 5.8, Metal shader converter version mismatch

Hey, I’m trying to get a Mac client build working in a project that’s on 5.8, and we’d like to cook on Windows to match the cook-on-Windows flow for iOS. This was working on a separate 5.7 project but it’s not working on the 5.8 project- the cook itself succeeds, but the build crashes at startup time. The crash is a `EXC_BAD_ACCESS (SIGSEGV)`, `KERN_INVALID_ADDRESS at 0x3`, and the logs show

```

LogMetal: Error: Failed to generate a pipeline state object:

error: linking module flags ‘irc.version_minor’: IDs have conflicting values

LogRHI: Error: Failed to create graphics pipeline …

```

There are plenty of other LogMetal logs e.g. `LogMetal: Display: No .metalmap file found for …` and `LogMetal: Error: Descriptor: <MTLRenderPipelineDescriptorInternal:` lines.

The Mac running the build is a M4 Max, macOS 26.5.1.

The current theory is that it’s because of a version mismatch in the Metal Shader Converter tool between Mac and Windows in the engine. The Metal libs for both Mac and Windows were updated to 3.0.6 in CL 50054843, then CL 53352262 updates only the Mac version to 3.1.1, with the Windows version still being 3.0.6. The 3.1.1 version is shown in Engine/Source/ThirdParty/Apple/MetalShaderConverter/include/metal_irconverter/ir_version.h, and the binaries are in Engine/Binaries/ThirdParty/Apple/MetalShaderConverter. The AI-helped explanation was “At runtime the Mac Metal RHI creates a stage-in function using the engine’s Mac Metal Shader Converter dylib and links it to those shaders.”, and the shaders being cooked on a different version than the runtime is causing the `‘irc.version_minor’: IDs have conflicting values` error.

Do you agree with that explanation, and if yes could you advise us on a fix? I would have tried updating the Windows converter dll in the engine myself but I can’t find 3.1 on the Apple developer site, only 3.0.

Steps to Reproduce
I don’t think the repro would be project specific: using UE 5.8, build a Mac client where the cook was done on a Windows machine, then run the build and it should crash.

Hi Patrick,

Can you confirm that you are using the Metal Tools for Windows v 5.3? That appears to be the required version for 5.8. Are you using the IOS remote build from Windows?

Best regards.

Hi Patrick,

Your assessment is correct. Can you confirm which branch of 5.8 you’re on?

Best regards.

Hi Patrick,

It appears that release 3.1.1 from Apple omitted a Windows side update. You can integrate CL 57724933 which should drop in against 5.8.2. We will plan an internal fix along with the 5.8.5 release.

Best regards.

Thanks for confirming Patrick.

Hi, yes we’re using Metal Developer Tools 5.3, via AutoSDK. But it’s not using the remote build flow, it’s running on Horde where the compile happens on a Mac agent then the cook is on a Windows agent.

The stream is on 5.8.2 at the moment, although it will be updated to 5.8.3 very soon. It looks like those Metal folders haven’t changed between the two.

I just integrated that CL + tested and it worked, thank you!