IndirectLight building consumption #4328
Unanswered
ThomasGorisse
asked this question in
Q&A
Replies: 2 comments 3 replies
-
When you get a new IBL from ARCore you'll have to free up the previous IBL ( |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for your answer. We went on the wrong direction for solving a memory consumption. It didn't came from the IBL but from some duplicate calls to ARCore consuming functions inside the FrameCallBack. google-ar/arcore-android-sdk#1262 |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We are currently investigating some memory leaks turning around buffer Images consumption with the help of ARCore team here: google-ar/arcore-android-sdk#1262 (comment)
And it seems that Sceneform is kidnapping some image buffers ended with none available anymore for ARCore processing.
One of our think is that it could come from the environment cube map processed for indirect Lighting.
My first target is this call made from the frame callbacks.
My question:
Do you think this indirect light framed called could be consuming?
Sceneform indirect light is still made the "old" way and doesn't yet use the KTXLoader.
Beta Was this translation helpful? Give feedback.
All reactions