Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.0b10
Issue ID
1014075
Regression
No
[Metal] Depth&Stencil attachments of the system frame buffer could not be discarded
To reproduce:
1. Open user's attached project
2. Build "MainScene" for iOS
3. Open Xcode project and in build settings set Bitcode to NO
4. Run built project on the device
5. In the debug navigator click on FPS
6. Click on the camera button to capture GPU frame
7. Inspect the frames
Expected result: Depth and Stencil attachments could be discarded (at least manually).
Actual result: Unity always encodes "[setDepthStoreAction:Store] [setStencilStoreAction:Store]" at the end of frame.
Reproduced with: Unity 2017.2.2p2, 2017.3.2f1, 2018.1.0b12, 2018.2.0a6
Devices: iPhone 8 iOS 11.0, iPhone 7 iOS 11.0
-
colin299
Sep 20, 2018 03:02
I have the same problem also, I have written details in this post:
https://forum.unity.com/threads/metal-can-i-edit-unitys-screen-backbuffer-color-depthbuffer-load-storeaction.554449/
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 GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note (2019.2.X):
This should do a workaround:
https://forum.unity.com/threads/better-control-of-load-store-actions-for-camera.572749/