MTLCompilerService crash upon startup, slow performance and missing effects

[themacintoshnerd]

Title

https://xemu.app/titles/4d530064/#Halo-2

MTLCompilerService crash upon startup, slow performance and missing effects

Bug Description

When launching Halo 2 "MTLCompilerService" on macOS crashes. What follows is a black screen followed by poor performance (8 FPS in the Menu, wildly variable in game) and many broken effects. Including but likely not limited to:

• loss of blue tint on the menu screen
• hud is broken (letters work as do button prompts all other effects are MIA)
• clear hands and legs on the view model (a holographic effect almost)

This is just what I encountered while testing.

Expected Behavior

I'd expect preformance to be similar to Halo CE (which I can run much better than I can 2 all testing here was done at 1x res, I tend to play CE at 3x res on this same machine)

Menu should have a blue tint to it

Hud should have a cross hair, radar and shield status borders around the grenade indicators

Master Chiefs hands should be solid.

Actual Behavior

Expected Behavior

Actual Behavior

Expected

Behavior

xemu Version

Version: 0.7.96
Branch: master
Commit: 0ee7502
Date: Sun Jun 18 08:03:32 UTC 2023

System Information

OS: macOS 14.0 Sonoma DP2
SoC: Apple M2 (10 Core GPU Variant)
Driver: 4.1 Metal - 86
Shader: 4.10

Additional Context

mtl_xemu_crash.txt

Willing to test further if needed.

Lovely little project btw thanks for y'all's hard work :)

[mborgerson]

Thanks for the bug report.

• Regarding the visual issues you're seeing, they are already mentioned here: Halo 2: Flickering/depth issues on Apple M1 Macs #524
• Regarding performance, it is expected for now.
• Regarding the 'MTLCompilerService' crash, have you restarted your system lately? I have had issues after updates on macOS that were resolved by a restart.

In the future, please try to search for previous issues before filing, and when filing a new issue please try to narrow the issue report to a singular problem, so the issue can be more easily tracked and resolved. If you need to create multiple issues, that is okay.

[themacintoshnerd]

I see, should I close this issue and make one specifically for the MTLCompilerService issue?

A restart also didn't fix the issue fwiw

[mborgerson]

I see, should I close this issue and make one specifically for the MTLCompilerService issue?

Let's simply make this issue only about the MTLCompilerService issue for now

A restart also didn't fix the issue fwiw

Thanks for checking