Search Issue Tracker
Won't Fix
Votes
1
Found in
5.6.0f3
Issue ID
904634
Regression
No
[VR] Daydream rendering queue differs from other VR SDKs when using camera's clear flags as Skybox and a second camera
To reproduce:
1.Download and open attached "Artifacts.zip" project.
2.Go to Player Settings and make sure that in Virtual Reality SDKs Daydream enabled.
3.Build and run project on Device which supports Daydream SDK.
4.Connect Daydream controller.
5.Notice rendering issues on right eye.
Expected result: Scene is rendered without any visual artifacts in Both VR eyes.
Actual result: Scene is rendered with visual artifacts in Right eye.
Reproduced with 5.6.0p3, 2017.1.0b2.
DUT:
Reproduced with [Daydream]:
Google Pixel, OS:7.1.2, CPU:arm64-v8a, GPU:Adreno (TM) 530,
Build:google/sailfish/sailfish:7.1.2/N2G47E/3766409:user/release-keys
Not reproduced with [Cardboard][GearVR]:
Samsung SM G925F (Galaxy S6 Edge), OS:6.0.1, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zeroltexx/zerolte:6.0.1/MMB29K/G925FXXU5DQA7:user/release-keys
Verizon SM G930V (Galaxy S7 Verizon), OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Verizon/heroqltevzw/heroqltevzw:7.0/NRD90M/G930VVRU4BQA2:user/release-keys
Notes: Could not test on earlier versions because of compatibility issues. Reproduces only on Daydream. Works fine with Cardboard and GearVR.
Comments (1)
-
petrucio
Jul 04, 2017 09:24
Still getting this bug on 5.6.2, still preventing us from upgrading.
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
- Tile Palette grid is moved after entering Play Mode
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Font Import Settings documentation page is missing when the documentation button is pressed in the Inspector window
Resolution Note (2018.3.X):
This seems to be an OpenGL driver issue, and out of our ability to fix.