It doesn’t stop people from pressing the issue for future versions of the OS. It’s worth discussing. Balancing privacy and functionality is an ongoing engineering and research problem, and it makes sense for v1 of the OS to be the most restricted.

@mike_at_helium The title and first post refer to passthrough mode.

@renancoelho It seems to work here: https://ebidel.github.io/demos/offscreencanvas.html

@eskimo Why not push the over-the-limit string to stdio somehow so you don’t have to choose?

I’m not sure you’re the person to answer if you do not know the difference between the various immersive modes. No, passthrough (video of the real world) is not always on. No, not every mode is same. Each has different limits. @mike_at_helium I am hoping someone from the team can speak to the tracking limits in the mode that doesn’t have the ~1.5m limit.

@Developer Tools Engineer The terminology for the different spaces is still a little unclear. Is full-hand tracking available with passthrough on when it’s just a single app, too? Not just VR.

I think that’s why Apple partnered with Unity.

Thank you for clarifying!

@Graphics and Games Engineer Respectfully, I knew this would be the first suggestion, and it won't work. My MTLTexture is generated by a separate rendering subsystem, not something I am requesting. I do not want a new drawable unless there is a 0-cost way to substitute that drawable with another MTLTexture. Can you advise further? (I reply so quickly because I have notifications. :) ) Also, if I am misunderstanding, it's partly since I couldn't find examples of using DrawableQueue.

Also, this isn't for just one texture. It could be for hundreds/N. So it's not meant to be a single drawable thing.

@GeoffAtApple Might it eventually be re-enabled?

@Graphics and Games Engineer Thanks for that. The template, however, uses exclusively Swift code, not the C api shown in the talk. Could we also have a C/Objective-C template that only uses the minimal amount of Swift UI? The function names in the Swift API example seem very different too, so the correspondence to the C api isn’t obvious.

@DTS Engineer Thanks for that. The Vertex Amplification is a really nice touch! I think that this is great. At the moment the only thing I'd consider is whether a C-api / Objective-C-api template that hooks into the necessary Swift-UI code would be possible (like the WWDC sample). The swift function names and types don't always map intuitively to the C variants.

@gchiste I have a similar request. Would you have advice on how best to file a report like this? I had a “conversation“ in a different thread here and and it sounded like Metal + passthrough might be tricky. In a feedback request, would you like to see some suggested solutions?

@DTS Engineer I only just saw your reply (whoops). I added to the feedback report.