Closed cabanier closed 6 months ago
@bialpio what do you think?
Any update on this PR?
Any update on this PR?
@toji ?
Pinging @bialpio on the question I asked previously: Does the Android depth sensing use the GPU accelerated path at all?
If not, I'm inclined to say that the GL_TEXTURE_2D
path should be dropped prior to merging.
Pinging @bialpio on the question I asked previously: Does the Android depth sensing use the GPU accelerated path at all?
Ah, sorry, missed the in-review comment. No, we do not support the GPU-accelerated path for our ARCore-backed implementation on Android.
Pinging @bialpio on the question I asked previously: Does the Android depth sensing use the GPU accelerated path at all?
Ah, sorry, missed the in-review comment. No, we do not support the GPU-accelerated path for our ARCore-backed implementation on Android.
Could we update the sample so it works on Android as well? Maybe by uploading the depth to a texture?
Pinging @bialpio on the question I asked previously: Does the Android depth sensing use the GPU accelerated path at all?
Ah, sorry, missed the in-review comment. No, we do not support the GPU-accelerated path for our ARCore-backed implementation on Android.
Could we update the sample so it works on Android as well? Maybe by uploading the depth to a texture?
Let me look into that, I think the public sample may not have the changes that happened in our internal, for-testing sample.
Preview | Diff