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!

Thanks for the heads up, that's great news! :) Btw: is there a reason why these kinds of fixes rarely make it into to the release notes (https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-15_4-release-notes)?

Hi Daniel, yep that's a valid usecase. I'm afraid though there is no way to export your scene from RealityKit into a .reality file – at least I none that I know of. This would probably be a good candidate to file a feedback radar for. What should maybe work is editing and saving your USDZ file (if you have one) in the Xcode scene editor which should support Unlit Materials via the emissive channel.

Hi, I fear adding interactions could prove troublesome. Even with the SceneKit option afaik you don't get support for touch gestures etc as it just renders the visual representation of the underlying CALayer. Potentially you could try rerouting touch events from your ARView to the UIView you want to display. Beforehand you could do a hittest and see if the geometry for the custom view intersects with the users touch. To reroute touch events you could like into the UIKit hitTest API: https://khanlou.com/2018/09/hacking-hit-tests/

Hi, thanks for the reply! I've created a new thread and posted a reply to you question on the custom shader thread (pardon – overlooked that!).

Hi, sorry just saw that. Apparently the threads do not get bumped up for comment replies. Regarding the use case: Frankly speaking it's kind of both. The shareable/downloadable custom materials use case is the more 'urgent' but I was also playing with the idea of creating a dedicated shader editor app – for custom materials as well as post processing effects. Related to that: is there a way to 'preheat' custom materials to avoid initial delays when adding them to entities in a scene? Something like SceneKits prepare method (https://developer.apple.com/documentation/scenekit/scnscenerenderer/1523375-prepare).

Can you give some info about what can lead to the console warning »ARSessionDelegate is retaining X ARFrames. This can lead to future camera frames being dropped»? Because I can't remember seeing that warning before iOS 15 and now even with simple projects I've noticed it quite a couple of times but haven't really found out the root cause of it yet.

Hello, it's somewhat late but here is the feedback number for my associated radar:  FB9762976