Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a1
Issue ID
1001306
Regression
No
[VR][Android] Bottom inner side area of VR eyes has sharp edges when Default Cardboard viewer is selected on Galaxy Note 8
To reproduce:
1. Download and open attached "case_997887-AndroidStereoTest.zip" project.
2. Build and run on Galaxy Note 8 device.
3. Notice Sharp edges in the bottom inner side of the VR eyes.
- Issue won't reproduce unless Headset in VR settings is set to "Default Cardboard"
Expected result: The area at the bottom inner side of VR eyes is smooth, without sharp edges.
Actual result: The area at the bottom inner side of VR eyes has sharp distorted edges.
Reproduced with: 2018.2.0a1, 2018.1.0b8, 2017.3.1p1, 2017.2.1p4, 2017.1.3p1
Devices under test:
Reproduced with:
Samsung SM N950F, OS:7.1.1, CPU:arm64-v8a, GPU:Mali-G71,
Build:samsung/greatltexx/greatlte:7.1.1/NMF26X/N950FXXU2BQKG:user/release-keys
Not reproduced with:
Samsung SM G930F, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880,
Build:samsung/heroltexx/herolte:7.0/NRD90M/G930FXXU1DQJ3:user/release-keys
Google Nexus 6P, OS:7.1.2, CPU:arm64-v8a, GPU:Adreno (TM) 430,
Build:google/angler/angler:7.1.2/N2G48C/4104010:user/release-keys
Google Pixel 2 XL, OS:8.1.0, CPU:arm64-v8a, GPU:Adreno (TM) 540,
Build:google/taimen/taimen:8.1.0/OPM1.171019.018/4518263:user/release-keys
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note:
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.