Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.1f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1159817
Regression
No
[Metal/Vulkan] Projection Matrix in a shader is offset when CommandBuffer is used and the camera has a custom projection
To reproduce:
1. Open attached project "Metal_iOS_Bug.zip"
2. Open "SampleScene.unity" scene
3. Make sure that Metal Editor Support is enabled
4. Select the Main Camera in the Hierarchy window
5. In "Create Command Buffer (Script)" component change Projection Type from No Renderto Texture to Unity Default
6. Enter Play mode
Expected result: green overlay of the cubes are placed directly on the cubes
Actual result: the green overlay is offset and is not placed on the white cubes
Reproduced on:
2017.4.0f1 2017.4.28f1 2018.4.2f1 2019.1.6f1 2019.3.0a5
Reproduced on:
- iPhone 8 Plus iOS 12.0
- macOS 10.14.4 machine
- An Android with Vulcan enabled VLNQA00124, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
- Win 10 machine
Notes:
- Doesn't reproduce on OpenGLCore
- On Android, the green overlay can't be seen even with OpenGless2 or 3
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.1.X):
minor/cosmetic