When I try to view the 360 video example on the a-frame website with my Oculus Go, it works until I click the VR icon to go into true 360 format, and then all I get is a black screen. It was working this morning, so I am unsure what could have changed.
same issue with stereo 360
bit.ly/test-stereo
this link show a correction of the stereo component and worked well in vr few days ago.
I have seen this as well (working, then not working), wondered if the change might be caused by an update to the Go browser.
But it still works in some scenes even after emptying the Go browser cache, so I have some investigating to do.
I was able to reproduce the problem with the THREE example as well: https://threejs.org/examples/webvr_video.html
It does not seem to be specific to A-Frame
@DigiTec Any known problem with the Oculus Browser + Video on the Go? Problem not exclusive to A-Frame.
Known issue. Fixed in 4.6.2. Caused by some issues when introducing foveated rendering.
As workaround - disable Fixed foveation in chrome://flags (set it to None).
the workaround works, thanks!
Is there a way to fix it in production?
Definitely, it will be fixed in the next release.
Indeed, disabling foveation works. Had the same problem with simple photosphere.
@Utopiah @WellanDraco Where can disable foveation on Oculus Go (Oculus Browser) or A-Frame?
on the browser via the flags page... that's why I asked for a fix in production (cant ask every user to modify their flags)
@VasuBhog On the browser, the reason why i asked for a fix for production (cant ask every GO user to set flags before accessing vr)...
This should be fixed in latest Oculus Browser and A-Frame master.
Most helpful comment
As workaround - disable Fixed foveation in chrome://flags (set it to None).