Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b6
Issue ID
878818
Regression
No
[Daydream][Android]Performance reduced by ~15 FPS in complex scenes compared to 5.4 GVR13
Steps to reproduce:
1) Download attached project 'TurboButtonDaydreamPerfSample.zip' and open in Unity
2) Make sure Virtual Reality Supported is enabled and Virtual Reality SDKs set to Daydream in Player Settings
3) Build and run 'prd-Forest-02-atls' scene on a device
4) Check FPS on the screen
----- Should be around 40-45 FPS(check attached screenshot '5.5.0b7.png')
5) Now open this project in 5.4 GVR13
6) Build and run 'prd-Forest-02-atls' scene on a device
----- Should be stable 60 FPS
Expected result: FPS should be stable 60FPS as in 5.4 GVR13
Actual result: FPS is much lower in 5.6.x version compared to 5.4 GVR13
Reproduced with:
5.6.0a6, 5.6.0b7
Note: This feature started since 5.6.0a6 in Unity 5.6.x
DUT: Google Pixel XL[marlin], Adreno 530, OS version 7.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment