Forum Discussion
[OVROverlay] Black board appears while quick move with Underlay cubemap
We setup a demo scene with:
- add an OVRCameraRig
- add an OVROverlay. configure with Underlay & Cubemap
- clear Unity's Skybox
We run this scene on Android, then shake the phone quickly. we can see an black board appear, looks like the board move too slow to catch up phone moving.
This can be reproduced with:
Oculus Utilities v1.15.0
Unity 5.6 and Unity 2017.1
Demo project: https://github.com/sycx/CubemapOverlay/tree/black_border (note: checkout black_border branch)
Here is the screen shoot and video captured by oculus
- add an OVRCameraRig
- add an OVROverlay. configure with Underlay & Cubemap
- clear Unity's Skybox
We run this scene on Android, then shake the phone quickly. we can see an black board appear, looks like the board move too slow to catch up phone moving.
This can be reproduced with:
Oculus Utilities v1.15.0
Unity 5.6 and Unity 2017.1
Demo project: https://github.com/sycx/CubemapOverlay/tree/black_border (note: checkout black_border branch)
Here is the screen shoot and video captured by oculus
11 Replies
Replies have been turned off for this discussion
gconvergen said:
I wouldn't count on this being high priority for a fix - it's very, very hard to trigger with the headset on and impact, in my opinion, is extremely low.
It happens in 5.5.4p4, Utilities 1.15 as well, for what it's worth.
Yes, this is our headache here(we are in the same team). This is the barebone demo project specially been setup to demonstrate the issue we encounter in our live product.
In the live product, with the glasses on, we can observe the black border "torn out" more easily when nodding our heads quickly(S6, S7, S8, all the same), and it becomes more frequently when there were small load spikes by some background works, although, our FPS counter rarely went down below 57~58.By the way, with the cubemap layer totally disabled, i.e, only use Unity's skybox for background rendering, we can not observe this effect.Our best guess, this is caused by the rendering pipeline setup, when we mixed the usage of overlay within Unity, but we are out of leads at the moment. :#
The above observation is wrong, see update from @sycx below.- Here are some screenshots to explain the problem:
First, without OVROverlay, while moving head quickly, Unity expanded black area.
Then, we enabled OVROverlay, we can see expanded area override by rendering output from OVROverlay cubemap - any update? :) @imperativity
- @imperativity oh wow, that's really fast, can't wait for the update!
- We found the Cubemap function still broken in 1.20 release.
@imperativity any further information? Will it fix in next release? - @imperativity any update?
- Just checking in to see if there is a fixing coming
- @imperativity
We tested cubemap functionality in 2017.3.1f1 and 2017.3.1p4 with 1.24.0 Utilities. still got this error message:OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_ENUM: enum argument out of range
