iOS Metal crash at launch

We’re having a problem getting builds with Unity 2017.2.0p1 on iOS launching without Metal crashes. Is anyone experiencing crashes like this at launch? Any ideas what might be causing it?

We’ve had problems with Metal before with MSAA and other stuff but so far I haven’t managed to track this crash down.

Crash with 2x antialiasing enabled;

Crash with no antialiasing;

Please submit a bugreport.
Thanks!

@Mantas-Puida hey :slight_smile: I’ve finally tracked this down to configuration, I think. I will submit my repo shortly and post the case number here in case you want to follow up (Case# 968798). As with some previous bug reports you’ve looked at for me years ago, I’m trying to do some multi-camera compositing and it’s just not working.

My current test devices are iPhone 5S, iPad Air (original, A7) and iPhone 8+. Currently a scene with a single camera that’s set to clear depth-only causes the crash. Using the forward renderer with hdr enabled, if I use 2x antialiasing I get the crash above (with the source texture type not compatible). With no antialiasing, I get another crash that mentions command encoders (failed assertion `A command encoder is already encoding to this command buffer’). Either way, it crashes. I have double-checked player settings like ‘Metal Restricted Backbuffer’ (unchecked) in case anything might have been causing problems.

It seems to be related to hdr. Disabling hdr on the camera and in graphics settings means no crash.

The same project works fine on OSX, any settings.

At the moment this is was a bit of a showstopper for us. Everything was working on Unity 5.6 but Unity 2017.2 has been a bit of a nightmare all round. Thanks for keeping an eye on the forums - I’ll submit the bug report now.

Submitted bug report with project, Case# 968798.
Additional bug report with another repro project, Case# 969730.

Update 17/11/2017: The bug was reproduced by Unity QA.