Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.1p4
Issue ID
764799
Regression
Yes
[iOS] Frame rate is unstable on 5.x, leads to CPU throttling
Steps to reproduce:
1. Open attached project
2. Build for iOS with 'Development build' and 'Autoconnect profiler' enabled
3. Build Xcode project and run on device
4. Open the profiler window and make sure it is connected to the device running the app
5. Observe Camera.Render CPU time and FPS (top-left corner in the application) as you do the following steps
6. Add 35 characters to the scene using the "Add Char" GUI button
7. Add 12ms of CPU delay using the "Add 0.5ms CPU Delay" GUI button
8. Notice the Camera.Render time jumps to 10-12ms as you increase the CPU delay and FPS drops to ~30
All 5.X versions exhibit more or less the same behaviour. In 4.7 - Camera.Render stays at ~5ms and FPS stays at ~50.
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
Add comment