[Chromium] Black background shown instead of real world in some AR experiences

[svillar]

Some AR experiences do not properly show the real world video stream and show a black background instead. One example from the Wolvic start page is the "Jumpy Balls" game. The problem appears with both Meta (using passthrough layer) and Pico (using blend modes) so it must be something not related to the way we do mixed reality.

Using the remote inspector I could indeed see many critical errors related to WebGL, so it must be something in our Chromium port. For example

WebGL: INVALID_OPERATION: drawBuffers: COLOR_ATTACHMENTi_EXT or NONE
bundle.mjs:10787 THREE.WebGLRenderer: Can't change size while VR device is presenting.
WebGL: too many errors, no more errors will be reported to the console for this context.

the first error was repeated 256 times before the engine stops reporting.

[svillar]

Some AR experiences do not properly show the real world video stream and show a black background instead. One example from the Wolvic start page is the "Jumpy Balls" game. The problem appears with both Meta (using passthrough layer) and Pico (using blend modes) so it must be something not related to the way we do mixed reality.

Using the remote inspector I could indeed see many critical errors related to WebGL, so it must be something in our Chromium port. For example

WebGL: INVALID_OPERATION: drawBuffers: COLOR_ATTACHMENTi_EXT or NONE
bundle.mjs:10787 THREE.WebGLRenderer: Can't change size while VR device is presenting.
WebGL: too many errors, no more errors will be reported to the console for this context.

the first error was repeated 256 times before the engine stops reporting.

Meta Browser show the same errors, so that must be a threejs issue, the problem must be somewhere else. Interestingly the meta browser spits this

Feature 'dom-overlay' is not supported for mode: immersive-ar

while Wolvic does not

[msub2]

Hmm, I remember three.js's ARButton automatically tries to insert dom-overlay, but Meta Browser doesn't support it. Is it possible it's getting hooked up to an existing Chromium interface for DOM overlay that's somehow interfering?

[svillar]

Hmm, I remember three.js's ARButton automatically tries to insert dom-overlay, but Meta Browser doesn't support it. Is it possible it's getting hooked up to an existing Chromium interface for DOM overlay that's somehow interfering?

Maybe, I tried enabling the DOM overlay support in our chromium port but it does not change anything, but it must be something related.