PreAlpha 0.5 #127 crash on macOS [UNITY ISSUE]

Locked
User avatar
Jukic
Posts: 68
Joined: Sun May 13, 2018 5:51 pm

PreAlpha 0.5 #127 crash on macOS [UNITY ISSUE]

Post by Jukic »

Hello,
on macOS (High Sierra; 10.13.5) Legacy Stable 0.5 #122 16-Jun-18 works ok, but the new build PreAlpha 0.5 #127 17-Aug-18 crashes immediately on launch with:

Application Specific Information:
-[MTLRenderPipelineDescriptorInternal validateWithDevice:]:2400: failed assertion `No valid pixelFormats set.'

all the best!

User avatar
Interkarma
Posts: 7236
Joined: Sun Mar 22, 2015 1:51 am

Re: PreAlpha 0.5 #127 crash on macOS

Post by Interkarma »

Hey there! :) Could you let me know your system specs and attach a zipped copy of the full output log?

Check the guidelines topic for location of player log on your platform.

Cheers.

User avatar
Jukic
Posts: 68
Joined: Sun May 13, 2018 5:51 pm

Re: PreAlpha 0.5 #127 crash on macOS

Post by Jukic »

sent you a msg.

all the best!

User avatar
Interkarma
Posts: 7236
Joined: Sun Mar 22, 2015 1:51 am

Re: PreAlpha 0.5 #127 crash on macOS

Post by Interkarma »

Thank you for the log. :)

I'm posting below for completeness.
nitialize engine version: 2018.1.4f1 (1a308f4ebef1)
GfxDevice: creating device client; threaded=1
2018-08-28 22:10:23.073 DaggerfallUnity[30434:660851] Color LCD preferred device: Intel(R) Iris(TM) Plus Graphics 640 (low power)
2018-08-28 22:10:23.073 DaggerfallUnity[30434:660851] Metal devices available: 1
2018-08-28 22:10:23.073 DaggerfallUnity[30434:660851] 0: Intel(R) Iris(TM) Plus Graphics 640 (low power)
2018-08-28 22:10:23.073 DaggerfallUnity[30434:660851] Using device Intel(R) Iris(TM) Plus Graphics 640 (low power)
Initializing Metal device caps: Intel(R) Iris(TM) Plus Graphics 640
Begin MonoManager ReloadAssembly
- Completed reload, in 0.186 seconds
WARNING: Shader Unsupported: 'Daggerfall/Automap' - Pass '' has no vertex shader
-[MTLRenderPipelineDescriptorInternal validateWithDevice:]:2400: failed assertion `No valid pixelFormats set.'
It appears failing shader is "Daggerfall/Automap". This file had a few automatic changes as part of upgrade to Unity 2018.1.2.

https://github.com/Interkarma/daggerfal ... c361451133

The change is effectively modifying the following from:

Code: Select all

OUT.pos = mul(UNITY_MATRIX_MVP, v.vertex);
To:

Code: Select all

OUT.pos = UnityObjectToClipPos(v.vertex);
It appears these changes have broken compatibility with Jukic's integrated GPU (Iris Plus Graphics 640).

Jukic, we will try to find a solution for you, but I can't promise anything as your GPU might not meet minimum spec. Will look into this in more detail when I have time.

Possibly even Nystul will be able to assist as the original author of automap shader.

User avatar
Jukic
Posts: 68
Joined: Sun May 13, 2018 5:51 pm

Re: PreAlpha 0.5 #127 crash on macOS

Post by Jukic »

Hey all,

great. I will also look into it!

All the best!

User avatar
Interkarma
Posts: 7236
Joined: Sun Mar 22, 2015 1:51 am

Re: PreAlpha 0.5 #127 crash on macOS [UNITY ISSUE]

Post by Interkarma »

This is a Unity-related issue fixed in Unity 2018.2.0a8.

https://issuetracker.unity3d.com/issues ... -assertion
https://issuetracker.unity3d.com/issues ... g-on-metal

Fix does not appear to have been back-ported to Unity 2018.1 at this time. Cloud build currently targets latest 2018.1.x.

I'll look at switching over MacOS cloud build to use latest 2018.2.x. I have an upgrade to 2018.2 in pipeline regardless, but if I can fix for MacOS sooner that would be great.

User avatar
Jukic
Posts: 68
Joined: Sun May 13, 2018 5:51 pm

Re: PreAlpha 0.5 #127 crash on macOS [UNITY ISSUE]

Post by Jukic »

Back after some time away from the comp...

Wow, You are wonderful Interkarma!

User avatar
Jukic
Posts: 68
Joined: Sun May 13, 2018 5:51 pm

Re: PreAlpha 0.5 #127 crash on macOS [UNITY ISSUE]

Post by Jukic »

Hey hey,

just had the opportunity to try build #131 and it works like a charm! thank You !
(no mods)

User avatar
Interkarma
Posts: 7236
Joined: Sun Mar 22, 2015 1:51 am

Re: PreAlpha 0.5 #127 crash on macOS [UNITY ISSUE]

Post by Interkarma »

That's great to know, thanks for getting back to me. :)

I'll bring the whole project up to 2018.2 near term. There's a few things I want to work through first.

Locked