Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.1.0b8
Issue ID
917983
Regression
Yes
[Mobile][Regression] Playing and then pausing wct to save performance in player massively impact wct performance
How to reproduce:
1. Open user provided project
2. Build and run on device
- - Player at 30FPS, WCT at 15FPS
3. Click the 'Capture Interframe' toggle
- - Player at 60FPS, WCT at 1FPS
Before the regression:
- - Player at 30FPS, WCT at 15FPS
- - Player at 60FPS, WCT at 15FPS when 'Capture Interframe' is enabled
Reproduced on: 5.5.0a6, 5.5.4f1, 5.6.1p4, 2017.1.0b9, 2017.2.0a3
Not reproduced on: 5.4.5p3
Note: Reproduced on 5.4.5p3 using iOS
Devices under testing:
LGE Nexus 5X, OS:7.1.2, CPU:arm64-v8a, GPU:Adreno (TM) 418, Build:google/bullhead/bullhead:7.1.1/N4F26I/3532671:user/release-keys
Samsung Galaxy S5 Neo, OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-T720, Build:samsung/s5neoltexx/s5neolte:6.0.1/MMB29K/G903FXXU1BPF4:user/release-keys
iPhone 5 iOS 9.3.5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment