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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.