Hi, yes it's happening with my own Catalyst app as well and the issue is still present in Beta 4.

Good to hear, thanks! 🙏

Hi, yes sysdiagnose should now be attached.

Sure, please let me know if you need anything else. And if there is some sort of workaround I would also be really glad to hear about it. 🙏

Yeah this also something that hinders me migrating to RealityView, since using ARView (the RealityView UIKit equivalent) offers this options and works well. Maybe try using ARView for now? Or you could try accessing the backing ARView (assuming there is one) using something like https://github.com/FiveSheepCo/SwiftUI-Inspect – not pretty though.

Hi, thanks for you reply! So what I wanna achieve is to DISABLE tonemapping for the CustomMaterial when lightingModel is set to unlit, since it appears to be enabled by default and I couldn’t find a way to explicitly set a preference. Basically the texture I am passing in (ARKit Camera Feed) should be rendered exactly as-is, without any adjustments.

Lol that's funky. But yeah I fixed it in a similar way. I tried a new Codable wrapper for CLLocationCoordinate2D instead and worked with that. Thanks for your reply!

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