Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.4
2020.2
Issue ID
1235934
Regression
No
[iOS][Metal] Use of MTLHeap/MTLFence features results in GPU serialization of the Compute, Vertex, and Fragment workloads
How to reproduce:
1. Open the attached '1235934.zip' project
2. Make sure that the Development Build flag is checked in the Build Settings
3. Build for iOS
4. In the Xcode project's menu bar choose Product > Profile
5. Select Game Performance Instrument
6. Record for about 10-20 seconds then stop recording
7. Observe the GPU channels(Compute, Vertex, and Fragment) data of the recording in the GPU section
Actual result: Processes run one at a time
Expected result: Processes being run in parallel
Reproducible with:
- iPhone XR (iOS 13.4.1)
- iPad 9.7 6th gen (iOS 14.0b7)
Reproducible with: 2019.4.2f1, 2020.1.0b14, 2020.2.0a17
Couldn't test with: 2018.4.27f1 (MTLHeap/MTLFence features are not available)
Note:
- Screenshots of the actual and expected results are attached in Edit
- Fix was backported for 2020.1, 2019.4, 2018.4 streams
- Similar issues: 1252729, 1252731
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21