Search Issue Tracker
Not Reproducible
Fixed in 2017.1.X, 2017.3.X
Won't Fix in 5.4.X, 5.5.X, 5.6.X, 2017.2.X
Votes
0
Found in
5.4.4p4
Issue ID
924891
Regression
Yes
[Android] Increased frametime on GLES3 compared to Unity4
How to reproduce:
1. Open attached project 'u4_vs_u5_perf_disparity.zip'
2. Build to device
3. Inspect logcat for frame time messages
Expected result: Similar frame times between Unity4 and Unity5 when using GLES3
Actual result: Significantly bigger frame times (50ms~ -> 160ms~)
Reproduced on: 5.1.0f3, 5.2.5f1, 5.3.8f2, 5.4.5p4, 5.5.4p1, 5.6.2p1, 2017.1.0f1
Not reproduced on: 4.7.2f1
Devices under testing:
LGE Nexus 5X | Snapdragon 808 | Adreno 418 | Android 7.1.2
Samsung Galaxy S7 | Exynos 8890 | Mali-T880 | Android 7.0
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
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
Resolution Note:
Not reproducable: Old case, the reported unity4 project is no longer reachable.