Search Issue Tracker

Fixed in Unity 2018.2

Votes

0

Found in

2017.3.1p4

Issue ID

1025479

Regression

No

[Daydream] Rendering Corruption appears when switching back to Daydream mode

Mobile

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 2Core functionality majorly impacted

To reproduce:

1. Download attached project "Daydream_Issue.zip" and open in Unity
2. Run logcat
3. Build and run the project on an Android device
4. Insert into Daydream headset
5. Connect controller
6. Drag your finger in from the edge of the phone (on the side where the charging port is) to reveal the Home button
7. Press the home button
8. Press the task selection button (usually a square) on the Android device to pull up running applications
9. Press on this application (Daydream Issue) to bring it on screen
10. Reinsert into Daydream headset
11. Note the corruption, or return to 6 step and repeat until it appears

Founded issues:
- Flickering output in the left eye
- Dark/black rectangles. These rectangles are always in the same location, similar scale, and flicker
- Sometimes tracking stops for the main camera, however, the occlusion mesh tracks the phone but with an incorrect rotation

Notes:
- Logcat and images of this issue are shared in the comments section
- These issues are not consistently reproduced. Anecdotally it seems to be less than 30% reproducible
- In Unity 2017.1 it is easy to reproduce but in newer versions of Unity it is very hard to reproduce
- Does not seem to affect cardboard apps
- These issues only appear after pressing the Home button to switch to the Android launcher then using the task selector to return to the unity app
- Opening the task selector and returning to unity (without pressing Home first) does not cause these issues
- Opening the task selector then returning to unity resolves these issues
- Could not reproduce these issues when using 'Skip Entry' in Daydream settings
- Also affects fresh, empty projects
- Reverting the user's project settings to default values and removing user's scripts did not resolve these issues
- Benjamin Smith said that he reproduced these issues on all versions, so in any case, contact him

The User gave this additional info:
adb shell pm dump com.google.vr.vrcore | grep version
versionCode=160733190 minSdk=19 targetSdk=26
versionName=1.14.190701955
versionCode=160726230 minSdk=19 targetSdk=25
versionName=1.6.156794279

Devices:
- Google Pixel 1, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 530
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540

Reproduced on Unity 5.6.5p4, 2017.1.3p3, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0f1 and 2018.2.0b1

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.