Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0b4
2019.1.0a2
Issue ID
1083321
Regression
Yes
[macOS]Selecting a GameObject that uses a Standard shader produces a Metal error each time the Editor is restarted
How to reproduce:
1. Create a new Unity project
2. Create any GameObject that uses a Standard Shader (a Cube, for example)
3. Check the Console window
Expected result: no errors are displayed in the Console window
Actual result: 'Metal: Error creating pipeline state (Standard): Link failed: The type of fragment input user(TEXCOORD0) does not match the type of the corresponding vertex shader output' is displayed in the Console window
Reproducible with: 2019.1.0a2, 2018.3.0b5, 2018.3.0b6, 2018.3.0b7
Not reproducible with: 2018.2.9f1, 2018.3.0b3, 2019.1.0a1
Notes:
Not reproducible on Windows 10
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.1):
Fix verified in Unity 2019.1.0a8 (074c47d4e6ba)