Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.8f1
2022.1
2022.2
Issue ID
1397304
Regression
No
Custom Shader Texture is pixelated on M1 Macs
How to reproduce:
1. Open project "Bug Pixelated Texture Sample M1.zip"
2. Enter Play Mode
3. Observe the Texture
Expected result: Texture is not pixelated
Actual result: Texture is pixelated
Reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.13f1, 2022.1.0b6, 2022.2.0a5
Notes:
- Reproducible in the Editor and the Player
- Texture is not pixelated on Intel Macs
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
The shader uses a lot of half precision floats. Intel/AMD GPUs do not support half precision floats, but the M1 does.
This looks like a precision issue. On M1, actual halfs are used, leading to large rounding errors causing the artefacts. On Intel, where halfs are not supported, full precision floats are used instead, preventing the rounding errors / artefacts.
This issue can be resolved by changing the shader to user full precision floats where necessary.