Search Issue Tracker
Fixed in 2018.1.X
Votes
11
Found in
2017.2.0f3
Issue ID
970964
Regression
No
CPU cost of render canvas for moving world-space UI is too high in 2017
How to reproduce:
1. Download attached project file and open "test" Scene
2. Open Profiler and enter Play Mode
3. Watch cost of UIEvents.WillRenderCanvases in 2017
4. Watch cost of Canvas.BuildBatch in 5.6
Actual result: The CPU cost of moving world space UGUI render canvas is much higher in 2017 than 5.6.4, nearly doubled.
Reproduced with: 2017.1.2p3, 2017.2.0p3, 2017.3.0b11
Not reproduced with: 5.6.4p3, 2018.1.0a6
Occurring since: 2017.1.0a1
------------------
Issue no longer reproduces on recent releases:
5.6.5p1: 2-5 ms
2017.1.3p2: 3-4 ms
2017.2.2p1: 2-3 ms
2017.3.1p4: 2-3 ms
2018.1.0b11: 3-4 ms
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
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
jmitcheson
May 07, 2018 05:43
Backport into 2017 LTS at some point would be nice
samizzo
Mar 06, 2018 23:51
We're seeing this on 2017.3.0p3 as well. The high CPU cost is a real problem for our game and causing serious framerate issues whenever we move the camera.
mkrzaczek
Jan 12, 2018 13:38
This problem is especially apparent on iOS. Unfortunately, the performance drop is significant enough to stop our upgrading to 2017.
Profiling from iPhone 6, Unity 2017.3.0f3:
https://imgur.com/BeYEr2d