You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2022. It is now read-only.
Hi, I'm not sure if this is an issue specifically with this particular build of Chromium, but I wanted to get this out there in case it is and anyone else is experiencing the bug. Basically, when you connect the phone (in my case, ASUS ZenFone AR) and start a remote debugging session in desktop version of Chrome, this is what you see (below). Note that the same static does not occur when using Vysor (which displays/controls the whole phone, not just the contents of Chrome/Chromium itself).
Actual screenshot during static/fuzz in session:
What is displayed in DevTools:
Does anyone else experience this?
The text was updated successfully, but these errors were encountered:
Yeah. If it helps, I've also noticed this on another app that utilizes AR.js to stream video to a <video> element, whereas this renders it to <canvas> via THREE.VideoTexture.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm not sure if this is an issue specifically with this particular build of Chromium, but I wanted to get this out there in case it is and anyone else is experiencing the bug. Basically, when you connect the phone (in my case, ASUS ZenFone AR) and start a remote debugging session in desktop version of Chrome, this is what you see (below). Note that the same static does not occur when using Vysor (which displays/controls the whole phone, not just the contents of Chrome/Chromium itself).
Actual screenshot during static/fuzz in session:
What is displayed in DevTools:
Does anyone else experience this?
The text was updated successfully, but these errors were encountered: