Forum Discussion
Export space mesh scanned on quest 3?
Hey, To cut to the chase, I want to scan my entire house, then export the space so I can load it into a 3D model. This is so I can take that low poly version of my house interior, and make my own 3...
Why does meta not allow access to spatial data for developers? That seems like an obvious thing to develop with given the hardware. I can't find an official statement saying "We don't do this because of a really good reason". Could meta clarify why this feature isn't available? And perhaps what could be done to make it available?
Privacy concerns about having data on the inside of your home. Same reason they don't allow camera access.
But we do this all the time. The app informs you that it will be collecting data. You can choose to allow/disallow access. Meta even asks you if you would like to share point cloud data with them to enable things like local multiplayer. When a developer downloads a development package to, say, generate their own point cloud, it doesn't mean it is automatically shared with Meta. This data could be used to power all sorts of apps. I agree that on a shipped app, it would need to inform the user of what the app intends to use it for and if it is sharing it with 3rd parties. I don't understand the privacy argument while developing an app at all. Could you (or perhaps Meta?) go into more detail? Maybe I am not understanding the argument fully.
I agree. Maybe they just haven't developed the SDK for it yet. They have a lot of new features to build and this is a very low priority. The low-resolution scene mesh is enough for most MR experiences I guess.
I'm totally fine if the answer isn't "we haven't gotten to this yet, but it's on our roadmap". That's fine. But so far everyone says the same answer on all forums I've read, "it's a privacy thing". That makes zero sense and I think many new developers to the quest 3 ecosystem are expecting to be able to power apps using depth/computer vision data.