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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment