Search Issue Tracker
By Design
Votes
1
Found in
2019.3
2019.3.3f1
2020.2
Issue ID
1238124
Regression
No
[iOS] Setting Store Action DontCare for MSAA RT, sets Store Action to storeAndMultisampleResolve instead
How to reproduce:
1. Open the attached 'StoreActionDontCareWithMSAA.zip' project
2. Build for iOS and open the Xcode project
3. Select Menu bar-> Product-> Scheme-> Edit Scheme
4. Set GPU Frame Capture to Metal and Metal API Validation to Enabled
5. Deploy the Xcode project to the iOS device
6. Press 'Capture GPU frame' button
7. In sidebar's Memory panel navigate CommandBuffer > Camera Render > Drawing > CommandBuffer.AfterSkybox
8. Select CommandBuffer.AfterSkybox and observe Store Action in the graph
Expected result: Store Action is set to DontCare
Actual result: Store Action is set to storeAndMultisampleResolve
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Couldn't test: 2018.4.23f1 CommandBuffer.AfterSkybox is not displayed
Reproducible with:
- iPhone 8 (iOS 12.0)
- iPhone XR (iOS 13.4.1)
Note: Screenshot of the result attached in Edit
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2020.2.X):
This is currently by design of the API