Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0p1
Issue ID
971304
Regression
No
[Metal] Shader does not work on Metal and does not produce any errors or warnings
Steps to reproduce:
1. Open “MetalBug.zip” Unity project
2. Double-click on “Cube” object in Hierarchy to focus it in Scene view
Expected results:
Shader works and Cube is rendered normally
Actual results:
Cube is rendered with a pink texture
Reproduced in: 2018.2.0a1, 2018.1.0b6, 2017.3.1p1, 2017.2.1p3, 2017.1.3p1, 2017.1.0a1
Note: works as expected in OpenGL
Comments (1)
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
richardkettlewell
Feb 12, 2020 14:46
This was actually a very specific user error (kind of) - their shader contained
#define INFINITY 1e10
but metal defines its own infinity, and it conflicted with the one the user defined.
the fix in this case was to rename the user's INFINITY define to something else.
if you have a different case of this failing, please submit a new bug with repro project.