If you add it in Xcode though, it is automatically added for visionOS as well. Is there a way to set entitlements plarform specific? Because I would like to keep the entitlement on iOS but simultaneously my target also supports visionOS.

Thank you for the tip! :)

Thank you, that's working well :) In Cinema4D the equivalent is "Morph Target".

Glad to hear! I think doing it in the Init of your view or the setup closure should be fine. Thats how I do it.

Appreciate the kind reply Sydney – thank you and fingers crossed!

@heckj do you maybe still have the Command Line Tools from the older Xcode beta selected?

Yeah it’s definitely new behavior and the docs could certainly use an overhaul in a couple places 😅

Glad it worked! 😊 They just added this method and system update condition stuff on visionOS. On iOS afaik systems always seem to be synced with the render loop by default. My assumption would be that since visionOS has high and variable refresh rates and there is certain logic that does not necessarily need to run on every frame, they added SystemUpdateCondition to make the API more flexible in the future: https://developer.apple.com/documentation/realitykit/systemupdatecondition

Hehe, glad it's appreciated 🙏 :) Interestingly I just noticed that I need to set the blend mode after assigning the texture. If I do it before, the blending is ignored. Not sure anymore how that behaved on iOS 15. Can test that tomorrow. Afterwards I can update the opacity one more time, then suddenly the texture resource is gone.

And there is nothing at all appearing for you in the Memory Graph Debugger? I get the same results on an iPad Pro M1 and iPhone 12 Pro.

Hmm, I'm currently on the public beta iOS beta (20A5312j). I could check if there is a difference to dev beta 3? When I paste your code into my sample project and I can observe the same kind of leaks within the Memory Graph Debugger. Not sure if it's the MeshAsset per se, but based on screenshot #2 above it seems to be related to re:AssetLoadDescriptor and re:MallocAllocator. I think there is definitely something going on, because there are no reported leaks when running the same code on iOS 15.

Any news on that front? I just checked and unfortunately this problem still persists unchanged in iOS 16 Beta 1…

Okay perfect – yeah I figured it might be helpful. Looking forward to the implementation then ;)

Hi, the ID is 9489378 Admittedly it's rather short and straight to the point though – let me know if you require more usecase details. ;)

No worries, glad it was helpful!