{"id":8584,"date":"2025-12-25T07:43:02","date_gmt":"2025-12-25T12:43:02","guid":{"rendered":"https:\/\/stepinto.vision\/?p=8584"},"modified":"2025-12-25T07:43:03","modified_gmt":"2025-12-25T12:43:03","slug":"realitykit-basics-entity-observation","status":"publish","type":"post","link":"https:\/\/stepinto.vision\/example-code\/realitykit-basics-entity-observation\/","title":{"rendered":"RealityKit Basics: Entity Observation"},"content":{"rendered":"\n

Starting in visionOS 26, we can observe changes to component data on entities.<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

Since visionOS 1, we\u2019ve been able to update RealityKit entities based on changes to data in SwiftUI. We commonly do this with the update closure on RealityView. Starting with visionOS 26 it is possible for SwiftUI to observe changes to RealityKit entities. We now have two-way communication between these frameworks.<\/p>\n\n\n\n

To explore this, we’ll create a scene that orbits a subject around a central point. There are four way points we can collide with. We’ll animate the subject with a timeline that runs continuously. <\/p>\n\n\n\n

\"\"
The demo scene in Reality Composer Pro<\/figcaption><\/figure>\n\n\n\n

When we reach one, we’ll capture the name of the way point and store it in a custom component.<\/p>\n\n\n\n