Search Issue Tracker
Fixed
Votes
0
Found in
5.4.0p1
Issue ID
826244
Regression
No
[iOS] Texture2D.ReadPixels reads pixels from incorrect position with Metal on iOS
Steps to reproduce:
1) Open the attached project.
2) Build for iOS using Metal as Graphics API.
3) Run the build on a device via Xcode.
4) When the app loads, press the 'SCREEN' button.
- Observe the captured area on a texture that appears.
5) Repeat 2-4 with OpenGLES 2/3 as the Graphics API.
When using Metal as the Graphics API, the area which is captured by Texture2D.ReadPixels is different from OpenGLES and the Editor.
This issue doesn't occur if the project is built as OSX standalone using Metal.
Reproduced on:
5.5.0b1, 5.4.0p3, 5.3.6p3
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 CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
- Editor hangs when opening Asset picker window for AssetReference and a lot of addresable assets are present in the project
Add comment