@Vision Pro Engineer Thanks for the reply, Michael Is the following based off what you've heard or do you have videos and files that show the behavior? Mostly based off user testimonial. I think we have recorded a couple instances of this during onboarding sessions, but in those cases, we suspected that screen sharing itself could be contributing to the issue. Do you have any logging in place that is capturing any RoomCaptureSession.CaptureError errors in production? Yes - we track all fatal scanning errors. We haven't noticed an uptick in those. It seems like another developer was able to improve performance by resolving a memory leak. Have you profiled the application when performing multiple scans in a row? We have done some profiling over the years, but it's difficult because the act of profiling itself severely degrades scanning performance. We have noticed that RoomPlan itself seems to cache/retain resources after scanning even if we have no active references to it. I believe we reproduced this
Topic:
Spatial Computing
SubTopic:
General
Tags: