Search Issue Tracker
Fixed
Votes
0
Found in
5.5.0a5
Issue ID
823580
Regression
Yes
[metal/hlslcc/runtime] Bigger CPU/GPU frame time on OSX and iOS Metal builds
Steps to reproduce:
1. Open attached project
2. Change graphics API to 'Metal' for Mac Standalone
3. Build 'Test' scene
4. Attach the built app to Xcode project and observe the CPU/GPU frametime (this can only be done in macOS Sierra update, previous OSX versions don't have this functionality)
Repeat these steps with 5.5.0 (trunk) and metal/hlslcc/runtime branch, notice the difference in CPU and GPU frame times.
My results:
trunk:
CPU: 28 - 30ms
GPU: 29 - 30ms
metal/hlslcc/runtime:
CPU: 33 - 35ms
GPU: 33 - 36ms
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Add comment