Block AR session creation until the ARCore device is ready |
||||||
Issue descriptionEnsure all necessary elements are ready including the GL thread / context, ARCore itself, and that we are ready to start producing frames when the session promise is resolved, that way we can deliver valid frames from the very first frame request.
,
Apr 26 2018
,
May 28 2018
,
May 29 2018
,
Jun 7 2018
The CL in comment 1 was abandoned. I don't see this bug number referenced code. It was filed in response to this code review comment: https://crrev.com/c/1005627/28/chrome/browser/android/vr/arcore_device/arcore_device.cc#135 Eventually, though, a TODO was added at this point for issue 837944: https://crrev.com/c/1005627/40..41/chrome/browser/android/vr/arcore_device/arcore_device.cc Thus, I think this is a duplicate. Really, though, issue 846521 is more similar to this description. It now blocks issue 837944.
,
Jul 4
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ijamardo@chromium.org
, Apr 26 2018