Search Issue Tracker
By Design
Votes
0
Found in
5.6.0f3
Issue ID
904173
Regression
No
[Metal] Render Texture coordinate Y orientation wrong. (0,0) coordinates return same result on either API
Steps to reproduce:
1. Open user attached project and "myscene"
2. Press Play and observe information in console
3. Switch graphics API from Metal to Open GL and vice versa
4. Press Play and observe information again
Expected outcome: On Metal API the 0,0 coordinate should be at the top-left. On OpenGL - bottom-left, resulting in the last statement being True for Metal API and False for OpenGL.
Actual outcome: Both API's ReadPixels() method returns bottom-left (0,0) coordinate. Last statement is false in both occasions
Reproduced on Unity 5.6.0f1, 5.6.0f3, 2017.1.0b1
Also repro'd on iPhone 6 + iOS 8.0
Notes: Couldn't test for regression, 5.5.x editor returns OpenGL API no matter the setting.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment