Search Issue Tracker
Fixed in 2017.2.0f3
Votes
2
Found in
2017.1.0f3
Issue ID
930653
Regression
Yes
An app with a 360-degree video and enabled Gear VR does not move smoothly and has a poor performance
Reproduction steps:
1. Open the attached project;
2. Enable VR and set to Oculus in Player Settings;
3. Build the scene "Main" on a device (OZOPlayerSDK -> Examples -> Scenes);
4. Open the built app and move a device to view the video;
Actual result: during moving a device, the view is jittering.
Expected result: the view should move smoothly.
Reproduced with: 5.6.1p1, 5.6.2f1, 5.6.2p3, 2017.1.0f3, 2017.2.0a1
Not reproducible with: 5.6.0f3, 5.6.1f1
Regression introduced in 5.6.1p1
With 2017.2.0b3 version, an app does not work at all.
Devices under test:
Reproducible with:
Verizon SM G930V*, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Verizon/heroqltevzw/heroqltevzw:7.0/NRD90M/G930VVRU4BQA2:user/release-keys
Not reproducible with:
Samsung SM G950U*, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 540, Build:samsung/dreamqltesq/dreamqltesq:7.0/NRD90M/G950USQU1AQC8:user/release-keys
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