Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
7.4.1
Issue ID
1284517
Regression
Yes
[iOS] [URP] Depth Prepass results in performance regression when MSAA is enabled and render feature using camera color target
How to reproduce:
1. Open the attached 'Archive.zip' project
2. Go to File > Build Settings and tick Development Build checkbox, switch platform to iOS
3. Build for iOS and open the Xcode project
4. Select Menu bar-> Product-> Scheme-> Edit Scheme
5. Set GPU Frame Capture to Metal and Metal API Validation to Enabled
6. Deploy the Xcode project to an iOS device
7. Press 'Capture GPU frame' button
8. Take a few GPU frame captures in Xcode and observe timings for Depth Prepass
9. Upgrade URP package to 7.5.1 and repeat the above steps
Expected result: Depth Prepass timing is similar to URP 7.3.1 or increases insignificantly
Actual result: Depth Prepass timing increased comparing to URP 7.3.1
Reproducible with:7.4.1, 7.4.2, 7.4.3, 7.5.1(2019.4.13f1), 8.2.0(2020.1.9f1), 10.0.0 - preview.26(2020.2.0b7, 2021.1.0a1)
Not reproducible with: 7.3.1(2019.4.13f1)
Reproducible with:
iPhone XR (iOS 13.4.1)
iPad 9.7’ 6th gen (iOS 14.2)
iPhone 8
iPhone XS
Not reproducible with:
iPhone 8 Plus (iOS 12.0)
iPhone 6S (iOS 13.3.1)
Notes:
- Doc of the test results is attached in Edit
- Tested using MSAA 4x, Metal Graphics API
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
- [Linux] Top left corner of the screen is unresponsive when the Editor recompiles
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
- Profiling information icon does not update for Light Mode
- [Linux] Type to select functionality is missing for drop down menus
- TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
Resolution Note:
We we're not able to reproduce the performance regression on multiple lower-end iOS devices, therefore the issue cannot be fixed. If you have any additional information regarding this issue, please submit a new bug report.